Well, it seems I still have a roof over my head :)
Had a bit of fun with SubSynth this evening. One CC midi linked to 4
even-order harmonics and another linked to 3 odd-order ones. These harmonics are
per note but it was still fun being able to have consecutive notes sounding
quite different.
However, this highlights a problem.
An 'ordinary' midi-learn can only link to 119 controls (and that's if you allow
sitting on standard ones), but with the grouping capability we can have far more
than that... per channel! So this raises two problems.
What is a practical number?
How do we handle the Gui?
In my test program over 500 lines were scanned in a few microseconds, but would
anyone really want that many? I really have no idea. Has anyone here used
midi-learn much?
Trying to update the Gui when making changes to such a large number becomes a
issue. You would end up with a massively long scroll in the window, which might
be quite slow to update and would suck up quite a bit of memory.
For this I'm inclined to go for 'viewing groups' of (say) 128 lines. This
gives the user a much more reasonable scroll length. The group numbers could be
automatically generated depending on how many lines there actually are. Also,
changing either the CC or channel number will change the position of the line
in the list, quite possibly a long way. Having groups means we can
automatically display the one the line is in.
There's a little bit more done to the Gui in the current master - still not
linked up though.
Finally, I could really do with some comments here guys. This is a long overdue
biggie and I *absolutely* want to get it right.
--
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:
http://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