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.
Aphelian Auv3
The midi channels need to be reset in AUM when
using multiple versions of the Auv3 version of Aphelian
on the same midi strip.
i.e. Auv3 i has midi channel 1 , Auv3 ii has midi channel 2
but is not reconnected upon session reload
and the same for subsequent Auv3 instances.
The midi connections need to be remade every time a session is reloaded.
Anyone else have this issue?
Thanks in advance.
Comments
I have setup 3 Aphelian AUs in a Midi strip, set each of them to a different midi channel and connected them to three synth using AUMs midi matrix. The synth channels also applied a MIDI filter to the respective channel.
All this was correctly restored on session reload.
BTW since each Aphelian Au is only connected to one synth, one wouldn‘t need to specify the midi channel nor apply a midi filter to the synth - this is only needed if the midi streams are merged. For instance when using a multi-channel-midi processing plugin which is reading midi from all Aphelian’s and which supplies the midi to all synth,
This is how I've configured the Aphelian Auv3's to send midi
to Kaspar a multichannel midi processing plugin.
Or like this to four or more instances of SynthMaster One
or a combination of both.
Either way the midi channels for the Aphelian auv3
have to be reconnected each time upon session reload.
Thanks for trying and confirming you don't have this issue.
Are the Aphelians stored in the ‚muted‘ state you have shown in the first picture, or is the session stored like in second picure with enabled Aphelians ?
I‘m on IOS 13.2.3 iPad Pro 10.5
No, that was merely for the screenshot.
iOS 13.3, iPad Pro 9.7
Could you make a sceenshot of a) the connected midi matrix prior to a session save and b) the midi matrix after reloading that newly saved session ?
Perhaps we are able to find out the boundary conditions of this problem
Exactly where you have marked your screenshot
in regards to the midi channels in Aphelian is where
I have to toggle the channel so that I can get
the midi channels transmitting correctly upon session reload
whether the session has been saved by myself or is
the automatic session reload by AUM itself.
@_ki
Matrix A
Matrix B
No difference.
Hmm, so Kaspar is still connected to the four Aphelian‘s .What of the connection do you need to ‚remake‘ on session reload, it seems i didin‘t understand the problem
i think it’s kaspar related possibly, i’ve had midi problems with that synth many times... its a fav of mine but the midi has something going on with it
Visually there is no problem but when I hit play I can only hear the
midi notes generated from the
first instance of Aphelian.
@reasOne
I’m going to double check a little
later to see if it’s only Kasper or
if it’s there with the rest of the
synths as well.
Did you check that the midi input filter on Kaspar Channel is restored to read all the channels of the Aphelians ?
BTW what actual steps do you do to make it running again on session reload . Do you unreconnect and reconnect them in the matrix, or do you need to restore the output channels on the Aphelians or do you need to change something inside Kaspar ?
I think this information would help us figuring out the problem
@reasOne
Totally bang on.
It is Kaspar.
Removed Kaspar, replaced it with other Auv3's playback no problem.
@_ki
To get the midi channels playing again I have to manually
restore the midi channels on the Aphelians themselves.
Hmm, in m test the three instances of Aphelian kept their channel setting (channel 1,2 and 3).
=> And that‘s were i was wrong. I shouldn‘t have trusted my eyes, but checked the note data
.
@JuanB
Aphelian AU does not correctly restore the output channel on session reload or on preset reload .
The midi output channel dialog shows the correct loaded value, BUT notes are always output on the last used channel regardless of the midi channel stored in the preset. Only manually changing channels in the midi dialog will change to a new channel. On a session reload, the last used channel defaults to one and therefore Aphelian always send on channel 1 instead of the configured channel.
How to reproduce:
Exactly this.
In addition to the forum post, i‘ve send the bug report to Aphelian Labs contact address.
Looking forward to an update for the Auv3.
Awesome.
is anyone finding swing is working in AUv3 Aphelian?
I'm having a similar problem- perhaps someone can help me.
If I set up 3 Aphelian AUs in a Midi strip (same midi channel, each controlling a different synth) everything works fine. But when I save the session and then reopen it, only the first instance will run- the 2nd and 3rd are frozen (even though they are still connected)
Is this a bug or is there a workaround I can try?
Sounds like a bug.
Word. let me replicate and see if it happens, then I guess I’ll do the standard restart, then delete and reinstall, and take it from there. Cheers for the info, you’re always super helpful @Gravitas and it is much appreciated.
No probs.
@BlueCircle I just tested state-saving with 3 Aphelian AU instances in AUM with different settings (selected notes, distribution, shape, events, timing, swing) and each of them feeds a separate bs-16 instrument with different sound.
The session restored correctly, all settings are correct and all three bs-16 start playing when i press start. iPad Pro 10.5 on IOS 13.6.
Any idea what differs to your setup ?
Some auv3 plugins don’t like
certain buffer settings.
I’ve had auv3 plugins crash at
buffer settings of 512 and 1024.
Either changing the buffer settings to
256 or 512 can sometimes stop the crashes.
I can confirm the plug-in buffer issue.
Here is my setup (trying to replicate yours) and unfortunately I'm getting the same results.
I also tried restarting iPad and deleting then reinstalling the app. I have an iPad mini 5 on ios 14.7. 1. I noticed your DSP is 16% and mine is 41%, not sure if that matters.
I want to try changing the buffer settings but can't figure out how. Really appriciate the help- I love this app.
To access the AUM settings go to the three horizontal bars/hamburger icon in the top right hand side.
Go to Settings
‘Sample Rate’ and ‘Buffer Size’ should be there.
With „same result“ you mean that in your case only one of the instances is playing after session reload and pressing AUMs play button ?
.
DSP shouldn‘t matter, that not only depends on the device used but also on many other factors (cpu temperature, which of the cores is used etc)
.
I now checked with 128, 512 and 2048 buffer size, and with 512b / 48Khz - in all cases the three instances send out their notes on sessoin reload/play.
.
A question: Is the white dot mowing along the shape in all instances when you press Play in AUM ?
In your screenshot (which probably was taken after pressing play and then stop again - because the current song position is 004.1) the white dot of two of the instances is still at the start position, even though it uses the same 8 beats 1/16 trigger setting. Therefore i assume that instances 1:2 and 1:3 are not running in your case.
I also checked that the dot is running even if no notes are selected in SEQ mode - and one would get a warning message „no notes selected“ in the shape display.
I now tried with Link enabled and Link disabled, and with the 177bpm you used - but still everything is playing after reload.
I once managed to provoke a different error by switching SEQ/ARP and back to SEQ: The white dot didn‘t appear on play, but the notes were still issued... In that error case, switching to „events“ mode didn‘t show any wider lines where stuff was triggered, even when changing the trigger settings... wierd, i didn‘t manage to reproduce this new bug.
When checking the midi settings of Aphelia, i noticed all my instances were using channel 3 (don‘t knot why) so i changed them to channel 1, saved and checked the session reload - i still can‘t reproduce your error with only one of the instances running.
.
BTW: What happens if you add a forth Aphelian instance ?
Another thing to check with a new session: Does a setup with two Aphelian and two bs-16 work and reload ?
.
And another idea: Could you zip your not-working AUM session (shown above in the screenshot) and attach it to your message ? We could try to load it, and depending on if it works on our device perhaps deduct something about the cause...
In the files app, navigate to ‚On My iPpad / AUM‘ and long press on the session file. In the popup select compress - this generates an ‚sessionname.zip‘ file.
When writing a message/replay in the forum, the editor shows an attach file icon (second from the right), navigate to ‚On My iPad/AUM‘ and choose the generated zip to add it to your post.
After upload, don‘t forget to delete the zip in On My iPad/AUM ! Otherwise AUMs file load dialog will show the session twice, but only one of them two can be loaded.
Can you check this at 44.1Khz please?
Yes- thats exactly it
No- The white dot only moves in the first instance after a session reload. In all subsequent ones the dot is "frozen"
Here is a video to show what is happening:
All my instances initially appear on channel 3 also but changing these around didn't seem to help
Yes
If so, it might be something that‘s stored in the session data for the two existing and bad behaving instances. If the new is running, save the session under a new name, do an clear session and reload the 4 instance version. Still only one running, or is the first and forth running ?
Only the first
Damn!
Always the same result: First instance always plays on a session reload. Any instance created after the first one, plays perfectly when first created but when a session is reloaded they are frozen -- whether all loaded into the same midi slot or as separate midi channels.
Attached- thanks again and really hope you can figure out whats going on