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.
Cubasis 3.7 sometimes not showing AUv3 automation.
Hi All,
Tagging @LFS in case he sees this. That said, I'm having a frequent issue with Cubasis 3.7 sometimes not writing automation/not exposing automation parameters for AUv3 plugins on occasion. This is what usually happens...
I lay down MIDI for a track, and I go to freeze the track, right? Then I start a new track, and suddenly I'm not able to automate the parameters of any AUv3 plugin as explained above. I'm not sure if there's a setting in Cubasis 3.7 to switch off exposing AUv3 automation parameters I may have accidentally bumped, or if this is indeed a bug. (I'm still becoming familiar with all Cubasis 3.7 can do, so do please bear with me.)
This happened in my "Blissful Bleass" project and in my recently-uploaded "Sleep, My Friend" project where I had to resort to using Cubasis' filter instead of Bleass Filter or FabFilter Volcano (which I'd argue are better-sounding filters).
Indeed, for whatever reason, Cubasis' internal plugins automate just fine without any issues, even after Cubasis disables my ability to automate AUv3 plugin parameters. If you know of a solution, please do let me know. Thank you kindly in advance.
By the way, I'm running Cubasis 3.7 (latest version) on iPadOS 18.1 on an iPad Mini 7 with 512gb storage. I'm also going to report this issue to Steinberg as well.
Comments
Here's the email I sent Steinberg support. It lists the steps I think will work in recreating the issue.
Let me add to this @LFS
Cubasis BLOCKS 3rd party AUv3 parameters from being exposed for MIDI Learn
Only internal Cubasis VSTs can be assigned CC and mapped to midi controller knobs and faders
PLEASE add 3rd party MIDI learn to record automation !!!
Thanks @jwmmakerofmusic
Not a problem. Maybe my issue is linked with the issue of Cubasis blocking 3rd party AUv3 parameters from MIDI learn. Hope I won't have to seek out another DAW app because of that. I'd prefer to stay inside of Cubasis (at least for the rest of this month as I continue participating in Jamuary).
As far as I’m aware Cubasis just doesn’t allow this at all. Was the main reason I wanted a refund that I was denied. supporting your own apps parameters and not your competition is really interesting and imo slimy
This is not true for automation though as auv3 parameters are visible. Not sure how midi learn relates to this. Agreed though, that midi learn should be available for 3rd party plugs.
I'm guessing it could be related to my situation, or maybe not. We shall see. 😅
FFS, Cubasis does NOT block midi-learn for 3rd party AUv3’s, the ‘feature’ is simply just not yet implemented…
What Cubasis could do though is to expose all the AUParameters (ie. pick from a list of available parameters) for the selected plug-in and allow direct drawing of the automation instead of having to write/record it first.
I’m quite sure @LFS is already preparing something which will be released when it will be released
@Samu is absolutely right. It’s completely incorrect to state that Cubasis 3 blocks this feature. It just doesn’t exist.
Can I also please just make this point here - not every developer wants to be part of this forum. If a developer joins the forum it gives the end user a direct contact with them and this forum has a reputation for bashing developers. We are privileged to have Lars as a member here - the guy in charge of Cubasis, from Steinberg - the originators of the DAW. Please, nobody abuse that privilege. If we want something added to Cubasis there are polite ways to ask. Always be nice, respect earns respect.
All due respect but why are you calling me out incorrectly dude?? [maybe I misspoke with blocking , someone told me Cubasis was not allowing them to be mapped but idk if that’s accurate now, but the rest of my point was true.]
third party Audio Units can’t be mapped to midi controllers like Hilda or whatever….this was discussed on the Cubasis forum at length
….and also me and Lars are very cool and I respect him immensely , and I am constantly supporting him and his platform, and you can even ask him if that’s true, so I don’t see how or why my “PLEASE” could be misconstrued as anything but politeness.
Honestly I’m surprised at your reply dude
In fact let me echo that point back to Lars , thank you once again for all you do and I hope you know I’m one of your most vocal proponents online
Misinformation spreads like wildfire. If a moderator in this forum says Cubasis 3 blocks mapping, next thing you know throughout the community people are asking why Steinberg would do such a thing. So as much as I don’t like correcting people, because they tend to react badly to it, it just needs clearing up that’s all.
As for what I’m saying regarding respect, I shouldn’t have to say it. But I’ve seen quite a few posts recently, some in this forum and some not, where people are rude, disrespectful and entitled. Some of which were directed at Lars. We’re all grownups, we can play nice or we will lose yet more developers from this forum that greatly enrich it with their presence. It’s just a reminder for all.
I have to confess, all the worrying about lack of MIDI Learn for AUv3 plugins has me a little confused. I just bought Cubasis on last month's sale and am in process of figuring out how it works. Yes, Midi Learn for AUv3 plugins would be nice to have. It would simplify things. But to my ears some people seem to be implying that you can't use external controllers at all with AUv3 plugins in Cubasis. That doesn't seem to be the case.
For any plugin I place onto a track, I can go into the menus and see which CC's Cubasis is mapping to which functions of the plugin. If I want to use external controller, I can just make sure my knob, fader, or whatever is sending the appropriate CC message for the plugin function I want to control. (Or, if I don't want to change mapping that my controller sends, I could insert Mozaic or some other midi filter into the routing to convert what the controller sends into what I want.). I'm not sure how much I will use an external controller with AUv3, but it's doable. Just not as simple as it would be with MIDI Learn. Or maybe I'm misunderstanding something.
I misunderstood @Jamie_Mallender ; I thought you were saying I was being disrespectful and entitled to Lars when nothing could be further from the truth. I’m one of his biggest supporters; ( I was the guy who put up the Cubasis section so I wouldnt diss their liaison )
And also I wasn’t spreading misinformation; I was relaying and paraphrasing someone else who made the point that yes:
Third party Audio Units (from independent and big name developers) cannot midi learn to your midi controller
If you want to record automation from an auv3; you can’t use your midi controller; you must use your touch screen
That’s why I was very specific in saying 3rd party midi learn; and I said blocking because yes, if the parameters are exposed to touch automation recording, then Cubasis midi learn is not allowing for them to be mapped to a knob or fader
So my polite request to Lars should be emphasized as just that - a polite request. It is not a demand and it wasn’t rude or entitled.
I do agree with your most important point - we have access to wonderful developers so we should address them with the most respect we could possibly give. Especially Lars who is quite patient with us lol
Thanks for your positive thoughts Jamie
No I don’t think you’re misunderstanding anything, what you said is bang on.
Is the statement in bold accurate? This is the kind of assertion that confuses me, where someone seems to be implying that you can't map AUv3 parameters to external controllers.
Midi Learn in itself has nothing to do with whether a parameter can be mapped to a knob or fader. Midi Learn makes it easier to map to a knob or fader. But you can always map it manually yourself; just make sure the control is sending the CC message that Cubasis associates with the parameter. You can see how Cubasis itself maps the cc's in the list of automation parameters for the plugin within Cubasis.
Also, you can see an example of how someone recorded AUv3 automation from an external controller in this thread:
https://forum.loopypro.com/discussion/comment/1344966/#Comment_1344966
Yea the statement is accurate
(Not really into using work arounds )
Either it does it or doesn’t
Hence the feature request
And yet the comment I linked shows a clear picture of how someone recorded automation of an AUv3 from their external controller, not using the touch screen.
https://forum.loopypro.com/discussion/comment/1344966/#Comment_1344966
I wouldn't even call it a work around. It's basically just how midi works, and how people did it before Midi Learn became a feature. Midi Learn is a convenience feature; it doesn't enable anything that can't already be done without it.
How about this:
1.You load an auv3
2.Click on midi learn
3. Tell me if you could assign a knob or fader
If you can do it, then I would like to know why none of my controllers assign mapping
Of course you can't assign a control that way. We are all in agreement that Cubasis doesn't support Midi Learn for AUv3s.
However, you seem to lack an overall understanding of how midi works, and what Midi Learn is. Go back to the comment I linked where the poster assigned an external slider to the expression parameter in SWAM Violin. He explains it well enough. Then figure out how to do it yourself. It's not using Midi Learn. It's also not hard.
You lack an overall understanding of my point - the feature request is MIDI Learn for auv3
What are you going on about ?????
This misinformation:
"If you want to record automation from an auv3; you can’t use your midi controller; you must use your touch screen"
Lmao
Yes - misinformation
When you just said
I think you should find someone else to talk to cuz I’m done teaching for the day
If I may offer an alternative solution, let's all settle down. This arguing adds nothing to possible solutions and workarounds. I don't normally try to steer conversations back to the original point, because in most cases conversations evolve in healthy and natural directions, but in this case, let's save this for the "rough house" (the "other" section). Thanks.
Closed per original poster's request.