Could someone help me with this:
I would like to control the “Wet” knob (picture below, look for the blue arrow) on BlueCat’s Acoufiend with a foot controller set to CC101. How do I map this in Cubase 14? Thanks in advance!
2 Likes
Hi and welcome to the forum,
Assign CC101 to one of the Quick Controls. Then right-click to the parameter and assign it to the given Quick Control.
1 Like
Thanks, Martin for the welcome and the answer.
I’m assuming that I click the “QC” in the right-hand corner of the plugin. Once I do that, I click the stylized “L” for learn and move the foot controller, right? I have tried that, but it doesn’t seem to be learning the controller. Is there another way to input CC101 that I’m missing? And when you say click the parameter, I’m guessing that you mean the parameter listed under the knob (or perhaps, the knob on the plugin GUI? ) I’m afraid that I’m still confused. Thanks for bearing with my ignorance, but could you give in a bit more detail the steps you took to accomplish this? I appreciate your patience.
Hi,
We have 3 different Quick Controls types in Cubase. Track Quick Controls (this is what I suggested to do), Focus Quick Controls (this is what you are using, now) and VST Quick Controls. Of course, you can use the Focus Quick Controls, if you like to use it this way.
To assign the Track Quick Control, open Studio > Studio Setup and select Track Quick Controls. Here, you can assign the MIDI CC.
1 Like
This is what the dialog, that Martin mentioned, looks like:
On the left, select Track Quick Controls.
Then on the right chose any of the 8 controller entries, double click the Address column and enter “101” (I used 106 in my example).
Also tell this part of Cubase to which MIDI port to listen to (yellow marking).
Close the dialog with OK. Select the track with your plugin on it. Open the QC (Quick Controls) in the Inspector.
For assigning a QC to the parameter in your plugin, the manual has a detailed description:
1 Like
I’m not familiar with that plugin, but if it has midi learn, you can just right click the wet knob, then work your foot controller. You might have to exit cc assign after you do that too.
Simpler than assigning the foot controller to a quick knob.
Edit: took a quick look here: Blue Cat's AcouFiend - Creative Acoustic Feedback Simulator Plug-in (VST, VST3, AAX and Audio Unit)
“…Full MIDI control and automation support, MIDI Learn…”
1 Like
Hi Felis,
Thanks for your comment and link. I do have the User’s Guide for Acoufiend, but when I follow it, it really doesn’t pick up on the CC controller for some reason. I know that others have no problem with it, but I’m having no luck at all. I’ve got someone on another forum who’s trying to help with this, so I’ve got some hope, but it is frustrating to have this issue. I kind of wonder if it’s because I have it as an insert effect, but so far, I’m at a loss. If you’ve got ideas on this, I’m all ears.
Thanks again,
Dan
Hi Johnny (and Martin)
Thanks, guys, for the comments; I think I’m about halfway there (thankfully!)
I’ve got the “EQ Low” on RealEight mapped to CC101 and working. It’s not what I was trying to do, but it’s a start in that at least something responded. Now, my question is this: can I map an insert FX (Acoufiend) the same way? If so, how do I make the Acoufiend available for mapping using the Track Quick Controls (or something else)?
Again, thanks so much for your patience; I seem to be getting there, but by inches. I very much appreciate all the help.
Dan
Daniel,
you chose the next slot of the Track Quick Control (click it), then activate the learning “L” in the TQC. The next thing parameter you move with the mouse will be mapped to that slot. So move the knob on the Acoufiend.
Let us know how it goes.
1 Like
The whole Quick Controls UX is not always very intuitive.
And this is on an instrument track. On an audio track you’d have to setup an additional MIDI track routed to the plugin you’d like to control.
1 Like
I beg to differ. it works without a MIDI track, of course. How did you come to that conclusion?
1 Like
Hi Johnny,
Thanks so much! That did it. In the interim and by going through this all, I also found a better order for Acoufiend and my amp sim (Archtype Petrucci) which sounds very cool. I totally appreciate the help!
1 Like
My bad Johnny, I am confused by the QC workflow.
After digging a bit more, here are some of my issues:
- in terms of GUI / UX, the L for learn is confusing, I thought it was learning the controller as in MIDI LEARN, instead it is learning to assign the controlled parameter.
- the Cubase MIDI Remote baffles me, it seems to come and go on every project? I have one Arturia MINILAB 3 and find myself always have to recreate it
- I used to set up QC through a MIDI track because it seemed appropriate to use a Midi Monitor to see my pedal MIDI coming through the Minilab MIDI Control Jack. And record it on a midi channel routed to the plugin.
- UX again, having to go tweak stuff in Studio/Track QC and VST QC which does say is obsolete and has to be done through the MIDI Remote is confusing. I’d really prefer a solid MIDI Remote feature that remembers my hardware and preferences for every song and ONE convenient place to control BOTH routing : the actual hardware controller and the software parameter, with all these things in a MATRIX next to the MIDI Remote (there is space horizontally for it) so that it’s clear for each track/plugin.
- The QC function is SO UNCLEAR as if the left inspector is highlighted the assigned buttons are NOT THE SAME as if the plugin is highlighted! Maybe a Track QC vs VST QC, I don’t know, I find it hellishly confusing as how can one properly manage if changing windows messes up assigned controls?!
- IF I setup my MINILAB 3 in the Studio window, then the expression pedal does NOT go through !! The reason I used a MIDI Track until now is the only way I could connect is to monitor enable my MIDI track routed to the SideChain plugin on my audio track and do a MIDI learn say on the BIAS FX2 Wah pedal so it could pick the expression pedal sent through the MINILAB via the MIDI track !! And the bloody issue is that it only worked for plugins with MIDI learn !! IK MIXBOX does not have it so I cannot fathom how to control the wah there !!
So I am probably missing some things there, but the truth is the QC and MIDI Remote functions in Cubase don’t have a smooth UX and are discombobulated, messy and confusing.
I REALLY wish for a smoother UX so I could plug, assign and control smoothly !
Thanks Johnny, Martin and all at Steinberg, I hope my comments are helpful and not too annoying 
Love
Antoine
2 Likes
So am I most often. It took me quite a while to understand the concept and I am not sure that I have figured it it all out yet.
I had exactly the same issue. Coming from MIDI I was so used to “Learn” assigning a MIDI controller to a software element. But here it is used to connect two software elements to each other.
That should not happen. My MIDI Remote is available anytime I start Cubase. I heard others describing the same issue as you experience. I am not sure if it happened with the 13.0.50 maintenace update.
Also: I am using something that I created with the graphical editor, not a programmed script. Maybe that makes a difference, maybe not.
In any case, the MIDI Remote Surfaces should not disappear unless you actively disable or delete them.
2 Likes
As I said many times on this forum, we don’t need yet more plugin effects or instruments, we need a smoother workflow !!
The efforts Steinberg made on VocalChain, Shimmer, StudioDelay etc… are far less interesting to me than fixing workflow issues.
Modulators are cool though. But I really hope there are some updates coming soon to C14.