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.
Loopy Pro Questions
This discussion has been closed.
Comments
When importing new audio into a clip, the clip name is not changing only the audio.
Searched around coming up empty. Also when clearing a clip the previous name stays, only the audio clears. Any help or advice?
Do you mean that the clip is not gettings its name from the imported sample file?
Are you using the latest version of Loopy Pro? A recent Loopy update introduced the renaming of a clip based on the name of the imported file.
All up to date.
No, when first importing audio, naming is working as expected. When switching that clips audio via importing a new audio, the new audio’s name is not importing just the audio.
Also when clearing the clip the audio deletes but the name stays.
Pics explained
Bottom pic is original imported audio. No problem.
Top pic is original cleared. Audio deleted but name remains. ???
2nd pic from top is the new imported audio onto that same clip spot. The new name is circled.
3rd pic from top shows the new audio imported but the name did not import with it.
@hibjshop : is this a correct restatement: "when importing into a clip that already has a name, the the clip is not renamed to be the same as the newly imported clip"
Yes. Basically the name is not following. Also name is not deleting when clearing a clip.
Thinking Im looking at the naming process different as intended.
Is Loopy clip naming more of a track/channel name rather than an actual name of the audio?
Thats the only reasoning I can come up with if it’s not a bug.
Importing only changes a clip's name if the clip hasn't been given a name. If you want the clip's name to be the imported file's name, delete the name before importing. (When you see "Clip 1" that is an indication that it hasn't been given a name).
I think the idea is that clip names are descriptive of the clip and you might not want to lose that name when the audio in the clip changes.
For instance, you might have named a clip "Intro - Ambience" even before recording. Or "Verse 1-Drums" or "Boom Bap" or whatever. The name goes with the clip. So, if you gave it a name as a reminder of the function, you might not want that changed when you clear the clip or import into it.
It might be nice when importing audio into a named clip if Loopy asked -- or if there were an option to clear the name when clearing the audio.
Ok understood and sounds like you understand me also. Much thx for your respones 👍🏼👍🏼
You might want to make the suggestion on the Roadmap ideas page.
@espiegel123 one more thing. Do you find levels on the volume in the mixer difficult to achieve smooth mixing/fading. It seems from 3/4 and up gets louder very quickly, and below that its very low.
I’ve always felt this about the faders in LP. The ones in the clips too.
I felt that way initially but have become accustomed to it ALSO worth knowing is that the fader has a 'fine adjustment mode'/throw-length adjustment. When you tap on the fader move your finger to the left or right and you see a new virtual fader whose throw gets bigger as you drag left or right and makes adjustment easier.
An option for fader scaling might be handy.
@wim @espiegel123 thx again for resonding, been at it all day.
Yeah Im aware of the lateral volume feature. Seems to help a bit however I think if it just had a better response, similar to the levels in aum (my comparison tester), lateral would not be needed and LP would be even better with less.
The naming thing has me refiguring workflow, like that ever ends.
Overall awesome app. Thanks Michael👍🏻
I think I stumbled across a bug while putting together my latest project. I have an incoming MIDI trigger bound to Note:Channel 1:60(C4):On/Off and the target of this is a Button Grid with Action of "Press 1". I edited Button Grid:"Press 1" to Send MIDI Message with Target AUM:PC:Chl 1:PC 39.
If I connect the AUM keyboard to Loopy Pro AU and hit C4 then mfxMonitor listening to AUM shows 0xC0 0x70 on note on, and 0xC0 0x00 on note off. Subsequent note-ons show 0xC0 and then some (seemingly) random second byte but I believe that the value is related to the velocity of the note being played into Loopy.
I do not see PC 39 anywhere in the output.
I can provide a simple AUM project demonstrating this, if needed.
Thanks.
Have you already checked the output when you manually press that button of the button grid to make sure that the button is working as expected without being triggered by MIDI? Can you do that and post a picture of the midi monitor's display?
I just tried it and it is working fine for me. I set up button grid and added send midi message with the parameters you mentioned. I routed AUM's MIDI to streambyter AU as a MIDI monitor. If I press the button, I see that it sent PC39 and if I MIDI Learn AUM's C4 to trigger that note, I get the same result
Tapping the button directly does output the correct value:
Tapping the AUM keyboard gives the wrong values:
Here is the routing:
Tapping the keyboard a couple more times:
The odd second byte is almost certainly velocity as it gets bigger as I tap closer to the bottom of the AUM keyboard.
I have attached the AUM session in case it helps.
Thanks for taking a look.
Could it be the on/off setting that is different between our setups? If I select “On” then it works as expected.
I was wondering about that. Is there a reason you want to send the same PC twice, on note press and release?
see if assigning a clip to the button grid (currently it > @MisplacedDevelopment said:
It seems to be . I get slightly different results. If the midicontrol trigger is on/off for me, I get only one event...a PC event whose value is the note velocity!
@Michael
The particular use case here was to simulate a toggled button inside a button grid (see https://forum.audiob.us/discussion/50895/atom-2-orchestrated-by-senode-ipad-only#latest). For my use I only send the note on if the intended state is “true” which causes the button to remain “on”, and if the state changes then I send a note off which clears the button.
It doesn't happen just for button grids. If you define a regular widget to send a PC and have the trigger be a note on/off, the PCs sent out seem to always be the velocity.
Just checking in to let you know that I’ve updated to version .16 and the issue remains.
I know there are a thousand apps to slice samples but is it currently possible to export the individual slices of a slice widget? I see no export icon so I’m guessing not but it would be useful to save an extra step in the workflow.
i don’t believe there is a way to export slices.
Thanks for confirming.
If I put 2 instances of the same loop into the Timeline / Sequence view, is there a way to use / try out different volumes on each of them?
Within a single loop, is there any way to adjust the volume envelope to change across the loop?
there isn't currently built in mixer automation. you could do this with some creative use of follow actions and a widget that has a couple of adjust parameter actions set to fire at different delays. Or you could use a midi clip launcher like lk to send midi commands to adjust the volume
I’m having another go with Loopy Pro after struggling with it a good while ago and not really gelling with it. One of the things I came across previously - and I can’t find the answer to (I’m sure it must have been covered somewhere).
I cut a wav into exactly the same length of clips (all beat synced etc) and load some of them all as loops into Loopy Pro - say 16 - 20 all 8 bars - long by dragging them over from Sample Crate, before grouping them and setting them to play one loop at a time. For some reason several of them seem to play at twice the speed that I was hoping for pitching that loop up.