virtualbox.org

Summary: With Windows 10 64-bit Pro version 1511 guest under VirtualBox, CD ripping with dBpoweramp was fine. After feature upgrading to Win 10 Anniversary version 1607, no AccurateRip can be achieved at all. Any help out there?

Long write-up:

System:

• HP Laptop EliteBook 8560w with internal CD/DVD drive
• Linux Mint 18.0 Cinnamon host
• VirtualBox 5.0.24 incl. Extension Pack, which is the most recent version in the Linux Mint software repository
• Windows 10 64-bit Pro as guest, incl. Guest Additions

dBpoweramp is THE standard for ripping audio CDs in a bit-perfect fashion called AccurateRip, which works by comparing CRCs of the ripped audio files to a web-based database of ripping results populated by the dBpoweramp users. To achieve this, the CD drive offset has to calibrated once after installing dBpoweramp. I have been using this software for many years in stand-alone Windows versions.

Error:

• When my Windows 10 guest was version 1511, everything was fine with dBpoweramp. My audio ripping results agreed with the AccurateRip database and prior rips by myself.
• However, after feature upgrading Windows 10 to Anniversary version 1607, I am never getting any rip to agree with the AccurateRip database. Fortunately, the Windows 10 upgrade process didn't wipe out my program settings (as reportedly occurred to others). I did also go ahead and deinstalled dBpoweramp completely (including deleting leftovers from the registry), then installed it from scratch, calibrated the CD drive again. All this to no avail - no bit-perfect AccurateRip results anymore, never.

Any help out there for the audio CD ripping problem?

Addenda:

• Yes, I know, VirtualBox 5.0.24 is not the most recent release, but it's the latest one available through the Linux Mint software repository. Yes, I know Windows 10 Anniversary is not mentioned as an "officially supported" guest OS by Oracle.
• But then, everything had been fine with Windows 10 version 1511 !!!
• And yes, I do also experience the heavy sound distortions / crackling audio occurring after upgrading to Windows 10 Anniversay, which has an Oracle VirtualBox ticket set up, but seemingly still lacks a solution.

Unfortunately the Various Linux distros may change Virtualbox in their repositories, so forum supporters may not know what has changed. Thus you will need to uninstall the Mint version of Virtualbox and use the official Virtualbox.org Linux installer to get help on a Virtualbox problem here.

That said, are you sure this is a Virtualbox problem? Does dbpoweramp and accuraterip work in a physical Win10AU PC? Did you try toggling the guest's CD drive pass-thorough setting?

One may need to allow time for Win10AU to be a supported guest.

No, I'm not sure it's a VB problem. All I know is it worked with my environment and settings under a guest Win10-v1511, and it malfunctions starting with W10AU-v1607 as guest.

Yes, I tried to toggle the CD drive communication in dBpoweramp, but to no avail.

I also know it worked under a physical Win10-v1511. Maybe I'll manage to get a physical Win10AU-1607 - but then, the dBpoweramp forum reports that the Anniversary upgrade does wipe some dBpa settings for some but not all users; there are no complaints about dBpa malfunctions in Win10-AU.

I will do more (install official latest VB) and report back then. Thanks!

111MilesToGo wrote:I tried to toggle the CD drive communication in dBpoweramp,

Sorry, I meant "toggling the guest's CD drive pass-thorough setting in the Virtualbox settings."

I have been experimenting with the settings of dBpoweramp CD Ripper, and I have been checking into my virtual machines in the current status of running Windows 10 AU v1607 as the guest operating system as compared to the previous status of the Windows 10 v1511 guest.

The results and recipe for solving the problem can be found here:
https://forum.dbpoweramp.com/showthread ... VirtualBox.
As stated, I have no long-term experience with the new settings of dBpoweramp CD Ripper. And I have no explanation yet for why a setting that ran fine under guest Win10 v1511 doesn't work anymore under Win10 AU v1607, sticking to the same VirtualBox 5.0.24 run under Linux Mint 18.0.

That said, I don't know whether it's a dBpoweramp problem, a VirtualBox problem or a change in Windows 10 which isn't taken care of in either dBpa or VB.

Any feedback is highly appreciated. Thanks!