I've having real problems getting midi support working reliably
between machines and would like to hear some other
input before I log a bug....
it seems to me that if you copy a patch that uses midi to another
computer and connect the exact same midi
controller, the midi support will not work at all until you go back
into the patch, go to the settings for the midi
controller then select the observed sources and select the controller
again....
so this means it's impossible to prepare a composition on one
computer and run it on another without first
editing the composition
and as a further consequence it means midi support doesn't really
work at all when you compile a composition
into a cocoa application... because when you copy that application to
another computer there is no
way to edit the patch to select the observed source without editing
the patch and recompiling the
application on that exact computer....
as a suggested solution we really need to be able to set midi
controller numbers, channels and
observed sources as inputs that can be changed in the patch rather
than in settings that can't be controlled
by the patch.
to test this I used a version of my quartonian vsm application that
has been modifed for midi control,
I set it up for an evolution uc17, got it working fine as a cocoa
app. then i plugged the same controller
into my second computer, which is running the same os and config.
midi support doesn't then work unless
I load the patch and reselect the "observed source" parameter....
seems to me this is really broken, can anyone else confirm this?
