midi in out event flow

[drakh]

I am working on some scripts which should work as adapters for launchpad, for my APC mini addons.

what i decides, instead of rewriting those addons, i am writing patches/scripts which should be prepended or appended to that patches so i don't need to rewrite the addons for apc, and use it just by simple chain of patches in rack.

but...

i expect that midi signal flow goes from up to down.

like in this example rack.

http://sensomusic.com/forums/uploads.ph ... utils.rack

and what happes when i go to the launchpad midi output device when i monitor what is happening there, is that it accumulates midi signals in paralel way. so the output device recieves singnals from both patches in the rack simultaneously. what is somehow for me surprising and disappointing. is that correct behavior?

[sephult]

I have seen odd combining and parallel routing that I was quite confused about as well.

I was always under the impression that all signals are sequential.

It does seem however as example: If you have a patch send midi to a plugin...even if in the plugin patch the MIDI looks terminated at the plugin, The MIDI still flows to the output Device.

I would think that yes, a logical top-down flow would be the best option, and should be terminated if a patch a MIDI Input is not wired to a MIDI output.


I am still confused to as well about the functioning of separate MIDI outputs coming from a patch.
They generally seem to merge on the patch output, rather than becoming parallel MIDI1, MIDI2, etc..

I have a Traktor F1 controller I just built that includes a nifty sequencer, problem is that I need to prevent controllers from affecting plugins.
For my case I had to MIDI bus the sequencer and create a secondary patch for an additional rack.

I am just getting ready to do an APC20, Traktor X1 mkII, and Traktor S4 controller companion as well, it would be nice if this would work so a separate MIDI output could provide the controller feedback, while feeding only a plugin in-line.

This makes me wonder on the behaviour with multiple MIDI output Devices, quite possibly they need to be similar to how the surround audio output is....with the ability to send MIDI1 to Device1, MIDI2 to Device2, and so on...

-Sephult

[drakh]

oh, i see. nevermind, it is possible to solve my problem in different way.

for your problem, what about sending signals to midi buses and then have separate racks for each controller, in which will be just simple patch listening for the midi bus for your device?

and yeah i know traktor software has it very nice solved with multiple midi interfaces.

[sephult]

Hi drakh,

"for your problem, what about sending signals to midi buses and then have separate racks for each controller, in which will be just simple patch listening for the midi bus for your device?"

That is what I had done with my Traktor F1 companion controller, I had to send to a bus and receive by ID elsewhere to send my sequencer.



"oh, i see. nevermind, it is possible to solve my problem in different way."


So what solution you looking at for correcting your problem?

(By the way, I think the Forum QUOTE is broken, I had to reply by color and manual quotes.....hmm).

-S

[drakh]

As you can see in my example rack which i linked, i wanted to solve it in a way that i will have thi spatches in rack, visible. Now i wrapped them in a patch as subpatches, which are prepending and appending another patches. It is not necesserilly problem. it is just a little bit annoying to maintain it this way - when doing updates to those patches - which i am now forced to use as subpatches. you can see that solution in arGRID, or PUSH Keyboard, which i uploaded recently.