Regarding your comment on software update, I agree largely in principle. There are instances where small bug fixes on a mature product which should not necessitate detailed change log, that's why you see many update logs with just one line like "security update", or "minor UI performance tweaks". In this instance however I think it would be beneficial just to have an official channel of communicating changes in the first place. Definitely not advocating for comms to be "perfect", "beautifully written", or "ideal", but "factual" and just merely existent would go a long way....the adjacent point to this is software changes that address known bugs.
Typically, those fixes/changes are noted in release notes. Sometimes they are driven by customer requests, or complaints. Sometimes they are enhancements that have been on the dev roadmap for some period of time.
That said, it is not always the case that detailed release notes are provided to end users/customers. That some here are making the case that they *should* be provided is understandable, but that is an opinion and not necessarily a generic software *obligation* in the process.
I think it depends on the nature and origin of the change, to some extent. And the company philosophy, perhaps.
If users are requesting a button that makes a fart noise when activated, a company will likely note when that feature has been added.
On the other hand, if the company has been working on a refinement (fix) for some sort of error logging, signal handling (I'm making these example up, of course) that uses less energy, etc. it may not publish those changes because:
--it reveals coveted knowledge.
--it reveals an issue you didn't even know existed, and was an edge-case.
--you wouldn't understand the details.
--they don't have resources to edit/scrub release notes for user-appropriate content.
In a perfect world, all comms would be perfect. Transparent. Factual. Beautifully written. In the real world, sometimes they fall short of that ideal, IMO.
That has been precisely my point, you wouldn't have known I was an owner, because it shouldn't have mattered. The issue being raised should be judged on its own merits instead of ad hominem, and ownership in any product should not be a pre-requisite to be treated with a base level of respect and honesty. The decision to acknowledge or obfuscate an issue being raised should not be contingent upon what gear the person owns and how much money they have spent. If I'm alone in this philosophy, that's okay, but that is what I believe and why I pushed back.and how would i know you are a Wadax Studio owner? before i posted i looked at your posts and your member info and did not see you post about that or disclose that. which is your choice. there is no requirement to tell us about your gear. but if you take strong positions then others are going to try and understand why you feel that way. part of that is your system details. i would not have posted what i posted if i knew that.
and for sure, welcome to Wadax. just because i give Wadax more credit for what they do do than you, does not make me right and you wrong. we just disagree. i think their communications to owners maybe could use some work but am ok with it. maybe after owning Wadax for 3 years i am more tolerant......i can see a new Wadax owner not wanting to give the benefit of the doubt. hopefully your Wadax dealer is working with you regarding your concerns. i assume as strong as you feel about this that you have reached out to him/her.
I don't think I give Wadax any less credit than you do, we simply do it in different ways. I believe Wadax makes such a phenomenal product and occupies such a position in the pantheon of audio that there should be confidence to honestly discuss what needs improving without diminishing the height of its achievements. I would hope this confidence is shared more widely.