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
Long press launch button and set note trigger with thru input off, or use parameter learn in AUM and tap the launch button.
Here's a video of a quick 90's DnB Launchpad Livejam I created with Atom 2.
Unfortunately I don't have the rigging to set up an overhead video of me tapping the Launchpad, so this explanation photo will have to do for now..
This takes me back! I’ll have to give Drambo a go at handling my samples. Is it a single Drambo instance?
@blueveek is this that tasty dnb you were talking about? 😂
Thanks @gregsmith
Yes- single Drambo instance with sliced Amen on track 1 (listening to MIDI ch1), sliced hot pants break on track 2 (listening to ch2), and the vocal sample on track 3 (listening to ch3).
I'm happy to give a break down of how I set it up.
Must add that this is a slightly unconventional setup, as I have not created any 'scenes' for my launchpad, and I am instead mixing and matching clips on the fly.
But it just goes to show how flexible a modular approach like Atom2 can be.
It’s coming. This was an early release by request of the forum so supporting material still being worked on.
Ask here though!
There is some helpful information in the wiki. The community is welcome to add to it to help others out:
https://wiki.audiob.us/doku.php?id=atom_piano_roll_2
It‘s probably some setting I don‘t understand, but I have this weird behavior with my Launchpad Pro MK3:
I successfully recorded a clip in one instance of ATOM. The instance is receiving and sending to channel 10 only (set up in AUM and ATOM). Its playing an instance of Ruismaker FM and I can trigger it as expected via session mode.
I then have another instance thats set to receive and send to channel 6. It‘s aimed at Model D. Here I am playing around with the Sequencer on the Launchpad just triggering notes on the lower part. So the sequencer is not actually running. But everytime I press D2 (MIDI note 51) the launched clip in the first instance stops. 😮
Every connection from the launchpad to the first ATOM clip is deactivated. So it shouldn‘t receive anything from there and even if it would receive anything why would it stopp my clip. 🤔
I can post screenshots if something is unclear. Any help appreciated.
Also the LPPMK3 is constantly sending a system message out. It’s „cable #0 0xF8 0x1 0xFF“. Is that a normal behavior? Never noticed that before.
Edit: I just realized, it‘s not just note 51. Seems totally random.
Yes. I've actually been helping Blueveek with the manual today.
It's coming 'very' soon.
Thanks for the explanation. Will have a play with it.
This is something I didn’t foresee when I was envisaging how atom2 would fit into my workflow. Since it came out I’ve gone back to starting every AUM session with a few atom2 instances which was always the quickest way to get some sounds and loops together with atom1.
After that you can just hook up the Launchpad and ‘perform’ with the clips to see what happens and comes out, creating variations as required. The launchpad isn’t required of course but is obviously more fun!
Then armed with your bank of atom2 clips, you can get LK involved and use it to arrange the clips into a song, or record out stems from your performance and move to cubasis for arrangement, or output into koala to cut up and remix - whatever you like really!
This flexibility is very exciting and atom2 was the key to unlock it all.
That is a midi clock message. Evidently the LPPMK3 is configured to send midi clock.
@zah
Yes. It will be available in PDF format.
A few questions: Does the session button light up? How does your routing matrix look like? Did you read my “Controllers” info in my first post on this thread?
Sounds like you’re monitoring the DAW in and out ports. Those are private and not intended by Novation to be used in your routing.
Clock
I sure hope it ain’t random.
So I reread your first post and set up a new session trying to fiddle around with the routing as little as possible. Here is what I came up with:
I can replicate the behavior I described above. It seems to be multiple notes that untrigger the running clip. The session button is lit. I can trigger the clips with the launchpad without problems.
And as you can see from the routing, the strange message is coming from the MIDI port. 🧐
Also kudos for your incredibly fast response. How do you manage to code while being so active on the forum? Are there two @blueveek or are you actually a transdimasional entity with a direct brain to computer interface?
@Artvarg you only need to route your launchpad into Atom2 if you are planning to live record MIDI notes into them (e.g. using the notes view on the launchpad).
If fact, you don’t even strictly need to do this either, since when an Atom window is open, it has an auto-routing option that records the notes from your launchpad.
If you’re only using the launchpad to launch clips you don’t need to do any routing into Atom, as this connection is managed auto-magically.
Hopefully the upcoming manual will do a better job of explaining the above (which I only wrote in haste).
Yeah, that’s what I concluded from @blueveeks first post. But the workflow I‘m aiming for is sequencing with the LPPMK3 and recording it into different clips. The LP sequencer has four tracks which I want to record and play back independently. The only way that seemed to work was routing the MIDI Port to ATOM and setting every channel manually in AUM.
Btw. I struggled to do this in LK too because of some timing issues with LK and the launchpad sequencer.
If it's the 0xF8 message you mentioned before, it's not a strange message. It's a standard MIDI Clock message. Somehow the LP is set to send MIDI clock. Disable that and the message will go away.
Understood.
Blueveek will be in a better position to advise because he also has the pro mk3.
I only have an Launchpad X
Has anyone tried to launch atom clips with the novation circuit? I know it isn’t the launchpad LOL but it is ... Novation 😎
Many thanks @giku_beepstreet @blueveek
Am I missing something or can we no longer preview notes with the piano keys in atom itself? I can preview notes with the pencil tool, but I want to be able to do it like I could in Atom v1.
No. But it has been requested.
Thanks for this, I now know what's going on. Atom 2 was interpreting the Pro's sequencer notes as pad presses while in Session mode. It's fixed in the latest beta, want to join to test?
It's a very simple addition, should only take a minute. I'll prioritize it for the 2.0.3 update.
I’ve just bought Atom 2 and I’m having a great time exploring its possibilities. I’ve tried to read through the the many pages of this thread, but there’s one thing I still can’t figure out:
If I load up 3 “atoms” in one midi channel on AUM (so, same track, different slots), how do I set it up, so that every time I launch a specific slot in this row, any other slot will un-launch automatically?
I use an AKAI MPD226 as my main midi controller.
@galmandsværk
'Track choking' —which is how we refer to it on the beta team, and what you are describing above— is currently only possible with a compatible Launchpad controller.
However.. there are already plans to make it the default behaviour for on-screen launching too, and Blueveek is keen to add this in an upcoming update (though I shouldn't make any promises on his behalf... he is juggling so many feature requests right now that it's unreal!!).
An alternative solution is for someone on this forum to write a hardware integration script for the Akai MPD226.
Hope this helps
Just to add to what @tk32 wrote, the main issue is that most AUM users are accustomed to the launch parameter being additive instead of "chokative" (I made this word up). At the same time, most Launchpad users are used to track exclusivity and choking. I'd like to have an option for toggling between the two modes, but I'm not sure where to put it and whether it should affect both at the same time.
So, track choking is currently only automatic when using the scripted controllers (all Launchpad Mk3s). Your options are:
Sure, but don’t expect too much from me. I don’t know how much time I‘ll find for music making in the coming weeks. 😐
I‘ll dm you my TestFlight later.
Atom 2 and chord progressions made me dig out a few apps from the iOS vaults. Exporting from Chordbot can lead to some complex arrangements.
Organizing clips in AUM and BeatMaker 3.
Check it out at 2:48!
Very handy tips thankyou.