TOPIC:

Hi,

  I just upgraded to the new Device Console (after upgrading USB audio driver etc.) The Device Console detects my SHD, and then throws up the prompt to initialize to default settings. I click on it as instructed by the upgrade manual, but after that the Device Console just seems to sit there and do nothing. It just hangs and has to be killed via task manager. Does anyone know how I can proceed from this step ?

Screenshot attached of what it looks like after I click on initialize to default settings.

I even left it alone for 10 mins or so after clicking the button. I see Minidsp Device Console using 50-70% CPU but nothing is happening. Have to kill it via Task Manager every single time.

Indeed, it is buggy on that step, as well as when trying to import an exported preset config.
A power reboot (or more) might help. At least this did the job for me on several similar occurences.
 

I tried rebooting the shd  multiple times. No use. 

gpoduval wrote:

I just upgraded to the new Device Console (after upgrading USB audio driver etc.) 

Does your 'etc' include successfully installing the new firmware onto your SHD?

Yup.

Based on all above info, I guess the best approach is to raise a ticket to miniDSP support, as any further workaround that may be suggested here, could be potentially dangerous for your SHD, i.e. brick it etc.

That being said, if I had no patience to wait support, or if I was ok with myself to take the risk, I'd try the below things:
1. Restore all presets to default through old SHD app, then try to connect through Device Console. Don't forget to export all presets prior resetting them to defaults.
2. Reinstall v1.50 XMOS / firmware to SHD. Uninstall PC drivers and reinstall them as well, then try to connect through Device Console.
3. Try connecting to SHD using Device Console on a different PC/laptop than the one failing so far.

In addition to this, with the new firmware, my display won't turn off even when I have it set to turn off after 10s. When I select that option, disconnect the SHD and reconnect, the display timeout is reset to 15. Even then, the display never turns off. 

Can I downgrade to an earlier firmware version ?

Minidsp should be doing a bit more testing before releasing buggy firmware.

I may be being overly cautious but personally I would not try to use the old plugin at all once the firmware has been updated. They aren't intended to be used together.

1.50 works fine with old SHD app, meaning that you still can configure Display settings just by connecting with old app. Thus, I don't see any reason to downgrade. 

Nervoservo wrote:

1.50 works fine with old SHD app, meaning that you still can configure Display settings just by connecting with old app. Thus, I don't see any reason to downgrade. 

My point is you've taken a risk even trying. It's entirely up to you if you wish to continue to do so but I don't think it's wise for anyone to advise others to do this. 

What is the exact risk to connect to SHD upgraded to v1.50 using old SHD app? How did you conclude that this is risky?
Asking because, as long as I've read manuals/guidelines etc, I was not able to find such caution by vendor but I may missed it.

Nervoservo wrote:

What is the exact risk to connect to SHD upgraded to v1.50 using old SHD app? How did you conclude that this is risky?
Asking because, as long as I've read manuals/guidelines etc, I was not able to find such caution by vendor but I may missed it.

My point is we don't know and manufacturer's don't always warn about things they don't expect anyone to do.

What we know is that it is required to update the firmware to be able to use Device Console, and that the last version of the plugin was designed to work with an older version of this firmware. As I said initially, I may be being overly cautious but we simply don't know.

Ok understand your point.

Actually I am forced to use the old SHD app rather than DC because the DC doesn't work. The old app seems to work fine.

Yes, it also seems to me that the best solution to solve the problem is to contact the support service or experienced programming specialists. After all, the error could have occurred in the code on the server side. I suggest visiting some professional online service and getting coding assignment help to sort out the situation. Usually, such online programming services usually have a large pool of experts with different skill sets. Whether users need help with web development, mobile app programming, data analysis, or any other area of programming, they can find dedicated support tailored to their specific needs.