<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;"> <p>Comparing H.264 playback with GStreamer and VLC Player, the latter seems somewhat more tolerant to stream anomalies. In general, VLC Player will freeze at least partially on the last valid image <span style="font-family: Calibri, Arial, Helvetica, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 16px;">until the next key frame is shown</span>, whereas GStreamer will display (sometimes severe) gray artifacts.</p> <p><br> </p> <p>Does anyone have an idea of what VLC Player is doing that GStreamer isn't (or vice versa) that could explain the different behavior?</p> <p><br> </p> <p>Is it possible to detect decoding errors and simply drop the associated frames?</p> <p><br> </p> <p></p> <div> <p style="font-family: Calibri, Arial, Helvetica, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 16px;"> Could there be an option in GStreamer or its components (codec maybe?) to make the display more tolerant to decoding errors?</p> </div> <div><br> </div> J. Roy <p></p> </div> </body> </html>