Windom: Installation/Technical Problems

Something I thought of (sorry if someone else has suggested this) we had no “update” issues when switching between different versions of snowmass’ (ie when only changing pic codes) we only have problems when the Fpga code changes.

Conversely I (and those testing/listening to different FPGAs) never have problems when only the FPGA changes. It’s related to the magnitude of the PIC changes or the location(s) of the stored parameters of a release.

1 Like

@Paul, i found a bug in the on screen + volume regulator of the DS sr.
When i push the + volume on the DS screen and then release it, it keeps on growing until 100.
The - volume does not have the same problem, when i release it, it stops right there.

@chris5 - digging that - I vote for calling it “Snowman”. (I hate Siri, BTW, if that’s who spelled that, but sometimes it is fun). Going to do a Snowman “Build” later… : ). A revision of the bits laid down in the yard, so to speak.
image

And Ted - hafta say Chris has a point here.

I encountered the volume control issue on the screen also. I assumed that it was an undisclosed feature. It certainly makes sense if the software load reverts to a low volume.

If you’re referring to it booting at 25, yes - intentional.

Paul:

I think everyone can appreciate your sharing opportunities in improving the DSD update firmware process as mentioned in post #160 above. This is in no way meant to be a complaint; consider it a nudge. I suggest rolling up lessons learned known at this time and updating the “Quick start instructions for updating firmware via SD Card” listed in the Resources Downloads section of the website with the understanding that all issues may not be fully resolved due to the multitude of variables impacting an upload. As you state and from others’ comments there are some meaningful lessons learned here to clarify the firmware update process to further limit upload problems. Examples are the importance of the SD card size, process to format the card, power cycling twice the unit twice, confirming the files are properly unzipped, and a suggestion to reload an earlier firmware version if necessary to gain a satisfactory upload of the current firmware. I can say i’d appreciate it for Windom and future firmware updates.

Clearly the PSA team is working on it as I just noticed that the firmware updates have been split into a MAC and a Windows version implying PS Audio has learned something along the way. When I checked earlier last week there were about 1550 Windom downloads, implying as you say the problem may be isolated. Currently there are 89 Windows downloads and 46 MAC downloads of the Windom firmware. Apparently some have stumbled on it as I have not read any announcement of the changes. I am also looking forward to hearing of the end user results associated with the “updated” or OS spilt firmware.

It’s not what’s going on. I’ve done many more installs than most, if not everyone here. I’ve experienced and/or debugged back the bad formatting errors, the forgetting to use the OS’s Eject function errors, the DS Jr not updating as reliably as the Sr (but only if it hasn’t been updated recently…), and done hundreds of updates with identical pic code, but different FPGAs. Also just FYI, using the newer FPGA’s with the Snowmass PIC code. Update problems correlate with differences between the source and destination sets of PIC code, not with differences between different FPGA’s.

2 Likes

OK - give me a minute - OK maybe an hour, to spell out what I’m trying to say re: the last couple of posts.

The thing this laughingly reminds me of is how I’d offered to be a liason between the PS engineers (though you’re obviously outside of that group, to some degree) and the Forums, as it was clear to me that direct communication/conversation between end users experiencing/doing the…uhhh…Gamma Testing, and Engineering would be of inestimable value. Most companies would call that “focus groups”, which I understand is fraught.

My point is not about the booting at 25 !
I use the DS as a preamp directly to a power amp.
When i touched the ‘+’ button starting at 50 then releasing it when it reached 60, the volume kept increasing till 100. Fortunately i wasn’t playing any Metallica when this happend.
It’s not unthinkable that you can blow your loudspeakers this way.

My reply was regarding this behaviour.

Jovo - That sucks… I was responding to watchdog though

Glad i’m not the only one suffering this behavior.
But, i don’t understand your saying about an ‘undisclosed feature’.
When i stop at 60 i want the DS to stop exactly there, can you imagine how load it gets when the volume goes all the way up to 100 directly into a power amplifier that puts out 180 Watts.

Well I get the reverse effect, i.e. it’s the ‘-’ direction that keeps going (annoyingly) - I’ve never had the volume keep increasing - that’d be very unpopular at 2am!

Mine did this once or twice as well. Good to have the amp outputs off while updating and resetting settings

I don’t interface with the display except to ensure settings are right for my system, no attenuator is about it and then I dim the display.

I would love a version of Ted’s code that runs without PIC interaction or routines at all.

See Windom: Sound Impressions Post #540:

Hi @badbeef, Thanks for pointing out my typo, and thanks for coming up with the suggestion to unplug all inputs before updating. It solved my update problems

Not meaning to call you out on a typo. We all do it. I just thought it was a Good One : )

Glad the “fix” worked.

1 Like

Neither do the rest of us. It does appear to be Happening, however. I didn’t like it for the first week because it sounded wrong in a number of ways.

It - or actually the FW for the DAC, or some still-not-understood interaction between the FW and HW (as perhaps Ted is inferring, given past PIC code interactions), is the New, primary variable here in all of our systems. If you “got a good load” from the get-go like the majority, I completely understand your thoughts. Even my own brother - whose ears and gear I love and respect - wondered what my Problem was.

Has anyone noticed a difference using the now specific Mac or Windows versions of Windom?

1 Like