Is it possible to force Ripbot to continue after crash/reboot?

[yorkman]

Once in a while my pc will freeze, reboot or have an hdd failure in my raid array forcing me to reboot Windows while I get another hdd, replace it, then rebuild the array.

Usually I use the 2-pass option because this enables the Lock option for the size which I always want it to be around 7900MB. I don't use 8192 as often it goes over the DL disc capacity.

So when a crash/reboot occurs, can I get Ripbot to continue from pass #2 at least? It'd be nice if we could continue from any point, but specifically from the time the pc was rebooted.

If this is not possible, where can I make this recommendation to have it added as a feature? I think it'd be very useful for many people. SCVD2AVI had this and even then it was useful.

[redwudz]

I haven't been able to restore the data after a crash yet with RipBot. But I've never checked to see if any temp files still exist or have any idea how to continue the program if they were available. A lot would depend when and why it crashed and what files are still available. But you could check RipBot's temp files and see if there is anything there.

I also use 7900MBs for a selected file size now as I had several RipBot MKVs that were too big at 8150MBs for a ImgBurn burn to a DL disc backup. Rather frustrating after a six hour conversion.

The author of RipBot hasn't visited here lately, but you could contact him directly at Doom9: http://forum.doom9.org/showthread.php?t=127611 There are a lot of posts in that thread and your question may have already been answered.

[yorkman]

I haven't been able to restore the data after a crash yet with RipBot. But I've never checked to see if any temp files still exist or have any idea how to continue the program if they were available. A lot would depend when and why it crashed and what files are still available. But you could check RipBot's temp files and see if there is anything there.

I also use 7900MBs for a selected file size now as I had several RipBot MKVs that were too big at 8150MBs for a ImgBurn burn to a DL disc backup. Rather frustrating after a six hour conversion.

The author of RipBot hasn't visited here lately, but you could contact him directly at Doom9: http://forum.doom9.org/showthread.php?t=127611 There are a lot of posts in that thread and your question may have already been answered.

Glad to hear I'm not alone on some things. After a crash/reboot, all the temp files are there. It'd only make sense to be able to continue rather than having to start all over. It's especially frustrating when your 8 hr encoding is at the 7 hr mark.

What kind of hardware do you have if 2-passes only takes you 6 hrs? I have Q6600 but overclocked from 2.40GHz to 3.60 and is stable (the system freeze I mentioned earlier is not related). I also have 8GB ram, Windows 7 x64 and using 2 raid arrays, 0 and 5 with the encoding being done on raid 0.

Thanks for the thread. I'll see if I can mention this feature there.

[yorkman]

Doom9 sux for registering. You gotta wait 5 days before you can post?! WTF!

[redwudz]

Doom9 isn't as 'friendly' as our site, but a lot of good info there. And we maybe have better spam filtering.

My PC specs are in my computer details. A Intel Quad 9550 OC'd to 3.4Ghz. I do rip the BDs to my HDD before processing with RipBot. No RAID. Takes between 5 to 6.5 hours for most conversions, BD>MKV, two pass with a target size of 7900MBs so I can back them up to DL discs if one of my server drives die.