19-Jun-2018, 08:43
(This post was last modified: 19-Jun-2018, 08:59 by Hifi_swlon.)
If the D hardware were staying the same then I don’t think anyone would expect the SD card situ to change - that would be very difficult. But it’s the CI board that controls all this stuff, and since it was designed in 2017 it should be straightforward. All the settings would stay in some kind of non volatile memory on the board and the board would initialise any reboots (it that’s still required - it may just be a requirement of the old cpu board). The SD card would be a way to keep things working through the transition, for loading the main firmware updates (at least the big one that switches the system to ‘over the air updates’) and as a fail safe.
Presumably D would have thought all this through before even embarking on the design of the CI. Then any changes required to the rest of the D hardware to make this work would have been made - and they did say they made changes and the CI isn’t compatible with non pro experts, so you’d hope they’d made these kinds of changes.
All this stuff is probably much easier for them than using an online configurator and SD cards in this day and age. It’s one system to code/support instead of several. It’s also much better for the user.
But of course only Devialet know what they intended and since they don’t really say what they’re doing or document anything it’s hard to tell. Let’s hope this is the one time where they really surprise us with how far ahead they thought, and how determined they are to bring the CI software and front end config to the same level of technical excellence as the hardware itself.
My day to day config of any other technical devices at home or work are pretty much controlled by some form of web gui or settings accessible over the internet (or local net if you like). Chrome audios, network switches, raspberry pis, router, you name it - when’s the last time you had to write a config file to an SD card using a separate computer and then load it to the device and reboot?
Presumably D would have thought all this through before even embarking on the design of the CI. Then any changes required to the rest of the D hardware to make this work would have been made - and they did say they made changes and the CI isn’t compatible with non pro experts, so you’d hope they’d made these kinds of changes.
All this stuff is probably much easier for them than using an online configurator and SD cards in this day and age. It’s one system to code/support instead of several. It’s also much better for the user.
But of course only Devialet know what they intended and since they don’t really say what they’re doing or document anything it’s hard to tell. Let’s hope this is the one time where they really surprise us with how far ahead they thought, and how determined they are to bring the CI software and front end config to the same level of technical excellence as the hardware itself.
My day to day config of any other technical devices at home or work are pretty much controlled by some form of web gui or settings accessible over the internet (or local net if you like). Chrome audios, network switches, raspberry pis, router, you name it - when’s the last time you had to write a config file to an SD card using a separate computer and then load it to the device and reboot?
>>> 1st Place Award: Devialet, last decades most disappointing technology purchase. <<<
