Great video. This setup is great. There are so many setup options with the mioXL, it's hard for us to cover all the different types of setups. We added the [i] in front of the Bonjour Name of the RTP ports recently. This was because many time people would rename the Bonjour Name of the RTP port, then switch to Initiator and copy that same name and then make a network session with the same Bonjour name and the the problems would start of who would fight for the connection. If you set the service order correctly in the network settings, you should be able to use your wifi and your mioXL without problem. You could setup the mioXM on that side of the room and talk to the other side. You can create direct connections between the mioXM and the mioXL. So the route would be DIN or USB. Let's say you connected it to HST1 (USB). By default this goes to RTP 5 on the mioXM. Leave the mioXM RTP ports in responder mode. Go to the mioXL and select any RTP port and setup as Initiator. copy the Bonjour Name of RTP 5 on the mioXM and paste it for the Bonjour name the Xl will connect to. Say you opened up RTP12 like in the video. You would bring the Akai over on RTP12 and the use MIDI routing to route to all the synths you need on the DIN ports. This would trigger all device on the same channel BUT you could go to just the MPC and let that do the routing. You could also create multiple prests on the XL so each prest sends from RTP12 (Akai) to a different synth on the wall. Go to the computer with USB from the XM, since you are so close. There are many options. Feel free to talk to us at our support channel and we can work with you to find the best option. Love all the little notes in here about the software.
Yeah! I've had a mioXL for years and it's a fantastic beast. They key to midi is to NOT route it through a DAW, but instead treat any DAW/computer as just another node in the studio. I write with just hardware, and then can stream it synced into a DAW, or put the DAW in control as the master clock and work in the box. Just the flick of a switch. Wish more people realized that this way of working is super flexible and powerful.
Well this is cool! Your slat wall system inspired me to create my own version and one of things I ended up doing was getting a mioXM to connect everything together. Now here you are arriving at a very similar solution for your wall of synths. Great minds I'd say!! :)
I use the MioXL too and it's fantastic, makes things so much easier. No more need for thru/merge boxes, and all devices become accessible from the DAW, like you mentioned. I also have a Blokas Midihub for some more hardcore MIDI filtering/processing, and I can route things to the Midihub from the Auracle software, no need to change cables. Game changer.
Nice tips , I’ve had a midi4+ for a few years , and it is the heart of my setup , I use the iPad to configure it, sometimes over the network. Think I’ll have to watch again , coz I never really got the hang of the rtp software on the pc. I’m sure I can improve what I have from your video, thanks.
I got this USB type C host port cable that allows me to connect my Iconectivity interface directly to my iPad which I thought was really cool. And can also plug the iPad into the MPC live and then plug the Iconectivity interface into the MPC live and use it as its audio interface as well as midi capabilities. And at the same time I can plug all my Roland system 8 system 1 M TR8S MX 1 directly into the MPC live and use it with no drivers. Then I found an appreciation for the MPC desktop software. I can go between logic Ableton and MPC desktop seamlessly. plugged the MPC live directly into my SC MTK 22 mixer and utilize all the channels as well as my iPad can see the mixer and see all of its channels as well. Out of all of the pieces of gear I have the Akai MPC ecosystem seems to be one of the most value added tools therefore I overlook some of its faults.... like a very terrible filing system… Why do I have to open a projects to save it to a different medium on the hardware. I should be able to utilize The hardware without any computer software to get the maximum file system. I should be able to copy paste files folders from medium to medium that are connected internally or externally to the MPC hardware. Anything class compliant the MPC live ecosystem loves. My MPC one loves it just as well. The force heck yeah.
I've been using a MioXL for a couple years now. Just got a 2nd unit to increase my port count and maybe use synths from two different rooms, or more conveniently from across one room. For sound over Ethernet, I am using Presonus StudioLive III Mixers over AVB networking. Networked MIDI and Audio is great! I am very happy with the MioXL. So far, I have only been swapping my host (iPad vs. Mac) by connecting the MioXL to a common USB hub, and then I plug that hub into my laptop, or my iPad depending on what music I am planning to make. I haven't tried the MioXL with my Akai Force, but I assume it will work the same as the Akai One. Now that I have two MioXL units, I will try a lot of different configs to see how they work. I haven't tried RTP from the MioXL to my Macbook yet. I believe it is even possible to RTP to an iPad in a similar way as you showed RTP to the Mac. But I have chosen to keep it simple and avoid RTP to Mac or an iPad directly because Apple doesn't really make this stuff a priority. Your issues with Initiator vs. Receiver is exactly the kind of issue I expect from trying RTP with a Mac. You didn't mention directly, but RTP for PC requires installing 3rd party software (rtpMIDI I believe - www.tobias-erichsen.de/software/rtpmidi.html). I tried it once for MIDI between my Mac and Desktop Windows PC. There were some problems but I didn't dive deep enough to know if it was just me). This is part of why I have avoided using RTP MIDI from the MioXL to my Mac. You can do AVB audio directly to a Mac as well (like from a Presonus StudioLive III mixer or MOTU audio interfaces), but for similar reasons (Apple doesn't make this stuff a priority), I haven't pushed the limits trying it out. I wish iConnectivity had an iPad version of Auracle, the MioXL configuration software. They use to to have iConfig for iOS and MacOS, but dropped support for it when they moved to Auracle. Auracle is good for the MioXL/XM, but still not up to snuff for their audio interfaces like the AUDIO4+ and AUDIO4c, which are audio interfaces that allow using two hosts (e.g. a Mac and an iPad) on one audio interface. Now I use AVB networking between multiple Presonus mixers connected as audio interfaces (e.g. a Presonus 32R) to do network audio sharing between multiple hosts. I imagine you can do the same with a couple MOTU AVB audio interfaces. Great video! Please do more on this topic. I know many MioXL/XM users would love to see them. Thanks!
I love my MioXL... only had for a few months but as an MPC X user I was looking for a way to bridge the gap of having my standalone setup and incorporate my Windows rig since I also use a lot of VST instruments... it did take me a day to get an understanding of what was going on with software GUI but after that it's game changing... what I'm still wondering if anyone with an MPC can help... when selecting port options I have to scroll through even unused options and I've been searching for a way to remove these
The iConnectAUDIO4+ is an audio interface that allows hooking up 2 computers at the same time, both sharing one audio interface (e.g. an iPad and a laptop). They have a new - the AUDIO4c. Almost the exact same thing as the AUDIO4+ but with USB C ports instead of USB 2 ports. The MioXL and MioXM are for MIDI only, no audio. The AUDIO4+ and AUDIO4c don't do what a MioXL or MioXM do. They share a MIDI IN/OUT port, but don't have multiple ports and no network sharable MIDI. The MioXM/XL series can connect multiple MIDI slaves (DIN or USB), but there is only one MIDI master (e.g. an iPad, Akai One, laptop, etc.). What was demonstrated in the video, though, shows a way to allow two computers to use all MIDI devices on your network, kind of like what an AUDIO4+ or AUDIO4c does for sound, but it requires buying 2 MioXM/MioXL devices to do it.
@@mglohmeyer Got it...I get the gist of what he is doing...when I had a hardware studio back in the 80s-90s, I used a bunch of MIDI switchers, MIDI thru boxes, etc. to do that kind of stuff. Of course, that was way before affordable networking, audio DAWs, etc.
I see you’re using your MPC One connected to your MioXL’s USB DAW port. Have you tried this with the MPC KEY 37 yet? I haven’t been able to get my MPC KEY 37 to recognize my MioXL’s midi ports this way at all, and I’ve only seen people on TH-cam do this with MPCs besides the Key 37. I wonder if that “new feature” of using the Key 37 as a midi controller in standalone mode broke compatibility with the MIOs. Let me know if your Key 37 can talk to your MIOs using the USB DAW port. Thanks!
So I just tested this and you're absolutely right, the Key 37 seems to break the USB connection! I'm going to notify both companies that something is up with the firmware of one (or both) boxes. I also tried it with the mioXM, same result. Thanks for sharing 🙏
@@teftymusictech Awesome. Or at least it’s not me being dumb. Maybe I should dump my Key 37 and get a One+. I’d really like to be able to connect my MPC to my big ole pile of synths, and if it won’t talk to my MioXL it’s not very useful for this purpose.
The solution to your problem with the Wi-Fi, is to set your physical port on a separate network that only has your midi and audio devices. This has a lot of benefits anyway, and isn’t that hard to set up. You basically need to have one router in there somewhere doing DHCP for those devicesor configure them all manually. Either way, it’s not a good idea to have your Wi-Fi and physical port connected to the same network because you will see other weird things happen in addition to what you already noticed.
Great video. This setup is great. There are so many setup options with the mioXL, it's hard for us to cover all the different types of setups.
We added the [i] in front of the Bonjour Name of the RTP ports recently. This was because many time people would rename the Bonjour Name of the RTP port, then switch to Initiator and copy that same name and then make a network session with the same Bonjour name and the the problems would start of who would fight for the connection.
If you set the service order correctly in the network settings, you should be able to use your wifi and your mioXL without problem.
You could setup the mioXM on that side of the room and talk to the other side.
You can create direct connections between the mioXM and the mioXL. So the route would be DIN or USB. Let's say you connected it to HST1 (USB). By default this goes to RTP 5 on the mioXM. Leave the mioXM RTP ports in responder mode. Go to the mioXL and select any RTP port and setup as Initiator. copy the Bonjour Name of RTP 5 on the mioXM and paste it for the Bonjour name the Xl will connect to. Say you opened up RTP12 like in the video. You would bring the Akai over on RTP12 and the use MIDI routing to route to all the synths you need on the DIN ports. This would trigger all device on the same channel BUT you could go to just the MPC and let that do the routing. You could also create multiple prests on the XL so each prest sends from RTP12 (Akai) to a different synth on the wall.
Go to the computer with USB from the XM, since you are so close.
There are many options. Feel free to talk to us at our support channel and we can work with you to find the best option.
Love all the little notes in here about the software.
Yeah! I've had a mioXL for years and it's a fantastic beast. They key to midi is to NOT route it through a DAW, but instead treat any DAW/computer as just another node in the studio. I write with just hardware, and then can stream it synced into a DAW, or put the DAW in control as the master clock and work in the box. Just the flick of a switch. Wish more people realized that this way of working is super flexible and powerful.
I have the xl. Changed my life. Makes setups so nice and easy. Highly recommend. Always wondered why more people don’t do videos about their products.
Well this is cool! Your slat wall system inspired me to create my own version and one of things I ended up doing was getting a mioXM to connect everything together. Now here you are arriving at a very similar solution for your wall of synths. Great minds I'd say!! :)
Didn't know about this one. Thanks for sharing. Very interesting !
I use the MioXL too and it's fantastic, makes things so much easier. No more need for thru/merge boxes, and all devices become accessible from the DAW, like you mentioned.
I also have a Blokas Midihub for some more hardcore MIDI filtering/processing, and I can route things to the Midihub from the Auracle software, no need to change cables. Game changer.
Nice tips , I’ve had a midi4+ for a few years , and it is the heart of my setup , I use the iPad to configure it, sometimes over the network. Think I’ll have to watch again , coz I never really got the hang of the rtp software on the pc. I’m sure I can improve what I have from your video, thanks.
I got this USB type C host port cable that allows me to connect my Iconectivity interface directly to my iPad which I thought was really cool.
And can also plug the iPad into the MPC live and then plug the Iconectivity interface into the MPC live and use it as its audio interface as well as midi capabilities.
And at the same time I can plug all my Roland system 8 system 1 M TR8S MX 1 directly into the MPC live and use it with no drivers.
Then I found an appreciation for the MPC desktop software. I can go between logic Ableton and MPC desktop seamlessly.
plugged the MPC live directly into my SC MTK 22 mixer and utilize all the channels as well as my iPad can see the mixer and see all of its channels as well.
Out of all of the pieces of gear I have the Akai MPC ecosystem seems to be one of the most value added tools therefore I overlook some of its faults.... like a very terrible filing system… Why do I have to open a projects to save it to a different medium on the hardware. I should be able to utilize The hardware without any computer software to get the maximum file system. I should be able to copy paste files folders from medium to medium that are connected internally or externally to the MPC hardware.
Anything class compliant the MPC live ecosystem loves. My MPC one loves it just as well.
The force heck yeah.
S teir indeed! this gave me some great ideas
I've been using a MioXL for a couple years now. Just got a 2nd unit to increase my port count and maybe use synths from two different rooms, or more conveniently from across one room. For sound over Ethernet, I am using Presonus StudioLive III Mixers over AVB networking. Networked MIDI and Audio is great!
I am very happy with the MioXL. So far, I have only been swapping my host (iPad vs. Mac) by connecting the MioXL to a common USB hub, and then I plug that hub into my laptop, or my iPad depending on what music I am planning to make. I haven't tried the MioXL with my Akai Force, but I assume it will work the same as the Akai One. Now that I have two MioXL units, I will try a lot of different configs to see how they work.
I haven't tried RTP from the MioXL to my Macbook yet. I believe it is even possible to RTP to an iPad in a similar way as you showed RTP to the Mac. But I have chosen to keep it simple and avoid RTP to Mac or an iPad directly because Apple doesn't really make this stuff a priority. Your issues with Initiator vs. Receiver is exactly the kind of issue I expect from trying RTP with a Mac.
You didn't mention directly, but RTP for PC requires installing 3rd party software (rtpMIDI I believe - www.tobias-erichsen.de/software/rtpmidi.html). I tried it once for MIDI between my Mac and Desktop Windows PC. There were some problems but I didn't dive deep enough to know if it was just me). This is part of why I have avoided using RTP MIDI from the MioXL to my Mac.
You can do AVB audio directly to a Mac as well (like from a Presonus StudioLive III mixer or MOTU audio interfaces), but for similar reasons (Apple doesn't make this stuff a priority), I haven't pushed the limits trying it out.
I wish iConnectivity had an iPad version of Auracle, the MioXL configuration software. They use to to have iConfig for iOS and MacOS, but dropped support for it when they moved to Auracle. Auracle is good for the MioXL/XM, but still not up to snuff for their audio interfaces like the AUDIO4+ and AUDIO4c, which are audio interfaces that allow using two hosts (e.g. a Mac and an iPad) on one audio interface. Now I use AVB networking between multiple Presonus mixers connected as audio interfaces (e.g. a Presonus 32R) to do network audio sharing between multiple hosts. I imagine you can do the same with a couple MOTU AVB audio interfaces.
Great video! Please do more on this topic. I know many MioXL/XM users would love to see them. Thanks!
Cool tech ❤. I'd have loved that in the early 90s before I went through big-MIDI-setup aversion therapy!
Great video, I try to achieve a similar setup with my mpc live but how do you connect the phantom to the MPC , by usb , midi port or via the mioXL ?
Mioxl is my favorite “synth gear” I own….
I love my MioXL... only had for a few months but as an MPC X user I was looking for a way to bridge the gap of having my standalone setup and incorporate my Windows rig since I also use a lot of VST instruments... it did take me a day to get an understanding of what was going on with software GUI but after that it's game changing... what I'm still wondering if anyone with an MPC can help... when selecting port options I have to scroll through even unused options and I've been searching for a way to remove these
I almost bought a iConnectAUDIO4+ but they discontinued it. Not sure what you are doing but it sounds interesting!
The iConnectAUDIO4+ is an audio interface that allows hooking up 2 computers at the same time, both sharing one audio interface (e.g. an iPad and a laptop). They have a new - the AUDIO4c. Almost the exact same thing as the AUDIO4+ but with USB C ports instead of USB 2 ports.
The MioXL and MioXM are for MIDI only, no audio. The AUDIO4+ and AUDIO4c don't do what a MioXL or MioXM do. They share a MIDI IN/OUT port, but don't have multiple ports and no network sharable MIDI.
The MioXM/XL series can connect multiple MIDI slaves (DIN or USB), but there is only one MIDI master (e.g. an iPad, Akai One, laptop, etc.). What was demonstrated in the video, though, shows a way to allow two computers to use all MIDI devices on your network, kind of like what an AUDIO4+ or AUDIO4c does for sound, but it requires buying 2 MioXM/MioXL devices to do it.
@@mglohmeyer Got it...I get the gist of what he is doing...when I had a hardware studio back in the 80s-90s, I used a bunch of MIDI switchers, MIDI thru boxes, etc. to do that kind of stuff. Of course, that was way before affordable networking, audio DAWs, etc.
So can the XM work work an mpc in standalone?
Anyone have experience with how MioXL compares with Conductive Labs MRCC?
I see you’re using your MPC One connected to your MioXL’s USB DAW port. Have you tried this with the MPC KEY 37 yet? I haven’t been able to get my MPC KEY 37 to recognize my MioXL’s midi ports this way at all, and I’ve only seen people on TH-cam do this with MPCs besides the Key 37. I wonder if that “new feature” of using the Key 37 as a midi controller in standalone mode broke compatibility with the MIOs. Let me know if your Key 37 can talk to your MIOs using the USB DAW port. Thanks!
So I just tested this and you're absolutely right, the Key 37 seems to break the USB connection! I'm going to notify both companies that something is up with the firmware of one (or both) boxes. I also tried it with the mioXM, same result. Thanks for sharing 🙏
@@teftymusictech Awesome. Or at least it’s not me being dumb. Maybe I should dump my Key 37 and get a One+.
I’d really like to be able to connect my MPC to my big ole pile of synths, and if it won’t talk to my MioXL it’s not very useful for this purpose.
The solution to your problem with the Wi-Fi, is to set your physical port on a separate network that only has your midi and audio devices. This has a lot of benefits anyway, and isn’t that hard to set up. You basically need to have one router in there somewhere doing DHCP for those devicesor configure them all manually. Either way, it’s not a good idea to have your Wi-Fi and physical port connected to the same network because you will see other weird things happen in addition to what you already noticed.
I already own one. 👌
I have an XL also.
Damn near mandatory in a modern studio.
pointy thumbnail