Warning: This is a long post detailing weeks of attempts to get a Nimbie bot working with dbBatchRipper. Skip to my plea for help at the end if you don't want a breakdown of what I've tried so far.

I have been trying for many weeks to get dbPoweramp to work with a Nimbie NB21-BR USB 3.0 autoloader. After working with Acronova support for a couple of weeks, we never got the first Nimbie working with dbBatchRipper. The first machine rejected about 250 different test discs after initially ripping about 12. The rejects started after I closed the dbBatchRipper software and reopened it the next morning. The Nimbie machine also randomly disconnects from Win 10 Pro after I run any of the db* software. Unplugging the cable sometimes gets it to reappear, but most of the time, I need to reboot the machine to get it to reappear in Windows after it disappears. If I don't run dbPoweramp/dbBatchRipper after a reboot, the drive stays connected to Windows. The Acronova tech and I tried different USB 3 cables and different USB 3 ports. We also tried it with several USB 2 ports and cables. We've tried it with and without the special Nimbie configuration file downloaded from the dbPoweramp site. We tried it with only dbPoweramp and the basic Nimbie driver installed. I've uninstalled and reinstalled all of the software and drivers too many times to count. I've manually removed the device driver in Device Manager (found by showing hidden drivers when the drive was disconnected,) then reinstalled it. The tech even tried to get it working for a couple of hours via remote desktop sessions, while I watched disc after disc being rejected out of the bottom of the machine. Eventually, even the Acronova tech gave up trying to get it to work and shipped me a replacement machine to see if the problem might be a faulty machine. Unfortunately, the brand new Nimbie rejects every disc using dbBatchRipper and disconnects the drive from Windows, exactly the same as the first Nimbie I tried. I'm stubbornly refusing to give up on the potential benefits of using an autoloader combined with the dbBatchRipper software. In addition, I have future plans to rip my Blu-ray/UHD collection to a media server, once I've ripped and archived my CD collection successfully.

To answer the most obvious questions: Yes, I ran the dbBatchRipper configuration application each time. I also double-checked the transcoder settings in the single disc db ripper each time before using the batch ripper. On most of the tests, the drive was configured as "Nimbie" using the file from the dbPoweramp site. I've unconfigured and reconfigured the drive many times. I've rebooted and even shut down my machine dozens of times, something I almost never do. My system runs 24/7 for months at a time before it ever needs to be rebooted. My machine normally only reboots if Microsoft installs an update which requires a reboot. There was no Windows update installed overnight on the day it stopped working. I checked the logs to make sure.

My hardware specs: (in case they matter)
* 8 core/16 thread Intel i7 6900K CPU with 64GB of RAM, - No overclocking on anything
* ASUS Sabertooth ruggedized X99 motherboard,
* Samsung 2TB Pro SSD boot drive,
* several (>5TB) internal Hitachi SATA6 hard drives,
* two internal optical drives (a Blu-ray writer and DVD writer - both rip perfectly,)
* many USB 3.1 & USB 2 ports,
* NVIDIA GTX 980Ti graphics card driving 1x34" 4K UHD display and 2x30" 2560x1600 displays,
* I'm running fully patched Windows 10 Pro (Build 15603)

** NOTE: I've also tried many of these tests on my Surface Book laptop (completely different hardware, but same OS build,) returning exactly the same results. It rejects discs until the drive eventually disappears from Windows. So, it seems to be an issue with Windows 10 in combination with dbBatchRipper.

I believe any minimum resource requirements should be easily covered by my desktop setup. On the other hand,... if you aware of any problems with any of that hardware, please let me know. The drivers are all MS-WHQL certified. The firewall and virus scanner are standard Microsoft issue, and neither has ever indicated a problem. But to be safe, I disabled both briefly for some of the testing with no change in behavior. The new new Nimbie drive also disconnects from Windows randomly, exactly like the first one. Oddly, I can play the music discs directly from the drive in the Nimbie without any problems using a number of different music player applications. I can also rip discs manually one at a time on the Nimbie drive using JRiver Media Center. The results on JRMC say the tracks were ripped with zero retries and zero errors. The resulting FLAC files play perfectly. So, the drive is verifiably capable of ripping the discs.

You might be asking yourself, "Why doesn't he just use JRiver to rip his collection, since he knows it works?" I purchased dbPoweramp Reference specifically because of the AccurateRip verification ability. My goal is to get 100% verifiable bit perfect rips to FLAC files along with your above average automatic online database meta data lookups for most of my collection. So, ripping everything with JRiver isn't really a valid alternative as far as my primary goals are concerned. Plus, the JRiver meta data database has more missing entries, which will kill the benefits of automating this process. I reallly want to get dbBatchRipper/AccurateRip working with the Nimbie changer, so I can run batches of disc rips unattended overnight and wake up to perfect results. I actually researched and selected your software first. I then chose to buy the Nimbie autoloader based on the recommendation I saw on your web site. If I can ever get it to work, I'm certain I will be very happy with this combination. But, I have to admit that I'm fairly disappointed with my experience so far.

SO... Does anyone have any additional ideas I can try in order to get dBBatchRipper working reliably? I've seen a few fairly recent posts about these (and similar) Nimbie problems on the forums, but none of them sound like they were ever fully resolved. Despite being pretty technically inclined, I'm frankly running out of ideas to try. Can anyone help me out? Thanks in advance.