This hasn't had a lot of attention since it was implemented in 2016.
The first thing I'm tackling is the problem of changed control numbers. As
mentioned previously we've always included a text description, so now I'm
developing the exact inverse of Data2Text.

If you fancy taking a look the branch is mlearn2

At first I thought I'd be able to piggyback the CLI interface, but this isn't
in fact practical, as the wording there was tweaked towards short unique
minimum text. Also not much of it can handle a single line full setup from top
level right through to (say) addsynth modulator envelope.

Although this is primarily directed at MIDI-learn, later it might be possible
to put something like an OSC wrapper round it, and you'd never need a manual -
you'd just twiddle the control and it will report the exact wording required :)

Although this would now correctly pick up all previously saved .xly files, as
well as any future changes, it can't realistically be backward compatible, as
the number changes were scattered over some time and would be virtually
impossible to identify :(

Once this is complete (for MIDI-learn), I'll look at the selection code.
Currently this is a simple list structure, so every line has to be individually
searched. I've a feeling a map structure would be better, so, for instance
you'd first scan for channel number or NRPN MSB, and then look for this point's
CC/NRPN LSB, and finally implement however many entries there are that match
this exact pairing - bearing in mind you can have any number of controls
independently adjusted by this.
I think the actual display should still look like a list to the user.

Currently I don't have the remotest idea how to do this!

-- 
Will J Godfrey
https://willgodfrey.bandcamp.com/
http://yoshimi.github.io
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-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel

Reply via email to