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
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?
I thought I read something about, ‘Export to Ableton Set’?
@RajahP
I also love any form of straight forward export to ableton
Sorry I don’t know the answer
But keen to hear reply
From blueveek:
(Quote) This can be done in AUM by mapping MIDI events sent from the “arranger” Atom, into the parameters of other Atom “clips”. Transpose, probability, tempo and a bunch more are already available. These emitted MIDI events could be either the exis…
Looks like it’s on the ‘to do’ list..
blueveek: (Quote) Exporting all Atoms into an Ableton session that only contains MIDI clips is doable, I've added it as a feature request to 2.x. Including the audio tracks in a host, well.. I'd have to reach out to a few folks to see if it's possible.
Just curious: would you want the probability to reset on every loop, or stick around? How do you see it comparing with a global "clip-level" probability setting that applies a probability equally to all notes?
Since all Atoms are capable of cross-process communication (yes, cross-process, not just cross-thread), sharing an Ableton set containing all Atom instances should be straightforward (because every instance knows about every other instance). I'd have to learn the file format for Ableton sessions first, so this won't make the cut for 2.0. But definitely doable in 2.x.
@blueveek
I'd like to propose another feature idea for Atom 2.x for your consideration.
This is an idea I posted about on this forum long ago, and it's one that I still think about.
Description:
Music on a piano roll is fundamentally midi notes placed on a timeline. At a basic level, the esthetic nature of music could be said to be derived from a combination of selected notes played in some particularly rhythmical way.
One of the most difficult tasks for a composer of limited dexterity, is live-playing notes to a complex rhythm in one take.
The Idea:
Provide a feature in the piano roll that will allow the composer to separate the entering of notes from the entering of the rhythm.
One way this could work is to allow for a two-step entry process.
This is the work flow I've imagined:
First - Note entry is done where the piano roll records like a classic step-sequencer. Each time a note or a chord is played on a keyboard, each appears sequentially on the piano roll, each occupying an exact same note length. The piano roll is acting as a buffer. it's holding notes and chords in a sequence. Once entered, this note buffer can be saved as a normal midi clip.
Second - The composer now wants to write their saved buffer notes to a new track, "re-playing" each sequential note on the buffer, using a complex rhythm. By some method they first select the buffer they wish to use. The transport can be started in an "audition mode" so either another track, a drum track, or a metronome can be heard.
The composer can now experiment playing the buffer notes using very complex rhythms by pressing any key on an internal or external midi keyboard. Each midi-note-on uses the velocity, and note duration "as-played" by the composer.
However, the "note information" for these live key strikes is taken from the note buffer. This allows the composer to focus only on developing the rhythm for how their note series will be played. It relieves them from requiring the skill to play both notes and timing in the traditional way.
When the composer has developed and chosen a rhythm for playing their notes, the piano roll can be set to record, and the composition recorded into a standard midi track which can then be incorporated in to the composers song.
You’re kind of describing Cykle I think
https://apps.apple.com/us/app/cykle/id1187680637
Thanks.
?? I'm looking at the manual for Cykle. I'm not seeing where Cykle records "hand played note timing" that can be applied to a sequence of pre-entered notes. Cykle also does not seem to have piano roll editing capability ??
The feature idea as I'm imagining it, (IMO) would be most efficiently utilized in a piano roll recording paradigm. It's purpose is for assisting the recording of complex compositions onto a piano roll midi track.
I’ve dreamed about this same kind of notes vs timing separation since iOS version Prehistoric. Especially since I was trying to be reproducibly musical on an iPhone 4s.
There is talk of a bundle to slightly discount Atom 2 for previous Atom owners, so you might end up with both and a discount on A2. Either way Atom 1 is still worth it, especially if you work in AUM, AB3, or Apematrix.
Export to Ableton Live Set would be a brilliant V2.0 feature! I’d settle for midi only, but if you did manage audio too, that really would be an, ahem, ‘g****chang**