Hello dear Cubaser,
I have a multi-hour recording of a band rehearsal. I want to cut out the individual tracks from the recording and edit them. This works, but there is one step involved that is giving me a headache. The first step is to “normalize.” I select all the events stacked vertically and press F7. Then I choose the “Normalize” process, set it to -3dB, and click “Apply.” It works perfectly for the first titel. But when I try to normalize the second titel, things get weird. I specifically select the second cut-out track—meaning all the vertically stacked events are highlighted—and press F7. “Normalize” is already selected there, but when I click “Apply,” absolutely nothing happens to my selection. Just for the sake of testing, I set it to -30dB. I could see that Titel 1 was being unintentionally altered, even though nothing there was selected. I have a workaround for this: I use “Bounce Selection” across all tracks for each “cut-out” section. That allows me to normalize them independently. But I wonder—is this intended behavior, or is it a bug? I don’t recall exactly when I first noticed this problem; it didn’t start with Cubase 15—it’s been annoying me for a while. So, Cubase allows you to select and normalize a section within an audio data set once, but never again? That can’t be right, can it?
Thank you for comments!
It sounds like you are normalizing BEFORE bouncing, which would normalize the entire selections such than the second normalize would have nothing to do because it the same events.
I don’t know what “F7” does. It’s usually best to write out what happens rather than what key you’re pressing since key commands can be customized and people then forget what the defaults were.
If you’re talking about Direct Offline Processing then there’s the option to “create new” clips that the event(s) refer to. If you did not choose that then you should try it. Not choosing it would process the underlying clip that the shared events reference, and I would expect the behavior you see based on that. But if you do select “create new” I would expect the outcome that you want (though I haven’t tried it myself).
Shortly after I posted I realized the response could be confusing. Mathias provides insight by referring to “reference”.
Basically, when you cut up the original recording into songs, the songs at this point are still references into the original recording. Your first normalize is for the entire recording, so is the second because it is a reference to the same material. Once you bounce (or other action to generate new events) now you can normalize them individually.
Thank you for the answers.
F7 opens the “Direct Offline Processing” window on my computer..
I think it would be great if I could handle the offline processing a little more carefree. In the zeal of the work, I forget about “bouncing” and come back to Bredoille again and again. Why isn’t this going automatically?
The “create new” option sounds very interesting, but unfortunately I don’t find it.
Where exactly is this option?
PS: The idea behind not creating new events and instead processing all of the “underlying” clip (audio file) instead is that you may have common things that you wish to address. For example, if noise is consistent throughout then maybe you want to just run a denoiser once for all events, instead of doing it once per event. I think that’s the reasoning. I always create new so…
I switched to “Create New Version.” Then I marked all the events (cut out) of a song and started normalization. Interestingly, now the event names are actually changed automatically, but according to a different rule as in “Bounce.” The problem, now there is no normalization at all. I can see about 5 songs at the same time through Zoom, no one responds to normalization. I also tested with -30dB, nowhere to see something, Hmmm …
Since that seems to be a problem, I would suggest you bounce the events to create new files of each and then normalize. I’ve done this a bunch in projects, but not lately. Hopefully that’s not broken!
Initial experimenting with Cubase 15 appears to be working. It will take a while to put together a video to show it, then you can judge for yourself. Hopefully, can complete this today!
