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
Not sure why it's not ok for people to ask the question every now add then though? It's just like an informal vote for the next feature really isn't it? I've bought Atom 2 and while I'm happy to be patient I can't actually use it in earnest without automation editing so every time I see an update on this thread I'm checking it in the hope that there's news on It. There's no point creating a separate thread specifically about automation editing - it will just drop off the first page and there's no guarantee anyone will update it. All we can do is wait add keep checking. And of course the dev should take a break if/when he needs to🙂
👍🏻
The CC editing isn't imminent. The discussion about this resulted in several people questioning the dev's commitment to getting it done.
If you honestly can't see why that would be irritating to someone that has been working uber-hard then I don't know what to say.
Trust that he is working on it and will get it done.
One could ask "has there been news?" if you are simply curious. And if the answer is "no news",come back in a month. Asking for time estimates when the dev has said that he can't estimate it, is irritating whether it seems to you that it should or not.
Lol.
Beautiful. Thank you.
Lol, if only it was also a chopping sampler, with a drum machine, and 24 Osc Synth, lol.
Definitely.
Ok if it's not imminent, that in itself is useful additional information thanks. I wasn't part of the original Atom 2 beta test and had previously bought Atom 1. I just made a working assumption that a core feature that was present in Atom 1 would be there in Atom 2 and was pretty surprised when it wasn't. I don't use the AUM clip launching stuff etc at all - my reason for purchase was to use it as a better MIDI editor than the one provided by my DAW (ZenBeats), which is one of the main use cases listed in the app store.
At no point have I personally asked for a timeline or questioned the Dev's commitment by the way. I've simply responded to other posts where people have asked about Automation Editing to say that this was the most important 'missing' feature for me too. As a former developer, personally, I'd consider this useful free feedback which would help me understand my users priorities rather than as a source of irritation but I guess we're all wired differently.
Anyway, I look forward to the day when I am eventually able to use Atom 2 in my projects. It's clearly a great app, just not usable for me in its current incarnation.
I just noticed a couple of weeks ago those lovely motion graphics icons in Atom. And I couldnt stop that grin on my face 🙂
End of message.
Yeh they are pretty lovely, and quite subtle
.....
....
Atom 1 did not have cc editing or even recording. So, it isn't the case that Atom 2 was surprisingly missing a key feature present in Atom 1. The cc recording/playback that was recently added (and which Atom 1 was missing ) paves the way for automation editing.
Ok I've just checked Atom 1 and fair enough, you're quite correct about that . What I was remembering was the Velocity Lane in Atom 1 which allowed you to edit the velocity of multiple notes simultaneously. At some point earlier in this thread there's a post saying that this will be reintroduced into Atom 2 (editing velocity one note at a time is cumbersome) and that this would probably also be the mechanism for implement CC editing (as is common in other DAWs such as Cubasis). So I was getting the two things somewhat conflated because I'd got the impressions they would both be implemented together to address both Velocity Editing and Automation...
Hey there,
I'm still struggling to find the "perfect" workflow with Atom-2 for me.
The thing that bothers me most right now is to find an easy and fast way for switching the midi-input between atom-instances (I'm using a korg nanokey studio).
Does someone know a good solution for that? Could it be possible to write a controller-scheme for the Nanokey Studio which is capable of that (I noticed that midi of a Launchpad pro mk3 works for the active atom-instance) ?
Thanks and All-the-best @everyone
I feel like a bit of a numbskull, is there a way to set the targeted channel other than hiding all the other channels?
It's pretty easy if you can hook up to a PC or Mac to configure the pads of the NKS to send something unique (such as changing them to channel 16), then map those to the AUM "Show Plugin" parameter for each instance.
I'm not sure a custom script would help much.
[edit] oops, I misread your post. I thought you wanted to bring the instances to the foreground. In light of that, I think a script could help and wouldn't be too hard to write.
script
I’m integrating this with my launchpad mini mk3. I will document / stream my setup soon
Answering my own question. The instructions are slightly different from what was posted:
Is there also some control at the top-left (per @blueveek's post) that is supposed to be available to change the channel targeted for editing?
The channel chooser might be more discoverable (for clipboard actions) if it were also available by long pressing the channel indicator that is found at the top-left (maybe via dropdown menu?)
@Hannes I used a Mozaic script to do that called midi multi cast. You can set one input and switch between output options which you can set to any channel or multiple channels.
https://patchstorage.com/midi-multicast/
Thanks @wahnfrieden and @SimonSomeone for your hints regarding Mozaic, both scripts could work in my case as far as I can tell. I follow discussions, patches etc. about Mozaic for month now and assume/fear that it is time for me to buy and face it .
@wim: Thanks. I will have a look at the existing Launchpad-scripts and try to find out whether its possible for me to extract the "foreground-part" out of it.
If someone had created a atom-script for a similar case I would be highly interested!
It has so many handy uses, I'm so glad I bought it. And usually someone has already made a script for that will do what you want. And if not some super helpful person will likely do it for you...
Also, just casually commenting "I haven't been around for a while / this is a long thread / [insert other excuse], so can I just pop in and ask again if my favourite feature is implemented yet" simply says "my time is more valuable then yours / I didn't even put in the absolute minimal effort of reading the change logs of the updates before asking".
Not that it's illegal by any means; just doesn't come across as very cooperative, esp with devs who seem to live a full second life on here just to serve us alongside their day jobs.
Just my very subjective two cents anyway.
Semi-duplicate so deleted!
As for failing to read every post in an 80 page thread, happy to plead gulity as charged to that one
I suspect pretty much the exact opposite of the above has been happening in relation to the change logs though. @blueveek very helpfully publishes detailed change logs here for each release and, in contrast to the way you describe it above, the posts asking about CC Automation are probably prompted precisely because it hasn't been mentioned in the change log.
@espiegel123 has comprehensively explained that there are good technical/architectural reasons why things need to happen in a certain order and that's absolutely fine but you're basically saying 'stop asking about this feature' aren't you? I just think that's unrealistic, especially when it's such a fundamental feature that a lot of people appear to be waiting for. Some people are bound to keep asking because by the time we're on page 100 of this thread these exchanges won't be immediately visible and not many people are going to check every post to see whether their question has already been answered. In any case in a month's time the answer may well have changed.
Personally I thought this was pretty much what this forum was for? Discussing apps, suggesting/requesting additional features you'd like to see implemented etc. Obviously there are lines that shouldn't be crossed and we shouldn't be haranging developers or accusing them of bad faith etc (agree with @espiegel123 on that 100%) but other than that I'm struggling to see what the big deal is...
Atom 2 really is a beautiful piece of kit! Here’s an alternative from the normally way its probably being used, but I think its still really efficient:
Could some one pls explain the different between track and channel? How do I set it so track 1 sends on channel 1 and track 2 on channel 2 etc? Or am I misunderstanding something?
For the life of me I cannot get track 1 on channel 1 and track 2 on channel 2 and the screen shot in the manual looks very different to what is shown in the app when I click on the track. Erm.
Thanks as always
Hello, I’m a little confused about this multichannel update. So I have one instance of atom 2, I set the track, record stuff into slot 1. But when I select slot 2, the midi data from slot one is still there, should it not have it’s own midi clip? It seems like all the slots in one track share the same midi info? Not getting it sorry.
Atom2 has a very flexible architecture that can be wired in many different ways depending on your preferences. Some of these configurations are internal to Atom -- for example, deciding which midi channels Atom is sending MIDI to -- whilst other connections must be made at the host level - such as the invisible wiring that routes MIDI from Atom clips into your desired plugin(s).
In a way, the definition of a 'track' is how you define it as the composer, and will also vary from host to host. For example, is an audio channel in AUM always a 'track'? - sometimes not. And is a bank in BM3 a single 'track' or multiple tracks?
To add to this confusion, Atom2 has its own definition of tracks (columns) and slots (rows), and this is used to both determine how clips should choke each other, and also set each clip's X and Y coordinates when using Atom with a compatible Launchpad controller.
Anyway, enough of my philosophical ramblings. Here are some quick descriptions of the most common Atom configurations.
Note - if you are using AUM (or Apematrix) you will need to manually connect each Atom clip to your audio/plugin channel using the host's MIDI routing matrix. If you are using other hosts (Drambo, BM3, etc) this is not necessary because MIDI plugins are loaded onto the instrument/plugin channel directly.
1. Multiple atoms per instrument (each atom is a single clip).
2. One Atom instance per instrument (where each atom contains multiple switchable patterns)
3. One Atom instance controlling all instruments at once (multi-channel mode)
4. Your own bespoke combination of the above and/or other setups
Thanks. So for option 3 how do I draw on different channels?
For method 3 (one atom controlling all instruments at once) there are multiple options for getting your notes onto each of the 16 MIDI channels...
Perhaps a kind soul could add a recap of @tk32"s posts above to the wiki article:
https://wiki.audiob.us/doku.php?id=atom_piano_roll_2
I think we’ll be skipping a few version numbers with the manual. so many changes to get through!
The next manual update will be 1.3 - and ready soon.