Log in

View Full Version : x264 produces crap output, players crash


Egladil
4th February 2006, 01:00
I have a problem: I've encoded some movie and the resulting mp4 file is 6GB, the problem is that if I seek to the data which is beyond the 4GB border, every player crashes, mp4box crashes. I'm able to mux the video in mkv, beu there every player crashes too and when trying to demux the raw stream only 4 GB are written and then mp4box (or mkvextract) crashes.

Anyone knows what I can do?

Sirber
4th February 2006, 01:01
So... your encode is bigger than the source?

Egladil
4th February 2006, 01:02
no, the source is 14 GB, it's HD material.

Manao
4th February 2006, 12:19
What was the version of x264 you used ? And mp4box ? And mkvtools ?

ryoohki360
4th February 2006, 16:37
I have a problem: I've encoded some movie and the resulting mp4 file is 6GB, the problem is that if I seek to the data which is beyond the 4GB border, every player crashes, mp4box crashes. I'm able to mux the video in mkv, beu there every player crashes too and when trying to demux the raw stream only 4 GB are written and then mp4box (or mkvextract) crashes.

Anyone knows what I can do?

I Have the exact same problem as you... i encode at 6mbits and around 1h33:54sec (witch is 4gig approx) it crash for a my encode. All movies under that mark work like a charm!

Rev408, and the MP4 itself crash so it's a problem with the encoder, VLC crash, FFDSHOW crash, CoreAVC Crash all without audio

Egladil
4th February 2006, 18:06
I used x264 rev410 cli, mp4box 0.4.1-dev. I must be a bug in x264 or gpac, I'll try encoding to raw stream, but it'll take a few days.

Manao
4th February 2006, 18:08
You can use very fast settings, it shouldn't matter. That may speed things up.

Egladil
5th February 2006, 02:19
Ok, did some tests, it seems that mp4 output is b0rked. encoding to raw stream, playback with vlc-> ok, muxing with latest mp4box and then playing->crash. encoding to mkv->works.

as stated before the players crash on the 4 GB border

bond
5th February 2006, 10:24
run mp4dump from mpeg4ip on the output mp4 and post the log here plz

Egladil
5th February 2006, 17:29
On a 9GB mp4 mp4dump says:

mp4dump version 1.2.8
ReadChildAtoms: of root
ReadAtom: pos = 0x0
ReadAtom: type = "ftyp" data-size = 16 (0x10) hdr 8
Read: majorBrand = avc1
Read: minorVersion = 0 (0x00000000)
Read: compatibleBrandsCount = 2 (0x00000002)
Read: brand = isom
brand[1] = avc1
ReadAtom: pos = 0x18
ReadAtom: type = "mdat" data-size = 9074710898 (0x21ce51972) hdr 16
Skip: 9074710898 bytes
ReadAtom: pos = 0x1ce5199a
ReadAtom: type = "free" data-size = 33 (0x21) hdr 8
Skip: 33 bytes
ReadAtom: pos = 0x1ce519c3
ReadAtom: type = "p,3" data-size = 1108602032 (0x4213ecb0) hdr 8
Warning: atom type p,3 is suspect
Warning: p,3 atom size 1108602032 is suspect
Read: data = <1108602032 bytes>
...
then comes 3.5 Gb of data
...
ReadAtom: pos = 0x5ef9067b
ReadAtom: type = "¯¾^" data-size = 1659965119 (0x62f10ebf) hdr 8
Warning: atom type ¯¾^ is suspect

then it bails out while printing "MP4ERROR:" on the console (stdout was redirected to a file)

bond
5th February 2006, 17:51
what verbose level did you use? try without setting verbose, the file should be much smaller

Egladil
5th February 2006, 17:53
I used verbose=3

without verbose it just works for a while, then prints "MP4ERROR:" and exits

bond
5th February 2006, 18:09
does the verbose output mention "stco" or "co64" somewhere?

Egladil
5th February 2006, 18:16
no it doesn't

