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
I can get it to record feedback in standalone mode, but with headphones connected (wired or wireless) I can’t get input at all
Hmmm 🤔 I have to be doing something wrong then. I’m on iPhone 11 Pro. All seems straight forward and I’ve been using iOS audio apps a good long while now.
Can’t imagine what could be going wrong.
Strange. I just tried it again. I was able to record a loop then overdub 3 times. I’m sure you’ve checked the microphone settings already. Reinstall?
I’ve an iPhone 7plus running 14.3 too. Going to try it as well
Oh, well this is interesting... I just installed Gauss on my iPhone 7plus also running ios14.2, connected my Bluetooth earbuds to it and launched Gauss. Working fine on the iPhone 7plus.
I double checked that I’d given Gauss permission to use the mic on the 11 Pro and it shows affirmative.
Shouldn’t be any significant difference between the iPhone 11 Pro & the iPhone 7 Plus should there?
I gotta run and have to abandon this for now, but I’ll try a delete, hard reset and reinstall on the iPhone 11 Pro later to see if I just got a bad install. I’m not surprised that I couldn’t use the Bluetooth mic, but it’s baffling that I can’t even use the internal mic with headphones attached.
Thanks for confirming @ecamburn !
It’s gotta be a problem with my iPhone 11 Pro or a corrupt install
No prob. Glad you at least got it running on the 7
Mood units goes really good with this to build up some loops with the overdub going and having so many spacey instruments all in one place
@skiphunt Just speculating: Could it be that the iPhone 11 records at 48khHz and the iPhone 7 at 41kHz ?
I have tested this in all different setups, even changing samplerates during use (by plugging in/removing headphones during a session) and it deals with that robustly.
I'm quite stumped. It smells like it's a combination of a specific iDevice with iOS14.2, but it would be so much easier to find the issue if I could actually reproduce it - but on all my devices it works perfectly on iOS14.1 and on iOS14.2
Just purchased Gauss and played around some. I’m confused not with Gauss but with some people making comments in this thread.
“It’s the looper I was waiting for”
“This is an Enso killer”.
I don’t own Enso, I do own a few other loopers (L7, quantiloop, etc). Gauss is not an utility or standard “looper”. It’s absolutely great and inspiring but it’s not meant to be a looper you resort to, you know, loop stuff. And the funny thing is it’s NOT MEANT TO BE.
It baffles me. “The looper I was waiting for”. Really?. A looper with triggers and sequence that’s purposely hard to sync, that pitches stuff and messes up the sound in wonderful ways... You guys should be doing TED talks.
When this arrives it’ll be usable as a “standard” looper. And I don’t even know if it should be, I think that wasn’t the original intention. I think we’re forcing @brambos to deliver functionality of a standard looper. He’s right in warning about false hopes.
This cracked me up. So true!.
Any Gauss owners using it with a midi controller? I’ve been trying to control the tape speed with CC, but I can’t hit the best speed - half speed. For that matter I can’t hit any of the ‘half’ divisions. They’re all slightly sharp or slightly flat.
The closest I can get to 1.00 is 0.99 or 1.02
Closest to 0.50 is 0.49 and 0.52
Closest to 0.25 is 0.24 and 0.27
Etc..
Can’t hit 0 either. It’s either 0.02 or -0.02
Can anybody with hardware controllers or other midi control apps verify this behavior?
For reference:
Edit: fwiw grid snap has no effect on it either.
I’ve been thinking something similar for the last couple of days. There seems to be little appreciation that an app is a series of intentional design choices, and that instead of trying to browbeat its designer(s) into making it be the thing you want, maybe you should respect their decisions and use a different tool if you need a different tool. Then again, I’m coming from the (guitar) hardware world, where a pedal is (to a greater or lesser extent) set in stone once it’s released, so I have different priors.
I see what you mean, but this is for a large part an issue with how hosts convert MIDI CC values into AU Parameter values (and that's not standardized). Remember that the plugin never gets to see those CC messages, only Paramater values...
These AU Parameters are floating point values, which allow precise settings such as 0.5, 0.125 etc. AU Hosts do the conversion, and I would expect a MIDI CC value of 64 to be exactly 0.5 (or controllers wouldn't be able to hit centerpoints).
That said, perhaps I can do some smart snapping on incoming AU Parameter values, although I expect that just as many people will dislike it ("I'm trying to set the speed to 0.01 but it always snaps to zero, what's up with that?"). Let me think about it.
Hey @brambos I bought Gauss yesterday morning and installed on my iPad and iPhone 11 Pro. Was going to play with it later in the afternoon, and that's why I messaged about how to select which mic to use since it didn't seem like it was using the mic on the bluetooth headphones. Figured it was a setting I missed.
I then spent the afternoon trying reseting the devices, trying 3 different sets of bluetooth headphones, and 2 sets of wired headphones. No signal at all on either the iPad or the iPhone 11 Pro.
After @ecamburn confirmed it was working on a 7 w/iOS14.2 later in the evening... I had some work stuff to do so I had to bail on trouble shooting. But very late last night I deleted Gauss off the iPad and iPhone 11 Pro. Did a hard reset of both devices. Then reinstalled. It then worked perfectly fine. I was even able to use the devices using AirPlay via the new Roku update. Internal mics worked in that set up too.
I don't know what to say. I swear it wasn't working for me on either the iPad 11 Pro or iPad 10.5 Pro running 14.2.
The ONLY thing different between my iPhone 7 Plus install that worked perfectly... was the time that I downloaded and installed. The failed installs were early Sunday morning. The successful installs were Sunday evening.
I just tested the iPhone 11 Pro again with all 3 sets of wireless headphones, and it's still working fine.
No clue what the issue could've been.
On a side note, and related to the mic selection... somewhere down the road, if you're making a list of possible updates to Gauss... it'd be cool to be able to select specifically which mic you want to use. As mentioned, the FilMicPro video app has an setting for audio where you can select Front, Back, Top, or Front/Back iPad/iPhone mics. Or, there's a switch on the audio setting window for "Bluetooth Mic". You turn it on and you can then select whichever bluetooth mic you have connected, either remote or the mic on the headset, etc. Might be a cool add for Gauss at some point.
Now... off to play with the app! thx
I believe you and I'm super happy to hear it's working now. iOS14 has been extremely flakey for audio, so I'm filing it in that cabinet for now.
Thanks for the update and have fun!
One possible thing that could have been going on... I had an app once where it needed permission to use the onboard mic. I granted the permission and it showed as such in the iPhone native settings for that app. Yet, still it wouldn't use the internal mic. I think it was a video app. After resetting, reinstalling, and then giving permission to use the mic again... the permission took, and I could use the app with the internal mic.
In that situation... even though iOS was showing permission granted... it still wasn't letting me use the app. Then, after reinstall, granting permission again (after a reset) the permission setting took. I want to say it was the Hyperspektiv video effects app, but I can't remember for sure. Same scenario though, and it appeared to be iOS related.
Cool, thanks for looking into it. I can’t speak for everyone, but I’m assuming the scenarios where users want 0.50 and 0.25 are more common than than for 0.49 etc. I just tested with a Nano Kontrol 2 and got the same results.
So looks like an Aum thing then. Not the first time I’ve gotten skipped values In Aum.
🍻
Edit: if its an Aum issue, maybe some kind of internal interpolation or smoothing in Gauss could be used? Probably a lot of work though
@brambos and @Hainbach , thanks for this app. I've struggled to get loopers to produce anything I liked in the past. For some reason I've clicked more with Gauss' set up. The result is that using Gauss has opened up some new avenues of expression that weren't there before.
Yeah this app is very creative, will be spending a lot of time with it.
I also don't think adding hardware control for functions already there takes anything away from the original goal, only enhances it's uses as a live tape instrument.
Yes! I think octaves and 5ths must be the prefered values for MIDI automation..binding MIDI Buttons for instant transpose
Yeah, I can relate to the pedal background.
I do think that being able to automate or somehow sync the rec button is really important. Specially if you want to record something like a guitar. But that’s a functional aspect to make it more suitable for certain scenarios. “Récord, pause, érase, rewind” is plenty.
I currently mostly play a 100€ home-made cgb guitar, it’s got 3 strings and it’s quirky in a lovely way, I adore it. Would I say “the guitar I always wanted, it’s a Telecaster killer”?. No. It’s something else. I still have my Telecaster if I want something that doesn’t sound like the devil’s intestines.
right, yes. Ok yeah that'll work.
cool. good to know. the videos i saw on it were all in hosts so never saw it in standalone mode.
thank you for the responses.
this is great info , thanks! glad to know the preset and audio are saved that way..and where they are. the re-naming tip is A++ . if i ever test in cubasis or aum i'll let you know!!
yes, i’m afraid that i would be one of those awkward types that would be narked by the snapping,, but shouldn’t it be connected to whether the ‘grid snap’ is on or not??
or am i misunderstanding? i would only be using Au automation NOT midi controllers.. would the au parameters be effected by any change made for Midi Control?
That was my suggestion as well.
Thank you @brambos for considering the smart snapping.
Likewise, this is the first looper that’s fully clicked for me, lovely work @brambos & Hainbach.
It’s a joy to use, the first time i fired it up & got it going i was gone for an hour.
Well the thing is there already is ‘snapping’. But the problem is that it’s snapping in increments of 0.03 and 0.04, skipping important values such as 1 - 0.5 - 0.25 - 0.125 - 0.
To illustrate, from 1 down looks like this:
1.02 - 0.99 - 0.96 - 0.93 - 0.9 - 0.87, etc.
So the issue isn't that snapping would occur if he made a change to CC response, it's just that snapping should be offset so that musically and rhythmically important values are not skipped.
So
becomes
The increments are the same, but the values are more musical. I'm not sure the best way to implement this, but if there were an offset there'd literally be no more 'snapping' than there currently is. From what I understand, this is a problem with hosts transmitting the midi data to the AU.
@aleyas Sounds reasonable to me. Personally, I'm not too worried about the specific implementation, I'd just love to have the feature.
aha! thanks for putting me straight... i’ll have to look closer and see if that effects anything i am doing