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
@BlueCircle Upon loading the Test3 session, the 3 Aphelians are in ARP mode. If i change them to SEQ mode (and add some notes to M1:3, the others have notes set) and press play, all instances are running and the dots are moving along their shapes.
.
BTW: I‘m not the Aphelian dev, just curious and quite experienced in hunting down bugs and beta testing. If we find out anything, we need to inform the dev via email ([email protected]) - last update was 10 month ago, lets hope they are still active.
Thanks again for digging so deeply into this. If I stumble onto a solution (or get feedback from the developer) I'll post back here. Cheers.
Pretty sure I'm having the exact same problem as @BlueCircle. I can't get more than a single instance of Aphelian to work at a time inside AUM. It's always the first Aphelian I've set up - if I create multiple Aphelians in a single MIDI "column", I can switch the order in the column and it's always the first one I've set up that plays. The others aren't moving when I drill down into them - it's as though they're missing AUM's "Play" event...
Just once I managed to get 2 instances of Aphelian playing simultaneously, but I didn't think to save the AUM session because I was still learning how it worked and didn't realise this would be a recurring problem for me. That suggests it could be some sort of config issue or possibly related to the order I start things inside AUM rather than a problem specific to Aphelian itself.
@monch1962 Oh that‘s some new information that it‘s always the top instance of several Aphelian instances in a single midi track. BTW: That‘s also the case in the screenshot of BlueCircle)
@monch1962 And @BlueCircle What happens if you use several midi tracks - ie only one Aphelian instance in each of the midi tracks ?
@_ki @BlueCircle I just did some more experimenting and found the following steps seem to let me have multiple Aphelians running simultaneously:
As long as I follow that exact sequence of steps, I can get a 3rd and 4th Aphelians running at the same time as the 1st 2. I haven't tried going beyond 4 yet
If I try setting up a 2nd Aphelian while AUM is playing, the 2nd Aphelian doesn't work
If I don't give the 2nd Aphelian's seq a few notes to play before hooking it to a synth and hitting play in AUM, the 2nd Aphelian doesn't work. If I only add notes to the seq after hooking it to a synth, it doesn't work
If I don't rotate the shape in the 2nd Aphelian slightly before I hit play in AUM, the 2nd Aphelian doesn't work
When I tried @_ki 's suggestion of restarting AUM & setting up 2 MIDI tracks with one Aphelian per MIDI track, the 1st one worked fine, but the 2nd one didn't. I then deleted the 2nd Aphelian (kept the 2nd MIDI track), recreated the Aphelian in the 2nd MIDI track and it worked. Very strange, and suggests there's some specific sequence/s of starting & configuring Aphelian that don't work.
If I set up an Aphelian instance and it doesn't work, I can delete that Aphelian instance (keeping the MIDI track intact), set up a new Aphelian in the same track, follow the above set of steps and the new Aphelian usually works.
There could easily be more nuance to it than this - that's just what I've observed so far. I'll keep digging
Thanks for the tests. BlueCircles problem starts when reloading a previously working multi Aphelian session - does that work in your case (when you did all the extra steps on setting them up) ?
.
Another thing that could be tried is using AudioBus or apeMatrix as host. These probably have a different timing or even different order in calling Aphelians AUv3 initialization routines.
Just tried AudioBus and any additional instances loaded after the first don't work at all. Even when building the session. They work in AUM when a session is first created (as _ki mentions) just not after a session is reloaded.
My current workaround is to save the additional instance settings as a presets in AUM, then reload and connect up each time. Not ideal but at least allows a workflow.
One more update. Installed AUM and Aphelian on my old iPad mini 2 (ios 12.4.1) and everything works perfectly. Then I tried a complete factory restore on the mini 5 and installed only AUM and Aphelian and have the same problem- so it seems to be something unique to that hardware/ios version.
I know it’s a different answer then what you are looking for but you can always record the midi in atom 2.
no more in the app store
This is odd there’s a thread on it… same with Oscilab.
Anyone still using/having issues with this app? It seems great but the recent App Store review, this thread, and no update for 2 years has me worried.
Yep, still issues. Such a shame
What are the issues you are facing? I don't have any on my side but maybe we use it in a different way...
The very first issue mentioned in this thread; I can't simply send midi to multiple synths within AUM
Ah that’s a bummer because the app seems cool and Oscilab is excellent. Or was? I haven’t used it in quite a while.
Yeah, total bummer. It's such a cool sequencer, but can't do the things I want with it currently...(or, maybe I could, but not without some tedious-sounding workaround) . It'd be cool if it just, y'know, worked...
Precisely. Guess I’ll pass on it for now then. Hopefully the dev will update it eventually
i cant say i ever understood the utility of Aphelion as an AUv3…one instance per instrument seems like it is contra the original idea of the app
hosted within AUM as a IAA source (without using its onboard instruments) routing the midi channels (5) to your stuff to AUM instrument slots might be the fun you’re looking for
I remember being exited about this one coming - but I never even think about using it now. It sits rusting in my app scrapyard.
Are there any other issues with the app? Bugs, etc?
nice and stable (as IAA at least including in AUM as instrument with midi routing in AUM). I cant speak to other used
The main issue is that as an AUv3, it seems that it only is reliable if there is only one instance. As an AU, there is only on track per instance unlike the standalone.
This. The standalone IAA version has all the features IIRC (haven’t tried it in a while). Even has built in drums!
The AUv3 is quite neutered from what I remember.
Edit: just checked; the IAA standalone still works perfectly!
So you only have 1 of 4 tracks if ran as an AU? Such a strange limitation.
Thanks for the comments guys! I’ve been eyeing this for a while. It’s not gonna be at the top of my list but I feel a bit better about getting sometime soon.
not so strange. it is meant for controlling other synths (it is midi only as an AU) and routing 1 to 1 is much more straightforward than multi-out (which might not have been a thing when it was published) our setting up filters. each instance meant to control a different synth.
I don't think it sold enough copies for the developer to find it worthwhile to keep putting resources into it.
It's a shame it wasn't more popular as it is a fun app and plug-in.
Oh I think I misunderstood. I thought they were saying when it’s loaded as an AU instrument you only have access to 1 of the 4.
As an AU it is just midi output and one shape. It can be a midi arpeggiator or sequencer.