bond
5th February 2006, 18:42
can you upload the output of mp4dump when not using verbose somewhere?

Egladil
5th February 2006, 18:46
it has no output other than "MP4ERROR:"

KWAGGA
6th February 2006, 02:16
I prefer mkv container, less hassle then mp4 and supports more streams, mp4 is pretty cool though especially using mp4 box to extract streams.

bond
6th February 2006, 13:48
Ok, did some tests, it seems that mp4 output is b0rked. encoding to raw stream, playback with vlc-> ok, muxing with latest mp4box and then playing->crash. encoding to mkv->works.

as stated before the players crash on the 4 GB bordertry muxing the raw stream with mp4creator to mp4 and check if that file works better

Egladil
6th February 2006, 17:04
well the version 1.2.8 of mp4creator (i didn't find binaries of later versions) produces pretty crap mp4 output, the seeking is corrupt after 2GB and the player crashes after 4 GB

bond
6th February 2006, 17:05
http://www.aziendeassociate.it/./cd//mpeg4iptools/mpeg4iptools-1.4.4cvs.7z

bond
28th February 2006, 21:36
if you want you can try if this compile fixes the problems:
http://files.x264.nl/x264.445.gpac.28.feb.2006.make.fprofiled.gcc.3.4.5.exe

Egladil
2nd March 2006, 11:02
I'll try that soon, don't have time right now. Thanks

bob0r
2nd March 2006, 11:43
or just try the latest from http://x264.nl

Latest gpac (then possible), same compile process.

Also Gpac is set to auto update again, lets see what it brings us.... :D

rocket_robot
5th March 2006, 01:06
I had similar problems with an HDTV encode using Staxrip. I figured out it was actually the MUX process in mp4box that was the problem, not x264. The latest version of MP4box (2nd March I think) completely fixed all my problems with files > 4Gb.

Ferux
6th March 2006, 15:05
I did not mux, I just used megui-x264 for the video encoding and i have the same problem.. So the problem cannot be the muxer, in my case (?)

I uses X264 rev 408.

Pretty stupid, after a whole week of encoding..

bond
6th March 2006, 15:50
same for you, use a recent compile for encoding

Matariel
7th March 2006, 17:19
For the ppl having problems, what OSes are you using?

The 4gig limit sounds very familiar...
Perhaps the file container only uses 32bit addressing or something.

smok3
13th June 2006, 20:31
well, same problem here;

started tor 13.06.2006 / 7:26:32,78
x264 core:45 svn-477
x264.exe --bitrate 8000 --nf --no-cabac --subme 1 --no-chroma-me --analyse none --me dia --threads 4 --thread-input --progress --no-psnr --output "G:\hvx200\film_1280x720.avi.mp4" "G:\hvx200\template_film_1280x720.avs"
MP4Box - GPAC version 0.4.1-DEV
GPAC Copyright: (c) Jean Le Feuvre 2000-2005
(c) ENST 2005-200X
ended tor 13.06.2006 / 14:18:38,26

so it is mp4box to blame?

Sharktooth
13th June 2006, 22:10
well, same answer ... USE A NEWER x264 BUILD.

smok3
14th June 2006, 09:21
ok, so it is definately not a mp4box problem? (since iam using that for muxing after encoding...)

bond
14th June 2006, 18:42
it should have been fixed, so try a recent build...

smok3
15th June 2006, 08:28
uhmm, iam unable to find a newer version of mp4box, all compiles seems to be 0.4.1-dev, any clues?

(a. anyway, i redid the encoding using the latest version of x264 and i did split the original - using avisynth trim - so that i get two 2 gig files which again wont play nicely in mplayer, neroshowtime, quicktime...

edit: 'mp4box -splits 700000 big2gigfile.mp4' did the trick, ah well...

b. i also did a nero recode 2 encode, but that wont play nicely at all as well, but it seems like my computer is a bit slow for that.. - staring at showtime bitrate display does indicate that there are huge bitrate jumps - i did 1pass vbr in all cases)