(03-19-2019, 07:25 PM)madmaxmiller Wrote: 0) make a backup of the original
I mentioned it in my main topic on the matter in the general section. But then the original is always available by re-installing
If you meant the 'original' in the sense of the user's definitions then yes, those definitions must certainly be preserved and these can be extracted by making a diff, and a diff uses tgwo files, one of them being an 'original'.
This being said, it's a bit rather ironic. The steps I have sketched here and in the general section can all be done automatically during installation. Heck, since the user never gets to modify this file directly, what's written in there is 200% known by the developers. And what can be done with a text file that's known very well ? The fiercest and most aggressive sed scripts can be launched upon it, extracting the user's definitions, changing their syntax (if the syntax has changed in the latest release) and putting then back in the new file that's installed with the new version. The installation itself can output to the console and in a text file for posterity a user-comprehensive list of anything that was done that could interest the user.
For instance, I certainly like way better toggling the mixbusses and VCAs using a single finger on a single key, which means I like my original 'b' and 'v' shortcuts for doing so. I don't like the new 'B' and 'V" since I have to use two hands or with one hand have to spend some time stretching and spotting the key whole holding the shift key.
After property taxes and entangled audio cables, it is the most annoying thing.
So in this case Mixbus install would keep mine and not try to impose the new ones. The installation script would see that the for that action the user has already defined a key, so let's keep the user's key.