[gst-devel] QT Demux with strange ouput ES data

[Daniel James Laird]

Hi,

I am trying to use the qtdemux to demux a ".mov" file that I have. I am using the qtdemux and then I put the output into my onboard decoder.  However it is failing to find start codes in the data.
I checked by running qtdemux on my PC (FC10) by running the following:
gst-launch filesrc location=term.mov ! qtdemux name=demux  demux.audio_00 ! queue ! fakesink   demux.video_00 ! queue ! filesink location=gstreamer.h264

I then try to use mplayer to play the output file of gstreamer.h264 and it too fails to find any video start codes.
If I compare the output of qtdemux to that of a reference demux that we already have I notice the following:

1.) I do not get a 'DSI header' at start of stream which helps to set up decoders.  This is not a major issue and I am sure can be resolved.
2.) The Data is almost identical except that the reference demux has a start code of 80 00 00 01 followed by the data. However the qtdemux is giving me 80 00 00 00 XX where XX is random this is followed by idential data as the reference demux.
  Without the magic header of 80 00 00 01 our decoder fails to see start codes and therefore bombs out.

I was wondering if anyone might be able to point me to why this happens (spec revision?) As I need to understand this rather subtle but important issue.

With regards,
Daniel Laird