Documenting issue from discord. Aaru lets you set 48x on a JB8 and allows you to dump a large CD in about 3-4 minutes, wheras redumper takes significantly longer. This is because when you try and dump at 48x with a JB8 on redumper, the drive will reach ~1670 sectors, pause, downrev, and then continue the rest of the dump at a much lower speed. A similar thing happens on DiC, except it happens at ~700 sectors, and is also even slower than redumper. This doesn't seem to be due to aaru using different opcodes, as dumping with drive generic on redumper produces the same issue, and aaru also captures full 2352 sectors and raw subchannels like redumper does. https://github.com/saramibreak/DiscImageCreator/issues/219 could be related, but according to superg, likely not. Tested on aaru using ./aaru media dump /dev/sr1 test.aaruf -O compress=false --speed 48 .
Documenting issue from discord. Aaru lets you set 48x on a JB8 and allows you to dump a large CD in about 3-4 minutes, wheras redumper takes significantly longer. This is because when you try and dump at 48x with a JB8 on redumper, the drive will reach ~1670 sectors, pause, downrev, and then continue the rest of the dump at a much lower speed. A similar thing happens on DiC, except it happens at ~700 sectors, and is also even slower than redumper. This doesn't seem to be due to aaru using different opcodes, as dumping with drive generic on redumper produces the same issue, and aaru also captures full 2352 sectors and raw subchannels like redumper does. https://github.com/saramibreak/DiscImageCreator/issues/219 could be related, but according to superg, likely not. Tested on aaru using
./aaru media dump /dev/sr1 test.aaruf -O compress=false --speed 48 .