It occurred to me that having a MIDI program change feature was all very nice,
but not a lot of good if the part wasn't enabled! Well now, in the *master*
branch settings, there is the option to automatically enable a part when it
gets a program change.
So far I've tested this under debian on two AMD 64 bit machines. It is a
very simple bit of code and seems to work perfectly on both, but I really would
like people to try this on other combinations. In particular, Intel 32 and
64 bit architectures. If everything seems OK, then this will be the trigger for
V 1.2.1
In the new_midi branch I'm still looking at separating GUI/MIDI/DSP stuff out,
but have realised there is another problem. I can't push all the load/save
stuff into the GUI as I originally thought - that would fail if someone was
running Yoshi headless! So I think I now need to have some form of intermediate
interchange level.
In discussions at the LAC a bit of a question mark was raised over ALSA
MIDI support. A lot of people seem to be giving this up and relying on bridges
like a2jmidi for legacy software and hardware inputs. Jack MIDI is already
synchronous so should be jitter-free whereas ALSA MIDI runs on a 'best
effort' basis. Added to which Jack is available for OS X and Windows so
concentrating on this could make a possible port to other platforms more
attractive - not to me I hasten to add!
Depending on how things work out, I'm now rather tempted to leave the ALSA
stuff exactly as it is (provided it doesn't actually get in the way) and
concentrate on Jack. What are peoples thoughts? Is anyone actually routing MIDI
via ALSA?
--
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.