Joined in 2023 
82 
63 About this deal
Easily store and recall unique MIDI routing, filter and merging setups to preset scenes, and recall them all directly via the mioXL front panel. Use your 22 network MIDI ports anyway you want. Connect each of the 22 RTP-MIDI sessions to any combination of physical or virtual I/O ports. Almost any combination is possible. Making it possible to streamline and expand your MIDI setup, no matter how massive or demanding. With all its advanced capabilities mioXL still remains accessible for anyone looking at doing whatever they want with music in creative ways. This is because of the simple interface that makes using these features fast and easy.
I have been noodling about with audio hardware & software for 30+ years. Reasonably familiar with midi routing, able to navigate most of my tools and toys without excessive reliance on manuals most of the time. New to mioXL : store and recall up to 32 presets directly on the interface, without even needing a computer!
iConnectivity mioXL USB MIDI Interface Features:
With mioXL™ you’re able to streamline and expand your MIDI setup, no matter how massive and demanding. Even though it’s our most powerful MIDI interface, mioXL™ is still accessible to all users, allowing you to do whatever you want with MIDI faster, better, and in creative and exciting new ways. iConnectivity’s next generation RTP/Network- MIDI capabilities, and what they’ll do for you. So what does this mean if you’re a musician or a technician? Well, thanks to something called RTP-MIDI, it’s possible to send MIDI data over an Ethernet network; LOTS of MIDI data in actual fact.
Our unique network technology is as easy to use as USB! Enjoy your new-found MIDI power without extra headaches.When messing with firmware and whatnot, I have to restart the Auracle app before it sees the device again. Initial support for configuring iConnectMIDI2+, iConnectMIDI4+, mio2, mio4, and mio10 within Auracle for X-Series. This includes routing (MIDI4+, mio4, and mio10 - mio2 and mio4 in subsequent release), filtering (all devices), remapping (all devices), preset save/load (all devices), RTP configuration (midi4+, mio4, and mio10), and USB host port management (midi4+, mio4, and mio10).
The configuration is easy and straightforward, and had the network and DIN working perfectly in no time. The one star is because connecting USB devices was a nightmare!!! USB routing offers "Host Reservations" so You can permanently map a USB port to a device, the devices getting assigned as you plug them in. VERY useful feature. After doing this several times (and after having returned the first unit hoping the second would be better),I finally gave up. MIDI Management - Our interfaces deliver MIDI reliably no matter what. When the MIDI data-stream gets heavy, our interfaces plough on where other interfaces choke.
Similar Threads
If you follow a similar process to what I did here, there's *NO WAY* to screw it up. This is literally as easy as it could possibly be. I'm a software engineer by trade true, but one that values a good HCI, and this one is great but has one major flaw that I didn't talk about yet. Ethernet connectivity means MIDI is on the network wherever you need it. Regular USB connectivity limits you to keeping your interface within 15ft of your computer. Ethernet connectivity gives you up to 330ft / 100m connection between you and your interface. Drop an interface in every room of your studio, or place an interface virtually anywhere in a venue. Modern USB Connectivity - Equipped with both USB Type-C and USB Type-A connectivity, mioXC lets you enjoy easy connectivity with most modern computing devices. Originally designed to provide robust and reliable network communication in event of nuclear war (no, we’re not making it up), network connection of computing devices is something which is now part of everyday life. Chances are you’re using it to read this blog piece, right now. Hope that helps!Yeah, absolutely for that scenario that is certainly one valid way to go. I just prefer to have dedicated in/out ports per device so I don't have to deal with merging or the confusion of channelization or remembering/documenting/re-documenting/forgetting-to-document any thru mapping I may have going on. So much more straightforward for my feeble brain to just look at a list of ports and know which thing is connected to which port by the name on the port.
Great Deal 
New Comment