Linux?

Does anyone here can share / have had any experience in using iConnectMIDI2+ with Linux? Specifically,

- MIDI between iOS devices and Linux computers - does it work?
- Audio between iOS devices and Linux computers - does it work?

I intend to buy one, and I use a Linux computer for my musical nuissances.. And would love if any good soul that has one of these could share some light (or perhaps test and give us some feedback?)

Dev team? Any thoughts?

Sorry for bothering you and thanks for a possible reply.

Comments

  • Oh I see this question is over a year old now! Just started playing with connecting a Linux Mint machine to iConnectAudio4. Preliminary results are it sees the device and can play/record audio. Looks like it passes MIDI into Ardour4 - but I have not even begun to understand how Ardour4 works yet (never used it before)...not sure if I'll continue down this path or not, but its entirely possible iConnectivity devices may work with Linux. You will have to use either Win, Mac, or iOS to configure the audio & midi routing - but with the Audio4 interface you can have two hosts connected at the same time! Hope this helps someone...
  • As a quick follow up, yes I was able to route iOS audio playback into a Linux machine through the ICA4. I used the PulseAudio driver loopback module to hook the input to the output and it played through the speakers on the linux machine. There was delay/latency - but I'm not using a realtime kernel at this point - so maybe that would help.
  • The 32 bit version of the iConnectivity configuration utility is running just fine under Wine. I think i had to install an additional library with the help of the winetricks utility, though.

    My MIO10 works flawlessly as a class compliant USB midi device.
    I wrote a kernel patch for the MIO10 that will display the names of the ports for the USB jacks assigned with the iConnectivity software.
    I also wrote an initial version of a userspace rtpmidi (=ethernet) driver for the MIO. Except for long sysex messages that use the f0/f0-f7/f0- f7/f7 syntax everything is working.

    So in summary: The MIO10 will soon be 100% working on Linux.
  • I'm beyond impressed, Drumfix!
  • I have a working rtp midi driver ready for testing. Anybody interested drop me a message.
  • @DrumFix - this is outstanding - I also applaud this with Nick. I would love to test. I will PM you my email address - very cool.
  • @Drumfix: I had a hard time yesterday getting the config utility to work under wine. Installation was straight forward but the USB-Midi port is not found. Which sound architecture is enabled in your wine config?
  • @iconnectivity developers: The dlls shows that you are using the qt library - which is also available in every linux distribution. What keeps you from compiling it for Linux? It would be so much easier for us if we had a native linux version of the config tool!
  • I don't even know how to select between alsa sequencer or alsa raw midi in Wine, but apparently my Wine configuration is using alsa raw midi devices. I also set windows version to "Windows 7" in winecfg
  • Note: If you have jack running with the midi driver set to raw or seq this will block the use of the midi ports in Wine.
  • @Drumfix: Thanks for your reply! Of course I had Jack running :-( I will test further tonight.
  • I have a working rtp midi driver ready for testing. Anybody interested drop me a message.
  • I uploaded the MIO ethernet driver for Linux to github now.


    Holger Dehnhardt is working on a config utility



  • Wow, this is great work!

    Let me know if you need any more documentation or assistance with this stuff. (I'm a big fan of FOSS work like this).

    Question: if we open sourced our current software would that make it easier for you guys to port? Maybe that's a conversation we should be having...
  • To make a complete USB midi driver patch for the names of the USB ports, the output of  "lsusb -v" for each of your MIDI devices would be fine. With that info i could prepare the patch for inclusion into the linux kernel.
    Currently i have this info only for my own device (MIO10).

    My opinion on opensourcing your software:

    Since the iConfig utility is a Qt application, opensourcing it (as GPL) would mean you can cancel your Qt subscription, because there is no commercial license needed anymore.

    And it is certainly easier to port an existing Qt application to Linux than to do a complete rewrite.
    Depending on the amount of platform dependent code in it the effort can range from an hour to several days.


  • We are currently discussing this in-house and hope to have a good answer for you within the next weeks. In the meantime, write to me privately rorpheus at iconnectivity.com and I'll see about getting you the info you need.
  • Hi Drumfix, this list should help you out:

    USB PIDs

    Our VID is 0x2321.

    The full-speed device PIDs are as follows (note that we have several PIDs for each product because we have multiple device ports and the device uses a different PID when operating in boot loader mode):
    • mio: 0x0009, 0x000A
    • mio2: 0x0003, 0x0004, 0x0005
    • mio4: 0x0006, 0x0007, 0x0008
    • mio10: 0x001A, 0x001B, 0x001C
    •  iConnectMIDI1: 0x000B, 0x000C
    •  iConnectMIDI2+: 0x000D, 0x000E, 0x000F
    • iConnectMIDI4+: 0x0010, 0x0011, 0x0012, 0x0013
    • iConnectAUDIO4+: 0x0014, 0x0015, 0x0016
    • iConnectAUDIO2+: 0x0017, 0x0018, 0x0019
    • ConnectAUDIO2/4: 0x0023, 0x0024
  • edited September 2017
    To make a complete USB midi driver patch for the names of the USB ports, the output of  "lsusb -v" for each of your MIDI devices would be fine. With that info i could prepare the patch for inclusion into the linux kernel.
    Currently i have this info only for my own device (MIO10).

    My opinion on opensourcing your software:

    Since the iConfig utility is a Qt application, opensourcing it (as GPL) would mean you can cancel your Qt subscription, because there is no commercial license needed anymore.

    And it is certainly easier to port an existing Qt application to Linux than to do a complete rewrite.
    Depending on the amount of platform dependent code in it the effort can range from an hour to several days.

    recently I start  blog on linux. Check it here


Sign In or Register to comment.