Last night I tried to put my Snowmass- and Bridge II v3.5.1-enabled DS into standby using the blue front-panel button. I pressed the button three times and each time the DS went into standby and popped back on virtually immediately. I never had that happen even once in four years prior to last night. Eventually, I was able to put the DS into standby using the OFF button on the remote, and it remained in standby until I turned it back on many hours later.
Note: I have an AC-powered Matrix X-SPDIF 2 connected to the DS via I2S, and the Matrix is powered on at all times. I have had the Matrix for many months and only experienced the DS doing an unwanted power-on for the first time last night.
If the PIC code has an affect on sound quality, why isn’t Ted writing the code for the display? What I mean is, he is often looking to achieve an end result with each new release and if the PIC code has a way to alter that sound wouldn’t it be appropriate to make sure that code doesn’t alter the end result he’s looking for? I completely understand why the Bridge software is handled by PS Audio, but seeing how the touch screen is an integral part of the Directstream I’m just curious as to why this isn’t the case. Graphical design is one thing. I’m sure they could tell Ted how they want it to look and function and he could code it in a way that sounds best. Or does PS Audio (and Ted) have faith they won’t lessen the results Ted is looking for by having someone else code it?
This split is pretty clean. I didn’t design the display processor board, there’s a lot of the display processor code that’s shared with other products and further all of the Bridge UI is in the display processor.
I did write the routines they use to talk to the FPGA which is also the code that “baby-sits” the FPGA.
I don’t want to have to be involved with each release they make of the bridge, with each change of the UI they wish to make, etc.
The sound quality differences are mostly minimizing the harm that any component does, so there isn’t some kind of synergy between the FPGA and the display processor to get great sound. They each try not to mess things up too much.
Another way of looking at it is I can make a bigger difference in the sound quality by spending my time thinking about and working on the FPGA code rather than tweaking the display processor code…
Nice for you… but it doesn’t help disprove the idea that the bridge might be part of the problem. If somebody who doesnt have a bridge had encountered the problem, then that would mean the bridge can be ruled out as a cause.
installed (easily) “Snowmass” yesterday. Could not hear loud, because it was 11 p.m. First heard the song
“Jenny Wren” from Paul McCartneys “Chaos and recreation in the backyard”. I nearly had to cry: Paul, I think I love you !!! Can’t wait till weekend.
Thank you to all of PS Audio.
I use DS with Bridge II 3.62 and not have any problems. At this 3 days. I have a little bug at first day use Snowmass but “power on/off” fix this bug. My DS sleeping without problems 3 last nights.
Agree with this description. the instruments and vocals have a greater sense of embodiment and focus and a deliver a very coherent resonance and decay. The sound stage and ambience of the recording venue is definitely more pronounced.
My DS not have sleeping on/off proplem. Only one - he is not turn off by remote control, if I press on/off button he is turn OFF and again turn ON in one monent. Blue button on the face plate on the DS doing same strange thing. another say - DS after installing Snowmass don’t want go to sleep mode.
Then I turn OFF DS on the rear side, wait two minutes. And turn ON. At this monent, my DS not have any problems.
Ohhh, no, one very LITTLE bug I have -
Awery morning I wake up my DS from remote control. Turn off the screen by “dim” button on the remote control. And then start play music by Bridge II (I listening my DS only by Bridge II v. 3.6.2). And then music is start playing - the screen on DS is ON, and I press “dim” button again. And all day awery thing is OK.
Sorry for my English, I’m Russian audiophile. :румянец:
They found the high refresh rate of the display was causing the issue and lowered it to 80 hz. it is a non issue. The PIC software is written by Matt and the team. That issue has been corrected.
