• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Multitrack bend marker quantize behavior

Hi folks, I'm running into some odd behavior that I'm hoping folks here can help with. I have a multi track drum recording and I'd like to tighten it a bit. It's comped from several takes. I have bend markers applied to the Kick In and Snare Top tracks, and then I group the tracks and apply some quantizing. The odd part is that when I do that it affects other non-selected clips in strange ways. Here's a quick screengrab showing the behavior. Note that I select some grouped clips, click the "Apply" button, and it seems to quantize the selected cips, but also does some other stuff to clips earlier in the timeline that are not selected.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Anyone know what's happening here? It's almost like it's doing strange things to other clips that are in the same take but not selected, but I have no idea why:
a - it would do that at all, and
b - why it seems to remove and reset other bend markers.

Thanks!
 
Anyone know what's happening here? It's almost like it's doing strange things to other clips that are in the same take but not selected, but I have no idea why:
Quantization works on clip level and not on event level and takes are just one single audio file. There are three solutions to this.
- increase the events you want to quantize a bit and create an additional bend marker at the beginning, so it's kinda give it a starting point.
- bounce the selection you want to quantize before doing it.
- create a new clip version (which is the easiest way in my opinion). This creates a virtual "copy" of the clip which won't take more space like bouncing.

Personally I don't quantize with bends, I do nearly everything by slicing. I don't like what bending does even with it's transient protection.
 
Last edited:
Quantization works on clip level and not on event level and takes are just one single audio file. There are three solutions to this.
- increase the events you want to quantize a bit and create an additional bend marker at the beginning, so it's kinda give it a starting point.
- bounce the selection you want to quantize before doing it.
- create a new clip version (which is the easiest way in my opinion). This creates a virtual "copy" of the clip which won't take more space like bouncing.

Personally I don't quantize with bends, I do nearly everything by slicing. I don't like what bending does even with it's transient protection.
Hi Navar, thanks for helping out.

Interesting...I've never known that's how it worked. So even though the clip appears to be a discreet clip on the timeline after comping, it's actually still a single clip and operations performed on it are performed on the full take? Also, how then did I end up with parts of the take being quantized earlier in the timeline but later parts not (that's what we see in my video)? Doesn't that mean that my earlier quantizing should have affected the whole take, including the later parts?

In the meantime, I'll try a slicing workflow instead of bend markers.

Thanks again,
Dean
 
Doesn't that mean that my earlier quantizing should have affected the whole take, including the later parts?
Yes, doing this inside takes can get messy. A selected take can be in the middle of the whole audio file, which means, that the data you see can before or after the take you are working in. It's a bit hard to describe :rolleyes:
If you like to test it by yourself, just take a recording made in takes. Create a new track and copy this event. Expand the copy to the left and right so see the whole audio file content. Now just add a simple bend marker in the first recording with the selected take and move it around. Select a different take and move it around. You can see where the bend markers are added on clip level and how it changes the whole audio file.
But that's by design inside SPro and there are several ways as described above to get over it, it's just something you have to know when working with takes and bend markers.
There are different stages of the content you see, the clip/file level and the event level. As an example: you can add a FX plugin to an audio event and this will be only applied to this single event, even if you have several copies of it. But things like bend markes or clip gain are a stage below and work on the whole file and every event, which contains this data will have the same process on it. That's why they've added the functionality of clip versions a few years ago. Before that, people like me bounced a lot of useless copies of single events to have fresh audio data. ;)
 
Thank you! Appreciate you taking some time to explain.

Last question - when using a slicing mechanic rather than audiobend markers do we still encounter the same behavior, or does slicing create new versions in such a way that we sidestep the problem?

Dean
 
Thank you! Appreciate you taking some time to explain.

Last question - when using a slicing mechanic rather than audiobend markers do we still encounter the same behavior, or does slicing create new versions in such a way that we sidestep the problem?

Dean
That depends on the material in question, usually there would be no such behaviour visible due to the slicing and how gaps and clips are treated.
 
Thank you! Appreciate you taking some time to explain.

Last question - when using a slicing mechanic rather than audiobend markers do we still encounter the same behavior, or does slicing create new versions in such a way that we sidestep the problem?

Dean
Slicing does not create a new version, it's just a different way of editing, you move the material and fill the gaps, which normally works very well if you take care of the crossfades and double check for any flamming double hits. But in difference to time-stretching you don't manipulate the audio data by itself. This process is know as "slip editing" and comes from older days when there were no modern algorithms available. There are a lot of ProTools based tutorials around this, but the process is the same in any DAW. Turns out, it still sounds good if done right. And normally, if the performance is okay, you don't have to move note by note. Often there are some bars which are behind or before but the whole section is nice and stable and you can get along by adjusting largers chunks.
 
Back
Top