hi. i am ready to start my first sonar song but i have run into a playback issue. every time my song loops, (using omnisphere) i hear a pop or click. i tried adjusting the buffer size from minimum to max and the problem persists. i use a focusrite 2i2 as my audio interface. how do i fix this? 
 
my specs: i7 4770, 16 gb ram, win 8.1 x64

How are you doing looping?
Is the Omnisphere track bounced?
Not enough to go on from the OP.
 

TomHelvey
How are you doing looping?
 
use the loop button.
 
Is the Omnisphere track bounced?
 
no, its not. 
 
Not enough to go on from the OP.
 

 
i was reading that sonar needs to be configured in audio settings but, i have no idea how to do this. the audio settings are very cryptic.
 
that said, its pretty badass that so many options are available. you can tell sonar is a very mature daw.

still having clicks. need help :( re installed, clicks still occur. if anybody is reading this, please help me however you can. would be very thankful. of course i will call support monday but if anybody has any suggestions please post them. 

Usually this is caused by a level difference between the end of the loop and start of the loop. The "brute force" answer is to add a very short (7 ms or so) fade in using slow in, and fade out using fast out.
 
Another reason could be setting the clip beginning and end to snap to zero audio crossings, but the loop markers are different. Zoom in really closely to find out. I always disable snap to zero crossings in preferences and rely on fades instead, as I find them more effective. Any kind of disparity between the clip start and end and the loop marker positions can cause a click.
 
However, I have noticed lately that some loops - not all - will click (albeit at low levels) even if there is a fade. I have finally been able to reproduce it and am sending the project to Noel to see if there's any kind of issue.

i tried everything and i do mean everything in audio settings. i heard this daw was problematic too. guess ill contact support on monday. this just sucks. 
 
i do understand what he meant. he was saying i should go to playback settings, and adjust fade in and out to 7 seconds. i also tried to use the zero crossings fix with no luck. 

Pressing the F1 key with a project open will open the manual. You've been at this farr too short a time to think this is a poorly designed software. I still struggle with things, and have been using this since Sonar 5... Patience and reading glasses help a lot.
 
BTW - The guy (Craig Freakin' Anderton!) who gave you detailed info is a monster user, galaxies beyond power user. Legend in many ways. If you didn't understand the info - RTM.

i 

jshep0102
Pressing the F1 key with a project open will open the manual. You've been at this farr too short a time to think this is a poorly designed software. I still struggle with things, and have been using this since Sonar 5... Patience and reading glasses help a lot.
 
BTW - The guy (Craig Freakin' Anderton!) who gave you detailed info is a monster user, galaxies beyond power user. Legend in many ways. If you didn't understand the info - RTM.

i want to say that i appreciate andertons help. thanx craig :) but unfortunately, adjust fade in and out to 7 seconds in playback, and doing the zeros crossings fix did nothing. so im at a loss here.

and i use a focusrite 2i2.

The fade in/out settings in preferences only apply to starting and stopping the transport. What Craig meant was to add fades to the clip if the audio has been rendered by freezing. If it hasn't been rendered, you'll have to use volume automation.
 
But the better way to prevent this is to make sure your loop points are located where the level is low, and not just at zero-crossing. Interrupting audio at a zero crossing won't prevent a pop if the surrounding amplitude is high.