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
Ok... I can do a lot with this thing..😷
Buttery smooth
@blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?
@ All as OT —> does anybody use program changes and what do you use for it???
P.s. I have no experience with it, but was always curious and could imagine that this would be nice to use together with atom2
Thx in advance 🙏🏽🖤🙏🏽
PC messages usually used to change presets. In a way it’s an automation tool (probably not yet implemented in Atom2, as most other automation features).
You basically send a number to a synth and it will load corresponding preset. Some synths with too many presets will allow you to define banks etc... this type of things usually detailed in midi specifications for the synth.
It was planned, but won’t be a part of the initial release. The big "automation" update is under development.
@blueveek will automation also include sending sysex?
Oooh...
Scripting lets you do that in 2.0 already!
In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.
However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot
This sounds ideal, and ‘yes, please’ to host clock, transport status.
My ideal would be - capture / rename sysex event in automation lane (to store presets) and edit in script
This app is a beast!
That’s great...always good to have s.th. for the future 😎🙏🏽
Will it release over the weekend? ☹️
We had music app releases last Sunday but its rare!
This update is coming soon
Well, if it’s anything like Xequence 2 (in Auv3), don’t even think FL Studio can compare.. it’s over 10 years now, ‘we’ have been begging IL for ‘drag and drop’ midi from the piano roll..
This is going to change everything... can’t wait..😎
I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!
i hope apple works weekends. i’m ready for it now 😃
The only weekend app drop that I can recall was Beatmaker 3: And nobody wants a repeat of that rollout!
Good work with the scripting!
Lots of predefined functions!
The “noop” contraction made me laugh
I’ve seen a few apps drop Saturday i think the most recent was loopbud
Fingers crossed. Knocking wood. Pretending to put the phone down and not care about refreshing this thread.
@blueveek : any sense of a timeframe for the black box record/playback to be available?
yes please!
Speaking of automation it would be nice (for later version) to allow separate
reverse (classic right to left and invert (upside down values) automation option , where notes are kept intact
@blueveek ?
It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.
Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.
I could be over simplifying, but that seems like all that would be needed.
With the sysex stuff I might revisit the Dixie/DX7 sequencer I made in mozaic last year, I only gave up as I got mired too deep in interface chaos, I’m thinking of having a do at it in max4live too...
I was thinking of it along the lines of what @wim is saying. Being able to record and capture sysex patches, and then send to hardware on different channels. Thinking of synths like TG33, to automate plock like triggers or change sounds on pattern changes. But to know, it's there in scripting side @blueveek.
Come to think of it, this could be a neat way to include other types of events such as bank/program changes, or CC messages that work more like P-Locks than continual values. Just add the idea of a drop-down to select the event type, and an adaptable editor for the type of message.
oooh. I like this idea a lot.
(I'm not sure how to handle it graphically however if there were multiple events occupying a single place in the timeline.)
I'm just contemplating a hypothetical here...
What if a Mozaic script was written that functioned as a translator device for sending either sysex or CC into Atom coded into a common Midi note message?
For example. One Atom instance is designated for sysex and CC use only. The instruments would I/O only to and from Mozaic, and not from that particular instance of Atom.
Let's say the Mozaic script receives CC data from a knob being adjusted on a controller. The Mozaic script would assign a single Midi note to represent the CC channel, send out a continuous series of 1/64th notes to Atom, and use the velocity value of each note to represent the CC value. When all the Atom instances are replayed, the Mozaic script reverses the process and uses the Midi note data from Atom and translates it back into CC.
Same process for sysex. If Mozaic could recognize an OnSysex event and put the data in an array. For simplicity sake, a different midi note could be assigned represent a given Sysex event. When Atom plays and Mozaic receives the note, is sends out the Sysex event stored in the array referenced by that midi note.
Perhaps that could be a way to allow some people do some stuff using CC and Sysex, while waiting for the version of Atom that contains the built-in automation functionality?