Connection issue with McIntosh DA2 DAC (ref#W1FFX1)

Support
1

What’s happening?

· I'm having trouble connecting to Roon

What type of connection issue?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

I can no longer connect to my McIntosh DA2 DAC

Describe your network setup

Nucleus + via Ethernet to Streamer, to DA2 via USB

2

Can you share a little more about your “streamer”?

3

Rasberry Pi connected via USB. That said, I tried a Dell Laptop connecting via USB. Roon actually sees that connection to the McIntosh DAC, so it can be selected, but the connection shows as busy. The laptop, running Tidal, to the same USB port works just fine.

4

No rush. I have an Auralic Vega also connected. Tomorrow, I can reconnect the laptop which shows the error and then I can send log files, if that works.

5

Well, technically McIntosh only tests and certifies Windows machines running their drivers with the DA1 and DA2 modules. My primary rig is an RME ADI-2 DAC (AKG) fed via RoPieee, but I also have a Windows 10 box for my DA2. But from the sound of your original post, it seems like what you had was working before and it suddenly now is not. Are you running RoPieee?

6

Yes. Initially, it was flawless. Now, it doesn’t show in devices. The PC is identifiable by Roon as a source but the port shows as “busy” when music is played.

7

Hi @Gerhard_Martan ,

Does the McIntosh DAC still work with other audio sources outside of Roon? Sometimes I have seen failing USB cables trigger this kind of behavior, does a different cable help?

8

It does. Using the same laptop connected to the McIntosh via USB, Roon sees the connection but won’t stream to it (connection busy). Tidal, from the same laptop, streams just fine. After I acquired the McIntosh, I connected a Rasberry Pi, that I had earlier built for fun, and it worked fine for weeks before Roon stopped seeing the DA2 in Setup.

I just ordered another USB cable but I doubt that’s the problem. Someone reported this same issue in 2020 but the thread was eventually abandoned so no resolution posted. When I find time to capture and post a log file, do I just use this support reference number?

9

Hi @Gerhard_Martan,

Thanks for your willingness to test a different USB cord.

You can send over a set of logs to our File Uploader. Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!

10

New USB cable should be delivered today. I just did the latest Roon upgrade. Roon no longer saw the McIntosh DA2 DAC until I started RAATSERVER. When trying to play to it, it still displays as BUSY. I’ll try to send the log file.

11

It is 12:24 PM. The last log file is 8:46 am. Can I expect another to be shown later?

12

Hi @Gerhard_Martan,

Thanks for sharing the timestamp! The log excerpt you provided shows a disconnect and reconnect cycle involving multiple audio devices. We’re also seeing

failed to connect(0) Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'

This confirms that Roon tried to reconnect to the audio devices but found that the underlying socket had already been disposed of — likely because the client app had already shut down or restarted its RAAT service.

Two areas to review based on this:

  • Make sure firewall or AV software isn't interfering with port usage on that client.
  • Ensure the client device isn’t going into sleep or low power mode, which can sever audio and RAAT connections.

We’ll be on standby for your reply!:+1:

13

I didn’t post any log files yet. The new USB cable was delivered. The computer worked immediately. The Raspberry Pi required a full reset to see the DA2 DAC. It all works again. Good call on the cable.

14

Hi @Gerhard_Martan ,

Glad to hear that everything is working properly again with the new cable, this is fantastic news! I’ll go ahead and mark your thread as solved, happy listening!

15

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.