iNFO-DVD
29th December 2005, 12:32
This post is something of an observation......
I was taking a look at the 'MediaInfo' program the other day on a couple of movies I'd ripped to my hard drive just for the purpose of testing the aforementioned program. I initially thought something was wrong with the program as the 2 movies I'd ripped, Pirates of the Caribbean & Terminator 3 (both Region 2 PAL), did not give out the correct information. MediaInfo got the audio streams back to front on the latter DVD and couldn't find any at all on the Pirates DVD.
MediaInfo to blame? Maybe, or maybe not!
The above programs were initially ripped using vStrip (multiple times using different options, both CLI and GUI) with the same results, something is not right..... (when I say ripped, in this case I'm refering to the program chain).
Now, DGIndex will accept these files fine and display the correct audio streams/information.
So, again, looks like MediaInfo is at fault, well, until we now rip the program chain with DVD Decrypter. MediaInfo now displays the correct information....... Like before, DGIndex accepts the file fine.
Well, vStrip to blame then? I don't know, vStrip has been held in high regard for many years, a bit difficult to brush it off like this, but something is wrong.
The D2V files made by DGIndex for the latter DVD using both vstrip and dvd decrypter were both DIFFERENT!
When scripted (AVISynth), the vstrip rip is out-of-sync, quite heavily (more than a second).
Again, it's easy to blame vstrip as it seems the most obvious, though something else does spring to mind.
Let's say, DVD Decrypter was incorrect somehow, it is a very popular ripper, so there's a good chance that when DGIndex and MediaInfo were made, and updated e.t.c, they've used VOB files created with DVD Decrypter, then they're geared to getting information from VOBs created with DVD Decrypter. So vstrip could be 100% correct but appear wrong as maybe that's not been used by other programs that give information on ripped VOB files, does that make sense?
Personally, I have the upmost respect for DVD Decrypter and view it as a damn good piece of code.
Why is DGIndex making different D2V files? Why is MediaInfo fluffing? Why are some programs OK with both rips and some not? Going to explore a little deeper with VOBEDIT to see what vstrip seems to be doing.
Anyone shed any light?
I was taking a look at the 'MediaInfo' program the other day on a couple of movies I'd ripped to my hard drive just for the purpose of testing the aforementioned program. I initially thought something was wrong with the program as the 2 movies I'd ripped, Pirates of the Caribbean & Terminator 3 (both Region 2 PAL), did not give out the correct information. MediaInfo got the audio streams back to front on the latter DVD and couldn't find any at all on the Pirates DVD.
MediaInfo to blame? Maybe, or maybe not!
The above programs were initially ripped using vStrip (multiple times using different options, both CLI and GUI) with the same results, something is not right..... (when I say ripped, in this case I'm refering to the program chain).
Now, DGIndex will accept these files fine and display the correct audio streams/information.
So, again, looks like MediaInfo is at fault, well, until we now rip the program chain with DVD Decrypter. MediaInfo now displays the correct information....... Like before, DGIndex accepts the file fine.
Well, vStrip to blame then? I don't know, vStrip has been held in high regard for many years, a bit difficult to brush it off like this, but something is wrong.
The D2V files made by DGIndex for the latter DVD using both vstrip and dvd decrypter were both DIFFERENT!
When scripted (AVISynth), the vstrip rip is out-of-sync, quite heavily (more than a second).
Again, it's easy to blame vstrip as it seems the most obvious, though something else does spring to mind.
Let's say, DVD Decrypter was incorrect somehow, it is a very popular ripper, so there's a good chance that when DGIndex and MediaInfo were made, and updated e.t.c, they've used VOB files created with DVD Decrypter, then they're geared to getting information from VOBs created with DVD Decrypter. So vstrip could be 100% correct but appear wrong as maybe that's not been used by other programs that give information on ripped VOB files, does that make sense?
Personally, I have the upmost respect for DVD Decrypter and view it as a damn good piece of code.
Why is DGIndex making different D2V files? Why is MediaInfo fluffing? Why are some programs OK with both rips and some not? Going to explore a little deeper with VOBEDIT to see what vstrip seems to be doing.
Anyone shed any light?