Now the dust has settled...
First off, I've realised there is a nasty little Gotcha associated with all
effects except EQ.
Usually people select one of the presets, and often stick with that in which
case there is no problem. However, if you change any of the settings then save
the instrument, next time you load it you will still see the preset name and
may not remember that you've altered it. If you then try other effects and/or
presets you've now lost these settings and re-saving the instrument will make
that loss permanent!
This will apply to all of System, Insertion and Part effects.
What I'm thinking is that when loading either a patchset or an instrument (and
by inference a state too) we check effects against the default values for that
type. For the GUI we can change the colour of the preset name from black to
blue - as that seems to be the colour we use for warnings, and for the CLI we
can add the word 'Edit' to the name. Whenever we select another effect or
preset, that would revert to normal, and whenever we change one of the controls
the warning would be given again.
There will be a time overhead, but that only really matters when loading
instruments on the fly, and as parts can only have 3 effects, it shouldn't be a
problem.
Another gotcha I mentioned at some time applies to addSynth voices, where if
you set (say) voice 4 to use voice 1 waveform, then later (forgetting you'd done
so) enter voice 4 waveform and start to edit it you are actually changing voice
1! This may well not be what you want. Although the word 'Waveform' is indeed
changed to blue in the voice window, there is no such indication in the
waveform window and I don't know how a suitably clear warning could be given
(bearing in mind the CLI would need it too).
One way out of this would be an extra config setting that blocks any attempt to
enter the waveform context in this situation - It would probably need to be off
by default... or should it?
Moving on a bit. Currently there is no way to copy or move a complete part to
another - short of saving it, switching part and re-loading it. It shouldn't be
a major problem implementing that. Is there any interest in doing so?
A user wanted MIDI-learn loading from a command line startup. We are not
currently using 'M' so hopefully it should be possible, and I *think* it can be
stacked with things like patchset and instrument loads (don't know about state
loads). Again, is there any interest in this?
Bank and root CCs.
When these were implemented they were made switchable bank as off, 0, 32
(defaulting to 32) and and root a off or any other unused CC (defaulting to 0).
Personally I've only once had these as root=32 bank=0, but frequently had
root=off. I've never wanted root to be any other value, so for consistency I'm
thinking it should be like bank. i.e. off, 0, 32. Yes? No? meh?
That's about all... for now :)
Anyone else got pet peeves?
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Yoshimi source code is available from either:
https://sourceforge.net/projects/yoshimi
Or: https://github.com/Yoshimi/yoshimi
Our list archive is at: https://www.freelists.org/archive/yoshimi
To post, email to yoshimi@xxxxxxxxxxxxx