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.
ATOM Piano Roll update is coming soon
This discussion has been closed.
Comments
Yes, you can do so with the "Patterns" mini map, the button for which is right next to the "Layers" panel, which works exactly the same but it's specifically for switching between patterns in the current instance. More granular MIDI control for those is planned for 2.x.
To quickly create a new pattern based on the notes/events in another instance, you can use the "Add as pattern" shortcut from the "Layers" panel (as seen in the screenshot). To copy to the global clipboard and reuse across clips, use "Copy to clipboard" (also as seen in the screenshot). I'm sure there's going to be videos about coming out.
Weekend means free time to work on Atom 2!
The more I mess around with LK the more 'anti multi-instance' I seem to become
(A single instance of a sequencer help me focus).
Sure for more than 16 midi-channels I'd need to use multiple AUv3 instances of LK but that very seldom happens.
(CPU on my Air 2 goes thru the roof before I reach 16 separate instruments).
So the obvious question regarding Atom 2 is if it's possible to have 16 different patterns each on a different midi channel running at the same time from one instance and easily switch between the patterns and edit them without interrupting playback? (I hope it's a BIG YES).
Cheers!
Think about this: there's no fundamental reason why "multiple clips on several tracks in a host" can't be equivalent to "multiple clips on several tracks in an AU". Atom 2.0 is aiming for tight integration with hosts instead of encouraging AU silos. This comes with the benefit of flexible routing, individual parameters for each clip, decoupled "automation lanes", and without the need of artificially filtering by channel (e.g. when communicating with external hardware). Regarding on this being cumbersome or not, I'm working out the details of this final piece of the puzzle with Jonatan, which is communicating the track and slot index in AUM so that each Atom instance knows it's "coordinates" on AUM's "scene launcher".
To be clear, I'm not arguing in favour of one approach or another. I'm trying to make a point that they're likely to be much more equivalent than one would assume. Ultimately, I encourage everyone to pick the right tool for their preferred style.
That being said, like I've mentioned before, I do have plans for a master Atom orchestrator, but this is likely going to come out after the initial 2.0 release.
@blueveek Gotcha...
The 'tightest possible' AUM integration imho would be to have a 'atom clip shortcut' similar to the keyboard icon in AUM windows but instead of a keyboard it could open the Atom instances that are used to control the object.
(Ie. if Atom is installed the AUv3 windows in AUM would show an 'atom icon' that is used to open the sequencer).
To keep the 'desktop' clean optionally hide all the Atom instance icons from the track view together with an option to minimize the AUM tracks to icons. Taping an icon would temporarily show the mixer and settings for a track.
Maybe I'm getting old but the constant panning and scrolling in AUM is driving me nuts and I'm more and more turning to apeMatrix or even the more traditional hosts like BM3 and Cubasis 3.
Cheers!
I think the concept of tighter integration between auv3 apps and aum is really exciting!
Let me know if there's already some way to do this, but for me i think the largest slowdown i face in a workflow with atom is the amount of clicks it takes to create a new auv3 instance. At minimum, you need to create a new midi fx slot (assuming youve already made the channel stip), press the + on that new slot, click on the Audio Unit Midi Processor submenu, search for app and click on it. So i would suggest some sort of "duplicate" feature in AUM that lets you more quickly duplicate an instance of an auv3. Maybe outside the scope this thread, but i think it does contribute a lot to the experience of using atom across many instances.
curious what other kinds of integrations you guys have been thinking about!
Very much this. Been awhile since Aum had any UX enhancements. A lot could be done in terms of # of channels in view. And I don't know if it's just me, but seeing 5x or more instances of the same app in the routing matrix is confusing as hell. Wish we could name specific instances, e.g., 'drambo bass' or 'DRC layer 1' to make navigating the midi matrix easier.
Did you know you can duplicate a track in AUM? Tap on the track name, and pick "duplicate".
Yeah, the balance is figuring something out which makes sense bound by the AUv3 standard, can be used by other developers too, and fits the vision each of us has for their app. Note that we're still exploring stuff here. So far the clip colors, context naming and indicators are in, along with up to date AU naming in the MIDI control settings, and we're still exploring the track/slot stuff.
A lot of the heavy-lifting with regards to naming can be done via the context name (e.g. long press on the titlebar in a window to rename). But that doesn't change some of the other bits shown as part of the label: the AU name itself, and some AUM routing info). One of my beta testers did mention that it would be nice to streamline the content shown in the MIDI routing panels/views, and I tend to agree.
🤤
%)#’ks
@blueveek sorry if this has been answered already.
How well does it perform with Cubasis 3? Could we do the same things you do in AUM?
Yes, everything should work the same and my testers are checking everything. The only limitation is the number of slots per track that Cubasis allows for audio units in general, but that should not be an issue once this is enabled in a 2.x update: https://forum.audiob.us/discussion/comment/879926/#Comment_879926
Nice one.thanks for the elaborate reply. Keeping an eye out for the release then.💪🏾💪🏾
Got my Launchpad yesterday and love it so much! Amazing thing and can’t wait to have this perfectly integrated with atom 😳
I've realised this AUM colour feature for Atom2 is also ideal for Mutemaster, and sent them a feature request
So potentially Mutemaster instances when they are unmuted on the channel could have a background colour signifying this and change colour when it's off... for me this will significantly increase the usability of MM.
Sweet! Here's the implementation details of this new "standard" we cooked up, for other devs:
Context name "xxx;yyy;$FFFF00$" will display "xxx" beneath the icon, "xxx yyy" in the title bar, and change the node's background color.
Leave out xxx, like this: ";yyy;$FFFF00$"
or leave out yyy: "xxx;$FFFF00$"
or only use a color: "$FFFF00$"
Thanks!
I will send over this info
Also anything where you could record into the app could use this colour feature too, I can see it being very useful in Gauss so you can see which instance is recording, when the gui is closed.
Perhaps @brambos might be interested in implementing it
@blueveek:
I am very impressed with what you are doing. Can you kindly clarify if Atom 2 can overcome the midi limitations in Cubasis 3, which as I understand it, do not permit midi information to travel within individual projects? I've read your most recent replies here, but am not sure if I've correctly understood you. I can see that AUM allows this, but am interested to see if you have been able to somehow circumvent the limits of Cubasis 3 and have one instrument channel feed midi into another midi instrument channel.
A little while ago I've built another plugin, called "MIDI Tools", that had a "MIDI Bus" AU which already does this: it allowed you to send midi across tracks in Cubasis (and BM3, and other apps with similar limitations). But tell me more about your use case so I can understand what you're after.
@blueveek: - thanks for the reply. My current use is to have single midi track with my main chord progression running along it and then feeding this to other instrument tracks with midi arpgeggiators, midi processors, custom Mozaic scripts and other AuV3 instruments. It's fairly straightforward in AUM, but I'm now interested to work with Cubasis 3 and take advantage of its automation recording which is where AUM cannot compete. It looks like the Midi Bus in Midi Tools would work - I hadn't seen it before - or perhaps you think Atom 2 would do this better - I like the idea of a central midi clip triggering other midi sub clips for additional control and performativity.
Right. My recommendation is to use Midi Bus: it should also work with the midi clips in a track inside Cubasis itself, no need to use Atom or any other custom MIDI AU for your chord progressions for example.
Atom 2.0 instances can be driven by other Atom instances (or other AUs), and can access state (e.g. the midi clips, etc.) from every other instance, but in 2.0 there's no way to have them trigger each other without actually connecting them, so you'll still need Midi Bus when working in Cubasis. However, I've mentioned this in a previous comment: the plan is to offer a centralised hub for clip launching in a 2.x update, which is likely going function regardless of a host's MIDI routing capabilities (think of it as a built-in Midi Bus).
Blimey. I bought Atom a couple of weeks ago to get my head around it before the update came. I was looking forward to midi import and pitch bend. Now you’re all talking in another language like Atom 2 is gonna be totally different to what I thought I was buying.
I think I’ll wait for @Gavinski to come to the rescue when this thing is born....
@blueveek: thanks for your kind and thoughtful replies. I've just bought Midi Tools and will see what they can do.
Don’t be worried. Atom 2 still works just like Atom 1 out of the box. The difference is in the deep levels of customisation available under the hood (if you’re interested in poking around)
If you don’t want all that advanced stuff, you can simply use Atom2 as a piano roll with some excellent new quality-of-life features.. like midi import/export.
Cheers @tk32, that’s good to know. I’m looking forward to the poke-around. I’ve been on a steep learning curve since lockdown began and I’m enjoying embracing different ways to make music and I’m sure all will become clearer when it arrives and the forum is full of tips. I really hope the draggy thing at the top is easier to drag to extend the amount of bars... 👍
@blueveek: will the midi import feature in Atom 2 automatically split multi-channel midi files into separate midi clips or will we have to separate multichannel midi files into distinct single midi files before importing?
So far Midi Tools/Bus works very well inside Cubasis 3 though perhaps it uses a little more CPU than anticipated. Thanks.
There’s so many ways other software can create/save midi files - it’s a hodgepodge of ad-hoc standards. Can you DM me an example midi file and I’ll let you know?