What version of the Extension Manager and CD Ripper are you running? Are you sure there is only one CD Ripper container running? You can check with the docker ps command.
Extension manager 1.1.2 and CD Ripper 0.5.0.
root@kokleda:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
889549fa491f theappgineer/roon-extension-cd-ripper:latest ā/usr/bin/env node /ā¦ā 2 weeks ago Up 8 minutes roon-extension-cd-ripper
9f3e8d676304 theappgineer/roon-extension-manager:v1.x ānode .ā 2 weeks ago Up 8 minutes roon-extension-manager
root@kokleda:~#
The two copies of the processes have the same PID (the ānode /home/worker /output processā) as the parent, so Iād assume they were in the same container?
I just released an update of the CD Ripper extension. Can you perform an update to version 0.6.0 and see if the issue is still there? If it is then please collect logs via the Extension Manager and share them with me.
The just released version 0.6.0 of the CD Ripper has functionality to unlock the Apple SuperDrive. I donāt own one myself so it hasnāt been tested yet. If anyone can give this a try and report back to me it would be helpful.
Thanks Jan, I have updated to 0.6.0 and am feeding CDs into the server to see what happens.
Perfect!, I will try this afternoon. At work now!
Thanks for looking at this. It did several CDs fine and then did a duplicate process on the next:
root@kokleda:/dev# ps -ef |grep whip
root 4493 3533 5 13:50 ? 00:00:01 /usr/bin/python3 /usr/local/bin/whipper --eject never cd rip --cdr --max-retries 3
root 4503 4493 1 13:51 ? 00:00:00 cdrdao read-toc --device /dev/cdrom /tmp/tmpde5g8oxa.cdrdao.read-toc.whipper.task
root 4511 1936 0 13:51 pts/1 00:00:00 grep --color=auto whip
root@kokleda:/dev# ps -ef |grep whip
root 4493 3533 5 13:50 ? 00:00:49 /usr/bin/python3 /usr/local/bin/whipper --eject never cd rip --cdr --max-retries 3
root 4690 4493 8 14:05 ? 00:00:00 cd-paranoia --stderr-progress --sample-offset=102 --force-cdrom-device /dev/cdrom 11[00:00:00.00]-11[00:06:20.19] /tmp/tmpidwwimvd.whipper.wav
root 4694 1936 0 14:05 pts/1 00:00:00 grep --color=auto whip
root@kokleda:/dev# ps -ef |grep whip
root 4766 3533 4 14:07 ? 00:00:05 /usr/bin/python3 /usr/local/bin/whipper --eject never cd rip --cdr --max-retries 3
root 4782 4766 0 14:07 ? 00:00:00 cdrdao read-toc --device /dev/cdrom /tmp/tmpb17wntqn.cdrdao.read-toc.whipper.task
root 4805 1936 0 14:09 pts/1 00:00:00 grep --color=auto whip
root@kokleda:/dev# ps -ef |grep whip
root 4930 3533 5 14:16 ? 00:00:01 /usr/bin/python3 /usr/local/bin/whipper --eject never cd rip --cdr --max-retries 3
root 4931 3533 5 14:16 ? 00:00:01 /usr/bin/python3 /usr/local/bin/whipper --eject never cd rip --cdr --max-retries 3
root 4935 4931 0 14:16 ? 00:00:00 cdrdao read-toc --fast-toc --device /dev/cdrom /tmp/tmpy012cq9p.cdrdao.read-toc.whipper.task
root 4938 4930 0 14:16 ? 00:00:00 cdrdao read-toc --fast-toc --device /dev/cdrom /tmp/tmpy3ec1pig.cdrdao.read-toc.whipper.task
root 4949 1936 0 14:16 pts/1 00:00:00 grep --color=auto whip
It is using python3 now though. I have set the Extension Manager to collect logs, where does it put them and what is the best way to share them with you?
Hello,
In my case it hangs in āreading tocā
Running in Proxmox Linux VM configuration
And the URL shows this error
Thanks
Hi @Frucoboti,
You installed the CD Entrypoint which is used to playback CDs and doesnāt support the Apple SuperDrive yet. If you want to use the CD Ripper, as you mentioned earlier, you can get it from the Tools category in the Extension Manager.
If the SuperDrive works for the CD Ripper then the Entrypoint will get support at a later time.
You are right! my mistake!
Itās now ripping, but, is it normal the speed?. Itās reading too slow. How many offset has each track?
Thanks.
Determining the drive offset is a one time event during drive configuration (assuming it can be determined for the SuperDrive).
Ripping is slow, the software that is used under the hood (i.e. Whipper) takes an accurate rip over speed.
Ripping crashed. Maybe the disc had some scratch.
But the trial period has goneā¦ 
Trying to solve another issue now, with credit cardā¦ I think I am going to buy a yearly subscriptionā¦
I will return in a few days.
Thanks
@Jan_Koudijs Hi again. Now, subscribed!
About ripping. Something isnāt working right. Tested with 3 discs. None of them got ripped.
More than 1 hour to return this error.
Maybe can I collect logs to send to you?
Thanks!
Happy New Year!
Had Roon lifetime for about 5 years now but this is the first time Iāve attempted to use the CD ripper as I had previously used EAC. I have to say, it worked easily and flawlessly! I donāt intend to be ripping too many CDs (basically just sorting a few albums with corrupted FLAC files) but will always use this from now on!
Nice work Roon team!
