Transport: Failed to select Roon as the current source [dCS Vivaldi]

Audio Gear Talk dCS
22

This may be due to some things that AO does in the process of “optimizing” the configuration of the host OS. From the DAC standpoint its communications are essentially the same whether you’re using ASIO or WASAPI. The real difference between the two is what parts of the operating system are involved in the playback chain. This could also be an issue with the driver itself or an interaction between Roon and the changes that AO makes.

Two things to check:

  1. Do you have the latest version of the dCS driver downloaded from the dCS website?
  2. Disable AO and try again. Do you see the same issue?

You don’t mention what version of Windows you’re running, but I have seen some issues with WASAPI on Server 2012 as the WASAPI support there is a bit of a hack. There could also be an issue with one of the recent Windows updates as it relates to the playback chain.

Any particular reason why you’re using WASAPI instead of ASIO? If it’s computer used solely for audio playback then there’s no reason not to use ASIO.

23

Experienced the issue with Roon glitching on sample rate change through the Vivaldi USB WASAPI driver prior to and after using AO

AO both on Win 10 and in a prior incarnation with Win 2012 R2…Single PC constructs…with Process Lasso also operative on the Win 10 build.

Am fine with using ASIO…just was (intellectually/debugger) curious as to why the WASAPI path was failing…that and a mild touch of OCD :slight_smile:

24

7 posts were split to a new topic: Playback instability when changing sample rates [dCS Network Bridge]