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
Hippy
Thanks for the Scenes kick in the pants! I am definitely getting some more uses out of it now!
@StudioES I'm not far enough along yet to fully profit from your wisdoms, hopefully I will be at some point, but this just to say generous posts and thank you.
EDIT: Except now you've taken your toys away. Pity.
....
Strange. Probably best to just slowly tip toe backwards on this one...
Can only presume trouble at Mill.....
Hope everything's ok with ya @StudioES
@tja you're into an area of the app that I find confusing too. The app is crazy flexible and deep. Within a bank, you can sequence multiple plugins loaded onto multiple pads, and also sequence one shot samples loaded onto other pads. And it will all work just fine. FWIW, having banks perform specialized purposes (as described in my doc) helps me keep things straight (basically, I don't go where you're trying to go
). I'll have one bank serve as a drum sampler (loading one shots on to pads), but I won't load any plugins into that bank. If I want to sequence sounds from a plugin, I place it into a separate bank. This is similar to what you'd do in a standard DAW, you'd have a drum sampler (like NI Battery) on one track, and a drum plugin (like ruismaker) on a separate track.
When it comes to editing recorded MIDI in the Pattern editor, it's really easy to get lost. I don't have all the answers to your questions, but here are a couple thoughts that will hopefully help.
*It's really important to know what view you have activated (either Keys mode or Pad mode), and which pad is selected. What's displayed in the pattern editor varies depending on "where you are". Make sure to check the pattern ruler on the left side of the pattern editor. It displays what pad is selected.
*When you record MIDI for a plugin, it is recorded on to the pad the plugin is loaded on. So you'll only "see" the MIDI that you've recorded for that plugin if the pad hosting the plugin in selected. Since MIDI data for a plugin is pad specific, to see the notes you recorded for the plugin you have to bey in Keys mode. You will also "see" C3 notes displayed (if in Keys mode) if you tapped this pad while recording in Pad mode.
*What MIDI data actually gets recorded when you record in pad mode is still a bit of a mystery to me. It's not clear what actual MIDI notes are being recorded. When you toggle to Keys mode, only the notes that have been recorded for the selected pad are shown, and notes recorded in pad mode are displayed as C3. In Keys mode of course, when you record MIDI by tapping pads, the MIDI notes displayed on the pads are what gets recorded.
*While I find Pad mode confusing at times, I also find the pad mode display in the pattern editor to be very useful, if your bank is set up so that's only hosting samples, not plugins. When a bank is set up this way, the pattern editor when in pad mode only one row per pad. This makes it really efficient to sequence MIDI (and edit it in the pattern editor) for a bank set up to only host samples.
Me too
just noticed all his posts on the intua forum are gone too.
As for the sage BM3 advice @ecamburn, man, huge props on being so well thought out and concise.
My more inelegant contribution today is “Raaaahr, Audio tracks BAD!”. Having a couple three minute long audio tracks present renders song navigation super chuggy and results in buggy viewport behaviour needing a restart. When i converted these two tracks to slices on banks (with ‘create pattern’ selected) then all my woes went away.
Well, talk about confusion of notions!
I’ve read through this elaborate explanation from @ecamburn three times, I still don’t get it. Well, probably just me.
Will have to try it out in practice. Anyway thanks to all for trying...
Would you mind over explaining this for me please?
Here is a sound file loaded as an audio track.
Rather than use it as an audio track I will use it as a sliced sample. This improves performance and allows for better editing/fx opportunities etc
Step 1 - make a bank and load the sound file on a pad.
Step2 - Use the autoslice to set the grid divisions...
Step3 - Tap Save to save slices. Turn on ‘Create Pattern’
Step4 - note that the bank now has a new pattern (you need to drag and drop it onto the track)
Step5 - however when you edit the pattern and zoom in you will see a small bug where the new slices are slightly off from the grid.
Step6 - select all the slices and quantise them
Step7 - you can now delete the audio track
Now you can enjoy the bounty of slices! In addition to deleting, modifying and rearranging slices on this first bank I recommend creating new ‘companion banks’ for derivative (copied and modified) slices. It looks like it would be complex but once you get into it, it is pretty sweet.
@AudioGus thank you for breaking this down! Really appreciate it.
@AudioGus That's great stuff Muster Gus. Not quite ready for it over here in my kitchen, but I'm putting it in the pantry for a meal later on. AND at the exact time I'm following your map up comes a tweet from INTUA reminding that "Plenty of exciting things are coming soon..."
Thanks AudioGus for your work there, very appreciated
No prob peeps. Let me know if there is anything else I can do.
Hmm, there’s tons of yearly wipeouts:
As long as it wasn't the yearly breakdown....pity though, some helpful stuff there.
I was just trying again to get a drum loop loaded into the sampler and set it up to loop until I press the pad again. I can’t seem to make this happen at all. Is there something I’m missing?
There are three trigger modes: hold - (which I would have expected to hold the pad until pressed again) stops playing as soon as the pad is released, one shot - of course won’t let me loop, and release - which starts playing upon releasing the pad. Is there really no way to have it actually hold the note/loop until pressed again? Seems like a very strange oversight for this type of app.