TOPIC:

Just installed Dirac 2.5.3, same problem ;(

I bought my SHD in August 2019 from Deer Creek Audio. The Activation key was included in the package and was used to "unlock" the files (miniDSP plug in and Dirac Live plugin) from the miniDSP login account. Once used I've never had to use it again. This was still Dirac Live v1.

It was a convoluted system which made the user experience less than satisfactory as I recall. I had to call Deer Creek Audio several times to figure out what to access, I messed up and could no longer use the key, they had to issue me another key and finally, three calls later, I was able to download the files.

I hope that they have done away with it because a new user does not need that frustration. In any case, I ended up getting access to software for another product line in the process.

UAC2 driver seems right for the audio driver. I imagine the SHD is technically a Compound USB Device, meaning that different endpoints can have different classes. It presumably implements audio, DFU or similar (Device Firmware Update) and some class for SHD control. The specialised SHD control is used from the specialised SHD plugin app. I presume that since audio and firmware update capabilities are the same across all products the firmware update capability and the audio capability are both in the UAC2 driver.

lmerino wrote:

Just installed Dirac 2.5.3, same problem ;(

I suggest contacting Technical Support.

Hi, I reached out, have not heard back yet. Trying everything I can think of in the mean time.

Thanks

To update,

Got a tip from another forum that someone else had the exact same problem. They wiped out their computer and did a fresh install of Win10 and it worked.

So i tried that, and sure enough it works. Problem is I did a fresh install on a desktop in another room and I can't wipe my laptop at the moment to bring into the living room.

Hopefully support can help identify some stray .dll or registry entry that may be messing things up. Perhaps from an old install of Dirac I assume? Although I never installed anything prior to v2 on this machine, but I did use Dirac with the audio processor they offer. Perhaps once Dirac looked for the plug-in version it doesn't look at the USB connection? It's expecting the software processor instead? Or could just be some other random program?

I don't think old Dirac versions will matter, in my experience you can have many different builds of all versions installed and they don't intefere with each other. DAP on the other hand could be relevant, I'm guessing not many folk have DAP installed and an SHD.

entripy wrote:

I don't think old Dirac versions will matter, in my experience you can have many different builds of all versions installed and they don't intefere with each other. DAP on the other hand could be relevant, I'm guessing not many folk have DAP installed and an SHD.

I suppose. The surprising thing is that this is on both Mac and Windows, but I did have the audio processor on both at some point. I've scoured both machines trying to get rid of any trace of old Dirac info, but no luck. At this point I'll wait for tech support to reply and see if they have any ideas, otherwise I'll just need to wipe out a machine so I can do some measurements.

So just an update. I was able to get my Windows laptop to connect to the SHD, but not my macbook.

On the windows machine I found that a program I had installed had sideloaded LabView from National Instruments. That software was running an application web server on port 8080. I have no idea why!!?? but alas.

The original software I had installed was a DSP GUI from Parts Express to control one of their subwoofer plate amplifiers. I had installed it on both my laptop and desktop at some point or another. When i uninstalled it, i was able to connect to the SHD just fine.

Unfortunately that software is not even available on Mac, so i never installed it on the macbook. So i still dont know what the problem is there, but at least I can use my windows machine for now.

Thanks

www.minidsp.com/forum/dirac-series-suppo...r-device-my-solution

that message may suggest how to diagnose the problem on Mac, maybe