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 export/import between devices
Just wondering how is this working for you.
I have a project on my iPhone XS that I exported to my pro 11 so I can work on it on a big screen and reimport it back but it seems it’s not as straight forward.
Firstly there’s massive discrepancies between the size shown within loopy’s project page and exported file size. There’s also wrong/outdated instrument racks in Drambo auv3.
I’ve tried to leave apps open to let it upload it to iCloud thinking perhaps things are partly uploaded but that didn’t quite work.
Any tips and tricks you have up your sleeve?
Cheers
Comments
I’ve never had an issue moving between devices if both devices have all the AUs referenced.
How are you exporting/moving the projects?
Can you post screenshots showing the size discrepancy(before and after)?
Re Drambo, as a test can you try exporting a simple project that has a Drambo rack, post a screenshot of what it should look like and share the project? If there is a state-saving/restore issue, Michael could probably use an example.
And you should try loading the same rack in another host and share to your other device to see if the issue is on the Loopy or the Drambo side
One other question, for the file size discrepancy, does the oroginal project show the same size in Files app and in the Loopy Pro project browser?
No, it doesn’t
Can you post screenshots of the project size display in Files and the size as displayed in Loopy’s project browser?
The second picture is not the same project. Loopy shows the project that is On My Ipad. Please screenshot the project that is in the Loopy folder pre-export not after being exported or moved.
In case it isn't clear, the Project browser is displaying stats on the project that is in the Loopy Pro folder.
You also didn't answer the question about how you are exporting. Are you copying the project using Files app or Exporting the project from the project panel?
Exporting from the project panel, does not export savepoints. So, an exported project doesn't have audio that was stored for save points.
I export the only way I know how. I go to the page with save/export etc and tap export project to files.
Does the original Loopy Pro project have save points? That could be one explanation. The save points wouldn't be exported. Also, I'm sure that there are temporary files, undo data, and other things that aren't and don't need to be exported.
Are you sure you have the same version of Drambo on both devices? Are all the instrument racks on the original Drambo instance available on the other? I don't think the actual instrument rack is part of the export.
You might have to do a separate export / import of the Drambo project. Loopy can only save the state (notes, automation, parameter values...). It can't save and export the actual modules and racks since they aren't part of the state.
As for trying to recreate the set up in a different host I just don’t have time for that. I just saved the Drambo session inside Drambo and reloaded it separately. Still there’s some weirdness going on.
The other way is to drag the project from Files to whereever you want to put it. Exporting a project from within the app strips out (as I explained earlier) save points and any media associated with them that are no long in your project. If you deleted the save points from the copy on your ipad, it would be about the same size as the exported file. Sometimes the exported file is a little smaller because Loopy can do some optimizing when exporting.
If you want the Drambo issue resolved, you'll probably need to provide and example to both Michael and Giku -- it is hard to know based on what you said whether it is a Drambo or Loopy issue.
I do this quite a bit, airdropping from iPhone to iPad and back again. I had problems at one point with apps like Koala and Drambo not keeping their state, but that was solved in an update some time ago I believe as I haven’t seen it for ages.
Is Loopy Pro up to date on both devices?
Its all the save points that create the size discrepancy, those aren't exported as mentioned
Both Loopy and Drambo are latest betas.
They work mostly fine in every other respect. I just made an exact copy of Drambo’s content on the second device so at least that is up to date. The thing is that I’d add some modules within Drambo and save the project, then save the loopy session and on reload those newly added modules wouldn’t be there, meaning that the previous state was loaded.
Anyhow, I don’t work with several sessions anymore. I have one do it all session so once copied it should all be fine.
@supadom : if there is a problem with Drambo state not being correctly exported, it would be very beneficial to the community if you posted such a project , so that Michael and Giku could address the issue.
Hmm strange one. Thinking about it, I’ve been using the same sequencer template in Drambo for a long time, so haven’t actually added any new modules to the Drambo instance for a while.
Im always recording new notes into Drambo though and they all seem to save and export in one piece.
One other thing that’s different is that I’m not on the Drambo beta, so have the latest production release.
I get that but I’ve done the back and forth between the devs before and unless I have time and energy for that rather than working things out by finding solutions from others here first.
I also know they’re both busy people so would get them involved only as a last resort.
All you have to do is send them the exported project and a screenshot of what the Drambo patch should look like when open.
I promise that with a bug like this both devs would want to fix it as it would benefit many users.
Following this thread because I've definitely had similar issues porting between iPhone and iPad, but I haven't needed to in a bit.
I would think the devs would be pleased to get bug reports if you're a beta tester for both apps. Hopefully you'll have the energy to sort through it with them at some point, If you can't figure it out. 🙏🏽