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
@branis I think I got that sorted…. Here is another question. Is there anyway we can set a trigger before the 1st bar? Meaning like in Xequence I could extend my note before the 1st bar so I could always have that as a mute? Does that make sense?
Updated.. thanks..
Edit.. BTW.. did notice LK does import Probability settings from Ableton Live’s Mini export.. but LK’s midi export (with Probability settings) is not showing up in Ableton… and Bitwig.
Yes Bitwig 4 (beta) reads Ableton and Fl Studio project files now.. amazing..
Maybe try setting trigger quantization to None and just add trigger notes in your master clip where you need them:
Yes.. Thanks I have it that way anyway. I figured out that I just need to make sure tracks that I want to unmute are muted before I start playback. In Xequence you can extend your timeline before the count so that you don’t have a volume or sound if you set that before.
@sinosoidal
Hiya, it's me again with questions.
I've just loaded up LK to evaluate it.
I have both the LaunchControl XL mki and the Launchpad X.
Both default to Ableton compatibility mode when connected to LK.
When I select one or the other in "Controllers"? the other one still
defaults into Ableton mode or something happens which isn't expected.
For instance when the LC XL is selected as controller and I press the pads
on the LC XL mki, the LP X's capture midi button becomes lit.
When the LP X is selected as controller and I go into Session mode,
once I press the tracks to be selected on the LP X the buttons on
the LC XL mki light up and goes into Ableton mix mode though it's
supposed to stay in default Factory mode or whatever custom session
I've got selected.
Is this a bug? or a problem with the way I'm routing it?
Thank you in advance.
Okay, found out why the "Capture midi" pad becomes lit.
@onerez If you are trying to sequence clips in LK by using midi notes to trigger them, then I think you will need a separate instance.
In your destination LK instance setup up midi learn assignments for each clip in your session.
In your source LK instance create a clip that sends notes that will trigger the clips in each track.
I’m not sure it would work by routing internally.
Another thing to consider is clip quantization. Two options:
1) Turn off clip quantisation on your destination LK so that they get triggered immediately when your notes arrive. Otherwise notes might be a fraction late arriving from the source and have to wait until next beat/bar.
2) Send notes from your source LK just before the beat and leave quantisation settings on in the destination LK.
@soundtemple thanks for the reply. I actually am getting it to work with one instance. Works very well. I used the set up that @branis posted.
On the other topic. What I mostly referring to is using a note to trigger a mute/unmute. This is a problem if you can’t have that trigger before the timeline, don’t see anyway you can have a trigger before the first beat.. in LK. you will get a small sound before the mute kicks in. I did this before in Xequence.. see pic below. But like I said, for tracks that I need to mute/unmute as long as i mute the AUM channel before I start the whole clip its fine.
@onerez glad you got it sorted
@sinosoidal How are midi learn settings saved? It seems I can save them to a project in an AUM session, then switch to another project and save some different midi learn settings. Returning to the original project re-loads the original midi learn settings. This is great.
However, if I open a new AUM session and load LK and open one of the saved projects the midi learn settings are gone. They are not saved in the stand alone version either.
It seems like they are local to the instance in AUM but that instance can store midi learn settings for multiple projects.
I think it would be better if midi learn settings were saved with the project and regardless of where you open the project (standalone, AUM or different AUM session) it should re-load the settings with last changes. This is how it is with everything else in the project. What do you think?
Also, every time I open an AUM session with LK in it the Controllers and Midi settings are all reset from where I have my settings when I save to exit back to everything being active. Weird because I thought that actually got fixed recently.
Also, even with LK all controllers off it seems LK responds to midi learn assignments from my Launchpad mini.
See this video. Only Mozaic is receiving midi for logging purposes from the Launchpad. All Controllers and Midi inputs are off. There is no midi routed into LK from AUM, yet it’s responding to midi learn assignments on CH0.
https://photos.app.goo.gl/xDe67tz1oCLxwhsUA
LK 1.11.0 Beta (build 246) is now available and introduces custom clip time signatures. You can change them here:
You're feedback is always welcome
Excellent news!
Awesome!
Great new feature! Thanks!
Hurray!
Brilliant
Should I post feedback here or via TestFlight?
You can post here
The option of non-4/4 time signatures is great.
I think some tweaks could improve the workflow -- as it seems like one has to set the meter for each clip as you add them -- unless I overlooked something.
I would recommend adding a master time signature that individual clips can override. When a clip gets created, it should use the master setting. If one changes the master setting, it wouldn't change already existing clips. That would facilitate the most typical use of meters -- where either an entire song is in one meter OR where different sections of a song are at different meters. So, this way, if the master is 3/4, I can create clips for that section of the song knowing that each new clip will be in this meter. I can then change to 4/4 to add clips for a 4/4 section and set it back to 3/4 to create more 3/4 clips.
As it is know, it is a lot of work to have to set the temp for each new clip -- and if you are creating clips by recording, you don't have a chance to set the tempo before hand.
Are you suggesting adding a custom time signature to the LK session (affecting clip triggering timings etc) or simply a "template" that simply would let the user define which is the default clip time signature when it is created?
We aren't planning a LK session time signature for now. We have some priorities regarding VS and we don't have the time to think about this for now.
But if you only want some shortcut to easily create clips in a given signature, that would be easier for sure, and we could add that!
The key thing is that one shouldn't have to set the meter for each clip -- and it should be seamless to record a new clip at your preferred time signature. Some way of setting the default time signature for new clips seems pretty essential. Possibly you could have any new clip be the same time signature as the most recently assigned meter -- but if there isn't some obvious way to see what that was -- that would be confusing. And however it works, it needs to persist across sessions in that project. I.e. if I create a project with clips in 3/4 and come back to the project, new clips should be in 3/4 without my needing to manually assign 3/4 to new clips.
Currently, if I create a new clip by recording, it is 4/4 regardless of other clips.
I agree with that. Very nice new feature!! And master time signature is also needed
LK 1.11.0 Beta (build 247) now also has custom song time signatures
@espiegel123 @Janosax
Now you can choose the song time signature. Created clips will automatically have the same time signature as the song (this include the created clips with recording). This setting is saved in your sessions and can be change from session to session.
Remember that when changing song's signature, clip triggering timings will behave accordingly with the current selection. So, for instance, a song with 3/4 signature with a clip triggering of 1 bar, will trigger clips on a 3 beat basis instead of 4.
Thanks for adding this. It makes things much better.
I noticed a coulle of little details you might want to look it:
Thanks for reporting. I'll look at those issues!
If you have any trouble reproducing them, let me know.
Very nice thanks 😊
I haven’t had time to try this yet. Excellent addition. Does it listen to the host time signature?
You set the project time signature which can be different from the host -- and you can have clips with different time signatures -- which is great -- so much music is not not one time signature all the time.
Yeah I get the flexibility is useful, just was surprised if the song time signature isn’t set by the host, but I guess not all hosts do different time signatures like AUM does.
The first issue is fixed, but could you tell me a little more about the second issue. I'm trying to replicate but can't find a way to do so. Maybe i'm misunderstanding the issue and not doing the right steps