Devialet Chat

Full Version: New configurator backward compatibility
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Hi 
I wonder if  New configurator  can support old devialet firmware 
Basicly I am asking if officially the new  configurator has backward compatibility with 7.x firmware
Good question. Because they haven't provided an alternative Configurator to the best of my knowledge then it blooming well should be backward compatible! I don't think anyone's been having issues with 7.1,1/7.1.3 with the current Configurator? (Or Le Configurateur as it now appears to be universally called).
I can not understand why Devialet didnt give the user option to choose
If user select firmware 7.x all new options needs to be disable automatically so the user will not need any interaction or questions .
same as the option that was before for old DP .
For me it looks like Devialet is under huge inverters business pressure .
releasing undebug product ... and far far away from the perfection they asking to present .
looking at the way the config file is structured by [keyword] style sections I would expect a config file created on the new configurator to be backward compatible with any old firmware. [New sections] should either be meaningless to the old firmware and ignored; if not there would be a flood of very serious startup problem complaints, so I'm inferring from the lack of such complaints that it is, indeed, backwards compatible for the reason above.

The greying out then becomes a convenience and customer-interaction topic. it's poor to lead the customer into thinking he has to set an option_x that doesn't exist on his machine, but how does the Configurator know which firmware you have installed ? I'm not sure asking the customer to enter firmware version in the Configurator is a good model either, since there WILL be people who make errors.... probably best to do what they have done: one Configurator fits all.

I agree it's not perfect but they're treading new ground offering this in consumer hi-fi; maybe there's a better way to do this but possibly not with the current system architecture.
I believe the best way would be a real online configurator. That is the Dxxx would appear through a web setup and loads it's current information. From there users can configure on the fly with no need for SD cards and this way the true web configurator will be able to tell which firmware version the Dxxx has and accordingly offer only compatible options.

Could this be implemented let's say via an adhoc Ethernet connection ?


Sent from my iPhone using Tapatalk
(21-May-2015, 08:53)amabrok Wrote: [ -> ]I believe the best way would be a real online configurator. That is the Dxxx would appear through a web setup and loads it's current information. From there users can configure on the fly with no need for SD cards and this way the true web configurator will be able to tell which firmware version the Dxxx has and accordingly offer only compatible options.

Could this be implemented let's say via an adhoc Ethernet connection ?


Sent from my iPhone using Tapatalk

I think that many user-friendly things will happen when Dialog gets compatible with the expert line, at least this is what I heard in Munich about the remote, so I guess the configurator too. Dialog will allow the expert line to be interfaced properly with the web directly.
(21-May-2015, 09:40)philoouu Wrote: [ -> ]
(21-May-2015, 08:53)amabrok Wrote: [ -> ]I believe the best way would be a real online configurator. That is the Dxxx would appear through a web setup and loads it's current information. From there users can configure on the fly with no need for SD cards and this way the true web configurator will be able to tell which firmware version the Dxxx has and accordingly offer only compatible options.

Could this be implemented let's say via an adhoc Ethernet connection ?


Sent from my iPhone using Tapatalk

I think that many user-friendly things will happen when Dialog gets compatible with the expert line, at least this is what I heard in Munich about the remote, so I guess the configurator too. Dialog will allow the expert line to be interfaced properly with the web directly.

I would not appreciate to be forced to purchase an external device to be able to configure my amplifier. I absolutely support amabrok's thoughts on a proper real time configuration tool that omits todays SD card method
(21-May-2015, 08:53)amabrok Wrote: [ -> ]I believe the best way would be a real online configurator. That is the Dxxx would appear through a web setup and loads it's current information. From there users can configure on the fly with no need for SD cards and this way the true web configurator will be able to tell which firmware version the Dxxx has and accordingly offer only compatible options.

Could this be implemented let's say via an adhoc Ethernet connection ?

This would be a much better approach IMHO since apart from compatibility issues it would also resolve concerns about the current configurator becoming unavailable for some reason in future.

I'd still find the ability to save the configuration in plain ASCII format useful, because it would then provide a mechanism for (external) version control of the configurations - to allow back-tracking if you make a mistake or otherwise prefer a previous configuration.

It should be possible to implement this via the existing Ethernet connection.  Mabye there would be a need to bootstrap the configuration to set IP addresses if not using DHCP.

I suppose there might not be enough non-volatile storage on the Devialet to implement the web server and all the pages needed to support a configurator similar to the one we're used to.
One thing I ran into with reverting back to 7.1.1 with a new post 8.0.0 compatible configuration was that SAM configuration was not backwards compatible.  The amp came up with an error message that the SAM configuration was not compatible or something similar.  Now this was on the day of 8.0.0 release, so I can't confirm it is still that way.  I also did not try using 7.1.3 with a new post 8.0.0 compatible configuration, so I can't comment on that setup.  I have since tried 8.0.0 again and have now switched back to 7.1.3 with a pre 8.0.0 configurator.  I was going to do some critical listening of 7.1.3 later today to compare to 8.0.0 which I liked better than 7.1.3 initially.

If it is still the case that a current SAM enabled configuration will not work with pre 8.0.0 firmware (at least with 7.1.1), then SAM must be disabled along with DPM and ???.

Anyone experience this with new SAM (SAM2) going back to 7.1.1 or 7.1.3 ? 

Kerry 
Pages: 1 2 3