TOPIC:

Hi,

I updated my SHD Studio to the new DC software and firmware yesterday. My old Display Settings seems to have been reset since the update. I can’t find the Display Settings in the new Device Console software. Or am I missing something?

It would be nice to add that feature again. 

I can't find it either. I too, updated yesterday. I know they've had a problem with burn in on the display. Maybe this is the cure. I previously had the display on full all the time (when turned on), but I suppose I'll get used to it going off after 2 minutes. 

Sunde wrote:

Hi,

I updated my SHD Studio to the new DC software and firmware yesterday. My old Display Settings seems to have been reset since the update. I can’t find the Display Settings in the new Device Console software. Or am I missing something?

It would be nice to add that feature again. 

I don't think you're missing anything, and I believe Ed is right that the flexibility has been removed with the aim of protecting the OLED displays.

Thanks guys!

Too bad if thats the case though. I actually want to set the timer to a lower setting. I used to have 5 sec before the display shuts off. I just want to see the display when I change something. Then I want to enjoy music without distraction. 

This works fine as well. But I liked the feature earlier.

Personally I understand stopping displays being on all the time as this clearly can lead to problems but I agree it would be nice to still have the option to adjust how long the display stays on for.

For real? They took away even the dimmed always-on setting? Unbelievable. 

To be fair, it's still in beta.

EdHowarth wrote:

To be fair, it's still in beta.

Fair point. My take is that this isn’t something they should change forcibly. Many of us have been using our SHDs a certain way for years. miniDSP can add a new disclaimer about burn-in or something for those who want to keep always-on, but they shouldn’t just take away that behavior from existing users. I keep mine on the lowest dim, but always on. That isn’t perfect — the change in the Dirac logo in 2022 doesn’t look great and is an annoyance — but worse is all of a sudden forcing me to use the timed turn-off option.

If anything, I was hoping they would allow us to have an always-dimmed, always-on. I don’t ever want full brightness in my dark listening room. Just because I nudged the volume 0.5db doesn’t mean I want the screen brightness to change. Let me keep it fully dimmed all the time if I want! That would be so easy for them to program, I don’t know why they haven’t thought of it themselves and delivered it. 

There are probably more polite ways to tell the devTeam that we really want this setting to be available instead of grumbling around about this.

If you don't want to be a beta Tester than don't install the software...jeeez

Always attack the devTeam for every little misstep isn't gonna help anyone.

just my 2 cents

edit:
for the record I would prefer to be able to set at least the timeout setting between 5 secs and a few minutes.

Maybe there is a way to program a screen protection which walks thru the oleds every 15 mins or so, so they don't burn in. For always On option of course.

Sunde wrote:

 I used to have 5 sec before the display shuts off. I just want to see the display when I change something. Then I want to enjoy music without distraction. 
 

oh yes, I second this! Thanks for mentioning this, so I will wait with upgrading the software and hope that this feature will be implemented again.

Why do they use a OLED display anyway?  It is monochrome and worse looking than most LCD displays.

Did anybody wrote with the devteam to ask if they will implement the display dim timeout and brightness configuration in device console?

If not, I would write a remark in the announcement thread.

I've not updated the software yet and the auto display off won't effect me, it's as I run it today but has the ability to adjust the brightness been removed? I listen at night in a darkened room and can imagine the display coming on full brightness whenever I touch the control to be jarring. If this is the case I might contact @DevTeam and add another voice asking for this feature to be reinstated.

itskaefer wrote:

There are probably more polite ways to tell the devTeam that we really want this setting to be available instead of grumbling around about this.

If you don't want to be a beta Tester than don't install the software...jeeez

Always attack the devTeam for every little misstep isn't gonna help anyone.

just my 2 cents

edit:
for the record I would prefer to be able to set at least the timeout setting between 5 secs and a few minutes.

Maybe there is a way to program a screen protection which walks thru the oleds every 15 mins or so, so they don't burn in. For always On option of course.

Gotta love the folks who rush to miniDSP’s defense even though we’ve all seen this company commit a ton of unforced errors.

Indeed, I did ask them what I should expect from Device Console, as a person who used the always-on and always-dimmed feature (with mandatory timer on the dim, even though I’d like it dim all the time). I made the case that they shouldn’t take away a basic interaction behavior away after having the unit out so long. I am including the entirety of my email here so that I’m not accused of being rude or unreasonable. You may say the tone is a bit unfriendly, but that’s life.

Do I understand correctly that if I update my SHD to DC that I will lose my ability keep my screen on the lowest dimmed always-on setting? I have always used that setting. You can’t just take that away from people in the middle of their ownership. Put a burn-in warning on if you want or something, but you shouldn’t be removing features under our noses. Please clarify. 

If anything, I had hoped DC would let me keep the screen always on the lowest dimmed setting, even if I change the volume. That’s what I really wanted. Always dimmed, always on. 

Thank you,

Their reply, and this is the entirety of it:

That is indeed correct that the feature is now hardcoded to turn off automatically on the SHD  like Flex series has been. 
If that doesn't fit your needs, maybe you could just stick to the older version of plugin and just not upgrade? 

Hoping this info helps and feel free to contact us if you have further questions. 

Not a single word about it just being a beta, or that the display behavior is still being decided. No acknowledgement of my use case or them rethinking this. Just a suggestion I stick in the past and don’t get to enjoy any of the big updates they say they’ve made with Device Console.

If you don’t like what you’re hearing about the SHD’s display with Device Console for SHD, then 1) absolutely do not install Device Console (if the reports of bricked units here and ASR didn’t already scare you off), and 2) tell miniDSP that you want the display left alone (or, like me, improved with more flexibility, not less!). 


 

notman wrote:

Not a single word about it just being a beta, or that the display behavior is still being decided. No acknowledgement of my use case or them rethinking this. Just a suggestion I stick in the past and don’t get to enjoy any of the big updates they say they’ve made with Device Console.

If you don’t like what you’re hearing about the SHD’s display with Device Console for SHD, then 1) absolutely do not install Device Console (if the reports of bricked units here and ASR didn’t already scare you off), and 2) tell miniDSP that you want the display left alone (or, like me, improved with more flexibility, not less!). 




 

I think I've seen one* example of a bricked SHD across both fora, which was resolved with miniDSP Support's remote help rather than the unit needing to be returned for repair. Possibly I've missed others but let's not make something minor seem like a major problem. Importantly though this issue looks like it has been addressed by the updated DC version released yesterday going by this change log:

Device Console ChangeLog (minidsp.com)

Note that this latest release is no longer labelled as beta too.

The idea of simply not updating to Device Console in your case is clearly a good one in the short term with honestly little downside for you. Where I can see an issue is if long term there needs to be an update for ongoing compatibility with Windows/Mac OS, or for compatibility with a Volumio update.

*Edit: just checked out of curiosity and see there were two examples on the main ASR thread.