Page 1 of 1

MIDI I/O routing is confusing me.

Posted: Sun Sep 06, 2015 2:04 am
by Fuzel
Hi, all. Here's the setup....

Image

I want my Moog V to recieve MIDI from both the Arp and CCstepper simultaneously. The Arp provides note data while the CCstepper provides CC data to modulate the cutoff/res etc. The Moog's MIDI From menu only allows you to select one input.....

Image

....but perhaps I can get the Arp and CCstepper tracks to reroute their MIDI directly to the Moog instead? Apparently not. Despite the Arp and CCstepper being MIDI-only I have no menu option for MIDI To only Audio To .

My solution was to create an additional pair of MIDI tracks and set them up like this....

Image

....which seems terribly wasteful.

Why can't I just route MIDI directly from the Arp and CCstepper tracks? Why is their no MIDI To option for them, after all they produce only MIDI and no sound?

Thanks for any advice.

Re: MIDI I/O routing is confusing me.

Posted: Sun Sep 06, 2015 11:33 am
by broc
The reason is that the VST standard has only 2 types of plugins, instrument (midi>audio) and audio effect (audio>audio), but no midi effect (midi>midi).
Instead a midi effect is implemented as *instrument* with additional midi output (even if it doesn't produce audio), and thus on Live tracks such plugins are loaded as instruments with audio output.

So in your case, there is no simpler solution.

Re: MIDI I/O routing is confusing me.

Posted: Sun Sep 06, 2015 1:12 pm
by Angstrom
Yes. That's the issue.
As some possible alternative It may be possible to create a midi routing matrix device in M4L but any such devices I've seen have incurred monstrous latency for some reason. I guess some hidden flaw exists which prevents the API implementing this correctly. For Example: in that new M4L pitchshifting pack there's a midi router which is as sluggish as a drugged slug.
Well, If you want to stagger into the dark and mysterious world of M4L/API limitations, you are a braver man than me. The discoverability is poor. You'd need to already know it back to front to know if it could achieve what you want.



So, I suggest that you accept the native implementation. Just think of these midi router tracks of yours as matrix rows and simply group them named as "routing" and fold them up and put them at the furthest right of your track list, and forget about them.

Re: MIDI I/O routing is confusing me.

Posted: Tue Sep 08, 2015 8:40 pm
by Wlkwes
Hello,

I am facing a similar problem, quite simpler though.

I would like to use ccstepper to modulate a parameter of an native effect of Live, like the freq of a filter,
but I cannot see how to do that. I mean I read the Live manual but yet, it's very obscure to me.

Could you please telle me how do you use ccstepper with your Moog?

Best regards,

Edit: A small precision, It seems I can route ccstepper to another plugin, like a VSTi that has midilearn and that works,
I just can't figure how to use ccstepper with native live effects.