View Full Version : Critical error in scenarist when ripping SW AOTC
Wensleydale
7th November 2003, 12:43
When using big3 to rip the second disc (special features) of Star Wars AOTC, I get a critical error which forces scenarist to terminate during the importing sequence.
I've had other problems with scenarist when it comes to discs that have a lot of vts sets.
Any ideas on how to remedy?
CCE 2.5, don't remember what other versions of all the other proggies.
P4 2.66/533 (oc:ed to 3ghz), Giga-byte 8PE667 mobo, 1gb ddr 333 (oc:ed to 375mhz)
ShaneZ
8th November 2003, 17:25
Originally posted by Wensleydale
When using big3 to rip the second disc (special features) of Star Wars AOTC, I get a critical error which forces scenarist to terminate during the importing sequence.
I've had other problems with scenarist when it comes to discs that have a lot of vts sets.
Any ideas on how to remedy?
CCE 2.5, don't remember what other versions of all the other proggies.
P4 2.66/533 (oc:ed to 3ghz), Giga-byte 8PE667 mobo, 1gb ddr 333 (oc:ed to 375mhz)
Could you be a bit more elaborate on the error? That does not give us much to work with.
Shane
Wensleydale
13th November 2003, 09:23
Well... I don't know if I can actually. At first, during importing, the program sort of refuses to respond even more than usual, and then I get the error message that it has to be shutdown, and then the question of whether I want to report it to Microsoft or not. Not!
I can tell you a bit more of what I have done though. Since the disc contains of an extreme bunch of extras (and since I don't know better) I set the bitrate of the extras to 4500. Don't know if that should matter though... The disc contains 10 VTS sets.
Last night I gave up and resorted to DVDshrink (the horror!). The result was not good, but I'm gonna learn to live with it.
Hopefully I won't run into this problem again.
For some time I've also been struggling with another non-main movie disc so to say, Fawlty Towers. Every time I got to scenarist I got the error "place holder, precheck from db failed". I solved this though by finding a thread in the forum that dealt with the problem. In case any other newbies would like to know the problem was, re-authorist didn't load the first PGC into DoCCE4u, so I had to do this myself.
Almost lost faith in the big3 there for a while but now it's full speed ahead!
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.