Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Using Launchpad X with WIDI UHost?
Has anyone managed to get this combo to work? It connects OK but my troubleshooting suggests that the WIDI device only forwards the first MIDI port presented to it by the host device. In the case of the LPX there are two MIDI ports, one for DAW control and one that spits out MIDI and it looks like only the DAW one is being transmitted, which is not very useful.
I have tried turning on programmer mode but this did not help. I was hoping there would be some secret setting in either the WIDI or LPX which let me disable or choose whether to ignore the DAW port but maybe not.
I saw in another thread that someone had got their LPPro working with this device so I had assumed it would just work.
Comments
This limitation (only one virtual port) is specifically noted on the CME web page, so it is likely fundamental. I wonder if you can somehow trick it so it picks up the normal port; not much hope tho'.
Thanks @uncledave , I did see that and I suspect is the root cause. As you say, I was hoping that someone had been able to find a way of tricking either the WIDI device or LPX into using the correct MIDI port, or maybe to switch the order that it looks for them.
I see that @CME_WIDI_2020 sometimes posts here - is this a hard limitation of the WIDI Uhost? If so then is there a possibility of a future update letting us select the MIDI port of the connected device via the iOS WIDI app?
I tried it some time ago and it worked in the Launchpad app, but not in LK or LP pro
@MisplacedDevelopment in the other thread for the LanchpadPro... Possible they were using the DIN midi port on it and not the USB-C?
Little update on this one - I updated my LPX to firmware 2.0 and my WIDI Uhost to Bluetooth firmware 0.1.7.7 (USB firmware 3.6) and now I can use my LPX wirelessly to control my iPad over Bluetooth!
I am kicking myself for not testing it immediately after updating the LPX firmware as I cannot be sure whether it was that or the Uhost update that fixed the problem.
The device now appears as "WIDI Uhost Bluetooth" in AUM.
Now to find a suitable battery to run the WIDI from!
How about with mini mk3?
My battery choice for Uhost is 'Veho Pebble Pokket Micro', it has a built in USB-C plug.
https://www.amazon.co.uk/Veho-Keyring-1000mah-Portable-VPP-016-PK/dp/B084B827QF/ref=pd_lpo_1?pd_rd_i=B084B827QF&psc=1
Thanks for that @steve99 . I just cancelled my order for a very short usb-A to C cable to use with an existing battery as the Pebble was only a few £ more and looks like a tidier solution.
Does the WIDI device publish both the DAW and MIDI ports of the LPX? If not (and it sounds like it doesn’t), which port is it publishing?
It is publishing just the MIDI port now. The problem I had in the OP was that the Uhost selected the LPX DAW port with no way of changing that and now it selects the MIDI port, again with no way of changing which is selected.
It is possible I suppose that this may have broken behaviour for someone so I will not be updating again in a hurry in case it is "fixed", but for me the MIDI port was what I wanted the Uhost to select by default.
For those that don’t know, this means that the LP’s midi out from Notes and Custom mode will work but session mode and programmer’s mode won’t.
Are there Any bt-midi USB adapters that support 2 or 3 virtual ports?
For note- the $20 M-vave Bt-midi USB adapter does the same thing - the midi port is auto selected to Note and Custom work fine, but Session/programmer are missing
(Hmmm.... I wonder if I pick up a WIDI U-Host on old firmware for DAW_in/out and not update, split the USBC out of the LPX to two adapters into a 2port battery....... 🤔)
I think it’s because the USB can define multiple ports, the original midi had to use separate cables or ports physically, in the future it may be possible but I don’t know any but maybe a usb to usb device could.
Not that I have ANY of the knowledge towards it at this point, but I am now wondering if an Arduino board could act as a signal splitter/combiner, one USB in, 2 (or 3 for pro) out (but also in. 🎶 Buh duh dum dah daaah I'm pedantic 🎶), each to a separate bt adapter.......
Though I do have a brother in law who's run quite a few Arduino projects...
That could be possible.
I think that won’t work well with Launchpads. As an owner of an LP mini MK3 I was interested to use it with Grooverider GR-16. Because the MIDI protocols the different Launchpads are using are pretty similar, I had the idea to write a converter (in Mozaic) that translates the SysEx messages from the LP mini into the LP Pro protocol and back. It turned out this won’t work: GR-16 (and probably other Launchpad supporting apps) are not using SysEx device discovery, but are actually expecting a virtual USB MIDI interface with a specific name.
Intriguing af
I doubt that would effect this concept, seeing as how currently LPX on bt-wifi is proof positive working without a common name on both WIDI (earlier in this thread) and M-vave (personal) - and before updating firmwares, op had the same generic bt name but it was full working DAW_in/out
So theoretically, splitting the out and combining the in wouldn't be an issue on the bt front, it would 'simply' be signal mangling management
Sounds like a grooverider dev decision on reading the device or sending/receiving messages