On Sat, Oct 12, 2013 at 11:35 AM, Jerry Paterson
<[email protected]>wrote:

> Hello,
>
> Thank-you for your reply.
>
> I was hoping to avoid putting volume changes into the sequencer as I was
> trying to reuse the patterns throughout the composition at various gains.
>

I figured.


>
> I compiled the latest version of ZynAddSubFx, but didn't see separate JACK
> outputs.  I'll go back and check for the experimental branch.
>

I believe the branch is called 'multi-jack'.


> I'll go ahead and try jm2cv as it sounds very useful.  Thank-you for
> pointing that out.
>
> I tried to start non-midi-mapper and it immediately crashed.  I started it
> from NSM and it then it ran.  I'll fire up under GDB and see if I can
> provide a patch.
>

Non-midi-mapper is only meant to work under NSM anyway. Basically all of
the OSC stuff only works under NSM currently (because NSM is used for
client discovery/naming). Eventually it should be possible to use the new
JACK metadata API to exchange this info instead, and then it will be able
to work without NSM.


> A week ago, I had also tried using two instances of ZynAddSubFx, but it
> behaved "twitchy".  Even though the CPU load was low, the sound was
> erratic.  I adjusted parameters in JACK server but did not help.
>

I don't see how that's possible. The two instances shouldn't be able to
interfere with each other.


>
> This morning I thought it might be useful to create a new Strip Module for
> Non-mixer.  Based upon your other modules, I have module that can be
> inserted into a strip signal chain that allows the user to select which
> MIDI channel to emit messages to.  The idea would be that each module would
> have a series of OSC controls that would then emit MIDI messages on what
> ever channel and MIDI CC is desired.   I have to learn how to teach the
> journal to create instances of this module (persistance) and it doesn't
> appear the existing frame work supports creating JACK MIDI output ports.
>  In essence, it guess this module would remove the need to have something
> like jm2cv in the workflow.  Would you be interested in incorporating a
> module like this?
>

Not really, that sounds overcomplicated. It would be easier just to add a
MIDI output mode to the Control Sequence in Non Timeline. That's been on my
TODO list for a long time--it's not that it's difficult--just that it
requires a little GUI to set the channel/CC number. Isn't that what you
really wanted in the first place? I'd happily accept a patch for that.

Reply via email to