jlesage
Automatic ripper rips on loop the same disc
Hello,
I'm running my docker-makemkv as an automatic disc ripper with many optical drives in parallel. The problem that I encounter is here for example that with 3 discs inserted. It's gonna rip disk 1,2,3 and then disk 1,2,3 again until there's no memory left, adding "-XXXXX" to the name of the folder.
By the way, is the fact of being able to rip in parallel actually worth it to reduce the global ripping time ? Or is it therefore way slower for every drive individually.
Is there any way to avoid that?
Thank you!
[makemkvcon-4] Current progress - 98%, Total progress - 99% [makemkvcon-4] Current progress - 99%, Total progress - 99% [makemkvcon-4] Current progress - 100%, Total progress - 99% [makemkvcon-4] Current progress - 100%, Total progress - 100% [makemkvcon-4] 10 titles saved [makemkvcon-4] Copy complete. 10 titles saved. [autodiscripper-4] Disc rip terminated successfully. [autodiscripper-4] Ejecting disc from drive 4 (/dev/sr6)... [autodiscripper-4] ERROR: Failed to eject drive 4 (/dev/sr6). [autodiscripper-4] Disc detected in drive 4 (/dev/sr6): GA30EGT7. [autodiscripper-4] Starting disc rip... [makemkvcon-4] MakeMKV v1.15.4 linux(x64-release) started [makemkvcon-4] Current operation: Scanning CD-ROM devices [makemkvcon-4] Current action: Scanning CD-ROM devices
Here is what usually happens , once the disk has been fully ripped, either it doesn't automatically ejects it as it should, or it ends up doing it. In both case, anyway, he detects the same disc as a new one. Therefore, it starts ripping it straight away for a second time (and then third, fourth time etc ... until i remove it), under the name GA30EGT7-PlIioo here for example.
Do you know how to prevent it from ripping same disc multiple times?
Here is what usually happens , once the disk has been fully ripped, either it doesn't automatically ejects it as it should, or it ends up doing it. In both case, anyway, he detects the same disc as a new one.
I guess that if the disc is successfully ejected, it won't rip the disc again unless you manually close the tray ?
Do you see the issue when disc ejection is disabled ?
I think the thing is that the tray automatically closes after a period of time.
But still, even with the disc ejection disabled it keeps on ripping it a second time after yes
I fail to reproduce the issue. To which value did you set AUTO_DISC_RIPPER_INTERVAL ? With auto ejection disabled, when the disc finishes to be ripped, how much time after that it starts again ?
I'm having the same issue. What's weird is I can sometimes exec into the container and just run eject /dev/srX and it works fine. It's hard to know what is happening since the output is pushed to /dev/null I'll see if I can modify the script to see what's actually happening.
OK so yeah it just prints this out.
eject: cannot open /dev/sr3: Resource busy
and for some reason when I jump on the container and try to eject manually it still says it's busy.
I'm running this on a desktop and I believe it auto mounts the disk when I put it in there. Should it not be?
The latest image will display the error in case ejection fails. It will also perform retries if ejection fails because drive is busy.
I'd have to check but if the makemkv gui is still auto mounting the disk it probably is. There's a bug somewhere detailing how the gui specifically is preventing the disk from being ejected. I'll have to see if I can find it. I ultimately switched to a different ripper because of this issue, so I'm not sure when I'll be able to try it again.