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.
Developers: Please support "All Notes Off" and "All Sound Off"
Just a friendly suggestion to all MIDI sound generator developers, no matter if standalone or AUv3:
Please support "All Notes Off" (CC 123 with a value of 0) and possibly "All Sound Off" (CC 120 with value 0). They're a very important and straightforward means for a sequencer to get back to a known state when stopping or when a sequence is edited during playback.
= "All Notes Off" should simply turn off all running notes on the channel. This is by far the most important.
= "All Sound Off" should do the same, but ALSO kill any reverb tails, delay feedback lines, etc.. this is a nice bonus, but not strictly necessary.
In my recent testing with a lot of synths, I found that:
= some synths do react to "All Notes Off", but implement it as "All Sound Off".
= other synths do not react to "All Notes Off", but do to "All Sound Off", acting as if it were "All NOTES Off".
= many do not implement either message, meaning currently the only way for a sequencer to reliably kill all notes is to send 128 individual "Note Off" messages, which causes 128 times more overhead in an already resource-constrained and often unstable system ("iOS music making").
While we're at it, "Reset All Controllers" (CC 121) belongs to the same class of messages that are very useful for stable integration between sequencers and sound modules.
More details on all of these can be found here:
https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message
Thank you! 💙☝️🤨
Comments
A very good shout !
I have already contacted every developer so far, but thanks for the offer
I'm actually compiling a list of problems with titles and details, and tagging all problematic AUv3s that I find in the process with the corresponding tags.
If Xequence ever gets AUv3 support, I'll probably put warning icons next to problematic plugins in the list, and / or also present this list on a website.
I know it's not "nice", but so far I find working with AUv3 plugins, both for music making and as a AUv3 host developer, a bit frustrating due to lots of problems in many plugins.
After this experience, I'm sure EVERY AU host has such an embedded list of problems and workarounds that invoke special code paths for some plugins!
I appreciate this post. When users are effected and other developers have to try and cover up these deficiencies in another developer’s app so their host app doesn’t get blamed, it degrades the quality and reliability of the musical environment. Thank you for informing other app developers about these issues.
Probably, but it is the wrong way to fix the issues, as you have said, fixing the AU's themselves is the real answer... I like the idea of the warnings, it will save me from keeping my own mental list of AU's that I won't use because of them being somewhat unreliable or unpredictable
