CD Unloading Delay (Nimbie)

[setfield]

Hi,

Just got myself a Nimbie and I am working through digitizing my library.

Everything working great but something I am curious about. The "Unloading CD" and "Loading CD" steps of the batch ripping are taking very long. Way longer than the time to rip a CD. Is this normal? Here is what I have for my Batch Ripper settings:


Any suggestions?

Thanks!

[Spoon]

Re: CD Unloading Delay (Nimbie)

How long to load and unload a CD?

On the 2nd image, click 'test' to load and unload manually.

[setfield]

Re: CD Unloading Delay (Nimbie)

How long to load and unload a CD?

Minutes. Is this normal?

On the 2nd image, click 'test' to load and unload manually.

Are you recommending I do this during the batch ripping process? Would that go against the whole automated aspect of using the Nimbie?

[Spoon]

Re: CD Unloading Delay (Nimbie)

Not during the batch rip, just to see how long it takes to complete the test load.

[setfield]

Re: CD Unloading Delay (Nimbie)

Six minutes to load and the same to unload.

[setfield]

Re: CD Unloading Delay (Nimbie)



Here's an example... This CD single is still "processing" after 21 minutes.

[Spoon]

Re: CD Unloading Delay (Nimbie)

You would have to try Nimbies own software as a test to see how quick it is.

[acline444]

Re: CD Unloading Delay (Nimbie)

Hello: I was looking at Nimbie. I would love to know how that is working out. Are you planning on selling the unit after you are done ripping?

[THambrecht]

Re: CD Unloading Delay (Nimbie)

Do you use Windows 10?

Then we may have a similar problem.
It usually takes about 1 second to load and unload a CD.
But for a few weeks now, we have had the problem that after a few CDs, suddenly a CD can no longer be loaded - or ejected.
It takes hours to load ......
If you then switch off the nimbie and the software restarts, it works for the next 25 CDs. By the way, the mechanical ejection at the button of the nimbie is also blocked.
We are very "very" sure that this problem is caused by a Windows update that we installed around April 2020.
As soon as we do an rollback to an older version of Windows 10, the problem is gone.