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.
Comments
By the way, you can report/ask thing to @xglax as well because he is one of the developers too!
This falls into the rare category of synths that do stuff my other synths can’t.
Still delving into the possibilities, lot’s of options for tweakers.
So far no clicks or pops on iPad 2018
Thanks for that. I’m pretty tempted, which would be the first iOS synth I’d also purchase on Mac.
Me, too. I have DRC and Sunrizer on both iOS and Mac so this would be my third.
Very tempting...
I honestly don’t get how anyone would need to use an Apple Pencil with this app. All of the controls are super easy to use via touch only. And the keyboard?! Seriously?
Maybe iPad mini?
Sample import from the Files app is playing nice so far in the beta. File size is limited to 2 MB
If someone is already using their Apple Pencil with other apps it will interrupt their flow if they have to stop using the pencil to interact with this app.
Addressed in the beta
Is it possible for you to send us a video replicating this issue so i can see your settings and try to replicate your issue? We have a Roli seaboard block on the office, and i was messing around with it and wasn't able to get stuck notes from it. And we aren't being reported by other MPE users about this problem, so it has been difficult for us to tackle this issue.
Thanks for the reply! Other users (well, at least one) did mention that here, actually, not just me, but it seems to be fixed in the new update, thank you, really enjoying this
Thats in fact an issue we have to work on. Because of scaling problems we were having, we fixed a minimum size, but when FRMS is hosted the host's windows affect our desired minimum. We'll definitely address that problem when possible! Thanks for pointing that out!
Sorry, must had passed that. Glad is all fixed and that you're enjoying it
Nice work
Any news of recreating the AU parameter issue @xglax?
Does anyone else have this problem?
I see that Nuno could not recreate the problem yet, but for me it doesn’t work which is strange...
@Carnbot if you point me to the post of the problem i could verify.
Sorry, I've been very busy. Please explain the issue to @xglax to see if he can replicate!
Thanks, I’m just having a problem with automating AU parameters from other apps/ hardware, can you confirm or is it just me?
@Carnbot @sinosoidal @xglax I just hooked up the Rozeta LFO to the FRMS „Master Level“ inside AUM. Works functionally - visually there is no change to the respective element inside FRMS. Is that what you mean? ATM i have no hardware handy - could test that later on if needed.
Thats strange. You're suppose to have visual representation. Maybe @Carnbot has the same issue, and is being tricked by the lack of parameter movement. But, me and @sinosoidal have movement. Thats a tricky issue, because as you said, you're getting the sound right.
That’s interesting, for me there’s no visual or audio change...will try a reinstall..I tried resetting the “midi in” settings in the AU, but no difference. I get midi input from midi keyboards and also the mod wheel works
@Carnbot @xglax
My error, excuse me - i get visual feedback if i select the right destination :facepalm:
If i select „Layer 1 Level“ i get visual feedback. In the first try i mapped to „Master Level“ but did not switch to the „Global“ Tab.
So at least this one parameter seems to work ok. Did you use any specific parameters @Carnbot ? Maybe there are single parameters that do not respond?
Ok, weird, just tried my Air 2 and it’s working perfectly..which is on iOS 13.3..
so it’s my Pro 2017 12.9 on 13.4 has the problem
Ok I think it could be the current AUM beta is causing the problem, I just installed the current AUM beta on my Air2 and it’s broke the AU parameters on Frms as on my Pro...but it’s working with other apps.
This is odd, are any of you on the current AUM beta?
@Carnbot @xglax
Tested again with Layer1 Cutoff - also ok. Audio and visual feedback are identical.
Used same channel, different CC.
@Carnbot Are you using it as AU or Standalone?
I remember i had problems in stand-alone version with MIDI at the beginning - the color-scheme is somewhat misleading. One can not clearly see if MIDI IN-Channel and/or MIDI Source is selected or not.
If i select MIDI In and the check-icon is „white“ then it actually is off... That was what irritated me the first time. (In standalone mode that is)
@MrBlaschke The color issue will be fixed in this update
@xglax Glad you found that - its ok for me. It just irritates if you try it for the first time
Several people complained about the same. In fact it was a little counter intuitive. We hope the new enabled color feels more right
I’m testing the AU parameters in the AU, I think it’s something to do with the current AUM beta, this seems to break the AU parameters in FRMS, but not other apps. Can you confirm if you are on the appstore version of AUM?
Yup - latest Store version. I am not on Jonathans Beta-List.
I can see FRMS AU parameters are working in apeMatrix, so it’s strange that the AUM beta breaks the AU parameters of FRMS...
I'll talk to @sinosoidal about this to see what is going on