Hey guys, recently I was doing audio detect silence on 15 vocal tracks, and I wondered how I could make it so that the events resulting from this process align with the grid. I don’t need them to be stretched or moved, I just want the events themselves to snap to the grid as per my quantize settings at the start and end. After that, I would quickly go through them to see if any of them got cut off too much, then apply fade-in and fade-out. Right now, I have to do all this manually. Thanks.
Hi,
I really don´t understand what you´re asking for to be honest.
You want the events to align with the current grid but you don´t want them to be moved. At the same time you want to keep the grid as is. Hmm.
There are two possibilities: Either move the events to the grid or move the grid to the events. Or do I miss a third option here which is obvious but just not for me?
I mean that you can manually clickhold and drag the very edge of specific event so it snaps to the grid. How to do it auto for many events? Or at least how to make all events to snap equally, when you select them and drag the edge of one.
Hi Vitek,
I really don´t get it. If I dragged the edge of a freshly cut sub event after silence detection I would simply stretch out this event to its original length. In other words I would restore the silent part.
Can you please make a screenshot before/after. I really don´t get it.
Anybody else…?
If all the resulting audio events of a Detect silence process remain selected, I can adjust the size of them all by redimensioning just one, on my end. This, both for their start and end borders. With Snap on and Snap type set to Grid, the events start or end positions are adjusted accordingly.
Sure, this is not done automatically, but maybe the Project Logical Editor could help, in this case…
On my end, I can resize the resulting events, too. But - and this is the crucial part - only in a way that the original event is partly restored with the parts of the event that were under the threshold. So, resizing doesn´t make sense unless silence is added. Am I missing something? I sure do…
It begins to make sense if fade in/out processes are applied in the same way on all the resulting events, as to tame/get rid of any anomaly or little noises that could have remain in the original event, I think.
Maybe automation would be better, for this kind of treatment, but well, to each his own…
Hi,
thanks for helping me out here, appreciated
I´m afraid that´s not the point… the outcome is the same. If you resize your subevents (be it with or without fades which move with the new borders anyway) you add parts of the events which were detected as too quiet (or silence) by the threshold. I just don´t get it… why would you remove silence with a threshold if you undo it afterwards. What am I missing…
It is undone only in a very partial manner (adjustment of the events size to grid, which maybe follows a 1/64 quantize setting) and I guess that the fade in/out process is aimed to cover this.
I’m thinking also of a way to correct in a more or less smooth way an eventual bad sonic or noisy environment. But what do I know ? Just hope that @vitek246 will give us more precisions on the matter.
… who knows - we will find out.
I was under the impression there was some sort of magic feature I didn´t know of. And there are quiet a few of them under Cubase´s hood that I am not aware of, that´s for sure. So let´s see what @vitek246 has to say!
@Reco29 @cubic13
Sorry for the late response.
Look, guys, if I select all events and drag one of them to the grid, all the other events just increase by the amount of silence that was added to the event I’m dragging. What I need is for all the others to “round off,” so to speak, to their own grid values. Something like this at least:
And the best scenario fo me will be this:
After that plan was to apply fade in (and fade out for the end of the event):
So the question is how to make it at least ‘semi-auto’? Or maybe with logical editor and macro or any other tool i can make this with 1 button?
I know that I can cut off the tails with the scissors, but that’s a workaround, and doing this for the start and end of each event in the project takes a lot of time.