Log in

View Full Version : MeGUI: First 2 to 2.5 minutes are missing


dialsc
23rd October 2010, 00:42
hi,

i'm used to use megui to make h264 encoded videos from dvds quiet a while now. recently i reinstalled my windows 7 machine and now i'm facing a strange problem.

every dvd rip i encode using megui is missing the first 2 to 2.5 minutes of the movie. allthough i see the begining of the movie correct in the aviSynth script editor preview window, the first approx. 150 seconds are not getting encoded and then the movie starts.

i'm using the latest development version of megui which is 0.3.5.22.

anyone got an idea what the problem could be?

thx,

dialsc

dialsc
23rd October 2010, 02:38
i've figured out that i reported a wrong problem. the problem seems to be related to vlc which i use to watch the mp4 after encoding. vlc cuts off the first seconds and jumps into the movie at about 150 seconds.

i have no glue why it behaves that way. i've never seen it doing things like this. but with outher players the mp4 a working as expected.

very stupid, isn't it?

Sharktooth
23rd October 2010, 14:37
i was scratching my head trying to figure out what the hell could it possibly be...

dialsc
24th October 2010, 10:38
i've figured out something more on this problem. when i start muxing the video/audio streams into a mkv using mkvmerge GUI it gives me the following error (translated by my self ;-))

Warning: 'C:\MY_MOVIE\myMovie.mp4': This file contains at least one frame with a negative timestamp. Therefore all timestamps are shiffted by 00:00:00.080 to have no timestamp being negative anymore.

also interessting is the fact that when i encode it as xvid (XviD: Const. Quantizer 2 HQ) it looks like it works as expected...

dialsc
24th October 2010, 12:28
one more information. if i run one click encoding, the resulting mkv seems to be fine.

Sharktooth
24th October 2010, 14:21
that's the timestamp problem with recent build of x264. basically a GPAC problem...
use the JEEB's x264 build to fix that.

dialsc
24th October 2010, 16:47
ah, seems like we are getting closer to a possible solution... ;) do you mind giving me a little hint on how to do what you suggessted?

Sharktooth
24th October 2010, 16:55
the problem was discussed here: http://doom10.org/index.php?topic=718.0

dialsc
24th October 2010, 18:15
i gave that a try and so far it looks good. i'll report the final result.

dialsc
24th October 2010, 19:13
yes, that solved the problem.

thank you very very much!

RBO
29th October 2010, 10:04
that's the timestamp problem with recent build of x264. basically a GPAC problem...
Hi, I tried to reproduce but I couldn't (x264 rev 1745, GPAC-mp4box rev2210). Can anyone send me a file or a description of what's going wrong with GPAC?

Please contact us when you have such problems... otherwise bugs won't solve themselves ;)

Thanks,

Romain

Sharktooth
29th October 2010, 14:19
@RBO: please refer to: http://doom10.org/index.php?topic=718.0
also you can get on irc (freenode) on #x264 or #x264dev and contact the x264 developers.