Log in

View Full Version : DVDShrink and Big3 Combatibility Fix


n1ck0s
19th March 2004, 19:23
After some testing I'm almost certain about why DVDShrink doesn't like most Big3 backups.

IFOupdate often comes up w/ a warning:

- WARNING: Source to Destination mismatch
Original time = 00:12:22
Newly Authored time = 00:12:21

, which is the reason of non-compatibility.

Two choises here:
1) Fix length within Scenarist and recompile
2) Do the ifoedit trick (see quote below) ONLY to those VTSs that gave a warning w/ IFOUpdate. You can of course perform the trick to all VTSs but it can save you some time.
BTW, this can be corrected in IFOEdit by just letting it correct the IFOs (in VOB Extras, check "Correct original IFO files" and uncheck everything else). I noticed that this usually produces a smaller IFO. Only thing is that IFOEdit messes up here when there are multiple angles, see RB's post
After this trick remember to save. I would say that you should also do a "Correct VTS Sectors" but it seems that is not needed! If you foolow the instruction above a "Correct VTS Sectors" at the end wont change anything at all.

P.S. This worked for me for about the last 7 dvd backups. It should work for anyone else also. Try and post here.

D3s7
19th March 2004, 20:44
??

I've never had a problem having to run DVDShrink on a Big3 backup although I'm slightly puzzled on why you would need to... bitrate calcs are fairly accurate.

n1ck0s
19th March 2004, 21:01
(From 20 or so backups) Once or twice my final image was just a few MBs off. Another time it was way off due to an audio track which was left out accidentally. Instead of reencoding and recompiling, using DVDShrink is much faster.

Plus the feeling that everything is as ok as possible!

D3s7
19th March 2004, 21:05
aaah

I've only ran 1 movie through DVDShrink post Big3 that it didn't like however I later found it didn't like the original too...

n1ck0s
19th March 2004, 21:27
According to this thread (http://forum.doom9.org/showthread.php?s=&threadid=68769&highlight=dvd+shrink) it seems that most Big3 backups have that issue.

Hmm, it might just be a ReAuthorist thing... I'll do some more tests tommorow.