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
Ah, is this still the case?
Shouldn't... but the preset you referred to was saved during that time, so it is probably corrupted.
Gotcha, thanks.
Btw, I just did a quick test of this setup and preset loaded the Xequence project correctly.
Just a very simple 4 bar text of 8 synths but still getting crackling when incorporating AB3.
Anybody else get the crackling with AB3? here’s the preset...
http://preset.audiob.us/uRnTzZWOS28fVCF
Very very much this. Instruments loaded into AB lanes work and appear just like instruments loaded directly into AUM with the added bonus of the AB panel switcher.
My iPad would literally kick me in the stones if I tried to load that preset. I wouldn't even get to the crackling.
Ha, ouch!
I can load up the same 8 synths in an AUM & Xequence setup with no audio issues. I'd really like to integrate AB3 but the extra overhead for my setup is a no go atm.
I'll try again though, adding the synths one by one to find my ceiling.
Did you do the “reset audio session” thing in AB3? Can’t remember the exact name but it’s in the top right.
Ah no, I hadn't seen that. Will give that a try, thanks.
Works fine for me iPad Pro 9.7 (2016)iOS 12
The Preset I uploaded?
Hmmm. Wondering if my 12.9 (Gen 2) Pro is still experiencing the old Graphics v Audio CPU issues then.
Great set up. Worked a treat! 👍🏻
I wonder what is the current state with this issue. Is anyone able to save and recall states with Xequence? For me it is only loading the last used project and not recalling anything at all.
@nick sorry, it should of course work every time. I haven't ever been able to make it not work here, so until someone provides me with detailed info how to make it happen every time, it cannot be fixed (I'm also still not sure if it's a problem in Audiobus or Xequence).
If there continue to be issues, I'll have to consider removing state saving support.
@SevenSystems I’ve noticed it’s necessary to tap on Xequence icon in Audiobus immediately after AB preset loading to allow for proper state saving recall. If you’re not fast enough, last project will be used and no restore.
I also encounter crackles with Xequence and AB, and also suspect graphics over audio priority issue with my iPhone 7 Plus in that specific situation since I’ve updated to iOS 12.
Thanks for that hint
so far, I‘m only getting the last used project, no matter how fast I switch to Xequence...
here is what I do:
This should show loading Audiobus state saving in Xequence and restore your related project.
I added a few state saving apps to the setup and noticed that, when saving the preset, the other apps confirm that sate is saved, but Xequence does not ...
@nick, thanks for the info... that's appearently still the same problem that I've spent days on trying to solve. It seems like Audiobus somehow doesn't "recognize" the state from Xequence and thus doesn't save it.
When you load that Audiobus preset and then immediately switch to Xequence, do you notice a "Loading Audiobus State..." screen at all, or only the "Xequence" logo and then the last state of the last project?
Anyway, I've put in another "guard rail" into the Audiobus state saving code that might potentially fix the remaining cases when it doesn't work. Thanks for the help @nick and @Janosax, will probably put this update out today.
And sorry for the trouble for the few persons who seem to be affected. Lost projects are of course completely unacceptable (even though it seems to be a constant problem in many iOS DAWs), and I have never heard of a single case of an even slightly corrupted, much less completely lost, Xequence project when the normal "Save" function, the AutoSave function, or the automatic crash recovery functions are used. So for everyone: rest assured that project saving and loading is as robust as a compressed granite rock in Xequence.
I don‘t get any Audiobus loading screen at all. I see a Xequence screen for a split second, then the loading logo and then the last state of the app
by the way, thanks for looking into this so quickly
No problem. As I said, bugs, especially ones involving data loss, are totally unacceptable. It would be much easier to find and fix if it ever occurred here! (I just followed your exact steps and the problem -- of course -- didn't occur.) It's probably a Race Condition -- a very nasty "typical" programming problem where the outcome depends on the exact timing and/or order of events / user input.
I suspect that you have to name and save the new Xequence file for AB to pull up the correct or latest version of the Xequence project.
I tried without naming or saving, and AB did not reload the edited Xequence project. It pulled up the version without deleted notes.
After naming and saving, AB seemed to pull up the correct updated Xequence project.
I think also resaving the AB preset would help it pull up the current versions, after you make changes to Xequence. This should get AB to resave the app state for Xequence.
I’ve had some issues with the state saving. I think it’s in audiobus side. I find if I hit save preset TWICE it will save. Sometimes the initial save doesn’t bring up the Xequence state saved prompt.
This has only happened about 2 out of 10 projects. I was doing some testing the other day on it.
@CracklePot saving / naming the project before saving the AB preset shouldn't be necessary. What you saw was probably just a coincidence.
@ruggedsmooth that sounds interesting. Yes, if that "State saved for Xequence" message doesn't come up, then you can be 100% sure that the preset is corrupted and doesn't contain state for Xequence.
It also doesn't help that Audiobus completely deletes the state of a particular app from a preset if the state couldn't be requested successfully, instead of just keeping the LAST state that WAS retrieved successfully.
On the whole though, even if I were assured by the Lord Himself that state saving is error-free, I would still recommend saving important milestones of your project in a "normal" fashion. State saving is really just a convenience feature mostly intended for simple presets in synths etc., not for saving complex, large datasets.
I mean, to use an extreme example: what if you host a DAW with audio tracks in Audiobus, and save its state. Is it supposed to save all audio tracks, including all audio recordings (potentially several Gigabytes) in that preset? Obviously, that doesn't work (I know it because the size of a preset is also limited to a few MB...)
@SevenSystems Ok. If anything, when I didn’t save the new Xequence project, it did the flaky state save thing, pulling up the previous Xequence state without the latest changes. That may help you recreate the strange behavior.
@SevenSystems
did some more testing and it seems there is more than one thing going on.
for example, I was able to save a preset with Xequence state now (no idea why it worked this time). but I was only able to recall it by switching to Xequence really fast
so it seems there is something flakey with both saving and recalling
@nick thanks for the info. I've put out an update that addresses one potential thing that might cause this in some situations. I'll continue to investigate.
@SevenSystems : have you been in touch with Michael Tyson about this? He seems very interested in helping developers with AB-related woes.