Avoiding MIDI loops / setup with kenton MERGER & THRU boxes


#21

Glad this helped you.

Though you may consider an iConnectivity MIO MIDI interface in the future.

I sold most of my merge / thru boxes since I have 2 MIO’s. They’re really great and powerful MIDI devices, adding a lot more flexible routing and les cabling compared to using Kenton boxes or others.

I’m very happy with them, and their support is great too…


#22

I agree about iConnectivity, they are a great company. Great products, top support, really nice people who will bend over backwards to make the customer happy and genuinely too (well that is the impression I got when dealt with them). You forgot to mention, excellent USB MIDI connectivity.

BUT, I won’t be selling my other routers anytime soon, I like to change things quickly without needing a computer. I tend to attend to my MIO like a hardware firewall; set and forget until something new pops up and needs rules added for it.


#23

" midi input channel " also on my wish list by now :slight_smile:


#24

Has someone used the new " anti echo / Auto midi A or B " ?

Live mode / recording :
Somehow discovered last night and had suddenly much better results ( less midi looping ) since switched on to " anti echo / midi B " .
Not sure why still sometime some notes can pass thru and creating annoying loops ( keep recording midis ) but the new options are far more efficient even still on record mode !

Paq


#25

let me explain my current config, it might help some people strugling with midi loops and thru boxes:

Currently using 2 chains of 2x Emagic AMT8/Unitor (= 2x2x8 midi I/O = 32 midi I/O in total). These are midi interfaces, but can also function as midi patchbays, with some limitations. I use them mainly as patchbay.

All are configured so that every input sends to all outs, except its own.
with some exception for some input devices (midikeyboards and such) and the pyramid itself. it’s quite a complicated puzzle sometimes, so I document and plan in an Excel spreadsheet
one pair of ins and outs for each chain goes to the pyramid, the ins first into a midi switch (philip rees). Not a merger, because with the switch I can easily stop the pyramid from recording whatever someone else in the studio is playing live on the synths without having to dive into the pyramids menu

the pyramid is set to “anti echo” => “on”, so that the input does not go to the outputs (as my Emagic chain is handling that). With other sequencers (alesis mmt8 for instance) this would be called “midi echo” = “off”
currently very happy with this setup, as its more flexible.
also see this topic:
http://squarp.community/t/rename-anti-echo-to-midi-echo/1272

only downside i guess is i can not play synths from “chain 1” with keyboards from “chain 2”, and vice versa, but it would become complicated with the channel overlap anyway. I could do it if I change the pyramid “anti echo” config with one of the auto settings, but just thinking about the repercussions makes my head hurt

still have some other gear I would like to add, e.g. Atari with some synth editor software on it… but in the past I had midi loop issues with that so I’ll wait untill this current config is considered “stable” on its own.


#26

Does someone know why we still get sometimes midi loops annoying returns ?


#27

Set midi echo off by default and you’ll never get midi loops…


#28

Hi , it’s even worse because it keeps re recording the sequence .
I Have especially issue now with Roland SH01 …

I must admit I have all roland Clans input and output attached into Squarp


#29

I take it by “Clans” you mean all your Roland gear. And if they are all set to THRU then you that’d be why you are still getting a loop. You may need to get a splitter if you are chaining MIDI to get it to all of your instruments and then only have the one you wish to record from going back into the Pyramid.

If you are running more than two MIDI instruments off your sequencer and then send any of them back into it, it’s a good idea to draw a MIDI flowchart to visually analyse your set up. It really does help with pinpointing issues and acts as a reference for what’s going where when you are setting up sequence track MIDI channels.


#30

Yeah . Got connected all Roland aira and boutique .
As we know the Roland boutique as pretty delicate sometimes to make it work especially using several midi merge and thru boxes .
Roland JP08 made tons of trouble and as well Sh01a .
I took those two and connected them via USB to midi ( thanks to midi patch bay OS X ) .
And seems to work finally much better .

Someone can share similar issue with those two combined with those midi merger boxes ?

Thanks
P.


#31

As much as Roland squander their MIDI legacy with crappy implementation, there shouldn’t be an issue with using them before or after any powered merger or splitter.