GNOME Bugzilla – Bug 556521
[PATCH] typefind: improved MPEG4 start code recognition
Last modified: 2008-10-19 11:52:17 UTC
Please describe the problem: I have a camera that specifies a YUV clamping section in the visual object header. However, mpeg4_video_type_find always assumes a 5-byte visual_object_start_code. The attached patch allows start codes up to 10 bytes (the maximum according to http://xhelmboyx.tripod.com/formats/mpeg-layout.txt ). Note, I'm going to make a more extended patch with more functionality in a separate bug report. However, I wanted to submit this already in case the other patch isn't accepted. Steps to reproduce: gst-launch souphttpsrc location=<JVC camera MPEG4 stream> ! typefind ! fakesink Actual results: ERROR: from element /pipeline0/typefindelement0: Could not determine type of stream. Expected results: video/mpeg stream recognized Does this happen every time? Yes Other information:
Created attachment 120702 [details] [review] Patch to fix the issue
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 556537 ***