FR: Event Input Module (On Global Level)

[LYTZ]

Hey all,

just some food for thought...

Checked back on Mulab, tried to sequence into it from an external
modular sequencer... Couldnt...
(Clarification: With that I mean I would need to get multiple/different midi sequences
from different ports connected to different targets in mulab at the same time .
Basically like multichannel audio recording, but in this case just with midi. )

So I came up with the idea of an Event Input Module.

Heres why:
I'd really like to see a Event Input Module on a Global Level, so that
external midi inputs form different ports/sources can be hardwired to specific
racks/synths/whatever in Mulab.

This would allow us to drive Mulab with external stuff like in my case (modular step-) sequencers.
Which is what I wanted to do. But realized now I cant...

Just the same thing like the audio input module. But for midi ports in that case.
Should be easy stuff actually.

Maybe worth a consideration.

Best,

tL.

(PS: Also it's highly unusual that you can't select various input ports per track by default.
Is there a specific reason for this?)

[pljones]

Currently MuLab supports 16 MIDI channels, merging all your (up to) 16 MIDI input ports. It allows you to "hard-wire" at channel level (see Project -> Edit MIDI Input Channel Targets).

Adding port-level support is something that's been a FR for a long time and, as such, I guess "Should be easy stuff actually." can be assumed to be a wrong statement...

There's a lot more powerful stuff I'd like to see to extend MIDI/event processing, such as ungluing sequences from the composer at the top level of MuLab (similar to MuZys) and thus allowing them to be treated as something an event can trigger, loop, etc. Having the event input module available at top level also helps with doing more magic things.

[LYTZ]

Adding port-level support is something that's been a FR for a long time and, as such, I guess "Should be easy stuff actually." can be assumed to be a wrong statement...

Lol, okay I see... Just thought it was an easy thing because its usually very common.

There's a lot more powerful stuff I'd like to see to extend MIDI/event processing (...)
Having the event input module available at top level also helps with doing more magic things.

Indeed. That would open a lot of useful possibilities. So we would both be happy then it seems...


Best,

tL.

[nenneb]

Maybe it helps using a MIDI-merge-box (Kenton, PocketMerge, MidiSolutions ...) to route your different ports to one line you can handle within MuLab. Only adjust your modules to different channels.

[pljones]

@nenneb, MuLab can happily merge multiple MIDI Ins all by itself without needing additional hardware. What LYTZ is after is retaining the 16 channels on each port and knowing which port each event came from. For example, a hardware sequencer might use all 16 channels and a three-manual organ might use three channels: you don't want to merge these, you want to keep the ports separate, targeting the first port to one device (a MuX, maybe, that splits by channel and then triggers different subsequent processing per channel) and the second to another (e.g. an Organ VST that understands the channels).

[LYTZ]

What LYTZ is after is retaining the 16 channels on each port and knowing which port each event came from. For example, a hardware sequencer might use all 16 channels and a three-manual organ might use three channels: you don't want to merge these, you want to keep the ports separate, targeting the first port to one device (a MuX, maybe, that splits by channel and then triggers different subsequent processing per channel) and the second to another

Exactly. Different ports is the magic word here. Not channels...
Midimerger is a good idea, but wouldnt work in most cases when you have different sources.



Best,
tL.



(On a side note: I tried Jack Router yesterday. Usually it could do such stuff,
but unfortunately it doesnt work anymore.
Probably because of my OSX Version or something.
Maybe one of you guys want to give it a shot: http://jackaudio.org/
Its pretty old code but you can route audio and midi cross application between
the Jack Insert-vst in *both* directions without latency...
Its basically an Audio/Midi Server Application. It can also capture or hijack system-midi
and system-audio (as defined in the Audio/Midi Setup on OSX) and route them to the Jack Vst.
Shame it doesnt work for me anymore... )