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.
Bram Bos apps au parameter record not working in Cubasis 3.6.6.
hello people & @brambos
strange thing: in the latest cubasis version , if i put, say, Hilda or Fluss as a synth on a midi track i cannot record knob movements into Cubasis automation track using the W/R buttons!?
weirdly if i put either of these apps as “processors” into the insert effects slot (of audio or midi tracks) then Automation works as expected ??
am i doing something wrong? has anyone else experienced this?
no problem recording automation in , for example, any of the Gadget synths on a midi track ( and that definitely DIDN’T work when they first made them all AU plug ins )
any insight Mr Bos?
Comments
No… did they break it? It used to work for the last 6 years…
AU parameter automation has become a right mess since Logic Pro came out.
Maybe Cubasis started using the touch information that Logic Pro and Auria ask so require for automation recording?
I fear that may be the case. The weird horrible implementation that is supposed to be optional according to the AUv3 documentation.
And which is completely incompatible with the way my UIs communicate with the rendering engines
RIM presented what sounded like a not unreasonable argument to me as to why touch information was needed for a DAW to be able to reliably overdub automation passes.
I can give equally reasonable arguments for why the plugin shouldn't have to disclose to a DAW what's going on inside its own UI/view (not even my synth engines get that information.. they get a parameter state and that’s what they get to work with. Clean MVC separation)
In fact, why assume that controller messages are only generated through touch/click interactions in a screen? For example, when the sliders in Fluss bounce around they are generating controller messages, but there is no user interaction whatsoever.
The model is poorly thought out and should not be the de-facto method (and in fact it isn't, according to the documentation).
But yeah, I've made a plugin host in the past, so I know why this makes things easier for them. But that much harder for plugins.
just as a follow up , it just seems to be Hilda , i’ve just checked Ripplemaker , the ruismakers , hammerhead , and they seem to be ok,
but no knob stuff goes on in Hilda as synth ( boo, shame )
and actually i can get something going in Fluss now for some reason maybe because i recorded some midi notes in ... will try that with Hilda too
Mononoke ,, well that just seems to be instant crash / black screen ,
not tried Trouble maker yet , and i don’t have Salome,,
will try on another ipad and get back to you.
Thanks for the heads up!
I tested Hilda and it works as it did before for me.
Hilda live pads always had an issue with recording automation, especially since Logic (smh): are you talking about how if you record automation the live pad will be enabled upon playback? It just looks problematic but it plays back correctly.
ok, so it’s an ios 13 thing , yeah i know , WAAAAY too legacy , but for various app needs this one needs to be stuck there, and i think it’s perhaps Cubasis on ios 13 not behaving as your apps all seem ok in things like Apematrix using automation lfos etc ( which , of course , haven’t been updated so much in recent times )
moving to the bigger ipad using ios 15.7 , Hilda works aok , and indeed Mononoke seems to be functioning fine there too ,
so i’ll have to curb my excitement for Cubasis 3.6.6 on the legacy pad right now ,
possibly too much to ask that @LFS can have a peek at this , i usually update the ios 15 one first to check , all seemed good so i bumped up the ios 13 ipad , mostly due to excitement over the audioglue cut’n’paste possibilities..
my bad!!
yeah, even on 15 with it working , the live pads are a bit kranky, but at least their record data registers and you can go in and edit the automation lane ,,
way back in ios 13 land none of the knobs or pads register so you don’t get the auto lane ..
weird that the earlier BB apps all go fine though? must get Salome at some point and test that.