There’s a process I do on bass guitar sometimes where the bassist has a lot of sliding string noise, so I low pass and eq it out on just the slides. I would do this with Audiosuite in Pro Tools on every selection I wanted to affect. I assume this is done with Direct Offline Processing?
How do I do the same process to multiple sections on one event? I saw something about “Pin Process” in some videos, but it doesn’t show that option in my Direct Offline Processing window. I’m on Cubase 15 Pro and am using Fabfilter Pro Q 4.
One thing I’m trying to figure out is the workflow for this type of process as I mentioned above. What I would do in Pro Tools is open the Audiosuite plugin, change the parameters to what I needed it to be, make a selection, hit render, and it would render the selection. I could then make a selection anywhere on that track and hit render and go through the track and lessen the squeaks by a low pass filter just on the squeaks.
I’m trying to figure out this same workflow.
What is the best practice? Make a selection, split the event, and process the event? Or just make a selection on the event without splitting anything and process it? I can’t figure out an efficient way to do this multiple times in a row. I see there used to be a “Pin” function on older versions of Cubase, but I don’t see it here on 15 Pro.
Also, I’m seeing “The Project contains events that use the same audio material as the event in this editor! Click “New Version” if processing should apply only to the edited event.” and there is “Continue” or “New Version” button. I’m not exactly sure what this is referring to or what this means. This also seems to happen when “Auto Apply” is off and I hit “Apply”.
EDIT: I think I figured out the above bold dialogue box that came up. I had to change “On Processing Shared Clips” in Preferences > Editing > Audio from “Open Options Dialogue” to “Create New Version”.
I accidentally chose “Cubase 14 Defaults” in “Preferences Presets” and it wiped out all of my preferences. I assumed if I didn’t hit “Apply” or “Ok”, it wouldn’t have stayed that way. I was wrong!
I typically end up splitting events just because I like to see where processing has taken place. As with many other things in Cubendo key commands and macros are your friend. I have one where once I have a selection made the key command splits the event and crossfades. I also have key command shortcuts for some frequently used processes in DOP, like sending to RX or using a DeClick plugin.
As for repeat processes you can either select the split events and process in one go, or you can process as you go. For some jobs I actually prefer to engage automation Preview mode, open a plugin in an insert (like Pro-Q) and then tweak it until I like the sound. But then I make a decision to either punch the automation or to drag-drop the plugin into the DOP window which then processes the event after which I turn Preview off without punching.
And for convenience’s sake I also often drag a process into the favorites section in the DOP window. A single click there will process the event with whatever plugin(s) you selected and saved as a favorite.
I’ve yet to try this in the latest update so I can’t promise it works as it should but it was said that previous bugs were ironed out. I’m just saying that because if you’re on an older version it might be worth updating. If you’re going to use DOP that is.
Thanks for the reply! I’m not familiar with automation preview mode! I’ll have to look that up!
On another note, I watched the video, but it didn’t seem to go over the use case I was wondering. It seems older versions of Cubase have a “Pin” mode where you can just use the same process over and over, which is very convenient, but it doesn’t seem to be here in Cubase 15 Pro. AM I missing something there, or did they get rid of that?
The solution I’ve found so far is to copy one process, make the selection on the next part, hit poughkeepsie + X, select that event, then right click “paste” in the processes section. I was wondering if there is anything faster similar to Pro Tools where you just have the process already and hit “render”.
I know there is the “Favorites” as well, which I imagine is one click, but the “Pin” idea seemed to be the ticket, but it doesn’t seem to exist anymore.
I can’t recall a “pin mode” in Nuendo. Was this in DOP or somewhere else? And how did it work?
When you’ve applied the process once - instead of copy-pasting you could drag it down to favorites. Now that process with those settings is remembered, even as a batch (i.e. if you have several plugins processes in series you can drag them all down and that’ll be one favorite).
So since you wrote that in PT you would “open the Audiosuite plugin, change the parameters to what I needed it to be, make a selection, hit render, and it would render the selection. I could then make a selection anywhere on that track and hit render” this would be the same, no? Same order, right? With clicking a button when repeating.
So, the video I watched was this, and I didn’t realize, but I believe he’s using Nuendo, so maybe that’s why there is that “Pin” mode. It’s a little older video too. He talks about it at around the 5:30 mark:
I’m thinking that the “Favorites” option would be closest to how it works in Pro Tools at this point. But, the “Pin” option seems pretty much the same as Pro Tools does, which would be awesome to have.
The difference with Pro Tools with opening the Audiosuite plugin is that if you open the plugin and get the settings once, you just leave the plugin open, select the audio range you want to affect, then hit “Render”, and you can do that anywhere you want and as often as you like as long as you don’t close out the plugin, so it isn’t a matter of searching for the same plugin, setting it, and doing it over and over etc.
Now, with Cubase, the closest would be having to make a favorite to achieve this, and then select apply on every event you choose to. It’s similar of course, but the way with Pro Tools is non committal in the sense that you choose the plugin you need at the time, change how you want it, and then hit render on any selected clip or location you want. It’s kind of the same workflow with getting a “Favorite” with the plugin you need at the time, but it’s a slight extra work step involved, and if you don’t use that process often, you have a committed “favorite”; a process which you can easily delete of course, but the “Pin” function in the video above would be really nice since it would be less steps and less thinking. I also am not sure how it works with Favorites if you can edit the process per event if they need slight tweaks? That’s something I’d like to know if I don’t get to try it soon enough.
But all in all, that “Pin” feature would be really great!
Ok, I understand now. I never use “Pin”. Maybe that’s a Nuendo-exclusive feature.
I think there is little difference here using favorite though. It takes you one click to pin a process, and it takes you one “drag” to put it in favorites instead. After you have done that it takes you one click either way to apply that process. So you’re literally not saving any time at all using “pin” versus "favorite’ - except that after a while you’ll likely want to delete the favorites you’re not using.
Anyway, I support your request to also have it in Cubase. Seems silly to not have it included.
Yes. If you click a favorite all that happens is that it recalls those saved processes with saved settings and applies them to the selected event(s) after which the processes are listed in the top-left section of the window. Just click on the process and adjust parameters if you need to (only have to select the process if it’s more than one I think).
I guess the way you put it, that’s true. Just not having to make a favorite that you may delete later just seems unnecessary, but it doesn’t take long to create or delete.
And, thank you! That’s good to know you that can edit each clip independently!
If you feel that “pinning” is really helpful then you should search for that as a feature-request-topic with Cubase tagged and upvote it. If it doesn’t exist I think you should create a new thread and request it, and tag it feature-request.
