On Thu, Jan 6, 2011 at 5:31 AM, Sascha Schneider <ungleichklang@email-addr-hiddenwrote:
> 2011/1/6 Jeremy <jeremybubs@email-addr-hidden>:
> > Okay, looking at the sources a little more, it seems like all we need to
> > port is the minicomputerCPU component. The editor can just be used to
> > communicate to the plugin using the lv2ExternalUI extension.
> > Jeremy
>
> Not all, .. minicomputer is actually 8 synths on 8 different
> midichannels all playing one sound monophonic.
> as LV2 we only need one synth that is polyphonic.
> Need to ad Midi-Mapping, cause the controllers are hardcoded in the engine.
>
> regards, saschas
>
So wait, I'm a little confused by this. Are you saying that the engine is
composed of 8 copies of the same synth, each being monophonic, but allowing
you to do polyphony if you redirect the notes to different channels each (so
each monophonic synth plays a different note)?
If you want to make something like that polyphonic that would be very easy.
You'd just set up a queue of open synth engines. You could even set the
polyphony by an option that you could adjust (at the expense of memory).
So if you're worried about that, don't be worried. Since it is a Jack app,
it's already largely in the format we need, you just need to add some
metadata, and switch around the way it handles MIDI and OSC (well, that's
the time-consuming part). As for the GUI, I think since it uses OSC, you
could just add some metadata and it would work as a LV2ExternalUI (well,
very minor source code modifications would be necessary). However, if
you're interested in designing a new GUI, that would be possible too.
Jeremy
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Received on Thu Jan 6 16:15:02 2011
This archive was generated by hypermail 2.1.8 : Thu Jan 06 2011 - 16:15:02 EET