Tone control

[krass]

snip...... As someone wisely asked, "why isn't this just via wifi?" But it has that old world charm...love it......

I think it's not via wifi because the configuration items include items that are setup post boot (and are not hot-swappable, such as changing input/output functions at the hardware (socket interface) etc). If the configurator were only used for things like tone settings, then it would surely have been possible to build an architecture that allowed update of these parameters via (say) wifi. 

Because the Dev Configurator is much more invasive in its configuration possibilities, including the WIFI configuration, then you could not use the current architecture to reconfigure the unit parameters over wifi (except if the Wifi config was separated from the remainder of the configuration process and decoupled from the post-boot reading of the config table). Even if they had done it this way, it would have led to a 2-stage post-boot architecture which would have been a mess.

It seems a fairly logical and safe approach, necessary because of the unique ability that the Dev allows reconfiguration of very fundamental items right down at the level of the hardware/software interface. It also ensures that the user is not dependent on wifi to configure the unit !!!! (which could be unavailable for any number of reasons). 

I appreciate this approach for the reasons mentioned above.....
ymmv of course !
mike