H264 to streamable mp4

bomba jhonata.poma at gmail.com
Wed Apr 27 13:15:13 UTC 2016


Rudolfs Bundulis wrote
> Ok this is extremely weird. Can you post lets say the first 16 bytes in
> hex
> from the file? Normally an mp4 file should begin with an ftyp atom so you
> should have the FourCC ftyp in the bytes 5-8 (first 4 are size), but it
> seems that the actual contents are totally different.

0000000 0000 3c01 6f6d 666f 0000 1000 666d 6468
0000020 0000 0000 0000 0f00 0000 2401 7274 6661
0000040 0000 1800 6674 6468 0000 2800 0000 0100
0000060 0000 6400 0100 c000 0000 0401 7274 6e75
0000100 0000 010a 0000 1e00 0000 4401 0000 8f18
0000120 0000 f401 0000 df18 0000 c800 0000 0f18
0000140 0000 0000 0000 1c18 0000 6400 0000 3918
0000160 0000 9001 0000 1318 0000 c800 0000 ff17
0000200 0000 0000 0000 b11b 0000 9001 0000 0f18
0000220 0000 c800 0000 2518 0000 0000 0000 7f18
0000240 0000 f401 0000 1819 0000 c800 0000 3718

keep in mind that this is a /live/ source. The muxing problem could be
originated by GStreamer not passing the required * atom when the client
connects.



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/H264-to-streamable-mp4-tp4677114p4677159.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list