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
@mgmg4871 can you tell me what setting in Live Guitar and Alchemy you have to get it to work? I'm usually good at figuring this stuff out but I'm at a loss when it comes to Alchemy and Sunrizer. GB works, Music Studio works, BS 16i works.
@AkaMarko I have internal synth set to off in Live Guitar in settings menu. I have midi in set to Live Guitar in Alchemy. I have Alchemy ticked in Live Guitar in midi setting. Also SecretBaseDesign gave me a tip of opening AB first with 512 buffer setting selected to eliminate distortion.
@mgmg4871 okay I'll try that. i haven't used it with AB because ALCH's not on the bus.
@AkaMarko I got that tip from SecretBaseDesign because I had distortion issues. He said AB sets the buffer size to 512 and it works for apps that are not AB compatible. It worked.
Is it just me but quite often when strumming, strums are missed (ie. I strum but there is no sound). This unreliability limits its usefulness. This is just with the internal sounds, I haven't tried Midi yet. Using iPad 2
@PhilW I notice that if my fingers touch the fret lines it will miss a strum.
@PhilW -- when you strum, how close to the strings do you start? The area where we detect the strum doesn't go too far above or below the strings, and if the swipe motion starts outside that region, it doesn't get detected (this is sort of the way iOS touches are handled -- the touch/swipe "belongs" to the area that it started in). We might expand the touch area a bit in the next release, but I'm trying to hold some space back for some controls that I'm planning on adding in the future.
Is there any way to flip the UI around?
As a long time guitarist and guitar teacher the default view is upside down, imho. In one of the help tutorial videos it mentions turning the device around but I'm wondering why the UI can't be flipped instead of the device itself.
Maybe I missed something and there's already a way to do this as I haven't had much time yet to play around with LG.
Thanks!
@yowza -- the UI is set up so that you can play the app as though you were holding a guitar. The screen on the iPad faces away from you (just as the "front" of a guitar faces out towards the audience). It's pretty different from most of the apps available, and might take a bit to get used to (particularly for non-guitar players).
Or are you talking about the text on the screen (the numbers to mark the frets, the chord name, song title, and so on)? If you look down at the iPad, with it facing away from you, then the text is upside down -- I could add a toggle to flip it one way or the other. If that would be helpful, I'll put it on the to-do list.
Right now, the interface is designed for right-handed guitar playing, but we'll be adding support for lefty in the future.
@SecretBaseDesign Flipping the text would be helpful but my default preference is to always view the fretboard from the playing perspective not from the audience's viewpoint. Your default view is what I see when I look at the fretboard of a student during a lesson but not what I want to see any other time as a player. Maybe having some way to toggle between the two views and yes having the text right side up in player's mode would be great, I'd make that my default view if possible!
Maybe I was doing something wrong but I had to physically pick up my iPad and flip it to put it in playing mode and with the charger and audio cable plugged in, it wasn't fun.
It would be nice to get to the playing view without having to flip the device.
I hope this makes sense, thanks for listening!
LG is not working with Auria. Is there a fix in our future??
@BobFederer -- can you expand on what's not working? I have not seen any problems with recording into other apps. The samples that Live Guitar loads are fairly large -- any chance this is a memory limitation on the iPad?
Re strumming, that may be the issue, I'll try to be more "controlled" in my strumming style and see if that sorts it! Edit - yes i am sure that is the cause, but I would appreciate if it could be made a little more "forgiving" in a future update.
@SecretBaseDesign Due to never having bothered with chord charts, tabs and the like, I'm going to ask a really dumb question here. If I want to specify a chord that has notes played higher than the 9th fret, I end up with double digits in the chord spec. Eg. 0 9 12 0 0 0
The problem is that if I enter this as 0912000, it looks like the 0 9 12 is a 0 9 1 2. What's the correct way to specify this?
@PaulB -- just put spaces between the numbers if there's anything past the 9th fret. What you've got in your example should work like a champ. The app is expecting either 6 digits, or 6 numbers separated by spaces.
I've run into a bug, where things don't work as planned if you Tweet the chord set (brain failure on my part); this will get fixed in the next update, which isn't too far off. There are a bunch of minor things I'd like to tweak.
Thanks, I'll try that.
Here's a quick video using MIDI to control @Ryan's Yamaha Pacifica patch in BeatMaker 2... Touch location maps to velocity, and Ryan's patch maps velocity to different note types (open strum, palm mute, pinch harmonic, and so on). Good clean fun!
That was quick. Impressive. Should have thought of this myself, I had all the information. Lol
@BobFederer -- thanks for the pointer. We found the bug with recording into Auria, and have a fix. The updated version should be submitted to Apple shortly.