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 love this app but am still very confused with the saving
how do i save this project?
i don’t even know what project i’m currently in hehe
i hit save on the sequencer but how do i make this a project i can recall later??
i don’t see a save this project option
i think with auv3 it’ll be a quick state saving thing right in aum but for now im so confused haha
So when you save in the Sequencer window, it just saves the sequence to your Scene.
To then save your Scene, scroll to the bottom of the Chord strip along the left edge, and hit the ... button. You can save your Scene in the Edit window that pops up.
Also, in the Folder shaped button in the top-right corner of the main interface. This is where you load up your saved Scenes, but you can also hit the Edit button to bring you to the same window where you can save your Scene.
But yes, make sure you save your Sequences in that Sequencer window, then save your Scene.
ahhhh thank you much man! i think i get it now!
i think auv3 would make this much easier with stare saving so hopefully that can still be done but def for now this helps a lot
You’re welcome.
I love this app so much, I am always happy to help out with questions when I can.
I want everyone to get the most out of it and have a great experience when using it.
i really love it to, but i always get lost in the save so i feel like i never go back to projects i was working on so i have to start fresh every time...iaa has always felt that way and TS especially has a strange save process but i think i grasp it more now
Great update, thanks @moodscaper !
Hi Folks - thanks again @CracklePot for helping out - much appreciated, and yes... I hold my hands up in shame (or should that be hang my head...) Anyhoo - yes. Saving is a total mess. Initially, when you just had a bunch of chords and instruments it was manageable, but the app has evolved a lot since then. So yes, saving is on my list of things to sort out. And...
just a heads-up that I'm aware there's an issue with the sequencer "stuttering" when using Ableton Link. Working to get a fix out ASAP. :-/ (update: fix submitted for review)
Just grabbed this - can anyone recommend a getting started vid? Not too long and waffley, as I seem to have problems with long vids on this iPad.
Edit - just watched Doug's excellent last tutorial, so sorted now.
haha no shame this app has progressed so much and is a fav around here. it makes sense the way it panned out with everything added on. do you think auv3 state saving will make it easier? saving it within the aum auv3 version as preset or even as a session
The CC update brings instant sweet modulations to Continua etc. Nice touch with the on/off toggle of movement on single or all CCs.
@moodscaper I think there is a small bug when changing CC speed in settings while playing held notes (with CC animation going), for instance when changing from slow to fast for a CC. I need to exit Touchscaper and get back in to actually see this change.
Nice bonus with the 5 slots in settings, effectively giving you 50 different LFOs to control. Do you think it would be possible to extend the sequencer to program which of the 5 slots to be active at any step? Perhaps even using the dice randomizers.
Well that was pretty cool. I just plugged the iPad into the laptop using IDAM, and had Touchscaper playing synths on three different channels in Ableton, and the rhythm playing a drum rack, all recordable as MIDI.
Only request is more straightforward saving - just a save/save as option to save the whole thing.
Five stars from me then!
If your iPad can manage a 30 min video, then the one that came out today on the latest update is also a nice tutorial on how to make a moving bassline with Model 15.
Hi @bleep - I'm afraid the automation speed doesn't get reflected dynamically, but if you re-assign it, it should pick up the new speed setting. Also, as you've noticed if you background the app, it's actually re-assigning the automation under the hood automatically.
Re sequencer integration, anything is possible
I'd been thinking about some kind of CC sequencer stuff, but not sure when I'll get to it - some other stuff to look at first I think.
Well... the hardest part is going to be adding support for auv3 in the first place. Imagine every single thing you can change in a scene, or every single thing you can configure with MIDI... (we're talking hundreds of parameters here) that then you need to decide which of these will also be exposed as an AU property so it can be "state saved". It's potentially a huge amount of work! Still trying to get my head round what needs to be done / can be done...
Assuming I can map it out, I'm proposing to take a sort of "phased" approach to this. The first (and most important) thing I want to do is basically replace IAA with AU for the audio connectivity side of things, so I can basically just forget about IAA going forward.
Cheers! I'll check that one out too, haven't sussed the MIDI CC stuff yet.
Sometimes it seems easier to break apart a huge IAA app like touchscaper into the individual components for AU. Like the touch synth and 2 keyboards as an AU, the chord looper as an AU, and the sequencers as an AU. Maybe even make the sequencers single track, and ppl load up however many they need. The different AU components can be connected back together through midi into a sort of custom version of the standalone app.
Maybe this is way too crazy of an approach. I really don’t know. But a couple of apps did something like this for the AU version. Aphelian and iVCS3 have stripped down AU components of the main standalone app.
Just throwing out a suggestion. I am sure you will devise the best plan to move forward to AU support.
Loving this awesome app!
I just updated to the latest version, and now orbit is no longer working for me. What changed? I didn't see any mention of a change in the orbit section of the user guide.
Hi @mungbeans - do you mean orbit after pressing hold on the main view, or orbit from the sequencer? Seems to be working OK for me - are you tapping hold, then orbit, or just orbit? There may have been some tweaks around that at some point as it's an old feature / bug. If you're still having problems, please could you let me know steps so I can try and reproduce the issue - thanks.
This app gets the A.Kinkujin seal of approval. Just a great way to easily get something really fun going. I look forward to the updates!
Orbit works for me for touches set to Hold.
@moodscaper is there anyway to add the ability to add touches to Hold after some are already in Hold mode?
Maybe tapping Hold while holding the new touches adds them to the group of Hold touches, instead of deactivating Hold.
Do a long press to deactivate Hold, or even a double-tap, maybe?
Not a huge deal, but if you end up taking a look at the Hold and Orbit code, I thought I might as well ask.
Maybe single-tap to deactivate hold (the current method) and tap-and-hold to add further touches to the hold collection? Thinking that this adding operation needs a tap-and-hold anyway, whereas deactivate can be quick.
Yeah that would work too.
Just whatever seems like the most intuitive, least confusing way.
If it can’t be added, no big deal.
I can always just grow more fingers.
😆
Thanks for the update but seems to be a small bug for me with midi out, it only seems to work for me when hosted as an IAA. All the virtual midi ports only appear for me if you host it as an IAA generator. The ports should appear even when not hosted as IAA, so I think it's a "background audio" bug...that's an IAA issue I think. Nice update though
Yes, I get the same thing.
But Midi Out still works in Standalone, although you have to select the destinations and other midi setup in Touchscaper’s midi panel.
That does seem to work, but I prefer to see all the separated ports in AUM to map things more easily.
Yeah, me as well.
I think you are right about the BG Audio thing, too.
OK... I need to find the person that said they'd prefer NOT to see the separate ports when NOT running in an IAA host :-/
If running in an IAA host the multiple ports are shown, if not, they're well... not shown. I detect those changes and hide / show the ports accordingly. This was a "feature request". The app "knows" if it's running in an IAA host or not. It has to check almost constantly because IAA is a PITA. The "feature requester" was pretty insistent (to say the least) it should work that way. The fun part of developing an app is to see who insists or something being one way or another I guess
Or you could have an option to say "show all MIDI ports even when NOT running in an IAA host"... Sorry if I sound a bit tired of this sort of thing because I know you're all cool guys and I really appreciate your support, but it can be a little tiresome when you get these conflicting suggestions, then get taken to task for doing something that someone else demanded you do. I think / hope all this goes away with AU but I'm not so sure.
It was user error, somehow the animate orbit switch had got accidentally flipped.