Would 'create fades with fixed length' solve it ? ( in the fades dialog box )zandurian wrote:Yes, not the issue because if I understand correctly: working, successful, right sounding crossfades are being screwed up while bouncing. I remember living with the fear that a bounce was not going to reflect what was heard before bouncing. It meant that every bounce would have to be rechecked start to finish to see if there are deviations from the original.stephentayler wrote:If we are talking about crossfades, there is one shortcoming in DP that is more efficient in ProTools. PT will not allow a crossfade to go beyond the bounds of the soundbite, alerts you and will adjust the range accordingly. DP will allow you to create a crossfade even if there is no audio present, and it does not alert you, so clicks at soundbite extremes may be exposed.
I'm pretty sure this isn't the issue here, but it is worthy of note when creating crossfades.
Cheers!!
SWT
I don't mind being allowed to crossfade past a soundbite's boundaries but I wish an there was a way to see the edges of both (just to have a heads up) while creating the crossfade.
I think to have tried it successfully...
Or maybe use individual length / curves ?
If the soundbites are cut at 'non zero level', clicks should appear, not ?
Listening / playing = only 1 active soundbite is heard, not so when bouncing ?
I stopped bouncing too... just record in realtime to a new track
Best
Klaus