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
Cool. That was a feature I wanted him to add too. He’s awesome at doing this, so he will certainly make it possible.
So , I am trying to import midi files from Piano Motifs into Helium . Seems that no matter which "share" option I choose from Piano Motifs , I am able to import them to Helium , but when I then try to drag and drop the "accompaniment" to Track 1 and then the "melody" to Track 2 , I always get a popup that warns about replacing everything and then it does ..... How do I drag and drop the 2 different parts , files , to different tracks without ALL tracks being replaced ?
Thanks...
Version 1.28 is out:
Added the public.data type to imported documents to see if it solves the Share Sheet issue.
You can now share MIDI files from AudioShare using the share sheet (Helium now shows in the list).
Fixed a clipboard controller issue when copy/pasting an entire whole state.
Added experimental LaunchPad integration.
Added a collaborative mode for sharing LaunchPad with Neon (Select from Launch Button Options).
Added a new Deep Copy (multi-track) and Deep Paste options (long press copy/paste).
Deep Copy copies the selected loop of ALL tracks, both notes and controllers to the general clipboard.
Deep Paste allows you to paste notes and controllers for a single or ALL tracks.
The import MIDI song prompt now tells the user where the files were stored after import.
We now accept more specific UTI types from other apps with drag and drop.
Haven't got time to trawl just now so … does Helium support midi in? Individual sequences being triggered by external midi controller in my case (and not locked to host transport timing if running in AUM for example)
Yes, this is what is so great about Helium (for my use case, at least). There are several options available that allow you to either trigger the sequence holding the gate open or stop the sequence if you let go of the note. (I use Mozaic to set my gate to a set length so that I can use a foot controller to launch sequences separate from the transport.) Take a look at the YT videos about "snapshots".
Great thanks, sounds like it could fit the bill nicely
With snapshots it seems triggering is limited to instant or quantised to end of snapshot. Is there any way to quantise a snapshot change to bar or beat?
Yes you have to control them by midi, trigger notes list is in Helium help. You can use any virtual remote like Xequence keys.
See that video I made on some of my song creation workflow
👆 what @Janosax said. I have to hand it to Paul—he nailed the snapshots options in Helium. I suspect it flies under the radar a bit but for those of us who need flexible tools for live applications it’s nice to know that someone pays attention. Thanks @4Pockets !
@Janosax Thanks for the response and video, but I want to be able to switch snapshots mid snapshot quantised to bar or beat. Your snapshots are 2 bars long and switch at the end of the snapshot from what I can tell.
For example near the end of bar1 can I jump to beginning of bar3 by triggering snapshot2? I think it will wait until the end of bar2.
Do you mean you want to ‘get off the grid’? I’m wondering if that can be achieved with remote loops functionality simply by unselecting Remote Transport Control (RTC selector under Remote button)…. ?
Yes! This is exactly what happens. I trigger loops with no transport, completely unquantized. You can also switch quantized to the beat.
@wired2moon I use snapshots as "scenes" so they can be quite long. I have other apps with "scenes" also. I want to use a single trigger to jump all apps to a new scene (quantised to beat or bar) at any time during the scene (ie not necessarily at scene end)
My understanding is that Helium currently only offers instant or cue change for end of snapshot changes. I want to know if there is a way to send my trigger during bar 3/8 and have the snapshot change at end bar3 instead of instant or waiting until end bar8.
The launch button options have a launch quantize option for BAR, BEAT, IMMEDIATE. I want to know if I can do this with snapshots.
@lukesleepwalker How do you quantise to beat?
C3+ octave is quantised to end snapshot
C4+ octave is instant
C5+ Cue one shot play?
C6+ Immediate one shot play
C7+ Gated one shot play
I want Cue next beat/bar but that doesn't seem like an option?
The RTC button doesn't seem relevant to what I am trying to do.
Ah, sorry, I misunderstood your first question and missed your second post with more detail. Helium does not do what you want, sadly. It either snaps instantly or to the next loop point. That launch button quantize feature does not affect the launching of snapshots; my understanding is that it works with the launch buttons in AUM channels. What you are asking for would be a nice addition though; contact Paul about that one.
@lukesleepwalker No problems. Thanks for clarifying.
Cheers @lukesleepwalker and @soundtemple
Out of interest, any idea how much of the above can be done with StepPolyArp Unit?
I think you could do it with AUM Helium launch button and several Helium instances in stack mode, on several midi channels.
@soundtemple I’ve found a way of doing it, video is being uploading.
@soundtemple and @lukesleepwalker here it is!! Latch from Midi Tools or similar is needed for proper midi remote, as AUM launch button is built for launch button direct trigger or midi sequencing in mind.
@Janosax that’s wild! Very cool that it works… You got me thinking about other ways to use those launch buttons and stacked Heliums now.
@wired2moon Good call! SPA is the other app I use all the time for these use cases. In addition to the stuff you mention, it has some fabulous randomization features that can nicely mix things up in a sequence that repeats for a while. It doesn’t do what @soundtemple asked about however. It’s either the end of the loop point or instantaneous.
What are the steps to record multiple channels at once in different midi tracks?
This is not possible unfortunately. I already asked for this a while ago, but it seems that it’s perhaps not easy to implement as it’s not added yet. You have to use multiple instances for that and map record buttons to same midi message (same for loops remote triggers).
Got it, thanks, so same limitations as Atom, disappointing.
´> @auxmux said:
LK does this, but I don’t find it stable enough for true live. And no AUM’s timeline sync. But for production it’s nice. Hold shift allows to enable several tracks REC buttons and you can filter midi input channel per track.
Yes, the one glaring "hole" in Helium, IMHO.
Agreed. I will ask again
Hopefully, an update to MidiMixer will tie everything in nicely.... in AUM...
Edit... or MM Ver. 2
Ah right, I always forget that I can record LK. I usually make clips in there directly.
I don’t want to bother Paul if the following is simply a MIDI protocol limitation, or something maybe somebody can chime in if it’s a feature request or bug.
So, I keep the RTC on its own channel. I only have a problem with stuck notes if I schedule a loop and then enable record. As soon as the loop changes I get stuck notes. This happens even if the currently playing loop only has midi notes in the beginning, in other words having plenty of time for note off messages to occur.
I have no problems if I schedule a loop, wait for the loop change to occur, and then enable record, but it’d be a nice seamless flow if I could achieve the former, since I wouldn’t have to wait an extra measure (or however long the loop is to play thru) in order to begin recording.
I should mention that the same behavior is occurring whether I’m using the default baked-in loop scheduling keys with a dedicated RTC channel, or if I’m mapping to the loop schedule visible in the AU parameter via AUM’s MIDI control.