Opened 8 years ago

Last modified 7 years ago

#1974 new defect

DVD/VOB audio initial offset not detected in MEncoder

Reported by: subjunk@… Owned by: reimar
Priority: normal Component: core
Version: HEAD Severity: normal
Keywords: Cc: compn, rggjan@…
Blocked By: Blocking:
Reproduced by developer: Analyzed by developer:

Description

Using the following command on r34053:

mencoder -dvd-device dvdfolder dvd://1 -oac mp3lame -of mpeg -ovc lavc -o output.mpeg

The audio is often (but not always) offset by roughly -420ms.
I have ripped 3 DVDs to test so far, and 2 of them have this problem while the other one is fine with the same command.

It also happens with the following commands:

mencoder -dvd-device dvdfolder dvd://1 -oac mp3lame -of mpeg -ovc lavc -mc 0 -noskip -o output.mpeg

mencoder -dvd-device dvdfolder dvd://1 -oac copy -of mpeg -ovc lavc -mc 0 -noskip -o output.mpeg

Also just loading the VOB files directly produces the same result:

mencoder VTS_02_1.VOB -oac mp3lame -of mpeg -ovc lavc -o output.mpeg

Attached is the output.

MPlayer plays them all perfectly, this bug only affected MEncoder.

Attachments (1)

DVDAudio.txt (4.1 KB) - added by subjunk@… 8 years ago.
MEncoder output

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by subjunk@…

MEncoder output

comment:1 Changed 8 years ago by compn

  • Cc patriotact@… added

-demuxer lavf change anything ?

comment:2 Changed 8 years ago by subjunk@…

It makes the audio offset by -250ms instead of -450ms.

I should also note that I used a command previously that worked and was broken in recent commits. It was the same as above but with -oac copy:

mencoder -dvd-device dvdfolder dvd://1 -oac copy -of mpeg -ovc lavc -o

output.mpeg

And that worked perfectly until it broke somewhere between r32848 and r33107.

comment:3 Changed 8 years ago by subjunk@…

I had a look through the log between r32848 and r33107 and based on the comments it looks like the revision that caused the bug I mentioned in Comment 2 is one of the following:

r32950/r32951
r32982
r33084

I'll see if I can compile them to check.

comment:4 Changed 8 years ago by subjunk@…

OK, confirmed that it was r32950/r32951 that caused it.
I have compiled r34327 with r32950/r32951 removed and it seems to work properly like before.

comment:5 Changed 7 years ago by rggjan@…

  • Cc rggjan@… added
Note: See TracTickets for help on using tickets.