Audiolense ASIO - Device Initialization Failed following upgrade

Support
1

Roon Core Machine

Windows 10 Computer, i7-4790T, 16GB RAM
Roon Version 2.0 (build 1272)

Networking Gear & Setup Details

Ethernet. No VPN

Connected Audio Devices

Chain is Roon → Audiolense ASIO → RME Fireface
Some other “Roon Ready” devices used in other rooms (all of which are working)

Description of Issue

“Device Initiationalization Failed” error when attempting to enable Audiolense ASIO following upgrade to the most recent version of Roon. I’ve un-installed and re-installed both Roon and Audiolense Convolver but the problem remains. Also, I’ve renamed the RAATServer folder to force Roon to create a new server but this hasn’t solved the issue.

2

Any advice as to how to diagnose the problem?

3

Hey @Andrew_Stamp,

Thanks for taking the time to write in, and my apologies for the delay in getting to your thread!

Do you experience any playback/initialization issues when playing audio from other sources outside of Roon?

From your core diagnostic, we’re seeing success when playing to 8 channel. When this issue occurs, how many channels are you attempting to play to? If you could test out a few different formats, that would be helpful.

I’ll be on standby for your reply. Thanks! :+1:

5

Ben -,Thanks for the response. Answers in bold

Do you experience any playback/initialization issues when playing audio from other sources outside of Roon?
No. I’m able to successfully playback from JRiver Media Center to Audiolense Convolver ASIO

From your core diagnostic, we’re seeing success when playing to 8 channel. When this issue occurs, how many channels are you attempting to play to? If you could test out a few different formats, that would be helpful.
I’m unable to get to the point of playback with the Audiolense Convolver ASIO end-point as I cannot enable the device. The plan, however, is to just output 2 channels. Note: as a work around, I’ve set-up another device with convolution within Roon but this is not my preferred method.

7

Hey @Andrew_Stamp,

Thanks for the update! As a next step, I would look to update the sound drivers on the Audiolense via the manufacturer’s website. A fresh reset may also help if they’re already up to date. I’d also double check that the firmware is up to date as well.

After this, I’d also refresh the RAATserver database once more:

  • Create a Backup of your current Roon database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the Roon App to generate a new RAATServer folder
8

So I’ve done the following:

  1. Updated Windows
  2. Uninstalled AL Convolver, re-started and then installed the latest version
  3. Renamed the RAAT Server as suggested

… but the problem remains, i.e., Audiolense ASIO is seen as a device but it cannot be enabled.

10

Thanks for the update @Andrew_Stamp,

While our team investigates this a bit more, I’d be curious to see if a fresh database may help. Steps to follow below:

  • Create a Backup of your current database
  • Exit out of Roon
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon”
  • Rename the “Roon” folder to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the backup

Thanks!

12

Hey @Andrew_Stamp,

We were able to discuss your issue on our team call today, and are curious to see if your RME device is set up/enabled as WASAPI?

Roon may be recognizing the RME as WASAPI and therefore causing the ASIO device is failing. You won’t be able to run both at the same time, unfortunately - ASIO devices essentially run in exclusive mode.

If you remove the interface from your chain, can you enable the ASIO? As a next step, test out disabling WASPI in Roon and elsewhere on the computer.