Firmware 12.3.0 + DOS 2.2.2

[iamwappie]

Yeah that’s going to be tricky. Presumably they’d never release the ‘secrets’ behind SAM, but they could host the SAM database externally so that it could be accessed by the pro configurator. But if Devialet went under and you got locked into having it disable SAM that would be one thing, being locked into being stuck with the wrong SAM would be another. So as long as you had the ability to disable it while keeping all your other settings at least you could still use your amp if you changed speakers and they weeent around.

I think Roon are there to stay but it’s also a decent business move to publicly state your committed to leaving a Roon that would still run in the event the company ceased to exist. Not sure what the reality of that is with all their external ‘paid for’ metadata but I guess they could leave you without all that but with a system that would still play your files.

Hopefully neither will disappear and we’ll get a local configurator for the experts.

Selecting a speaker just results in a text block insertion in the cfg file which for the same speaker will be the same for everyone so it would just be a matter of selecting all speaker profiles and collect all specific SAM text blocks, build a GUI and some piece of code (not rocket science) en voila. That the beauty of the text file simplicity.

I had problem editing the CFG file and then noticed it had a CRC on first line...

https://en.m.wikipedia.org/wiki/Cyclic_redundancy_check

[url=https://en.m.wikipedia.org/wiki/Cyclic_redundancy_check][/url]I assume this prevents simple editing?

Sorry just realised my mistake, I was editing the dp_cfg.txt file, is this the one you referring to re SAM?

Yeah you can’t edit the config file by design. I get that they’re protecting consumers from harming their hardware, but I wish they had an advanced mode where users could elect to edit the text files. This could be a lot quicker in the right hands (and especially if documented). And it’s not like their own configurator doesn’t make mistakes.
Believe it or not, some of us are technically competent and prepared to take responsibility for our actions.

I'd guess that a simple CRC is indeed for safety so customers can't easily change the config file and possible damage the system but it is by no means a hurdle as security measure. Manual changing the config file and generating a new CRC should not be that difficult. Question is if which part of the config file (or the complete file) the CRC is generated.