On Wednesday, March 02, 2011, Don Garb wrote:
> MIDI Start (Transport) and MIDI Stop (Transport).
I have no idea if we support these or not, but if they're not working, it
probably means we don't. I'm afraid I can only speculate wildly here, because
I know practically nothing about anything in the "how MIDI guts work" area.
> Also, when I go to manage Synth Plugins, RG knows that I have Hexter
> installed and I can select it, but it's not aware of my other soft
> synths like Horgand, Bristol, mx44, Qsynth, and ZynAddSubfx. How do I
> let RG know that I have those installed?
Hexter is a DSSI synth plugin, the others on that list that I recognize are
free-standing, independent applications.
The way to use ZynAddSubFX, for example, is to start it up, and then go to
Studio -> Manage MIDI Devices. From there you can either connect something
that already exists in the "MIDI Playback" column to the "ZynAddSubFX (write)"
port in the "MIDI outputs" column, or you can create something new on the left
and connect that instead. Then assign tracks to play through the instrument
that's connected to ZynAddSubFX, and there you go.
If any of these things (eg. QSynth) happen to support controllers or program
changes (ZynAddSubFX doesn't support program changes, and any controller
support it might have is limited to non-existent), you can define them in the
studio for use elsewhere (instrument parameters box, and the control rulers in
the matrix and notation editors).
> And lastly, I can define the rotary controls on my Korg using the Midi
> Playback Controllers dialog, but how do I route those values into my
> soft synth plugins? Thank you very much for your help!
For synth plugins (as opposed to free-standing external applications) it turns
out that you just can't. Synth plugin instruments have the instrument
parameters of audio instruments, which means there are no controllers in the
studio to define, and there's no way to inform Rosegarden of what controllers
a particular plugin might be capable of understanding. I tested that
FluidSynth-DSSI can understand pitch bend messages (at a minimum) but the only
way to get them into a part is to develop the part on a track that's playing
through something other than a synth plugin instrument.
It's a gaping functionality hole. On the other hand, nobody has called this
to our attention since April of 2004, so there clearly isn't much demand for a
D. Michael McIntyre