Closed Selur closed 3 years ago
That's weird. Is it the same if you use the graphical interface?
Yes, it's the same.
I guess it's a problem in ffmpeg then. You could try replacing the ffmpeg DLLs with newer ones. The current ones are from 4.2.2.
too much trouble, just wanted to let you know that there is a problem. (+ I doubt that updating ffmpeg will solve the problem. ;))
Can I have the first 20 megabytes of VTS_01_1.VOB, please? Or however much of it is needed to reproduce the problem.
Sure, but due to copyright the question is: how can I share the link with you? Github has no private message function or similar. -> doh will send you a link via PM over at doom9
Thanks. ffmpeg has a problem with this. It doesn't examine enough of the stream to find the information about those two tracks. I "fixed" it.
using
using:
it reports
MediaInfo using
reports for the first vob:
mplayer using
reports:
DGIndex too finds all three streams 80,81,82.
No clue where the stream 83 comes from. All three audio tracks are full length and mplayer and dgindex can extract them all fine. Seems like there is a bug somewhere in the analysis of the source. If further info is needed let me know and I try to provide it.
Cu Selur