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.
iMini MIDI update updated what exactly?
I cannot tell what was improved. Still no channel number selection (definitely still Omni), stuck notes, MIDI message box staying blank still, no response to panic command, Virtual MIDI In port not responsive (so cannot use filtered controllers via midiBridge still). And where channel select should be is a permanent IAA panel. Which itself should be on the main page not on the connection slide-out anyway. And not taking up space if not in an IAA slot somewhere.
Please, tell me it is my tired old eyes just not seeing new stuff!
Comments
Just updated... Still no MIDI from BeatMaker 2 ?? No can do here.
No more stuck notes. Mod wheel working. Soak tested for 6 hours.
No kidding, there was an update? I'll check for stuck notes tonight, I've been able to reliably produce them in the past.
Yes - I had a bit of a 4/1 moment earlier @mrufino1 when having been excited that it was working great on one iPad after the update, I went to another iPad and with great enthusiasm started using iMini on that one too and I was getting stuck notes right away and I thought: "Oh no!" - but then I realized I hadn't updated it on that iPad. I did and all is fine. So, it was "reliably" broken before, but it appears totally fixed now :-)
BTW: I tweeted a thank you to retronyms and asked about further MIDI support.
And the reply:
@dwarman said:
@MusicInclusive said:
hmm...
@busker - I have been using it for the better part of 12 hours without any stuck notes. :-)
A glissando or two was sticking notes for me before. I just got home so I'll update it shortly then do lots of glisses. If it passes that test it will be onstage at my next gig. If not, iSEM stays in place.
I'll do some more testing for stuck notes since I seem to be the only person who found this. I had assumed from the update notes that better mIdi meant more functionality, but so far it seems to only mean stuck notes are fixed. Everything else missing is still missing, or still not working (like the MIDI message display and the Virtual MIDI In port).
I got no stuck notes at all. I was reminded that I am not funky though. Hope they fix that in an update...;-)
iMini virtual MIDI has always been flaky for me. But after this latest update, vMIDI doesn't work at all anymore. I'm running an iPad Air, 32GB with plenty of storage left, iOS 7.0.6. I'd update to iOS 7.1, but I need to find out how to backup my Korg Gadget projects first.
I will post to Arturia's forum as well, but this one gets way more traffic. Anyone else having vMIDI problems with iMini?
I don't think I'd ever even tried virtual MIDI with it, but I just did, and couldn't get it to work. Ports do show up, but nothing seems to be received.
I got ChordPoly Pad to talk to iMini yesterday but I had to try every MIDI setting in CPP until I got it to work. I think I ended up using CPP's Main MIDI out, whatever that is. Then I had to turn on the MIDI in from CPP in iMini's MIDI settings. Definitely not as easy as it usually is to get CPP to send MIDI out.
Check the MIDI settings in whatever app you are using to send MIDI to iMini and try all MIDI out settings even ones that you might think won't work.
I spent a fair chunk of time last night trying to get it to work with MidiSequencer last night with no success. I can occasionally get the blue MidiSeq device button to show up, but no actual note operation, although it controls the ISem just fine. Weirdly enough, the Little Midi Machine app does control the IMini, although I had to re-download it (LMM) before it got it to connect.
Does anyone else have any luck with MidiSequencer?
@mrufino1 - should I add you to AppZapp so I can tell when you are updated? ;-)
Also @Zymos, @yowza, @Audiohub and @Markomatic - I could send MIDI to it from Cubasis just fine. Started in an AB chain with iMini in input and Cubasis in output. Sent to Virtual MIDI - (sending to iMini didn't work - but Virtual MIDI did.)
@MusicInclusive said:
Similar experience using Chordion: Once I set the outs to Chordion Virtual Out, it worked like a charm; setting it to Session 1 and iMini In did not work.
Session 1 is usually your wireless network.
What's appzapp? I did update it last night then played it for a while, no stuck notes. No gigs this weekend but I will definitely use it next weekend when I have 2. Until then lots of practice, on a good day I barely play synth bass passably, on a less than good day, yikes!
Oh, ha! I just understood your joke. I'm from suburban NJ, I don't know if there's an update to funkify that....
@mrufino1 I've been to New Jersey - can definitely be funkified :-)
midiSequencer as is does not have a VirtualMIDI out port to select as source in iMini. Instead it attempts to send to iMini's VirtualMiDI In port. Which does not work. Hopefully the imminent update to MS will add the Out port and destination selectivity, then it can drive iMini.
not sure if I am adding anything new here, but FreEWI running in the background solves the Virtual Midi issue for me.