TOPIC:

Hi,
I was a happy owner of SHD Studio until now. I updated Windows previous UAC2 driver to v.5.40.0, firmware to current v.1.50 with DFU tool and MiniDSP Device Console to v.1.0.0. After that my SHL Studio lost sound on SPDIF output 1&2 and 3&4. The SHD Studio does not appear to be sending a signal out of either of the coax Digital Outs (1&2 or 3&4). My DAC doesn't give any indication of it is receiving a signal. My streamer connected directly to the DAC via COAX works very well.
Device Console shows live an active signal on both the inputs and outputs but there's no audio. My COAX cables are operational and the sockets in which they are located are correct.
All other hardware functions seem fine, the headphone output also plays music.  Reset all settings to default, Refresh XMOS, refresh DSP is not working. Going back to the previous plugin firmware version and then uploading the latest one does nothing either.

Also, I found things that bothered me.
1. The device console does not recognize that the USB driver is installed even though the current version of the driver is already installed in Windows 10 and seems to work correctly.


2. In the properties of the USB driver, I found the following entry in its event log (classified as an error):
"Device USB\VID_2752&PID_0045\5&292620dc&0&4 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_1C4F&PID_0002\5&292620dc&0&4
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(4)
Migration Rank: 0xF000FFFF00000023
Present: false
Status: 0xC0000719"

Previous versions of the driver always reported that the migration was successful. I have no idea what else can i do to fix the no sound issue...

You probably did check this, but as you did not mention it: Are the inputs connected to the outputs correctly in the channel matrix? And are the output channels unmuted?

Sorry to hear about the problems, but thank you for reporting. So I know I should wait with the update. Unfortunately the support will not be available for some days because of chinese new year, I think.

With my SHD connected via SPDIF (coax) to an external DAC it shows a 96 kHz signal all the time, irrespective of source selection or signal routing. Does yours @zborekrb? I'm asking because if it doesn't I don't think the issue can be anything to do with PC settings or how you have things configured in the plugin/Device Console.

Sorry to hear you're having this issue but I suspect this is one you'll need miniDSP support to resolve. If you haven't already you should contact them via the Support link at the top of the page. Although I'm afraid the Chinese New Year break will likely delay a response.

www.minidsp.com/forum/announcements/2100...new-year-break#63886

@gbr
Yes, I've been checking these settings to make sure everything is set up properly.

With my SHD connected via SPDIF (coax) to an external DAC it shows a 96 kHz signal all the time, irrespective of source selection or signal routing. Does yours @zborekrb?

Exactly, a properly working unit connected to the DAC via COAX should display PCM 96k constantly on my DAC's display. Unfortunately it doesn't show up.

I don't think the issue can be anything to do with PC settings or how you have things configured in the plugin/Device Console.

Agreed, but assuming that the USB driver is only used to establish a connection between the device and the software (device console).
At the same time, the manual says to install the USB driver before installing the firmware. So why install the latest USB driver if the old one worked reliably?

I keep in touch with minidsp support. For now, they say what's going on is odd.

zborekrb wrote:

Agreed, but assuming that the USB driver is only used to establish a connection between the device and the software (device console).
At the same time, the manual says to install the USB driver before installing the firmware. So why install the latest USB driver if the old one worked reliably?
 

The latest UAC version is needed for the firmware update to complete, which does of course happen via USB. I know as I tried with an old one at one point. An SHD can be used with nothing connected via USB or a computer having anything to do with music playback though, so nothing on a PC can be preventing you seeing the 96 kHz signal on your DAC.

@Ultrasonic
In previous posts I wrote that I updated the firmware using the latest USB driver installed on the PC. I lost sound after this update.
I observed that there is something wrong with the new USB driver installed in the system (Device USB\VID_2752&PID_0045\5&292620dc&0&4 was not migrated due to partial or ambiguous match).
As you wrote "The latest UAC version is needed for the firmware update to complete".
What if the XMOS/DSP update did not go as expected due to a USB driver error in Win10? Can you definitively rule out the influence of UAC on invalid firmware update leading to no 96k signal?
I assume the firmware controls the hardware and the firmware is responsible for the appearance of the PCM 96kHz signal at the COAX output of the device. In other words, the hardware is the executor of the will of the software.
Maybe this is overthinking and maybe I'm wrong, but that's all I'd like to suggest.

zborekrb wrote:

@Ultrasonic
In previous posts I wrote that I updated the firmware using the latest USB driver installed on the PC. I lost sound after this update.
I observed that there is something wrong with the new USB driver installed in the system (Device USB\VID_2752&PID_0045\5&292620dc&0&4 was not migrated due to partial or ambiguous match).
As you wrote "The latest UAC version is needed for the firmware update to complete".
What if the XMOS/DSP update did not go as expected due to a USB driver error in Win10? Can you definitively rule out the influence of UAC on invalid firmware update leading to no 96k signal?
I assume the firmware controls the hardware and the firmware is responsible for the appearance of the PCM 96kHz signal at the COAX output of the device. In other words, the hardware is the executor of the will of the software.
Maybe this is overthinking and maybe I'm wrong, but that's all I'd like to suggest.

Yes I'd understood the above. As you suggest the only way the UAC issue may be a factor is if it somehow meant the new firmware wasn't properly installed. Naively I'd have thought getting a message saying that the firmware had successfully installed probably meant it had but it's really only miniDSP support that can advise further. Note that the key point of my post above was that changing things on your computer now isn't going to fix the issue, and neither is changing settings in Device Console. I believe this is an issue with the SHD, be it the firmware or something else.

You're right. I just hope that the lack of sound is not due to hardware failure. But if it is related to the software, I think that in cooperation with the support, sooner or later we will manage somehow.