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
Yeah, that UI isn’t the best for editing velocities for individual notes, and designed more for broad strokes or adding chaos. There’s a few weird questions that might arise if I were to fix this, e.g “what happens when you select multiple notes”?
Really what’s needed is a proper way of editing velocity like in Atom 1, with cool lines and curves and all the shiny, and that is going to be part of the automation update.
Nice, I’m glad people are getting into scripting. There’s a ton that can be unlocked this route, the rabbit hole is deep
Changing the ordering is possible, but I’d like to avoid enabling too many wacky things (there’s maybe too many already, which could prove significant effort to support down the line). Can you let me know what you’d like to do first? Just change the order of buttons in a toolbar? Maybe hide some buttons?
+1 (and some sort of visual representation via shading or whatever would be nice in the piano roll when you get a chance down the line)
That could be cool, certainly an FAQ would at least be nice. I’m trying to capture a lot of details in the readme, but there’s probably some nuance to some things that is missing (e.g. “how can I add a script?” or “what happens when the app updates?”)
This can actually be done already using theming via CSS. I’ll add an example when I get the chance.
Can we get some volunteers to feed a page on the wiki?
I've put some of the tips and tricks in it, but the more the better -- and we could use an additional Atom Scripting article
Many thanks! Also, although the offset states aren’t recovered on the slider when moving from one note to the other but while playing the clip the velocity settings are respected right, for each note?
I will add as much detail there as needed, just help me to compile a list of questions. For example, if you think of something or you don’t know how to do something, chances are it’s a FAQ at this point Add it to the wiki and I’ll populate with an answer.
Yup!
I’d be happy to help with the wiki too
Thanks @blueveek . Your app is a wonder! I’d definitely leave a review on the App Store!
I've set up 3 related pages. The main page (https://wiki.audiob.us/doku.php?id=atom_piano_roll_2#atom_piano_roll_2) and a scripting/css page and a FAQ page. There are links to the FAQ and scripting pages at the top of the base page.
Much appreciation in advance to anyone that contributes.
Folks! Please also add links to any videos to the pages. Feel free to just add the video URL if you don't know how to embed the video -- someone else can clean that up.
@blueveek
Excellent. thanks @espiegel123
I’ve started adding a few bits. Hopefully you won’t have to clean my markup too much
Tx!
Ya of course, that makes sense. I'm interested in just doing some simple things. When you make the toolbars larger like in the sausage fingers version, it comes with the downside that not all the icons will fit on the screen without horizontal scrolling (especially because I'm using an ipad mini). The idea is to move buttons I need most frequently to be left-most in the order. Things like time signature, tempo, swing, or prob, to me personally are more "set and forget" items, compared to the buttons for zooming and opening the patterns menu which i am using constantly. But additionally, would be cool if i could move the zoom buttons to the right toolbar in the empty space above the Move button, but that sounds more complicated, so maybe that is too much for now.
I feel this question may be too specific for adding to the FAQ? but if you want I can add it there too.
FWIW, i tracked down the bug. If i copy and paste a Rack with Atom2 and Korg Module Pro to a new track in Drambo, Atom 2 crashes and refuses to initialize and the instance is forever corrupt on any Saved file that had it running before the crash occurred.
I posted a video here showing the issue. Looks like i can’t use Module Pro with Atom 2 inside of Drambo for the time being.
I hope the video helps @blueveek @giku_beepstreet as it demonstrates a repeatable issue you can hopefully instrument.
Video:
What an excellent video and report! From the video, it seems like the issue might be with the other plugins and not Atom. However, can you please send me the project or some way for me to reproduce this locally? If there’s a workaround I can add in Atom, I’m happy to verify.
Cool, this should be very straightforward. How about I name all of the buttons, then you can add an ‘order’ property to them in a CSS file to change the order in which they appear? (yes it really is that simple). DM me to hop on the beta and make sure we agree on the public API.
Patterns within the same instance are not:
Simultaneous
Consecutive.
They are only selectable, one at a time (per instance).
Is that correct?
Sure thing. Here you go:
https://www.icloud.com/iclouddrive/0noKaA0AMlYrij4l9Njz4yxYQ#Atom-modulepro-crash_file
If Atom fails to load upon opening the file, just remove it and add it again to reinitialize the plug-in instance.
Correct. I am currently experimenting with ways to make them triggerable. The upcoming 2.0.2 update will also add a non-destructive merge function that addresses the “simultaneous” aspect.
Has anyone made a video or explained how to trigger atom 2 sequences with LK?
I like the idea is using atom 2 for the sequencing but launching clips via LK. I don’t have a hardware midi controller
That sounds perfect! will dm
I got round to trying Atom 2 and LK together this evening, with LK launching Atom clips. It works really well. There’s something nice about separating the arrangement from the clips. LK does clip launching very neatly, Atom brings the extra depth and control.
Here’s a video.
I set all the Atom clips to ‘hold’ launch mode, and set the triggers to be an octave higher with each column, so first row would be C-1, C0, C1, C2 etc.
Second row would be C#-1, C#0, C#1, C#2, and so on.
LK clips are set to the same amount of bars as their corresponding Atom clip, with a long note trigger that fills the whole clip.
Hope this is helpful to some.
I noticed this not by copy and pasting, but just by saving a project with any Atom 2 instances would result in this behavior when trying to load it back up.
Yep. Something about how Drambo is handling the AUv3 instances of Module Pro does not treat Atom2 right.
I don’t think it’s anything specific to Module pro (which I don’t even have) but any track with an Atom 2 instance in it. This is happening no matter what kind of AUv3 instrument I’m using. Everything plays and gets along fine until I try to save and reopen the project.
Hrmm...i guess i haven’t ventured that deep into it since the first crash kept me from really using it in Drambo. I am sure @blueveek and @giku_beepstreet will figure out what’s going on soon.
Nice!!! Just commented on YouTube! Thanks for this