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
Yes, I think that confused me even more when testing my issue. I did test with note triggers in NS2 though and have the same issue with the pattern changes being missed when they occur at the same time as the hold note, i.e. this does not work:
This does work in MTS though so I wonder what NS2 is doing differently.
Sorry @blueveek , I hope you haven’t spent too long on this. One of my patterns was set to ableton or launchpad rather than hold which I think explains my issue.
Edit: I also realised I should be able to set the change and hold note to the same value and just set the velocity to pick the pattern as I am not doing anything fancy.
Alright...I was confused at first. So you still need to have individual instances of Atom2 running in order to play Patterns to individual Midi Channels in Drambo and AUM...so I have set it up in Drambo by binding Atom to the MAIN view, and then adding a Channel Filter to each instrument which receives Midi from it's Atom Midi host...as so:
MAIN with Atom instances:
Instrument Rack with Channel Filter:
I was hoping to have all my Patterns in 1 instance like it is in Helium...but it looks like the stability is there now...so I will just save a Template of the layout in Drambo for easy recall.
Thanks @blueveek
How do you record into Atom ?
Interesting Drambo setup @echoopera
I normally just put my Atom instances at the start of each track's rack (just before the Midi to CV module). It just works, with no further setup required.
I'm curious what the advantage is of putting them on the main track like you have done.
Atom 2 + NS2 hybrid works really well from what I have seen so far. If you have them both and are looking for more timeline flexibility yet still want the modular side of things then do give it a try:
The utility provided by NS2 clips means you can store whole sections of clip launch instructions together logically (and name them, which I didn’t show in this example) and move them around the timeline. You also benefit from the ability to alias clips so you can have one clip that can be repeated throughout your song yet you only need to change one of the clips to change them all. This way you really are repeating the minimal amount of data to arrange your song
In the example above I have one Atom per track, each listening on note zero for hold triggers and also note zero for velocity pattern triggers, meaning I only need the one note to trigger and change pattern.
The NS2 loop bar can be used to cycle part of the song to let you build up the tracks.
You can alternatively have a single control track with a MIDI send to all tracks, each listening on different trigger notes.
I’ll be trying MTS + Atom next.
I don't understand why you did it that way @echoopera. It seems a lot easier to just put one instance on each track. Then you simply create patterns in the instance. They will automatically associate with any Drambo patterns you create and automatically launch.
This is totally seamless and intuitive integration in my opinion. One is either controlling via Drambo's pattern or via Atom's. It's like the piano roll module I envisioned might be released in Drambo some day.
The way you have it set up is confusing to me. But if it makes sense to you then 👍🏼👍🏼
we need a manual for each host and daw
some compendium of tips and tricks would also be nice. atom wiki?
It would be interesting if in Drambo's hamburger view, the main track would stay at the top, you could see both Atom's view and your track view.
But as I see the routing, using an external keyboard and all tracks will "ring" at the same time. Unless Midi get's thru an Atom script, using receive* functions ( I think the launchpad script does it )
This is the beauty of Drambo
We can configure it however we see fit.
Honestly, for this layout, I chose the MAIN view so I could quickly access Atom instances from a single view. I also wanted the ability to easily control the volume of all of my instruments in a single view as I was editing my Piano rolls.
@tk32 There is method to my madness everyone
@blueveek @tk32 2.0.6 🎉
I’m pretty sure that there’s must be an easier way to use multiple clips within a Drambo pattern though. I also noticed the same problem as @MisplacedDevelopment did. Atom is switching patterns after the midi notes are generated (I had noticed the same thing in aum in earlier versions too). Sometimes it works but it appears wrong more often than right.
Here’s an example that shows both (the first note of each loop is accented, each clip contains only one note different from all the other clips, except Drambo pattern 3):
https://www.dropbox.com/s/erbp614781kdrpv/Atom Test e.drproject?dl=0
Cheers
@blueveek is there a way to add switching not only for playing patterns but also for editing? been thinking about routing a stream of midi data to atom and recording it to different patterns. could be useful for recording those evolving generative melodies, takes and for sort of comping.
Nice. Or if we could just press a button which Captures what we just played into a new pattern. Kind of like Ableton 11 and the Capture function.
We "badly" need an "Auto Focus" icon(show, edit and record current playing pattern.
In the meantime you can try to select a pattern manually , but you need to be precise, as it will record instantly
another variation of this could be something like ‘make a new pattern from selection’
You can always use the clipboard, or duplicate, then under process, use one of the various crop function.
Ah I cant keep up lol!!
Is the Drambo integration and overhauled patterns in the manual or is there is tutorial videos for setting up pattern switching using notes, CCs, PCs and even velocity.
Just not enough hours in the day!!
@skiphunt Well, here goes...
I find the insinuation in your post incredibly disrespectful to the developer. He chose the cheapest upgrade bundle possible which was one dollar! He completely kept his word in making the upgrade as close to free as possible. He then graciously responded to your complaints by gifting you a copy of his app.
You come across as unempathetic and entitled. This is the second time in recent weeks that you have received a free code in extremely bad faith. A huge amount of work has gone into creating Atom2 and Beatcutter.
You have been a member here way longer than I have but I don’t recall having this reaction to your posts. I genuinely hope all is well.
Gus
Let it go dude. If you have a problem with me or my posts, complain to admin and reference the posts you take issue with. Or, better yet... just hit the ignore button on my user account.
Take care. 👍🏼
Great with the new pattern switching. Looking forward to playing around with it.
One question: is it possible to name the individual patterns?
I’m thinking about making an individual Atom for each instrument (drums, pads, keys, bass, etc), and keep all the song elements within each Atom and then control them via a master Atom or LK. But I need some sort of overview, so the possibility of giving them short names (main, verse, intro, and so on) would really help.
/ edited for clarification
One more question (sorry...): is there a reason why colouring the Atom icons in AUM makes them a muddy colour instead of e.g. bright yellow like when I colour other plugins? For the sake of a quick overview, it would be great to be able to keep e.g, both my drum app and the Atom that controls it in the exact same (bright) colour.
I’m using it this way as well and so agree that it would be useful to be able to name a pattern.
@blueveek What is the most efficient way of importing a new MIDI clip into a pattern? If I import one then the existing patterns are removed, which I think is by design. At the moment I am considering whether I should have an instance that is used just to load things into and then access those things in other instances either via the clipboard or maybe layers?
I open a separate instance only for importing midi clips. Import, then switch to the instance where I want the pattern. Tap layers, the imported clip will be there with an “Add as Pattern” button. Repeat as needed. It’s quite quick once you get the workflow down.
Thanks @wim, that’s what I’m thinking.
Edit: yeah, this works nicely
I’m surely being very dumb, but what’s a ‘PC’ when it comes to a method to change patterns?
Can we assign different notes ourselves to change patterns in the Note change mode? What do the default ‘note 0’, ‘note 1’ etc mean? How do you route something to activate the changes? This happens automatically in Drambo when an Atom is on a track and the note change option is chosen, but it wasn’t immediately obvious to me how to set this up in AUM.
So pleased to see everyone enjoying the latest update.
I'll try to give a few quick answers to various questions - although you should probably wait for Blueveek to get the definitive take on these...
PC is for program or patch change, midi 0xC0
The pattern trigger is a modulo of the number of patterns. A modulo (%) is the rest of the division of a number.
If we have 5 pattern, to trigger, for the first one you can use note 0, 5,10,... and the second 1,6,11, ....usw
But the easy route it just to try some note, see which pattern is selected and adjust.
The problem with not using note 0 (or pc 0) and up, if you change the number of patterns you will have to adjust again.
Can't forget about it, it's prioritized accordingly in my Trello board
I know you're just teasing, but just FYI, there's no way for me to reply to TestFlight feedback, Apple doesn't provide this mechanism in the developer portal. I'll have another look to see what's happening with velocity-based pattern switching and will fix this in the next version.
I'm glad everything is working. Just FYI, the clip launch settings are per-clip, while patterns are always in immediate-gate switching mode (with legato), but that's the expected default. I will however have another look at this.
Some background: I suspect some hosts tell AUs that transport has "stopped" when looping back zero or the loop start point, even though that's not accurate. Apple provides specific states that need to be communicated for paused, playing, looping etc., but as far as I can tell hosts avoid them because very few AUs actually make use of them (or do it correctly), so they're unfortunately forced to optimize for the lowest common denominator. The way they do this is more or less up to the host developer's interpretation of what the lowest common denominator is.
The unfortunate reality is that hosts adapt to misbehaving AUs, which makes future AUs adapt to "misbehaving" hosts. Kind of like the 'quirks' mode in early 2000s web development where bugs become the standard, and every browser is forced to replicate the bugs of every other browser to keep everything consistent. It's a state of affairs that makes me quite sad.
That's a very clever hack! Glad you discovered it, the idea never crossed my mind.
Yes, I'm very happy to see this setup working for you. Some folks might keep each Atom track before the MIDI-to-CV module, but the way you've set it up also makes sense.
As an aside, I hope that at some point more users will understand that MIDI channels are not, in fact, MIDI tracks, and that this way of filtering MIDI is not future proof. For example, MPE assigns each MIDI note a different MIDI channel, so unless you want to record each individual note into a separate "track", associating MIDI channels with MIDI tracks makes zero sense (if you care about MPE). The only way for audio units to properly separate tracks and still keep everything together under one roof is with MIDI output ports, which are not dynamic (it's always a fixed number), pollute the global scope, and are not cross-host compatible, which is why I'm staying away from them unless something changes with the current AUv3 landscape.
Nice. I love this setup, and it fits well into my philosophy that 'song mode' is a concern solved at a different level of abstraction, either through another orchestrator AU (like how many use LK to drive Atom), or at the host level (like how you're using NS2 to organize all Atom patterns into a song).
I love this idea. I was just discussing with @tk32 yesterday about how "pattern from loop" or "pattern from selection" is a great shortcut instead of fumbling around with the clipboard.
"Slice to patterns" is the MIDI equivalent for chopping audio into multiple samples and triggering them. The way I see people using this is recording one (longer) melody, slicing it up into separate pattens, and then playing each bar/sub-pattern in varying orders. Mayhem!
Does it still happen if you set the tempo to something like 121.1? Me and @giku_beepstreet had a few issues in an older beta where rounding errors made it so that the pattern change messages that Drambo was sending could get lost. The way Atom implements it, it should be perfectly sample-accurate, but same could be said about Drambo, and perhaps we just don't match our "rounding" behavior
I'll investigate.
Not yet, but planned. However, for stuff like that perhaps you can use the "Duplicate Pattern" and "Clear Pattern" parameter controls, along with the new "Play Pattern" parameter. That being said, as with all MIDI-to-parameter mappings, they're not intra-frame sample accurate as far as I know so the timing will depend on your buffer size.
Not yet, planned.
If you search through the old "Atom 2 is coming soon" thread, you'll find two screenshot where I show both variants, and the bright node color mode that you're referring to was almost universally received as being worse than the more subdued color. When designing the color integration with @j_liljedahl, we both agreed that the darker colors look better as well. But perhaps there should be an option?
The magic clipboard or 'layer to pattern' approach are both valid. However, something similar was brought up in the past and I do agree that perhaps loading a file should be an additive operation.
Blimey these updates are very cool.
Q) is there an example how to use the new master clip feature?
You can also always just draw your arrangement notes at any pitch in your Atom orchestrator (e.g. starting at C4), and using the global transpose for it to pitch down the output to affect the right patterns. Find it in the top-left clip menu.
Bonus points: automate Atom’s global transpose parameter(s).