DAC driver problems? Or something else?

I had the 14 day trial and things went well, so I let it roll onto the full annual payment. So far so good…

Then gradually a problem starting happening, which is now every time I trim on my system. I would try to play an album and the tracks would all race through to the end in 3 seconds with no sound coming out. Then it would be alright again once I closed down Roon and the DAC and started again.

Initially this was happening every so often, but got much more frequent. I would switch on the laptop and DAC in the morning and every time I had to keep switching between WASAPI and ASIO driver options to make it work, but it’s a bit hit-and-miss.

When I select a DSD track it races through the tracks in 3 seconds, when I select a 16/44 file it says Transport not initialised (or something like that). In the last two days it now happens if I leave the system not playing music for a while. Eg if I pause the music and leave it for a couple of hours, then unpause, it happens again.

Eventally I always get it working but it’s not great having to spend 5 minutes solving this issue every time I want to play music.

I have a very simple setup:

Router > Ethernet cable > laptop (Roon core) > USB cable > Sony TA-ZH1ES DAC > amplifier etc.

My laptop is underpowered and I’m just using it whilst I convince myself to get a Nucleus. I do hope this problem won’t keep happening once I get one, but my computer knowledge is minimal.

Any suggestions guys?

I appreciate any help and thanks in advance.

Try changing the usb cable from laptop to DAC. Sounds like a comms problem and that is the easiest link to change.

Just switched to a different USB cable and got this message when I pressed play on a Tidal album and a CD rip album:

‘Transport: Failed to initialize the audio device’

You can press the signal path icon and it shows in purple and includes my DAC in the signal path.

Any other ideas anyone?

@Woo - tagging @support for you.

BTW - I’ve gotten those transport errors, as have other people. Can’t remember what the problem was, tho. I think it might have been when I was using Tidal, so maybe network problem? Dunno. Did you search the forum?

E.g. -

There are plenty others. I’ll leave you to the hunt…

No I didn’t search as I thought it was such a specific problem. I did read of another user seeing the ‘racing through the tracks’ error on the dCS subforum.

It happened again today when I had the music paused for 30 minutes. Unpaused it and nothing would play again. I’ve now found that if I pause the music until the DAC loses the signal (about 10 seconds) it will then not work again until I switch between the WASAPI and ASIO options again.

I’ve noticed the Transport error only occurs with PCM files and the racing tracks issue only occurd with DSD.

Thanks for reaching out, @Woo,

First, can you give a little more information about your setup?

  • What kind of laptop are you using? What kind of CPU does it use? Is the Core on an SSD?
  • Where is the media library stored? Is it directly on the Core machine or elsewhere on the network?

Does this behavior only occur when playing to the Sony DAC? If you play to System Output of the Core machine do you experience similar behavior?

Can you share a screenshot of the signal path when you are able to play to this device?

Thanks,
Dylan

Hello Dylan,

Thanks for your response.

My laptop is a Lenovo with Intel Core i5-7200U

The core is not an SSD, the laptop only has HDD. The music library is on the laptop, which is directly wired to the router.

I don’t know if the issue occurs with other outputs, as I really only use the Sony DAC. I can try the laptop audio output thpugh. I did use a chromecast audio early on and had no issues, but as I mentioned this issue has been becoming more frequent until now it’s every time.

Re signal path. It looks all good - file data, RAAT and ASIO driver all Purple. I’ll take a photo and show you.

Re signal path diagram. I can’t make it appear at the moment because it’s doing the ‘racing through tracks error’. When I’ve had the Transport initialize error I’ve been able to see a signal path diagram and as mentioned above it all looks perfect. Just that the track timer remains at 0:00

This is the screen when it’s working. To get it to work I have to switch between outputs (eg. WASAPI, System output) other than the ASIO, then re-enable the ASIO then select it again.

Thanks for the info here, @Woo!

If you use System Output on the Core machine is there any noticeable difference?

Thanks,
Dylan

When using System Output it plays OK, but not in correct format/bitrate.

Hey @Woo,

Thanks for giving that a try! Since the content plays okay via System Output, there may be a couple of things going on. To narrow things down further I’d like to propose a test.

If you have another machine that can be used as a Roon Core, try installing Roon there and test using that DAC. When you do this do you experience the same behavior?

Thanks,
Dylan

OK. So do I have to download the 14 day trial on the other laptop? Its my partner’s and has a SSD too.

Hey @Woo

You won’t have to setup a new trial, you can use the same login information as the current account. Just head on over to our downloads page, install Roon, and use your login information. Give this a go on the other machine and let us know how it goes!

-Dylan

Thanks for the advice Dylan, I’ve been busy at work and need to wait for some free time when my partner’s here to use his laptop for the test.

Meanwhile, using the switching driver method I’m still getting great sound in DSD256 via the Roon/Sony combo.

Closed due to inactivity. If you are still seeing this issue, please open a new support thread.