On Sat, Oct 12, 2013 at 1:24 PM, Jery Paterson <[email protected]>wrote:
> > >> 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. > > > It's an older laptop, but I'll go back an try again. > > >> 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. > > > > I take a crack at that. I was thinking that it would be a good idea to be > able to control through the mixer, but I can see that doing it in the > timeline would work. > > One thing I was thinking was one could use the persistence in the mixer > settings to persist settings in plugins that weren't managed by NSM.... > > Ahh. I think I see where you were going with it now. You basically wanted to use Non Mixer as a control surface for ZynAddSubFX's internal mixer (one which can accept CV and OSC automation). Well, I've thought about that use case as well and **have actually done some work on a project like that (tentatively called non-control-surface). Tricky stuff. Eventually this is all going to come together better--ZynAddSubFX is in the midst of being OSCified. For this particular case though, I think it would be much more useful to have the separate outputs per part in ZynAddSubFX and treat them just like any other audio signal to be mixed.
