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.
Sunrizer automation problem
I'm having trouble automating Sunrizer using Rozeta LFO in AUM. I've set everything up as I want it, in this case Rozeta LFO controlling cutoff for Filter 1, but there is no response from Sunrizer.
The same setup works for other synths, e.g. Zeeon, so I suspect that I've missed something setting up Sunrizer.
Any help is appreciated.
Comments
Did you simply try to use the learn function in Sunrizer? Here works great.
How do I do that?
Here you have it.
https://drive.google.com/open?id=1kgkFaDTIUGwroET_KKOcFRLqYTD6H-p5
But it’s true there seems to be a problem with direct automation au parameter of Sunrizer within AUM. If you don’t do the workaround with Midi learn it does not seem to work.
@giku_beepstreet : can you take a look at it?
I agree that standart au parameter automation in AUM using Midi CTRL does not work with Sunrizer. Also, if using Midi learn in Sunrizer, only one knob can be assigned to the same CC. With au parameter mapping, one could let the same LFO be sent to several au parameters (possibly with limited ranges and inverted values for some knobs).
But I’m having a hard time getting an answer to the question of whether midi CTRL SHOULD work. If it’s intended that it should, then there’s a bug that needs to be addressed.
Well, if it is an AU app (it is!), then the expected behaviour is that exposed AU parameters should respond when the host tells them to change. I believe AUM Midi CTRL takes Midi CC as input and translates this to AU parameter change events for the connected AU plugin. Could it be that Sunrizer AU only processes Midi events and ignores AU parameter change events from the host? That would explain why ApeMatrix LFOs don´t work, either (think I read that in some other thread).
Got it, thanks!
This is a bug. The Sunrizer app "exposes AU parameters" meaning you can go to MIDI CTRL and see parameters listed with assignable MIDI. But the Sunrizer AU parameters don't actually control the AU app.
Beepstreet either needs to hide the AU parameters or make 'em work. He's good, he's got it. I'm not worried about that, but yes, to be clear something is not working according to AU standards.
That was my thinking. I’ll just keep tabs on the release notes for the next update. Thanks.
Update is coming next week. Sorry about the problems, a lot of code has been rewritten. btw. Knobs movement automation works well.
Great news!