Wireless MIDI Interface mi.1 [Rev.2]

I just received my mi.1 MIDI interface and wanted to share my initial impressions. The design of this product is purely elegant in its simplicity. I have an old Yamaha DGX-200 keyboard with 5-pin MIDI ports. I also have an M-Audio uno 1x1 MIDI to USB converter, but I tried this Uno converter with the iphone camera connection kit, and it was apparently too old a version to be recognized by iOS 8 on my iphone. So I ordered the QUICCO mi.1 instead.I like...that I can attach my charging cable to my iphone while using this product (which I couldn't do with the camera connection kit).On first opening the mi.1, I found the unit, and a brief instruction sheet. The startup instructions are quite simple, but I did encounter one difference in my experience vs what the instructions stated. I downloaded the mi1 connect app from iTunes to my iphone and used it to connect to the mi1. What I did not realize, is that this app seems to be used for the sole purpose of transferring firmware to the mi.1, not for it's normal operation. When I first tried to download the new firmware to the mi.1, I received a prompt on my iphone instructing me to turn my Bluetooth off, and then back on, before updating the firmware. This prompt was not mentioned in the instruction sheet, and had me a little confused for a while, especially since I was afraid that breaking the Bluetooth connection while transferring the firmware might render the unit useless. But alas, eventually, I did succeed, following the prompt instructions, disabling, then re-enabling Bluetooth on my iphone, and THEN updating the firmware.My initial intent is to use this with the Organ instrument in GarageBand.My initial guess was to run the mi1 connect app, hit connect, then open GarageBand and play.....but that's not how it works. As I said above, the mi1 app is only needed to update firmware.To connect the mi.1 to GarageBand create(or open) a song, select an instrument, and then hit the "settings" button (looks like a 3-spoked gear) at the upper right of the screen. Select the SONG tab at the top of the page, then scroll down and select Bluetooth MIDI Devices. You should see the mi.1 listed as a device, with status "disconnected". Click on it, and connect. Exit out of settings, back to the instrument and begin playing. The MIDI notes from your keyboard will go to the instrument on your idevice and make sound.I am still working out the exact sequence to connect reliably. At some point the mi.1 will go "offline". For example, if I close GarageBand, go a distance from the mi.1, then return and open GarageBand, go into SONG Settings/Bluetooth MIDI Devices it will list the mi.1 as "offline". There is no response to touching the device status, so no actions are apparently available from this screen to reconnect to the device.Running the mi1 connect app does not cause the mi1 to re-connectDisabling Bluetooth on my idevice, and re-enabling does not cause the mi1 to re-connectTurning my keyboard (and hence, the mi.1) OFF and then ON causes the device status in GarageBand to change from "offline" to Not Connected.From here you can then touch the status and connect to the mi.1 and GarageBand immediately begins to respond to keys played on the keyboard.So, for now, it seems that once the device disconnects, it needs to have power cycled in order to re-connect. Beware, that the instructions state that you should always plug the device into the MIDI ports BEFORE turning on your keyboard power. So...I would not recommend unplugging the re-plugging the device with your keyboard on in order to cycle power on the mi.1. That could damage it if it was not designed to be "hot pluggable".Closing, and re-opening GarageBand did NOT disconnect the device.Separating my idevice (iphone in my case) from the mi.1 by a "large distance" caused the status in GarageBand to go "offline" and then to "NotConnected" when I came back in range of the Bluetooth signal. From here I was able to re-connect without cycling power on the mi.1.Latency: I'm not set up to measure the latency right now, but I did set both my keyboard instrument, and iphone instrument to Drums, and then played a key which produced a snare drum sound on both. I could definitely hear a "flam" sound (two drum hits occurring very close together) indicating that some measureable (and noticable) latency exists. I do believe that if I play with this enough, my brain will begin to compensate for the latency a little causing me to hit the keyboard on the leading edge of the beat. It's not so bad that it makes you tend to slow down, but it is right on the edge of being noticeable with non-percussion instruments.In summary, the fact that I was able to get this unit up and running in 15 minutes is a great testimony. It seems to work as advertised, and functions with acceptably small latency. A very cool product. Now I plan to purchase the Galileo organ app from Yonac Software and have some real fun, but that will require a controller with sliders and knobs which I do not currently have. Tomorrow's another day.

Just unboxed mine from amazon tonight and tested briefly. Super easy setup. Just had to find a powered MIDI port on one of my controllers - seems the RME Babyface MIDI is not powered. Ended up connecting to the MIDI I/O on my Behringer BCR-2000. Had it up and running with Ableton in about 5 minutes with heavy distraction from my 4-year-old asking me to play a video game with him. The connection seemed rock solid over a few minutes of testing. I was having a lot of trouble with drop-outs using wi-fi for the iPad MIDI, so the great performance of the QUICCO is a big relief, especially considering it's cheaper than the camera kit + USB interface!About the only feature I'd like to see added is a dedicated power input other than the MIDI power (make the power brick optional or via micro USB to keep cost down). If the Babyface did not supply power, I have a feeling few audio interfaces supply powered MIDI ports. I'm lucky enough to have plenty of MIDI ports on other gear connected via USB. If you don't have a powered port available on a USB MIDI controller, you may still need a USB MIDI interface to connect to a computer DAW.

It has been now 1 year and I still give it 5 stars even though the is no support and it stopped working after the app that came with bricked it after a firmware update. Once I figured out that I could get a connection using their Jukebox Player app it has worked great. I transmitt both audio and midi using my mi.1 to an iPhone and the audio to a little mixer and I can not hear any latency using my EWI 5000. Just wish I could cut off the midi in part.This is my earlier post before I switched from a WX11 to EW5000 wind controller.Keep in mind that this is only day one but I am impressed. I ordered this on Prime on Friday and had it by 2pm Sunday. I set it up withing 10 mins using my 90's vintage Yamaha WT11 which is an midi synth that I use with my Yamaha WX11 wind controller. I used it to test varrious apps like MusicStudio, Thumbjam and Magellan JR on my Iphone 6 plus. I was worried about latency as with sound over Bluetooth it is like playing in Grand Canyon but with ear phones I didn't find latency and issue. Thumbjam responded to wind control of vol and pitch bend as good as IOS midi apps can. I did run into a problem with my BT7 battery power midi interface as it did not provide enough power. I tried it with a M-Audio usb interface and that had enought power so I think I can find a battery power midi interface to bump up the power. I will contact tech support to see if they have any suggestions but I think I can find a fix for this issue. Their web sit warned that it may not work on all equipment so I am not supprised to run into this. I had tired the PUC wifi midi IOS interface but took it back as it keep losing connection and it was too difficult to reconnect. I tried switching apps on and off and I did get it to lose connection but was very simple to reconnect. It did not lose connection while playing but time will tell. I also connected my Iphone to a bluetooth speaker at the same time that I had the BTLE connection going and it did work but the latency made that not a good solution for real time playing. I would give it a 10 out of 10 as the company has made the set up very simple, if you follow the directions, and I am not one to do that often. I read enough on the internet to make sure I followed every step. This will not work on an Ipad 2 and I have an Iphone 5 that I will test it on but I expect the same results that I have on the Iphone 6 plus. Using the app Apollo you can link both phones so you can trigger midi apps on both at the same time. Not sue about latency until I test it.