Advanced MIDI Routing: Configuring and Using the iConnectivity mioXL
HTML-код
- Опубликовано: 9 июл 2024
- Once your studio has expanded beyond a few synthesizers, you need to start considering MIDI routing. Smaller MIDI interfaces don't have enough ports, and many modern synths require their own MIDI connections, as they use all 16 channels themselves.
In this video I talk about the problems with the MIDI configuration of my old studio, how I planned to correct them, and then introduce the iConnectivity mioXL. I talk about the various types of connections, and explain MIDI over RTP. I demonstrate how I hooked up the mioXL and configured it, then go through a tutorial demonstrating how to configure your mioXL, giving some example use cases along the way.
The iConnectivity mioXL on Amazon: amzn.to/3EZjxeF
0:00 Introduction
0:21 MIDI History & Limitations
3:36 The USB Problem
5:44 The iConnectivity mioXL
8:53 mioXL and USB MIDI
12:23 Profiles/Presets
12:58 Configuration Software
14:46 MIDI Routing Configuration
19:53 Preset Configuration
21:55 Filter Configuration
23:19 Remapping Configuration
24:05 RTP Configuration
28:59 USB Host Reservation
30:35 Summary
#MIDI #mioxl #iconnectivity 
Видеоклипы
"A LITTLE bit of delay or latency." I'm actually laughing out loud. I remember MIDI chaining stuff and by the time I got to the end of the chain, I'd be lucky if the synth triggered! Haha.
This video made the setup of my xl so much easier! The little interruption explaining the need for both usb and din midi for synths with custom apps was key. Thanks for your efforts to make this, well done.
Hey Scott - thanks for taking the time to discuss this! I appreciate you leaving out all of the unnecessary information and simply discussing the issues at hand and how this solves all of them. Truly appreciate it and ill make sure to use your affiliate code when I go to buy one : )
My MioXL sat unused for over a year before I finally learned the basics of configuring it!
The MIDI thru connector is a very interesting topic. Dave Smith at Sequential Circuits, who was one of the leaders in the creation of the MIDI protocol, did not like MIDI thru. He introduced it solely so that the Japanese manufacturers like Roland and Yamaha would be satisfied. Sequential Circuits have MIDI Manufacturers ID number 1. That says something about who created MIDI. If you have an iConnectivity mioXL, you never need to use MIDI thru.
Hi Scott - thank you so much for RTP explanation. I use mioXL more then 2 years and never get setup RTP correctly. Now I see - will do and finally will use my iPad as proper controller to my analog friends. Also, USB reservatio is great one. I must say I love mioXL as my routing is done in 2 ways - daw and dawless - both works great. My biggest advise to new users is - PLAN your DIN and DOCUMENT the cables :) This is still my itchy point and must fix it. Thx again
100%. I made a spreadsheet to keep track of all my MIDI and audio connections.
Great video Scott. Thank you kindly. I didn't know the display on the XL was touch sensitive until I watched your review/explanation. Much appreciated.
Great video. Thanks for taking time to make this video. We've added this video to our user video playlist.
Our new tag line for marketing "The mioXL, excels!"
We've watched this video a few times and hear the feedback in the video.
Fun note: If you touch the USB DAW LED on the mioXL twice you'll get a MIDI panic, in case you filter note off like in the video.
That's a great tip, I will definitely use that function!
We need an Ventura compatibility, at least Monterey
@@kevlew.mrlew_mrlewmedia All the iConnectivity interfaces work on Ventura. The Auracle X software is also working with Ventura.
Yeah its way better than the ones on your website those are a joke. I came so close to returning this thing just because of how annoyed i was with the set up
Scott! Sounds like you’re on the payroll now 👏🏼!
Thanks .... Scott, I needed this video!! I'm a drummer that fell in love with synth's and now have over 20.. ouch, old and new but just couldn't wrap my head around the mioXL until watching your video. Thanks-a-synth! 👍
Thanks Scott,
Your video was so informative and enlightening as to what I need in my studio of synths.
Until now I have been using my old school Roland A-880 midi patcher, which has served me well.
However, with today's technology and USB midi etc. I needed something to cover all my midi connections and routing possibilities.
Immediately after watching your video
I purchased the Mio XL.
I'm so excited to get it all up and running and I will be re-watching segments of your video along the way to help with the set-up.
Thank you so much for the excellent content of your video.
Liked and Subscribed.
Cheers
Paul
Great vid - the info from iconnectivity is really lacking for a non-pro - this made much more sense... thanks
I know you posted this while ago but I just got my hands on the XM coming back to hardware from vsts. You’re correct the documentation it’s awful and the dude doing videos killed my patience while presenting setup on windows . It’s like he got his hands dirty even touching it non apple product. Anyways good thing I found your video so I’m moving forward with my setup
Thanks, great in depth video! Got me one step closer to buying something that does not make sound, but WILL make me happy :)
Thanks for the great video. I've now got my MOTU MIDI Express XT on "Offer Up"... Being able to custom name everything just makes things so much easier. 1 more synth, and I will need to add a 2nd Mio XL to my rack. Thanks for taking the time and making this video. We really appreciate it.
Wow Scott! I was considering purchasing a MOTU unit, until i saw the amount of flexibility on the unit that you have in your studio! Definitely going to look into this mapping guru!
Hi Scott, Thank you for the video.
I have 2 Mio XL's connected via RTP to route even more midi synths.
Tip, if you run the latest firmware and you tap the DIN midi on the front panel you can see midi in/out animation with mini notes whenever midi is passing.
I was playing with the idea of making a video of the XL myself but you beat me to it, congrats on the video, great work!!!
And you are right. The RTP can be used to connect multiple XL's, one as initiator the rest as responder.
Yup, you can do the same for RTP MIDI or any of the others, to monitor the data being sent via those interface types. The best one is if you tap twice on the USB DAW LED, it sends a MIDI panic, to fix any stuck notes!
I have just got a 2nd Mio XL but confused about how to use an input on the first one from my Juno X (my master controller connected by DIN Midi to the Mio XL) to control a synth connected on my 2nd Mio XL. Both Mio XLs are connected to my Mac via Network/RTP connection only at present
There has never been a more informative video. Thank you.
Great information Scott, thanks
Extremely needed video. Thanks for being concise and touching on the necessary points!
Great Scott! I really dig your hair! Besides your looks I also like your enthusiasm and topics. Best Regards from Stockholm, Sweden Scandinavia
haha I get so many comments on my hair, I should have grown it out long ago!
Thanks for your kind words!
Great video. Thank you for making this.
Wow! Fantastic video. Well explained.
Fantastic video, so much better than all of the instructions the MIO guys have made. Now I finally understand :) they should hire you😮😅😅😅
Amazing info!!! thank you very much!! 🙂
Wonderfull explanations, thanks !
Your review is so simple! Thank you Scott, keep making great videos
this video is extremely helpful. thank you.
This was tremendously informative. Going to tackle my routing tonight. Thanks!
Hey! That was cool man. ✊🏼
Just got one of these, and I'm just getting into hardware. Thank you for clarifying a lot of things about this device! I really appreciate your work!
This is bomb, thank you so much scott for doing this, lifesaver !
Great video, thx ! 🙂
Great video. It helps me gain clarity. My Mac is set up and working over RTP/Ethernet but I'm also connected to the MPC X via USB. If I'm correct I need to duplicate devices in both lists so they'll both see my hardware. The MPCX will be USB-DAW and the RTP MIDI will show in my computer (ProTools/Ableton etc..). Great tip about using a blank preset for testing too. Thanks Scott!
Thank you so much Scott for this very informative video & helpful video. It really answered all my questions about the mioXL. Thanks again all the best
awesome vid thx for this!
Wow!.....Great video! I'm just the point of my studio where I need better midi management so this video Helps immensely. I'm still running a Yamaha QX1 and a Yamaha MJC8....they might be a "little" out of date lol!
RUclips just recommended me this video. I was struggeling to get my Mio XL working as I envisioned. Partly as you said, the lack of in depth documentation was making more complex setups rather unobvous. Thanks to this video I see where I got some wrong idea's . (I admit I'm a guitar player first, so MIDI isn't always that obvious to me)
note: your second pronounciation is closest to the French 'bonjour' but both are acceptable (especially for native English speakers)
Consider me a new subscriber!
Salut Joris! My Canadian high school French serves me well, I suppose. :) Thanks for the kind words.
@@ScottsSynthStuff are you based in Canada? I'm in Kitchener, ON if so.
@@JayKaufman I grew up there, but live in the US now.
Scott you my friend or a genius and a God send!!! I have two MioXL's that I have been trying to configure for some time. I partially have it working over RTP, but I do not have everything set up as I envisioned when I purchased them. I have an iMac and a custom-built PC, and I want to run them both as separate devices. I want to use either of them as an external instrument/FX bus/DAW. I think what you have shown in this video may get me on the path of accomplishing my dream. If I can do so I will be sure to post and send a video thanking, you and showing how I have it all configured.
I think you could do this - have them both pointed to the mioXL over RTP, they should both be able to operate it. I don't know if they could both open the same MIDI port at the same time (doubtful), but you wouldn't have to re-patch in order to use both.
Pity you don't have an affiliate link directly to the company as I would use it, amazon prices are way above normal price just as an FYI. I will purchase it directly from the company and let them know I'm getting it because of your video.
Thank for help. As you said the documentation is a nightmare, especially for no native English guys like me... but they improve the look of the software, so it seems less confusing.
BEST video and very in depth! thanks Scott! Yougave me the answer, I think, to my question about the wavestate and the mininova connecting thru the iconnect 4+. So if I understand it , I connect thru usb to cpu and then din thru the 4+, correct???? I am now going to see if I can get the RPT working the way you described.... thanks and love your Synth videos!
This was an amazing review!! Thank you for your work on this! It sure looks like the mioXL can handle a VST/External Synth Studio Environment without a sweat.... (i.e. My main use will be recording to DAW using VSTs AND external synths....... but I also want a "Live" Studio environment where I can play VSTS AND Hardware synths from a controller (no DAW). Unless I missed something... this mioXL would "Excel" at doing this without a sweat... (Maybe a little sweat from me trying to getting is all routed and working LOL!!) Thanks Again!!!
Yup, it would do that very well! Also have a look at Camelot Pro, it might be able to do a lot of what you're looking for, at a much cheaper price than hardware.
@@ScottsSynthStuff Thanks I'll do that... Right now (and I'm currently in test mode a piece at a time to make sure things work)
Since my home studio will 90-95% of the time just me with hardware AND VSTs doing my own recordings... I have GigPerformer and this amazing software can handle all the MIDI ins and outs and route VSTs and HW synths between one or multiple controllers...... That's my plan... to use GP as my MIDI Master Mapping Control for each "Song"/"Whatever"......... This mioXL looks to be perfect (and that reduces another piece of software I have to rely on....) That's my thinking?? You sure know WAY more than me!!! I really appreciate the details you provide.... it really helps guide me to my ultimate goal.....!
Hello Scott, great video! Thank you so much for this. This made me realize that with all my hardware synths, the MioXL is exactly what i need to solve all my midi problems. LOL. Also i was wondering, what is the brand of the keyboard stand that you have in the video? Thanks Scott!
They are OnStage stands. Two A-frames and a Z stand with second and third tiers.
I literally just got one of these devices in place of MOTU MIDI Express 128s/XTs. The MOTUs drivers were crapping out repeatedly on Windows 11 Pro and I'd had enough.
I'm excited to get RTP MIDI up and running, but for now I'm going to use it to route my many old school vintage synths into Ableton. Where it's going to get 'interesting' is having to route my USB MIDI devices that aren't class compliant (I may have to break out old school DIN MIDI cables) like my various KORG and Arturia devices, along with using my newly acquired Midronome to run hardware audio sync via Ableton and have everything slave to that. I've had a lot of latency nightmares with my various gear and want everything to hit on the dot when I press play, so that's why I'm going the Midronome route for master sync. ...Now I've just got to figure out a way to make it work properly!
@JayKaufman I have a lot of synths I'm going to be routing everything to/from AND have a MIDRONOME as well.... I, like you want everything to "hit on the dot" like you!! (I just got rid of my MOTUs as well and have the mioXL thanks to Scott and this video)... Would be interested in knowing if you make any progress with the MIDRONOME setup (Mine is still in the box and I'm still doing my Audio and MIDI cabling in the studio and it's going slow..... ) So it will be awhile till I hit the MIDRONOME setup (but anxious!)
@@unclejerrysworld I'm also not there yet. I have a friend who's used the mioXLs and the ERM Multiclock for this purpose - which is similar to the Midronome. I just need to speak to him on how to get it all set up.
He ran an entire live show off of this at the Barbican in London, UK for a well known electronic artist based off of the setup he designed.
@@JayKaufman Thanks for the reply!! Well THAT's reassuring to know!! So it is possible.... :) I understand.... like I mentioned, I'm still routing audio AND keep re-designing my MIDI routing.... (I think I need another mioXL for all the DIN INs and OUTS I need)... Working that out...... I'll gladly let you know what I learn as i get to the MIDRONOME.... from everything I see, the thing is SOLID and handles any and all timing issues thrown at it (which has me pretty excited!!) So we'll see I guess!!! :)
@@unclejerrysworld I'll try to make a mental note of updating you once I've got it figured out, but I've got ADHD so might get distracted by a butterfly or cat videos even though I hate cats. 😄
@@JayKaufman Thank you! I'll do the same...... Believe me.... I'm moving slow.... a bit at a time after work and on weekends.... So it's a slow go for me too and I'm the same!! :) Thanks Jay!!
Great video! What rack do you use for your polyd and mioxl? Looks like what I need.
Thanks, great video again, much appreciate
Thanks! It's a simple OnStage wheeled rack (although I didn't use the wheels): amzn.to/3XqDXE5
Hi Scott, very interesting video - thank you very much! I have a question about connecting multiple devices. You did show the knob to select different presets. Does one device control the other, in that regard, or does the user have to select corresponding or matching presets on each device, to make it work?
Fantastic video and explanation on all the parts Scott, thanks so much! Was having a time trying to figure out the connections between hardware. Do you have any mioXL specific clock sync tips for managing play, stop of multiple hardware outside of a DAW? I'm using Reason 11, two emu command stations, a moog sub 37, and there can only be 1 assigned. No worries if not, I saw your other video on clock sync and it was also helpful! Great channel, great content - thanks much √√
The only issue I have with that is that when my DAW starts playback or recording, it sends a bunch of MIDI transport commands, which caused the early MIDI implementation in my JD-800 lock up the synth. It also caused my System-8 to start playing back its sequencer. By filtering out transport commands in the mioXL for both of these synths, I fixed both of those problems.
Hey Scott. Great info. I was thinking along the same line as Ian in regards to networking. My question is do you have the studio on a sub network behind a different router/firewall or right on your main home network?
I didn't bother segmenting it further. I already have two network segments in my home, so it's on the "private" segment that the computers are on, not the one that all the various lights and other Wi-Fi devices use.
Heya, Scott, found your video. The best explanation of this complex matter I could find. Like you said ... their own videos aren't that great , especially if you are not a tech / comp guy like me. You did a superb job. Very well structured and perfect for people like me. Thank you for taking the time. Just one last Q: why did you setup individual RTP connections / links for all your Hardware connected? Is it because you don't have to route them but they are always connected to your computer / DAW via network? Why now only one RTP connection and route the rest?
Thanks a lot Scott. Greetzz from Amsterdam
Cheers
Riad
Each RTP endpoint is a virtual connection between a virtual MIDI in/out pair and a physical device. You could have a single RTP endpoint and route that to multiple devices, but you would have to have those devices set up on different MIDI channels - and those synths (particularly workstations) that use more than one (or ALL) of the MIDI channels, that wouldn't work.
The entire intention was to have unique, individual MIDI "ports" for each physical device, but without using up all of my USB resources like I had been doing before. Now all the ports are virtual, and get routed over Ethernet to the mioXL, which then distributes them to USB or DIN MIDI as appropriate.
@@ScottsSynthStuff thanks for the explanation. Now I understand. So Mio Xl is a very powerful unit.
Thank you
Sunny greetings
Great Vid. So to clarify, using this device WILL eliminate latency issues? More specifically when recording into a DAW. ie slaving the fantom sequencer?
My last observation I promise 😊 control of synths via usb with the Mioxl doesn't seam to be a runner if you need to use the Synth applications within your daw (patch editing etc.) so I think midi is the only route for control .
If the synth app is communicating over USB and doing so outside of. MIDI, then, you are correct, it will not work through the mioXL which routes only MIDI data.
Many thanks for the walkthrough 😊. I’m getting fed up with the lack of support for my two Emagic 8-port interfaces, saving up for an XL.
You didn’t mention SMPTE/ if the XL will lock to any kind of timecode…-?
Not sure I understand the question. The mioXL will pass through (and optionally filter) MIDI data, it doesn't lock to any timecode, or even care about timecode. If you encode SMTPE into MTC (MIDI time code), it will transfer through just like any other MIDI data, but the mioXL doesn't understand or even care what is in those data frames, it just routes them through to where it's instructed to send them.
Great video. At this moment I'm running two ESI M8UXL Midi interfaces. Both connected to seperate USB ports on my computer. To run both, I installed a driver by ESI to "see" both interfaces as one interface. So I have 16 DIN's in and 16 DIN's out. I don't use any routings at this moment, so, b.e. DIN OUT 1 goes to my Kurzweil IN and Kurzweil OUT goes to DIN IN 1. And All my synths are connected this way. Every synth has his own DIN IN and OUT. But I'm running short. So I was looking for one or more new MIDI interfaces. Especially expandable to my needs. After seeing your video, this is the one I need. Great explanation of all the routing, in and outputs etc. One question. What's the best way to connect one or more MioXL's to an Intel computer. By Ethernet, so just connect it to the same switch my computer is connected to, or use two separate USB ports on my computer, just as the MU8XL's are connected?
Thanks for the great video! I’m wondering about latency. How much latency does the router introduce, and is there much difference between RTP vs USB?
Ethernet is orders of magnitude faster than USB2, which in turn is orders of magnitude faster than 1982-era serial DIN MIDI. So latency is not an issue, I doubt you would be able to even measure it.
Very good, Scott! I´m in love with my Mio10, but i didn´t use RTP at all. Gonna take a closer look now :-)
Great overview of the mioXL, thanks for sharing. BTW, how is the System-8 connected (USB, DIN, or, both)?
Both, because Roland does boneheaded things like making ARP functionality over MIDI work differently depending on whether you're using USB MIDI or DIN MIDI. To my knowledge, only Roland makes their synths work differently depending on which physical MIDI connection you use - so to be able to use the ARP functionality in all the different ways I need, I actually have it connected via both and map it as two different instruments in my DAW. Idiotic on the part of Roland.
@@ScottsSynthStuff Thanks for the insights, much appreciated! I'll have to figure out if I connect the S8 to the MX-1, or, maybe split the USB to do both M-1 & mioXL (if possible).
Hi Scott, thank you for the most informative video! Now a question, how will MIDI RTP handle the midi thru within my DAW? I.e. I have 8 keyboards generally connected as "controllers" for any sound selected in my DAW. Now this track could be Moog One, Voyager, Rev 2 or plugin softwares ... I understand this must be possible but could you clear things out please? I use Studio One.
Hi, nice video! I'm wondering why I don't have the option to filter "start", "stop" and "timing clock" with my midi 4+? Can someone please help me with that? Thank you!
Hi. Thanks for your video, very helpful. During the video you said that Intel CPU's can only do 127 MIDI endpoints while AMD Ryzen can do 1000 etc. Can you please provide a link or somewhere that I can read more about that or confirm that? I assumed the number of MIDI endpoints is a Windows limitation regardless which CPU brand is used. I had a search about it but can't seem to find anything so please let me know. Thanks Scott!
Im trying to remember if an older midi thru box would work for a more current hybrid setup with hardware and computer. Seems like the older midi boxes have a connectivity issue to the computer.
Im looking at some older used MOTU units to try to be cost effective, buf i feel like i remember there being issues with them connecting to the computer.
Basically i have a coulle old rack synths and several newer synths that i run into an older soundcraft mixer which runs into an SSL2+ (with midi in/out) which goes into my laptop. I need a midi thru box to route all the hardware and dont want to daisy chain.
Can i use an old non usb midi box and run that into the midi on the SSL? or do i need to get a newer midi box because of the hybrid setup?
Would love to know how ro approach it.
(Also, RIP Modal)
Hi Scott! Thank you for this video! Could you explain how to link synths from Mio xl to the daw. I am using cubase 12 and I can get the Hydrasynth to work but not the minilogue xd and Korg op-Six. Thank you for you help!
Korg kind of does its own things when it comes to USB, and I was never able to get their class-compliant USB to work with the mioXL. For my Wavestate and opsix, I just used DIN plugs into the mioXL.
@@ScottsSynthStuff Awesome thank you!
Hey Scott, do you know why the mioXL limits the number of USB DAW MIDI Ports to sixteen? I assumed when I purchased it that I would be able to utilize every available port (12 DIN + 10 USB) so I could have each instrument on its own port in my DAW (Live). As it is, I am having to daisy chain several instruments, which is exactly what I was trying to avoid. Thanks for your videos.
What If for instance I want to use more than 1 keyboard to control any of my synths whenever I want. For instance: I have a midi track in my DAW and I want that midi track to listen to midi of all my keyboards and I want to send that midi data to one particular synth on midi channel 6?
Also, do you have the ModelD hooked up to a DIN midi port? If I wanted to connect 2 old synths to a DIN out port, 1 listening to midi 1 and the other to midi 2, daisy chained. I want to be able to control both old synths from all my keyboards at the same time. What do I select as my midi input source in the midi track and what would be my midi out device + port, say I want to control the vintage synth listening to channel 1?
In Cubase, I have each track's MIDI input set to "Any" and its MIDI output point to a specific synth. That means each track listens (and records) MIDI coming from any synth in my studio, but it plays only on the synth which that track is intended for.
My ModelD is hooked up via USB. When you have multiple synths on the same DIN chain, they must be listening to different MIDI channels (unless you actually WANT them all to play the same thing).
Great video - thought it was just me who thought Iconnects manual were horrible…. Do the keyboards need to be on a specific or same MIDI channel themselves in their hardware settings?
No, the mioXL will feed ALL MIDI channels through, that is of course unless you have set up filtering in the unit to prevent specific channels from being routed.
If using 5din cables, does it matter the cable connections… for example if Keyboard 1 is considered the Master, and the connection on keyboard 1 would be MIDI Out, would the connection on the MIO be DIN 1 IN or OUT? If keyboard 2 was considered the slave, then Keyboard 2 connection would be MIDI IN on the keyboard and what on the MIO?
Thanks Scott. I'm wondering if one of these devices would benefit my setup. I have a number of hardware synths which I'd ideally like configured and connected up to my DAW to be available for selection at all times. I've so far been unable to achieve this without creating an aggregate device. This in turn results in a number of problems of it's own such a CPU overload. With the mioXL, could I for example have all my synths connected and available in my DAW without ports changing (another common problem with aggregate devices). Apologies if this is a daft question. I'm quite technically minded but when it comes to midi and routing synths I often get flummoxed! Thanks :)
I've not heard of aggregate MIDI devices before, but I'm not all that familiar with Macs, so I don't know how that may work. I've only heard of aggregate audio devices.
As for MIDI, then yes, this would allow you to have all of your synths connected and accessible at the same time, appearing as multiple MIDI ports, without having to share ports or switch things around, either in your DAW or physically.
Would I be able to use this live to connect multiple synths to change presets to each song I play?
You could...but you'd also need something to organize what is being sent to what synth - I use Camelot Pro for this.
Hi Scott - I watched a lot of videos about this a year ago and, as you say, they were dire so didn't buy one. Yours is the best explanation of the mio out there 👍
However, I'm still confused over one thing which is probably due to my small brain, and that is RTP. Is this right - your computer and mio are both connected to your router so they are on the same network so that is the ONLY connection you need between the muo, your MIDI gear (apart from dedicated USB connections) and your computer?
If the computer is NOT switched on, will those routings still work?
What do the RTP ports look like in your DAW?
Maybe you could do another video on RTP for absolute dummies 😊
That's correct, it's only connected with network. The routing works Independent of the PC, so the PC doesn't have to be turned on. The small rtp driver app I show briefly in the video maps all the rtp ports on the network and makes them appear as MIDI ports on the PC, just as if it was any other MIDI interface. All of this happens pretty much automatically, it just (for the most part) figures it out for itself, thanks to Bonjour.
@@ScottsSynthStuff I think I've got it. Thanks Scott 😊
The mio will be on your network so if you had some connections to your PC and some to another mioXL and then you turn off your PC, the connections would stay for the other mioXL and the PC wouldn't be connected because it's off. As soon as that computer comes back on it'll connect again.
@@iConnectivitySupportI sort of got that but I was wondering if routings are made between individual instruments on the mio via RTP as in Scott's example, would those routing still work if the PC is not switched on. Does that make sense?
One question I have is for editors, do you use an RTP port/editor for each synth or just a generic editor port. (I'm guessing I'll only be editing one at a time, so a generic port may work).
Each synth appears as its own RTP port, so you can point anything you like at it.
how about the basic stuff like remap midi cables to midi channels, or remap midi channels from instruments ? couldn’t find if it has this simple feature, seems like it doesn’t.
Yes, you can! On the MIDI Remap page, you can map individual MIDI channels from one channel/device to another.
I gave up on recording MIDI for multiple MIDI devices decades ago. Two main reasons: 1) Midi when used in complexity is not perfect in recording and something like a foot pedal sustain may be missing when you play back. I have completed live play of 8 devices using a MOTO DIN router, then when playing back the sustain pedal that functioned during the performance was not recorded for one synth. 2) Even though there is a standard for MIDI, there isn't a standard for each synth to have in and out filters. ALL MIDI devices need filters to function in a group of devices. Some of the most important are simply left out, such as PROGRAM CHANGE: OFF. START/STOP: OFF. CLOCK: INTERNAL/EXTERNAL/OFF. and more.
So many years since MIDI began, and still no standard chip that can be installed on every MIDI device with all the filters needed to make the new device function with the others, old and new. I have MIDI devices that have some filters but not all. Some devices have basically none, I have a synth which receives all 16 channels in OMNI and there is no way to turn it off, this synth cannot be in a communication stream with others because I can't assign a channel. So many problems with a system that could be universally standard for all manufacturers and have a seal of this standard or compliance on the box. I have to look all through the MIDI implementation charts before buying to discover if the synth will be useless in my chain (thru's). Trouble is the charts are not accurate without knowing what the MIDI capabilities are. I have keyboards that have 8 channels of internal MIDI for sequencing, but these 8 channels are not available at the MIDI/DIN output or input!! So, between the variables of the MIDI architecture and the lack of standard in entire MIDI control, I have made many mistakes in buying. And buying has become stressful and time consuming.
Today, I keep the MIDI to a bare minimum of complexity, only using it to remotely control other devices. Clock may function or may not, never can be certain and so I don't have just one MIDI network controlling my 15 synths, groove boxes, sampler. And recording MIDI is out of the question now that multi-track audio is MUCH easier and thoroughly dependable in my 100% hardware studio. I have a DAW but only use it now a few times a year for editing samples. All my instruments are using MIDI but I have grouped them to function in groups of 4 or 5. I use lots of THRU boxes and one MERGE box. Example: I have my Roland Fantom controlling 4 Roland Boutiques, while my Casio MZ-X500 is controlling a Korg Krome and Electribe2 on another network. And another arranger controlling a Korg Minilogue, Triton, MinilogueXD and a Microbrute on another separate network. My Roland Gaia is controlling a YamahaDX while a MERGE from a YamahaMX49 controls both the Gaia and DX.
IF that sounds complicated, it is not, it is MIDI at its simplicity. Recording is then all audio going through 32 channels of analog mixing subbed to 8 channels of my hardware recorder. I record Vangelis's style using a floor covered in foot pedals and perform live in one take. I have an advantage over Vangelis using today's sequencers to provide back-up to my performing using two hands and two feet and MIDI to make complex arrangements, or simple or anything in between. This performance recording has allowed me to make over 70 albums in the last 10 years. The reason I love this type of recording is I capture the passion of the performance, the ebb and flow of timing and natural human music. Multi-tracking may be more perfect, but it is that perfection that makes it in-human. And there is no way I can get the same feeling from building a song one track at a time...to...performing the full orchestration in real time.
I have to disagree - MIDI when properly configured works great for complex recording. Sustain pedal (CC64) has been there right from the very start of MIDI 1.0, and if it's not being recorded and played back correctly, it's a configuration problem somewhere - but I've never had any synth or DAW that needed configuration to do that. Sustain just works.
As for MIDI filters, that's precisely where the iConnectivity router shines, as I demonstrate near the end of the video. Want to filter data for a specific channel? Want to filter specific CC's? Want to filter MIDI clock or transport control messages for a specific synth? It's dead simple to do in the iConnectivity box.
That said, I agree the plague of "manufacturer specific" MIDI implementations is a real problem. As long as you record MIDI from an instrument and play it back to the same instrument, you should have no issues. But there's no guarantee that twisting a filter cutoff on synth A is going to operate the filter cutoff on synth B. It might instead modify something completely different and unexpected.
The beauty of the iConnectivity box is that every synth is on its own virtual MIDI interface. There is no sharing of channels, no need to filter messages for specific synths, because the ONLY MIDI messages going to the synth are ones specifically intended for it. Unlike the splitters and daisy chaining of old, instead every synth thinks it is the only synth in the world, because there are no other messages going to it from other synths.
I think a well-planned setup based around the mioXL can definitely help with the live performance aspects you're talking about - not to mention that you can instantly pull up new routing configurations that could conceivably change for each song. For song A, your GAIA is playing your MX49 and your Elektribe, for song B, the GAIA is playing your Krome. No repatching, just change the configuration on the front panel.
You stated that the USB ports on the mioXL are MIDI-only, but the specs per iConnectivity say that they can also send and receive audio-over-USB, for devices that support that feature, as well. I paused your video when you mentioned they are MIDI-only, so maybe you mention the audio aspect after where I paused. Perhaps you meant only that you can’t expect to use the USB ports on the mioXL to plug printers, keyboards, etc., as if it’s a USB hub, but that it mmm the ports can only be used for MIDI AND audio-over-USB, for class-compliant devices … ?
Also, I subscribed.
I don't know what specs you're reading, but the mioXL is definitely MIDI over USB only. The virtual ports appear as MIDI devices. The DAW USB port appears as a USB MIDI device. There is no functionality or driver for audio.
MIDI over USB is a well-accepted universal standard. Audio over USB as implemented by synth manufacturers differs from manufacturer to manufacturer and sometimes even between individual synths, and each requires a manufacturer-specific driver to support it. There is no way that this could be done with emulated USB ports - the mioXL would have to know how to speak "Yamaha" in order to connect to a Montage's USB audio, and then somehow route that audio to another virtual audio interface that it itself provided to the DAW.
The only way it could work was if the mioXL was a simple USB hub, and blindly routed packets between the PC and the synth (meaning you could plug your printer into it) - but that's not at all how it works. The mioXL presents virtual MIDI ports to the PC (or exposes them via RTP) and then routes MIDI data from those virtual ports to and from its DIN and USB ports. The USB ports implement only the basic MIDI over USB functionality - no USB audio.
I WISH it had this functionality, as that would be tremendous - you could use it to aggregate all of the USB audio streams from various synths into a single USB audio interface on your PC, and get around the ASIO limitation of a single audio interface! But I think that is a pipe dream - such a device would need to be a computer itself that could load and run manufacturer-specific USB audio drivers in order for that to work.
@@ScottsSynthStuff The MODX7 sends and receives multiple audio tracks to my iMac without any need for proprietary drivers, as well as my Roland MC-707 sending multiple audio channels, and my Dreadbox Typhon. All without drivers. This leads me to believe there is a generic, host, audio-over-USB, class-compliment standard.
Within the product description specifically for the mioXL on Sweetwater’s site it is stated … “Synths, controllers, samplers, beatmakers - all computing devices connected to the mioXL can send and receive MIDI and audio from devices that are connected to any of its USB host ports.” How should we interpret this? Computer-to-computer-only, and not between instrument and computer(s)? Maybe, yeah. I know I had an iConnectMIDI2+ many years ago that was a MIDI interface, with no other audio capabilities, that could send and receive audio via USB to my iOS devices. But if my MODX, MC-707, and Typhon can send audio to my iMac with no need for drivers, what precludes an interface/patch bay/hub from simply passing these packets along as an intermediary?
@@InnerVisions68 So did get the mioXL in the end? Can you send audio over the usb hub?
@@kitespongan Haven’t gotten it yet, but still intend to. My thinking in mentioning audio-over-USB to Scott was due to my prior experience with it with an precious, older model of mio interface, and the assumption that there may be hardware pass-through of the portion of the USB data stream that would carry digital audio packets, and not any virtualization of any said USB data packets. I’m still curious, and looking forward to positively resolving this question. I’ll let you know when I get the mioXL.
I am planning to buy this interface based on this video. You did not mention (or maybe I missed it) specifically setting the midi channel on a Synth. If your cobalt is set on midi 1chan and model D on midi 2chan, and you route one to the other in the app will it play? Thanks
Yes you can, and you can even remap specific parts of the MIDI data (note on/off, CC's, etc) to different MIDI channels if you want.
@@ScottsSynthStuff that's pretty incredible, thanks for your help!!
Great stuff!
However, you mention latency when using MIDI Thru. Actually the THRU driver cicuitry (by spec) is as simple as possible just re-transmitting the signal after the input optocoupler, without any form of processing.
If there is (was) a perceived latency when chaining multiple instruments, the latency origin is WITHIN the instrument(s). Back in the day CPUs were not that fast, and some instruments would respond to MIDI slower than others.
But MIDI THRU is designed from the start of the development not to cause latency.
I think I replied on this previously, but here goes again. You're correct: Back in the day, MIDI THROUGH was actually physically connected (through optocouplers) to MIDI IN, so there was no latency. It was a perfect, instant copy.
Then microprocessors came along, a lot of the MIDI THROUGH ports got dropped, and we got switchable "MIDI OUT/THRU" ports instead. To duplicate the THROUGH functionality, they would just have the microprocessor duplicate the MIDI data seen on the IN port and send it to the OUT port, thereby replicating MIDI THROUGH functionality. However, in doing so, they introduced latency, because the processor would have to read, decode, re-encode and write the data. Have several synths in a row doing that, and you now have audible latency. There was no more direct connection from IN to OUT/THROUGH.
That's what we have for most synths today, unlike the original implementations in the 1980's.
Hello Scott. On the remapping page there is this option for "Poly Key". Is that for polychaining synths, or for making a poly synth mono? I can't find any information on this.
It is for polyphonic aftertouch, as defined in the original MIDI standard as "polyphonic key pressure." This will NOT filter polyphonic aftertouch from some more modern synths such as the Hydrasynth. The original MIDI standard allowed only 7 bits (127 different values) for this, whereas Hydrasynth sends it as 14-bit NRPN messages.
@@ScottsSynthStuff Thank you for clarifying this. Very much appreciated.
@@ScottsSynthStuffa follow up question: does this mean the polyphonic aftertouch data can be filtered so it will flow more easily? I have a 1990 MIDIBoard with poly AT.
Hi! You have midified your SH-101? It has only CV/GATE if I remember.
Yes, you can see details on it here: ruclips.net/video/23T7WGZgzJk/видео.html
I want to get one for my studio but I have two questions about the MioXL. I use Reason as my main DAW. I have for years not changing. But it limits clock to one output. Can I send clock to all my ports from one? DO I just filter out the Note Info? Second. My Arturia devices have an app that updates and manages patches and firmware. Can I use that through the MioXL? Thanks in advance. I cannot find good documentation on the mio anywhere and their RUclips does not accept comments so I can't ask there.
You can definitely send clock from one port to one, all or none of the devices. You can filter clock, note data, CC's, or whatever you want. If you want to have three clock sources and distribute those amongst all the other devices, you could do that as well. It's pretty flexible.
Unless it is doing standard sysex to send firmware (and synths haven't really done that since the 90's) you can't do firmware upgrades through the mioXL. You will still have to (temporarily) connect the synth directly to the PC to do the upgrade.
thanks@@ScottsSynthStuff
Hi scott. I am having midi issues. i am trying to control 3 different synths with 1 midi controller. synth 1 - micro freak 2- roland jx-08 3 - E-mu proteus 1. I am trying to use each synth independent. i set synth 1 to midi channel 1 and jx-08 on midi channel 3, and proteus on midi channel 3. i change channels from my midi controller global channel settings. the issue i am having is when i switch to jx 08 the proteus is coming through. i just want to be able to switch between the synths without them layering together. can you guide me in the right direction thank you so much.
proteus is on midi channel 2 sorry
I’m watching your video because the mioxl videos are bad. Thank you 🙏
Hey Scott,
I’m also a Scott, thanks for the video. It’s what I needed months ago, but just found it.
So I run 3 drum machines (2 Arturia, &1 Roland) fed by the MiniFreak, fed by the PolyBrute as the initial trigger via Din MIDI.
Works flawlessly. The problem is when I try to use either the Fantom 07, MODX6, the Hydrasynth 49, or The Iridium keyboard as the initial trigger.
The Hydrasynth does respond but tempo is not accurate, I guess it not having a sequencer may have something to do with that.
I’m not sure what MIDI channels the Arturia is operating on, but I have tried to dive into the MIDI functions on the synths that doesn’t trigger, and turned on as many selections as possible, but can’t find the solution. Any suggestions?
I wonder if it's the startup clock sync issue that I talk about in this video? ruclips.net/video/EjrvApZgMZo/видео.html
Hi Scott thanks for this video. I have a question, how's the clock sync via midi / rtp? trying the connection for the very first time, and the timing is terrible. is it my mio xl behaving like this or is it a common issue? even midi I have to say is not as stable as using just the regular host / din channels. Would be great to know how's your experience. Thanks.
Did you resolve the issue
@@xntricity6446 nah it seems like the sync is really not doable. I mean technically doable but timing is terrible. I gave up
@@marcopassarani9650 OK I was curious about same thing, did you ask tech support for any tips. Cheers
@@xntricity6446 honestly I didn’t as I was busy with other things. It was just an experiment to the see the options. Probably I will one day ;)
@@marcopassarani9650 no prob 😉
Is it possible to route MIDI that is connected directly to the computer, for example via Bluetooth, to ports on the iConnectivity without going through a daw? Or vice versa?
No. It can't magically know that there is a MIDI port on your computer. The mioXL's ports can appear as RTP MIDI ports on your PC, but you will need *something* to route the MIDI between the bluetooth MIDI device and the RTP MIDI port to get that MIDI to the mioXL.
@@ScottsSynthStuff Thanks for the answer, much appreciated, as you said it‘s a bit hard to get info about these devices. It does make sense thinking about it. I didn‘t take into account that Auracle is setting up software on the iConnectivity device, not doing routing on the computer itself.
I'm currently using a mini Windows PC to host and route my USB MIDI devices, and that's working OK, but its fan is a little noisy. Does the MioXL make any noise?
Nope, it's completely silent.
@@ScottsSynthStuff awesome, thanks!
@@ScottsSynthStuff The MioXL looks like a great box for just doing MIDI patching, but I've been spoilt by the Blokas MidiHub, which allows complex MIDI pipelines to be created, which means not just filtering, but also remapping, scaling, arps, delays, etc.
@@Hakucho64 Yeah, for that kind of stuff I want to use my DAW. :)
Midi Thru is an electrical solution, not a digital one. Meaning, the signal at the input get's electrically buffered and doesn't undergo any processing. This hardly introduces any cascading latency, other than the reaction time of the buffer (which is on the order of nano seconds, a millionth of a millisecond)
That's how it used to be....but the vast majority of digital synths today have a switchable MIDI OUT/MIDI THRU port, and the MIDI through functionality is performed by the processor...which introduces latency.
RTP is an internet standard, not an Apple thing. It's a low-level internet protocol like TCP designed for high performance multimedia delivery. RTP-MIDI is a MIDI standard which runs over RTP (much like MIDI runs over USB). It was proposed by U Berkeley and adopted as RFC 4695. Apple only comes into it in that their implementation of RTP-MIDI, called "AppleMIDI", deviated from RFC 4695 by using a proprietary session management protocol, now publicly documented. Other companies have since complied with Apple's version.
Whaaaat? Apple took an accepted standard, published as an RFC, and then put proprietary protocols on top? I can't believe it, Apple would never saddle an open, accepted standard with proprietary nonsense to lock users into a proprietary pseudo standard like that! That sounds so unlike them!
I'm a developer by trade. I HATE Apple, for exactly this kind of crap. Too much of:
if(iOS) {
do(special_apple_crap, to_workaround, proprietary_BS);
}
else {
do(long_accepted_industry_standard_method, that_works_on_everything_but_apple);
}
@@ScottsSynthStuff Well, before we get out the pitchforks, Apple was far and away the biggest implementer at the time (2006) and AppleMIDI is definitely an improvement over RTP-MIDI, much cleaner. They are to be blamed for not documenting it for a decade, but it seems to have been straightforwardly reverse engineered.
@@ScottsSynthStuff BTW, if you're a developer, send me mail (I'm the author of Edisyn, my email address is on the front page of the manual). I'm leading the group reverse engineering the Hydrasynth sysex spec.
@@ScottsSynthStuff I'm not a dev (sys/net admin by trade) but can read code and that made me chuckle.
They really need update compatibility for newer MacOS systems. Catalina was the last compatible OS and even there, you find numerous qwirks
Nice video! Could you please do a step by step video on setting up the network MIDI. I have two mioXL's and have tried to get them working but get super confused. There is no good resource for this. All the videos are terrible and leave me more confused. Love my xl's but iconnectivity needs to do a better job explaining how to set them up!
Did tech support help you?
@@xntricity6446 Yes, they did.
@@FattSunny great to hear 👌
@@xntricity6446 It took some back and forth, but they did get it working. Without any networking experience it is impossible to wrap your head around the setup. After some digging on networking and them responding to videos of my desktop it all kinda clicks. Having a big setup and two mioXl'S ALL working together totally worth the headaches. Would and do highly recommend them.
Easy to get around USB endpoints by using a multi-port dedicated USB PCI-E card (if you have a desktop PC) where each port is it's own host. In such a case of a 7 port USB PCI-E card, you have 32*7 end points. And if you have a laptop...well....you're out of luck. But yeah...I'd agree the MIO XL is better. Check out MIO XM for a smaller $249 option. Same functionality less ports.
The limitation is not per USB controller, it's per CPU. So adding another PCI USB card is not going to increase the number of available endpoints. It's one of the reasons my new DAW PC is an AMD instead of Intel - more than double the available endpoints.
Correct....I was confusing max number of usb tiers with endpoints. Sorry for the confusion.
I believe the limit is imposed by the XHCI USB controller. A PCIe card would bypass that and go directly to the PCIe bus. So it should work to increase the number of available endpoints although it then depends on the limits of the card and the card's driver.
Do a search on "Acroname How many USB devices can I connect?" for more info. (I don't think YT allows external links.)
I believe the limit is imposed by the XHCI USB controller. A PCIe card would bypass that and go directly to the PCIe bus. So it should work to increase the number of available endpoints although it then depends on the limits of the card and the card's driver.
What exactly is the usb endpoint limitation? Windows 7 used to have a 10 midi device hard limit? But not in windows 10 or above. Secondly people talk about usb cables longer than 5meters cause issues. I have been using 8 metre cables no problem and super speed hubs. I have 12 usb devices. Ideally for Rtp to be optimized. You would need to be separating your internet for Vst updates activation and the rtp network to an isolated network with a dedicated 10Gb network switch. Then two ethernet adapters on your pc. Or use wifi adapter only for inet and ethernet port for isolated rtp network. Also if you have conflicting bome service drivers like those with native instruments its a recipe for conflicts.
MIDI 2.0 MPE?
MPE is basically a "hack" extension to MIDI 1.0 in order to give it polyphonic expression. MIDI 2.0 has this baked right into the standard, so MPE won't be needed anymore.
@Scott's Synth Stuff cool thank you. So is this MIDI 2.0 USB DIN RTP HOST capable?
@@ET2carbon I have no idea...but I suspect not. It's not mentioned in the manual, and it's been out longer than MIDI 2.0 has been ratified. Perhaps a firmware upgrade one day? But I can't say.
@Scott's Synth Stuff I just looked, there is only MPE still no devices are 2.0 yet
I would never ever use that for gigging, it has a crap external power supply with an awful flimsy connector with bell wire cable. It’s not serious but if kit.
Like so many RUclips, 'cool/useful' sounding 'tutorial' video names, it isn't what the name suggests at all.
This isn't an advanced routing tutorial. It's a high-level setup for basic synth to synth communication and a bit of RTP setup.
Advanced would be far lower level on routing multiple things to multiple things and FAR more information about filtering, which is barely touched at all and is the very definition of the 'advanced' part of the device.
This is a routing-with-MIOXL video and nothing more.
Because that's the main purpose of this device, if you can make a video going indept please share it with us but if not stop moaning
i'll be honest, I don't know what this unit offers me. I plug usb devices in, they aren't recognised as what they are, some of them don't receive the power they are supposed to all of which I solved with a $110 x8 usb hub with on/off switches. once midi is in the computer, I can send it anywhere including over the network natively in audio midi devices, everybody can do this. I wish i never bought it. the documentation is truely the worst.