Clicks being introduced when bouncing split crossfaded audio tracks

Here are a few things you should investigate:
1. Make sure the split was at a Zero Crossing
2. Make sure the cross-fade is faded in enough to cover any artifacts
3. How are you setting up your rendering  and are you playing back the rendered audio through the same gain stages and effects? This will or may cause clipping artifacts.
 
I cross-fade allot and if there is an artifact upon export, its usually because the cross fade needs to be bigger, meaning it needs to be faded into the tracks more.
 
CJ

Thanks for the replies. To answer the questions, I've tried every combination of real-time/fast bounce to tracks and they don't make any difference. I've tried turning on/off options like 64-bit engine, fast bounce, different bit depths, dithering on/off. There's no hardware-reliant effects being used and I've made sure the fades are big enough.

What I don't understand is that if I play the project back and listen in real time there is absolutely no click at the crossfaded points. It's only if I try to render using Tracks/Bounce To Tracks or Export>Audio that the clicks appear (they are very small but enough that I can hear them and as I provide audio for broadcast I need to make sure the tracks are as clean as possible). And they only ever appear at the point where the crossfade was, nowhere else in the track.

To make it more confusing, it often happens randomly. Let's say there are four points in the audio track where I've split and crossfaded, a click might appear at one point but not another, but then on a different render it might be on one of the other crossfades, but always on a crossfaded segment.

The only way I've found so far to get a rendered track without clicks is to literally record 'what you hear' onto a new track while the project is playing in real time. But I thought this was effectively the same process as deselecting Fast Bounce during render (which doesn't work the same and will produce a click).

I'm just at the point where I don't trust Sonar to give me a true clean render of my audio without having to put headphones on and listen intently after every render.

To make it more confusing, it often happens randomly.

Well with this new info you supplied, I can tell you with 100% confidence that this is not a SONAR issue.
It is a Sound Card driver issue and/or a sound card driver setting issue, and/or a lack of having a good sound card.
 
CJ

CJaysMusic

To make it more confusing, it often happens randomly.

Well with this new info you supplied, I can tell you with 100% confidence that this is not a SONAR issue.
It is a Sound Card driver issue and/or a sound card driver setting issue, and/or a lack of having a good sound card.
 
CJ

My sound card is a Focusrite 8i6 with all latest drivers and PC is brand new last year from a highly reputable builder of custom audio PCs with no extraneous software/bloatware. Purely used for audio.

ASIO buffer size is 10.0 ms
Sonar reports latencies as:
Input 21.0 msec, 924 samples
Output: 31.0 msec, 1366 samples
Total roundtrip: 51.9 msec, 2290 samples

I highly doubt the PC is maxing out or under any stress as there's only a few tracks in this project and zero FX to use processing power.

I'm certainly willing to accept it might be a stray setting somewhere, but I'm curious as to how you can say with certainty that it's 100% not a Sonar issue. It could at least be a Sonar issue in combination with a particular hardware configuration.

But thanks for both your feedback - I'll investigate latency settings and see if there's anything else suggested that I can try.

Total roundtrip: 51.9 msec, 2290 samples

That is pretty darn high for round trip. If you have a good PC,you do not need to have your buffers that high. you have not listed any PC specs, sop i'm assuming your 'custom PC needs some updating.
 
CJ