Log in

View Full Version : 2 evils: out of sync vobs or jerky panning


robotjox
14th July 2009, 12:06
Hello, trying to rip an anime dvd into xvid using avidemux.

Problem:
If I open the vobs in avidemux they are out of sync

If I deinterlace the vob the audiosync is fixed but all panning in the resulting avi stutters.

This happens with each and every deinterlacing filter I use!

If I do NOT deinterlace the stuttering/jerkiness does not happen but the audio is out of sync :mad::mad:

I have been working on this for weeks now and tried every app out there. Can some helpful soul please guide me into the light?

thanks a LOT in advance

Guest
14th July 2009, 13:59
The audio sync issue is probably caused by extra black GOPs at the start. You should cut off all the black at the beginning.

The stuttering is caused by deinterlacing when you should be doing inverse telecining (IVTC).

robotjox
14th July 2009, 14:45
The audio sync issue is probably caused by extra black GOPs at the start. You should cut off all the black at the beginning.

The stuttering is caused by deinterlacing when you should be doing inverse telecining (IVTC).

thanks for taking time out to help me!!!

I tried what you suggested. I removed the start and ending of the movie and used the decomb telecide ivtc filter.
There is no stuttering or jerkiness, but the video is still horribly out of sync.

The strange thing here is that whenever I de-interlace the video the video goes into perfect sync?! (but then I have jerkiness)

robotjox
14th July 2009, 14:45
oh, I should maybe note that the source dvd is a pal pokemon dvd.

Guest
14th July 2009, 14:50
The facts you cite are all inconsistent and violate well-known facts. E.g., you say it's PAL but you IVTC and it is then smooth. Also, deinterlacing alone cannot change the audio sync (assuming no strange functionality within Avidemux).

Therefore, you need to post a link to the first 50-100MB of the start of the *unprocessed* first VOB. You can use DGSplit to cut off the front of the VOB.

robotjox
14th July 2009, 15:21
What I mean is that the unprocessed vob is out of sync as soon as I preview it in avidemux and any other encoder I have tried - if I do not deinterlace, the resulting avi (xvid) will also be out of sync. However the deinterlacing gives me jerkiness, so what I have is a situation where I can choose between out of sync/jerkiness

I will gladly believe that this is inconsistent, but it is nevertheless what I experience. Can this be some inherent fault in the dvd? I also read somewhere that the dvd-titles can get out of sync when you process them one at a time because the sound can be dependent on the other titles (or something??)

Here's a link to the first 100mb: http://www.filefactory.com/file/ahdg01e/n/VTS_01_1_VOB_0

thanks again!

robotjox
14th July 2009, 16:53
(the audio is in Danish but I guess you can easily still see when it is in sync)

Guest
14th July 2009, 22:03
The video is actually 23.976 progressive with the speedup to PAL 25fps implemented using regular soft pulldown (two extra fields per 24 frames). That's unusual for a commercial stream but not unheard of. That pulldown is responsible for the judder you see.

Your processing chain needs to ignore the pulldown flags and set the frame rate to 23.976 fps. One way is to use DGIndex with Ignore Pulldown Flags and then set the frame rate with AssumeFPS(23.976) in your script.

robotjox
14th July 2009, 22:29
thanks a bunch, for taking time out and all - very much appreciated!

This is very interesting. I have not used those tools before (I do most stuff in ubuntu), but I will fire up my windows box and give them a whirl. So you are referring to DGindex and avisynth, right?
So basically I am ripping the audio and attaching it afterwards, telling it to assume the video is 23,976 instead of the reported 25 - is that right?

Sorry, I'm by no means a hardcore video encoder, as I'm sure you have guessed by now, but I'm trying to learn :)

Guest
14th July 2009, 22:50
Yes, by ignoring the pulldown flags the video becomes 23.976 but keeps the same duration.

You get the async most likely because Avidemux ignores the flags but leaves the frame rate at 25. The converse could also cause it. I can't tell you which is happening as I do not know the internals of Avidemux.