Is there a way to move the crossfade point to the left by a specified amount during the quantization of audio clips? 
 
Split beats into clips by transient markers -> Quantize by Audio Clip Start Times.  The split is on the transient and therefore sometimes the crossfade even when small effects the transient. I would like to avoid this by shifting the crossfade point to the left before or during quantization.  I think that protools has a feature for this.  Do we have one in Sonar?
 
Thank you in advance
Demetrios

The most recent update to transient-detection algorithm tends to place transient markers late, typically 10-20ms into the attack, which can be quite problematic. The benefit is fewer missing, superfluous or grossly misplaced markers as with earlier detection algorithms, but to me, the late markers are a bigger problem because they're pretty much all misplaced, and there's no way to correct them all at once.
 
The only half-way reasonable way I've found of dealing with this is:
 
- Make a copy of the clip in another track or lane, and nudge it approx. 15-20ms earlier.
- Disable all markers on the original track using the Threshold slider.
- 'Apply' the markers from the nudged track to the original track.
- Scan the track for missing/superfluous/misplaced markers that need to be fixed manually.

brundlefly
The most recent update to transient-detection algorithm tends to place transient markers late, typically 10-20ms into the attack, which can be quite problematic. The benefit is fewer missing, superfluous or grossly misplaced markers as with earlier detection algorithms, but to me, the late markers are a bigger problem because they're pretty much all misplaced, and there's no way to correct them all at once.
 
The only half-way reasonable way I've found of dealing with this is:
 
- Make a copy of the clip in another track or lane, and nudge it approx. 15-20ms earlier.
- Disable all markers on the original track using the Threshold slider.
- 'Apply' the markers from the nudged track to the original track.
- Scan the track for missing/superfluous/misplaced markers that need to be fixed manually.

I have no idea what OP is talking about but this is extremely clever.
 
Good one.

Thanks, Beep. Necessity is the mother of invention, right? .
 
I've pretty much stopped using Audiosnap because of this problem, but when it can't be avoided, and it's just one or two tracks, this works pretty well. Note that you can continue to nudge the copy around after enabling Audiosnap to get the best 'average' correction for the whole track before applying the markers; 15-20ms is what I recall having to use in the past, but it could be more or less than that depending on the nature of the audio.

You could also select all the transient markers and move them all by the desired time on the current track. Would this not do the same thing as copying a clip that has been moved?

brundlefly
Thanks, Beep. Necessity is the mother of invention, right? .
 
I've pretty much stopped using Audiosnap because of this problem, but when it can't be avoided, and it's just one or two tracks, this works pretty well. Note that you can continue to nudge the copy around after enabling Audiosnap to get the best 'average' correction for the whole track before applying the markers; 15-20ms is what I recall having to use in the past, but it could be more or less than that depending on the nature of the audio.

Yeah, as soon as I read your post I realized the implications. Of course once the correction is complete just nudge 'er on back. I will likely be needing this in the near future. I've personally been using Reaper for any massive time stretching tasks (like multitrack sessions that are CPU/HDD intensive and require a quicker/more reliable workflow) but much prefer staying within SONAR for anything I can. With this method I might be able to use SONAR with an optimized workflow to align the vocal tracks of a live session (separately) overtop of the bed tracks I aligned in Reaper. So the multimic'd drums get mangled in Reaper hit by hit/measure by measure. Then I take the ORIGINAL live vox from that session (untweaked) and align them in SONAR because it's only two tracks and phasing shouldn't be a problem once the "dead space" on the vox tracks are snipped out (word for word if need be).
 
Guits and bass are being overdubbed on top of the corrected drums which will overpower any mic bleed from the original session (and a touch of EQ on the drum overheads should help even more in that regard).
 
So I get to work with totally fresh/non stretched/non-rendered/etc vox tracks (which are from the same live session) and stretch them proportionally to themselves over top of the Reaper corrected drum tracks (and the new overdubs).
 
lol... whatevs, just being able to do the vox in SONAR will make things faster/easier with this trick... and I find it's helpful to type up my plans here.
 
But yeah... you are quickly approaching scook levels of SONAR omnipotence thar, Brundledood.
 
Stay awesome.

reginaldStjohn
You could also select all the transient markers and move them all by the desired time on the current track. Would this not do the same thing as copying a clip that has been moved?

and this gave me more ideas to compliment Brundle's.
 
Essentially scanning sections of clips and where the transients have been auto detected, finding spans of said clips where I can tell a healthy majority of transients have been misdetected (like 30 second span or a minute span or whatever are MOSTLY late/early by x amount of milliseconds in one direction) then lasso/range select the transient markers for that section, hold Ctrl and "Move" the entire lot backwards/forwards (by dragging the center "Diamond" of one of the selected transients).
 
If the sections auto transient detection is almost perfect but merely late/early and there are only a few transients out of align with the rest of the auto detected transients (like they are mostly late by 10ms but only a few are off by 7 or 3 or anything other than 10ms) then those markers can be removed from the selection (Ctrl + Left Click on the unwanted selected marker) then the bulk move can be done and those wayward (or correct) markers can be done one at a time... which avoids a ton of one by one marker moves.
 
Yeah... sumthin' like that. Wicked time saver.

brundlefly
The most recent update to transient-detection algorithm tends to place transient markers late, typically 10-20ms into the attack, which can be quite problematic. The benefit is fewer missing, superfluous or grossly misplaced markers as with earlier detection algorithms, but to me, the late markers are a bigger problem because they're pretty much all misplaced, and there's no way to correct them all at once.
 
The only half-way reasonable way I've found of dealing with this is:
 
- Make a copy of the clip in another track or lane, and nudge it approx. 15-20ms earlier.
- Disable all markers on the original track using the Threshold slider.
- 'Apply' the markers from the nudged track to the original track.
- Scan the track for missing/superfluous/misplaced markers that need to be fixed manually.

 
You obviously know exactly what I'm talking about.  
Thank you!  Thank you!!  This I will try for sure. 

reginaldStjohn
You could also select all the transient markers and move them all by the desired time on the current track. Would this not do the same thing as copying a clip that has been moved?

Hmmm... I came up with the workaround because this did not used to be possible, unless I was always mistaken...?
 
Will have to try it.
 
EDIT: Well I'll be danged; works fine so long as you deselect the first marker if there isn't room to slide it earlier.