FixVTS doesn't fix? (Casino Royale)

[Redmondman]

After running into ripping issues with Ripit4me, I started using DVDFab HD to rip. So here's the full scenario:

Source: Casino Royale Standard-def Region 1
Rip: DVDFab HD 4.0.1.2
Fix: FixVTS 1.603 (all options checked)
DVDShrink: reauthor, title 1 (main movie), no compression

result: DVD Shrink reports "out of memory" at around 30% encoding point.

This was a surprise to me as I thought that FixVTS would fix "out of memory" errors. The DVD folder plays fine with PowerDVD6, but Shrink won't extract the movie.

So I guess I have two questions:

1. Known issues where FixVTS doesn't fix?
2. Other tools to extract a title stream without compressing?

thanks!

[blutach]

You may find that that (outdated) version of Fab outputted illegal cells that were probably not contemplated by FixVTS.

Regards

[Redmondman]

Thanks, but it raises a question for me. Presumably such an illegal cell would be *referenced* by the program chain I'm trying to duplicate, otherwise it would have been removed by FixVTS. (Oh, and for kicks and giggles, I also ran the folder through VOBBlanker and told it to blank all but PGC 1).

So I'm trying to understand a little more about the (at least) theoretical operation of these tools.

(but clearly I'll re-rip with updated tools :) )

[blutach]

Yes, I suppose it would be referenced, as VobBlanker (and FixVTS) remove unreffed material.

Regards

[Redmondman]

I could be way off the mark, but I have a guess as to the problem and a workaround.

If the PGC begins with an open GOP, Shrink ends up treating the entire movie as an open GOP and tries to buffer the entire thing.

Workaround:

1. Shrink the first chapter (this will fit within the virtual memory limit).
2. Shrink all subsequent chapters.
3. Combine the VOBs you get from steps 1 and 2.
4. Proceed as usual.

[setarip_old]

@Redmondman

Instead of a workaround, you'll find that RipIt4Me (I used v.1.6.4 for the R1 version of "Casino Royale") processes this "ARccos"-protected title perfectly...

[Redmondman]

I've got Ripit4me 1.7.1.0 which works as well, but essentially I got curious as to *why*. Ripit4me runs FixVTS as a post-rip step, so I couldn't understand (and still would like to) why:

-- dvdfab HD + fixvts --> Shrink = Out of memory
-- Ripit4me (dvd decrypter+Fixvts) --> Shrink = success

since my understanding is that ARccos protection involves adding unreferenced, bad cells to the VOB(s).

[setarip_old]

I can only tell you from my own personal experience of periodically using DVDFabDecrypter/DVDFabHDDecrypter since its inception, it seems that although it typically was capable of making viable 1:1 rips, for one reason or another, these rips were not totally compliant, so that oft' times the 1:1 rips could not be compressed by programs such as DVD Shrink or DVD2One.

For example, it was probably well into its second year of existence that it first came to light, and was confirmed, that the program was AUTOMATICALLY replacing what it deemed to be unreadable sectors, apparently based on only one read attempt, with "dummy" sectors.

[blutach]

While setarip is correct, I do believe the program has fixed those issues now. Certainly, the issue of compliance with one of the recent betas was debated quite hotly in the Official DVD Fab forum. My understanding is that packs without video are no longer part of DVD Fab (but it was a nice idea at the time).

Regards

[stars]

I can only tell you from my own personal experience of periodically using DVDFabDecrypter/DVDFabHDDecrypter since its inception, it seems that although it typically was capable of making viable 1:1 rips, for one reason or another, these rips were not totally compliant, so that oft' times the 1:1 rips could not be compressed by programs such as DVD Shrink or DVD2One.

For example, it was probably well into its second year of existence that it first came to light, and was confirmed, that the program was AUTOMATICALLY replacing what it deemed to be unreadable sectors, apparently based on only one read attempt, with "dummy" sectors.

Ok... thats why I was suprised to see that the movie Closer and Pursuite of Happynes had the same type of crapy cells...

stars...

[Redmondman]

That's what I needed. I have a more complete understanding of ARccos protection now.

What may be interesting is the reason I went from RI4M to DVDFab in the first place -- I got a new Optiarc drive, and it (with RI4M) wouldn't read Pursuit of Happyness at all. I/O errors weren't bubbling up to the application; apparently they were being handled by firmware/drivers (and put the drive in PIO mode to boot).

(Could be that I need to try the trick I recently read: start RI4M before inserting the disc...)

[setarip_old]

Could be that I need to try the trick I recently read: start RI4M before inserting the disc...That (only) serves as one of several ways to prevent any "autorun" files from playing - such as the recent shabby "new" Macrovision copy protection seen on "New Yorker Productions" DVDs (If you load the DVD normally, BEFORE starting RipIt4me, RipIt4me will not "see" the DVD)...