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
Two more observations. LK doesn’t take back control immediately after loading the AUM project. It happens when you hit play in AUM. Second thing is that disabling the Midi devices is not persisted in the state. I always have to turn the LPX off again in the Midi tab after loading the AUM project.
I've just checked the code and we are saving into the state of the project, the state of each controller.
Is Loopy Pro Launchpad X support plug n play? Or do I need to enable anything to make it work? I will definitely need to run some tests.
Plug 'n Play
Cool. Thx!
This is what I have found out.
LK is actually saving the state of enabled controllers. If I disable Launchpad X and then launch Loopy Pro with LK on a track, I will see on the launchpad:
This raises a new question that hasn't been raised so far because there was no hosts dealing with this devices in a plug n play manner like LK until Loopy Pro.
By default LK always loads a single track/scene project with all supported controllers enabled. When LK is loaded in Loopy Pro it will be in this state before the state being loaded, therefore LK will grab any available controller. When the project is loaded, state saved controllers will be enabled or disabled but at this point, the host (Loopy Pro) will not try to grab it again.
I'm not sure what the best solution will be. If we disable all controllers by default when LK is hosted it might become counter intuitive. But so far this is the only option I see.
Open to suggestions!
I think it would be the best if plug’n play is enabled by default but users can turn it off or on for each connected pad controller and this is stored in the project and AU state. Then you have the intuitive way that LK controls the device when it is loaded first time but when you don‘t want that, it can be adjusted in a persistent way for the project that you are setting up. If the behavior can be configured for each connected pad controller it would be possible to have one pad controller for LK and another for Loopy.
LK - standalone and auv3 during initialise (starting app) network sessions with mac are disabled.
I start Drambo, session network shows on mac.
Then I start Audio Unit MIDI in Drambo select LK, and boom. Network sessions are disabled.
Then I must start something other in background to reenable session network.
Like Thesys.
Standalone the same: opening LK will disabling network session.
LK is too much great to be left with such bugs.
We have uploaded one more beta of LK 1.12.0 (build 275) with the following changes:
Icons and automation interface much more usable on iPhone now 👍👍👍
We are still tweaking some little details. By the way, signature numerator / denominator is now under clip properties.
Thanks for your feedback.
I think I have missed this. Sorry!
Never used a network session. Can you please share with me a screen recording on how to reproduce this problem and how to debug it? Thanks!
@sinosoidal 4 hours session today with LK, Loopy Pro AUV3 and Koala AUV3 all in AUM and not a single LK crash!! Nice
That's precisely what is happening but when LK lets go the controller afterfuly loading the project, Loopy Pro doesn't grab again. That is why this is tricky. In order to prevent this, LK shouldn't grab controllers for the default song, because that will always happen after Loopy loads and sets the state on the controller.
Good news!!! what build have you used? The latest? or the previous one?
Awesome beta. Triplets and short note whaoo!!
Thanks a lot.
It was with previous one. Just spent one hour also on current one and no issues. Any differences?
Looking forward for your feedback!
No really. Just wandering!
Version LK 1.12.0 has a considerable amount of clean up in the composer section, but I'm not sure if that could be the cause of the hangs we were observing.
Would be nice to have velocity articulation on the same notes slider.
The very left high the very right low velocity.
@sinosoidal little feature request for you and your team: could you add an individual clip setting to make it decoupled from scenes triggering. Goal is when trigger scenes that individual clip will keep its playing/stopped state. Purpose is in live context: for example you record a drum part and want it to always play when you record bass and chords parts on various scenes. This helps for an easier and more natural flow. This decoupled clip should be still able to be triggered by individual/column play/stop buttons. GroupTheLoop uses something like this with its master loops group, which stay free of all other scenes. LK with individual clip decoupling settings and proper midi learning should do exactly the same thing without even major UI modification.
In the latest beta you can now record notes from the clip's keyboard (as long as the track is armed and the song recording is enabled)
Firstly, let me start off with saying I love LK, and use it quite a bit, for various things, in a multitude of scenarios. However, as we are talking about the Chorder module I just need to vent that I find it quite un-intuitive. No doubt user incompetence on my part, but anyways, let me vent my gripes with it here, at least once, and then I shall go back to being quiet about it.
To illustrate I took a few screenshots and annotated them.
Which results in this:
I would personally prefer if it worked something like this:
As I say it is probably due to user incompetence on my part, but as I find I need to "fight" the Chorder it steals energy from creating music, which in turn means I don't use it, which again is a shame, as it is "right there", in an app I most often have open anyways.
@xglax @sinosoidal I’m sorry to report but midi mappings are lost again on AUM session load:
Strange. Just tested that and mappings were successfully loaded. Can you try making a new aum session with a simple LK patch and check if the problem persists please?
That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.
Sorry for the work
@xglax @sinosoidal Another request: I’m trying to sync properly LK and Koala midi loops. I use LK clip actions (playing actions midi notes sent to Koala loops, which are not synced to bars but immediate). It seems that slight midi delay make Koala not playing first loop midi notes. Could you add a +/- delay slider for each midi action (at least playing and stop modes). Like on this screenshot, this will make my life so much easier
The latest build have a problem with scene chaining.
When clicking on the the a scene, LK never trig the next one.
If I double click the first scene then it work and then other scene are chained correctly
Thanks for this complete analysis. CHORDER needs a overhaul for a LONG LONG time. We have it as an issue on our long todo list. Let's see if we can make it happen in this trimester. Thanks for your incredible and detailed analysis of the problems you are expericening with CHORDER.
Thanks for raising this up. We need to investigate.
Great! 🤟🙌🙌
I also had the question about the similar “note bar” on the side of the chorder module. How does that bar work?. Can you set a scale for it?.
Keep up the great work! 👏