Devialet Chat

Full Version: Dual Mono users - Advice to create new configurations from scratch
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
There have been some recent posts on this forum that have advised that it is now Devialet's advice that Dual Mono users who wish to make changes to their configuration should create a new configuration from scratch, rather than modify an existing configuration you have saved on the Devialet website.

The question is, were you aware of this advice prior to these recent posts?  

To make the poll clear, I suggest that you vote per whether or not you knew to create new configurations from scratch, as of the 1st May 2020.

This might be stating the obvious, but voting in this poll should be restricted to Dual Mono users only.
NOTE: As far as I know, create a new configuration from scratch is not always required, but in some situations only.
I have tried twice now to make a minor change to the config and both times it resulted in changes in other parts of the config that I did not touch (tested by doing a filediff).

My guess is that upon edit, certain parts of the config default back to ... something. Perhaps with a lot of trial and error, it would be possible to discern what those are so that you'd now to always update that section of the config upon each re-edit. But I'm not sure it's consistent and it sure seems like that ought to be Devialet's job to figure it out and fix it. What's most surprising is that I'd have to think it drives them equally crazy. Unless they have better tools to do so.
Thanks to those who have voted. There are hardly enough votes at this stage to be considered statistically significant, but the votes so far do suggest what I suspected, that most of us were not aware of Devialet's "Configurations from scratch" recommendation.

One thing intrigues me though. So far five people have voted that that they did know of this requirement before May this year. Can I ask how you actually knew this? Maybe from reading this forum, maybe something else? I am genuinely interested to know.
I voted "no", because I haven't had any advice from Devialet about this (despite having used the configurator a couple of times quite recently). The only advice I've seen about not re-using dual-mono configurations has been in the form of accumulated knowledge on this forum, for which I'm very grateful.
I've made a mistake on my vote (voted yes instead of No - but I had Configuration issues and worked this out the hard way), and my confirm that any change on a Dual-mono configuration implies to make a new configurator, I've learned it by myself while seeing that a simple modification of the configurator could generate problems of desynchronization between Master and Companion for example.
It's a tricky question. I doubt Devialet has ever proactively advised dual-mono owners to avoid editing an existing configuration, but it's probably not wrong that most dual-mono owners now know to do so -- learning by trial and error, or here on DC or after submitting a ticket to Devialet or perhaps from a dealer.

What I'm not clear on is whether this problem has always existed or if it somehow cropped up in the last year.
What is the purpose of this survey?
daniel.avasilichioaei Wrote:What is the purpose of this survey?

The inspiration to start this poll came from an earlier post on the forum where someone stated they had received the following response from Devialet support:

since it is not a problem on single box configs and that most users that own dual monos understand the need to start a complete new config,  fixing this is not currently on their list.

When I read the above, my thoughts were firstly that I did not know the advice  that dual mono users need to start a complete new config, and secondly, if Devialet never communicate anything, how was anyone supposed to know this?  To be honest, I also thought how hard can it be to fix the bug in the configurator?  After all, it is not the most complex piece of software on the planet.

Poor communication from Devialet has been a common theme on this forum from the very start, but what we have here is a clear situation where there is a bug in Devialet's software, a bug that has the potential to cause a user frustration, and possibly even damage to kit.  It is also a bug where Devialet know a very simple workaround, dual mono users should start a complete new configuration.  However, not only have they failed to resolve the bug (which would be nice), but they have also failed to communicate that they are aware of a simple workaround to dual mono owners.  Personally I hate it when I am trying to do something as simple as update a Configuration and I stumble across bugs and issues.  I bought a Devialet to give me pleasure, not as a device to ruin my precious free time with unnecessary IT challenges and frustrations.

Devialet appear to have a "wall of silence" policy with respect to communication, but here is a clear example where this policy can directly cause problems and frustrations for customers.

So the primary purpose of this poll was to attempt to highlight if owners do actually "understand the need to start a complete new config" or not, and therefore highlight this issue itself.

Of course, I have no idea if the statement from Devialet support represents Devialet's official position on this matter, or if this was just a frustrated worker in Devialet support being creative.  Not that it matters much, Devialet's management are ultimately responsible for the training and performance of their support staff. 

In another thread, we have also recently leaned that Devialet have a "Voice of Customers" list, that is subject to management review.  So the purpose of the poll was to see if the result would back up my suspicions that most dual mono users were not aware of this workaround, and therefore have a solid case to request that this is added to the "Voice of Customers" list.

So far the results do back up this case, although I would say the number of the votes is rather too low to reach a solid conclusion.

Is this a complete waste of time?  Maybe, I am sure some people would take a view on this.  For me, it only took 10 minutes to set up the poll, and I am happy to keep chipping away at the communication issue, maybe one day it will afford some benefit.  (or maybe not)
Ok I understand. But what is the purpose of the "1st of May 2020"? What is so special about this date?
Devialet is just as good or bad, regardless of whether a user found out about the configuration from scratch before or after 1st of May 2020.
For example, I voted "Yes" because I knew long before that date. But, honestly, I have no idea where I found out (if I read here in the forum, if Devialet ever told me or if I deduced myself)...
Pages: 1 2