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
What controller are you using ?
@zah
Here’s the quickest way to insert bars mid-pattern...
I was really hoping to get some audio from this too. Art in the pianos roll and pressing play makes me smile.
This is very good news
Mine is an essential 61 too! Wow, great use for the display and buttons/pads. I’m not using atom2 at the moment because the lack of sustain pedal and other CCs... I use piano sounds or other sounds but with expression (after touch, mod wheel, Pb... so I don’t have a workflow yet, But will be my no1 sequencer the moment @blueveek implement the Backbox CC record/playback. Also will try you Mozaic script If I learn how to edit it. thanks!!
@blueveek i believe i was one who requested pattern change by midicc/note. in your beta, is it possible to put a pattern in a different slot on the same track? i.e. track 1 patterns 1-8 would take up all 8 slots on the launchpad column/AUM channel?
if so...this would be more than "very good" news
Well, several. You could go for the LaunchPad Pro MK3.
So I’m getting more into this. Thanks Tom for your help. Is there a way, maybe I missed it to scrub to a part in my timeline to audition new notes or parts I have put in? Meaning I have one Atom as the main sequencer and I have it playing others just fine.. but when I want to go to a part and try out new phrases or what ever the cursor goes back to the start all the time.... I know some silly setting I am missing.
Batch export MIDI from multiple instances at the same time is planned, it's easy to do.
Would you prefer a zip of all clips, or a single MIDI file with each active pattern on a separate channel? The beta now already exports all patterns in a single instance as separate channels in a single file, so I'm wondering how you'd prefer batch export to work alongside this new feature.
Have you tried using the loop markers to focus only the section you want to work on?
Is there something going on in the universe that I don’t know about?
This is the 4th time in 24 hours this line was used around me in the past 24 hours (once by myself)
"Auto" Toggle/Hold mode.
As I don't have any Launchpad, it's a bit difficult
Probably the easiest would be to code this directly in the Launchpad ..?
The clip "needs" to be in HOLD mode.
But to do it within Atom, in the LaunchpadPro Mk3.js file, look for the functions didPressPad and didUnpressPad
Then it's "just" the question to store the
timestamp
for that clip on pad pressed and check when we get it unpressed.There is a little more to it, but not that much
In these 2 functions it should be done within
if (isSessionView) { ..
afaikfor the timestamp, 5000000 represents 500 msec (half a second)
To use with a "standard" controller, using the Launch Note, this could be done with Mozaic or StreamByter(not 100% sure)
All keys are the same. It's only the intervals between the notes that determines the listener response. A minor = D Minor = any other minor chord.
This book explains it all really well How Music Works: A listener's guide to harmony https://www.amazon.co.uk/How-Music-Works-listeners-classics/dp/1846143152/ref=nodl_
No need to read that book. I believe Nigel.
Nigel? 🙂
How soon we forget...
Right - all makes sense now
hey man, I know you are obviously busy with all the feature requests and automation stuff. But just throwing this one as a reminder, any updates on the Launch Clip MIDI binding in AUM or otherwise?
@blueveek
Forget about all this, I can just use a single in and out in a js file, send messages as syssex(with port info) to MidiFire that will then send back to the appropriated ports: Host, tracks, command, to specific plugins..
As both Atom's js and MidiFire(64 ports!!) have zero latency, this should do
Are we not going to have cool tips n tricks videos from @blueveek or @tk32 to make things easier and more exciting for us?
Next version will include iOS 12 support.
Keep in mind that a MIDI channel is not a "track". It's just metadata. All this "channel is a track" stuff is relatively old nomenclature, which I consider obsolete in the digital era.
Why? For example, anything that relies on MIDI channels for separating tracks won't ever be able to support MPE.
This however is possible I'll log it as a feature request.
Perhaps I could add a
launchClipImmediate
function that overrides the trigger/release beat quantum settings?Adding the port ID will retain backwards compatibility with all scripts. I can do this, no problem.
I suppose by "ID" you mean the name then?
Hey! That thing is still logged in my features board, just not prioritized. I did have a look into it back then and indeed launching via parameter mapping has different semantics than launching with dedicated MIDI events. Unifying those is perhaps possible, but not a priority yet. Hope that answers your question.
I definitely would, but I'm swamped with my day job, and I imagine @tk32 and @winconway are as well, maybe even far more than myself (you might not know, but this is a weekend hobby project by financial necessity; iOS development is ridiculously unprofitable for apps like Atom).
Thank you, @blueveek.
Didn't think of it, but yes, this could be very handy.
In that case, I would really appreciate !
For me the index of
const INPUTS, const OUTPUTS
would be fine.Whatever is easier/better for you.
Edit: in case a port is not available, the index should remain the same.
I think the nomenclature is confusing, so let me clarify it now.
Emitting multiple patterns at the same time from an AU, in a way in which you can redirect them to separate instruments, while future-proofing for MPE, is fundamentally impossible. It's maybe alternatively doable with multiple MIDI outs, but the number of those isn't dynamic, I doubt you want to see some arbitrary (e.g. 16) outputs for each Atom instance in your routing matrix – it's not great UX.
So perhaps this makes it clearer why I insist on a clip per instance (among other reasons).
I doubt Jonatan is open to such exotic integration between Atom and AUM. But if you'll open the instances beforehand, then it's definitely possible to populate other clips from within a single Atom. So this is the way to go I think.
since i now use atom on every project and am highly emotionally invested in it i was wondering is there a way to become a beta-tester?
You wanted to do pattern switching in a single instance using CC messages, right? Drop me a DM with your TestFlight email.
@blueveek i mentioned this on Discord but didn’t tag you. I think a way to jump between instances via the Clips view would solve the multi instance concerns being raised. You can already see all of the midi tracks in the Clips view. A one click jump to each Clip instance to be able to edit would be a really good workflow improvement IMO.
I think Win said something like this has already been suggested so just wanting to add my support for the idea.
@blueveek I have been playing with Atom 2 inside NanoStudio 2 where I have multiple Atoms per track and the track data is used to trigger them in hold mode. It looks like you are hinting that pattern switching is on the horizon which would be great as I could then have just a single Atom per track. The problem on NS2 is that its AUs do not receive CCs, only MIDI notes. Some AUs have worked around this by allowing you to send a MIDI note + velocity as an alternative to CC + value. Is that something you would consider if pattern switching is on the timeline? Thanks.
You WILL be able to use either CC, program (patch) change or notes
Using cc: cc = 0 , cc value 0-127 = pattern
Using PC , value 0-127 = pattern
Using notes : pitch (0-127) = pattern
Sometimes I’m wondering if anyone understands what I’m writing
That's really good to hear, thanks for the info. So rather than a clip having a single trigger note, it will respond to n trigger notes, one for each defined pattern? If so then my scenario would work like this:
Today:
NS2 Track 1
Atom instance 1 responds to note 0
Atom instance 2 responds to note 1
When the pattern change feature is implemented:
Track 1
Atom instance 1 responds to note 0 or 1 and switches patterns accordingly
Much neater!
And for Drambo users it’s even more fun... oops