On 14/10/10 11:28, alex stone wrote:
[ ... ]
Just a note here. One problem with many apps, both opensource and
commercial is the notion of focus. Another window opening to access,
for example, loading patches on the fly whilst using a currently
loaded patch, may cede control. So if the user opens a new window, he
may find that his much cherished controller actions no longer work. I
know CCcontrollers are supposed to enact a single process, regardless
of which window is visible, if the app allows for specific and direct
controller association with a function or button/slider/etc, but not
all apps do this successfully.
Just a thought to add to the considerations.
I'm not real clear on what you're getting at here - bear in mind my
current combination of muddle headed wombatness plus medication. Can you
elaborate?
Cal, I didn't write that very well so i'll think on it a bit more, and
try and post something more coherent. :)
Yes, Will's fine patches will fit a standard midi bank.
So any bank/patch function you decide on, if fairly midi generic, will
enable us to access them. I would suggest here that you think about
giving the user the choice of assigning bank numbers to a set of
patches. For example i might have 8 banks, Will's being number 6. If i
can assign bank numbers, then i can use something like MSB 1 LSB 6
patch<n> to access the patches.