#1 Burning Software

Hi,

I have a quick and hopefully not a dumb question concerning the StarBurn_CdvdBurnerGrabber_GrabDVD call. When this is called for ripping a css encrypted DVD it seems like the drive is only running at 1x. I've tried with this several drives and get the same results with the sample grabdisc console app so is this a limitation of the drive reading raw sectors on a DVD or is there something else going on? The sample code does set the drive to max rip speed and it does call 'authorize' to unlock the dvd for reading. Could this be caused by the drive not supporting raw read mode for dvds? (pioneer dvr-112) I searched through the form and couldn't find anything concerning this.


Thanks,

Matt

Unfortunately when ripping CSS encrypted DVD we still need to store so-called "title keys" inside MDS image. That's why we do much more then just reading DVD content and storing it to the file. That's why ripping is so slow. It's not improperly set reading speed.

Thanks Aaron,

I suspected that was the root of the problem and there wasn't a way of speeding this up.

There's a way actually... We can authorize the disc, rip encrypted content and apply brute force attack against it. It will be much faster and we'll have burnable content but... It's illegal

Anton,

Is there any possibility of splitting the MDS create process into two separate processes? I noticed that the MDS file contains two different files--the MDS file which has the title keys of these encrypted discs and the XMF file which is basically the ISO image of the disc file structure. To speed up the MDS creation, you might simply read just the title keys off the disc at the very slow ripping speed (without generating the XMF file), then start a new process to rip the XMF file--which will pull the data off much faster.

Can you let me know if this is possible with the Starburn module to simply read the title keys off the disc and store them as an MDS file---without the XMF? This would allow us to LEGALLY make images at a much greater speed.

Thanks,
Doug

Unfortunately it's the way Daemon Tools people created it... We can do nothing except ask you to use GrabTrack(...) or use custom read and save to plain ISO.