24 Apr
2008
24 Apr
'08
5:37 a.m.
Hi there,
I am currently using the excellent whysynth with ghostess. Does
anyone know of a way I can assign different midi controllers to
different parameters for real-time editing? I am also trying to
work out the most efficient way to do a keyboard-split? I guess
running 2 instances of ghostess might be the best.
James
24 Apr
24 Apr
3:13 p.m.
On Thu, Apr 24, 2008 at 08:37:17AM +0100, James Stone wrote:
Hi there,
I am currently using the excellent whysynth with ghostess. Does
anyone know of a way I can assign different midi controllers to
different parameters for real-time editing? I am also trying to
work out the most efficient way to do a keyboard-split? I guess
running 2 instances of ghostess might be the best.
jack-dssi-host uses OSC to communicate between the GUI and the synth. I assume Ghostess
does too.
I wrote a custom Python script, using the "alsaseq" class, to translate MIDI
CC's to OSC in order to control NekoString via my MIDI controller.
I have been wanting to do the same for WhySynth but I haven't made the time to hack it
up yet. There's a lot of knobs and buttons on WhySynth-- more than I have available on
my controller! The hard part will be deciding which ones to map, and that's what's
been stalling the project.
I happen to like Python, but I suppose one could use PD and the mrpeach OSC externals to
do this too, or actually any language that has ALSA or JACK MIDI and OSC/liblo bindings.
-ken
3:34 p.m.
2008/4/24 Ken Restivo <ken(a)restivo.org>rg>:
jack-dssi-host uses OSC to communicate between the
GUI and the synth. I assume Ghostess does too.
Yes, if a DSSI host supports GUIs, then it also supports full control
of all the plugin parameters via OSC. That's part of the point of the
DSSI GUI protocol (to make everything remotely automatable).
Chris
25 Apr
25 Apr
12:16 p.m.
On Thu, Apr 24, 2008 at 6:14 PM, Ken Restivo <ken(a)restivo.org> wrote:
On Thu, Apr 24, 2008 at 08:37:17AM +0100, James Stone wrote:
Would you be able to share the python script? I am half-tempted to
work it up into a GUI for editing assignments in realtime..
James
Hi there,
I am currently using the excellent whysynth with ghostess. Does
anyone know of a way I can assign different midi controllers to
different parameters for real-time editing? I am also trying to
work out the most efficient way to do a keyboard-split? I guess
running 2 instances of ghostess might be the best.
jack-dssi-host uses OSC to communicate between the GUI and the synth. I assume Ghostess
does too.
I wrote a custom Python script, using the "alsaseq" class, to translate MIDI
CC's to OSC in order to control NekoString via my MIDI controller.
24 Apr
24 Apr
5:58 p.m.
Hi James,
On Apr 24, 2008, at 12:37 AM, James Stone wrote:
I am currently using the excellent whysynth with
ghostess. Does
anyone know of a way I can assign different midi controllers to
different parameters for real-time editing? I am also trying to
work out the most efficient way to do a keyboard-split? I guess
running 2 instances of ghostess might be the best.
Unfortunately, DSSI does not (yet) feature run-time assignable
controller assignments.
In addition to the OSC option others have offered, you can
hack the code to set up your desired controller assignments.
Look in src/dssp_synth.c for the function y_get_midi_controller(),
and you can see how Garett Shulman set up his. Tweak,
recompile, and you're off and running with fixed assignments,
at least.
For the keyboard split thing, take a look at some of the suggestions
mentioned in the 'Lightwheight midi transformer" thread here
recently (the misspelling is from the original post). Use one of
the MIDI processors to split your MIDI stream, then pipe that to
two synths. If your processor can do channel shifting, you could
use just one instance of ghostess hosting multiple synth plugin
instances.
HTH,
-Sean
6057
days inactive
6058
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Chris Cannam -
James Stone -
Ken Restivo -
Sean Bolton