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
In loopy pro’s project browser, there is a pseudo-folder called Audio Unit Extension Folder. The AU can see projects in that folder. Move copies of standalone projects into that folder for them to be visible in the AU.
Save the project into the
Audio Unit Extensionfolder. You can move multiple projects at once with the Edit button in the projects browser.https://loopypro.com/manual/#auv3 (projects paragraph).
thank you guys.
more questions are coming, of course I do my homework before posting here, so I ask questions I'm not able to find covered in the available literature (which doesn't mean they're not there).
thank you for your patience and support
After checking what you wrote I'm still confused:
I saved a project in standalone and put it into AUDIO UNIT EXTENSION folder > close standalone > open AUM > open LP > select FOLDER > select PROJECT > select my previously saved project: I get the question re unsaved changes (I guess it's talking about the project LP was set on the last time it was opened in AUM)
so I > DISCARD CHANGES: result is that the project is loaded with different settings than those I saved.
Same project showing different settings (midi assignments) depending if it's opened in stand alone or hosted.
What can I check?
Can you be more specific about what you mean by midi assignments?
Could it be that midi ports that LP has access to when standalone are not available when running as AU, only a virtual port is available.
midi bindings
ok, here it is:
it comes out some of the midi bindings were saved in CONTROL SETTINGS > CURRENT PROJECT,
while others were saved in CONTROL SETTINGS > GLOBAL PROFILES
therefore, of course, those saved in current project (hosted or standalone) are recalled when loading the specific project, while those which are saved in global profiles don't.
This shows that GLOBAL CONTROL SETTINGS of LP when stand alone are not shared with those of LP when hosted.
Can you confirm?
Is there any possibility to import those from stand alone to hosted?
I suggest moving the global bindings into the project.
You can move/copy bindings from an AU project to AU global profiles. Global profiles should only be used for non-layout specific actions.
Ok, it look like each time I move or copy a profile from one place to another, LP creates a new Default #.
Is this ok, or should I expect a "merge" option somewhere?
Creates a new default where? There has to be one global profile. So if you move the only global profile, loopy will create a new one. Also a project needs at least one profile in it.
If you copy, that won’t happen.
There is not currently a merge profiles option, but a project can contain multiple profiles.
ok, I'm working on it