Forgive me if you've already stated this, but are you saying that, if you record into your left channel, you get the full signal in the left speaker and residual in the right? And similarly, if you record in the right channel, you get full output in the right speaker and residual in the left?

Bristol Jonesey - No problem, thanks for your time.  What I'm saying is it doesn't matter if I record with the Sonar Input on L, R, or Stereo I have sound in opposite channel when panned 100%.  But it doesn't show in the meters.  Even if I bounce it down to Mono.  I imported a wav sample the comes with sonar and still the same thing.

I have searched the web quit a lot about the spiking and dropouts problems in the past and never found much in way of any answers.
Well hopefully Focusrite can help.

You've gotten a lot of helpful feedback.  Granted my box was from a different vendor (Presonus Firestudio Mobile), with similar configurations, I had the very same issue.  I was panning fine with my other audio card.  I bought the new interface and the problem was noticed right away.  At first I though it was something in my Sonar configuration. I spent a week on research and the forums for a sonar configuration.  Then I narrowed it to the routing between my mixer (32Ch-4bus) and box (three weeks of re-routing wires).  Then I tried just recording directly into the unit (bypassing the mixer), assuming that's how you are doing it, and Sonar still would not pan the tracks.  I believe I've narrowed the issue the software mixer for the unit.  I was not able to pan in the on-screen Presonus mixer for the box either.
 
My unit also came with Studio One DAW. My panning in there still did not produce any audible panning through my monitors.  So after three months, I retired the unit.  It was still new then, but too late to return.  I don't think it's a cakewalk thing or even a USB thing being that my unit is firewire only.  Have you tried using/configuring both the ASIO or WDM drivers.
 
Good luck!

Original Dunga - Yea I tried them all multiple times.....no difference.
Bristol Jonesey - I have ruled out Sonar at this point without a doubt.

Well I Installed Presonus Studio One and guess what?
All the same garbage.  
The panning problem, and the cpu spikes.
I tried everything in Presonus to get a 100% panned channel.  
I actually have no right channel in Presonus either.  
So it looks like it has to be my interface.  
So say I install Presonus on my Daughters Laptop and hookup the Scarlett and I still get the same problems it has to be the interface, correct?

What code media said..... I was having panning problems and was in OFFSET mode for a ton of the mixing project (also having other problems as well).
 
Hit the "O" key and sure enough, there were the volume and panning settings causing my problem.... reset each track to center and faders to 0db... starting mixing all over again and viola, all my mixing issues disappeared.
 
Now, I have been using SONAR for about 20 years now and this has never happened to me before (can't believe that I didn't hit a random letter O in those 20 years at least more than this one time)... so, is this offset feature been around for 20 years?  When did SONAR add the offset mode with the letter O the trigger?
 
Sorry to hijack this thread but I thought this would be a pertinent topic to discuss a bit more.
 
Jim
 

Never did resolve the panning issue.  All evidence points to my Interface but this thread kind of ran off into my other problem of CPU spiking and I wanted to post back about the spiking in case anyone else having this problem still.

Okay, I thought I had this solved before and it was not.  Hopefully this time it is!
Even though I had run numerous benchmarks on every piece of hardware in my tower.
There was nothing to extreme on the CPU temp, but thought it still may be an issue.
Cleaned everything up and put a better fan on my CPU.  It helped but I soon noticed the spiking again.
I swear I have already been through every option in Sonar at least a dozen times.  
I turned off Read and Write Caching and the problem seems to be gone.

Scook - Sorry, I guess I didn't your post last time.  To answer your question, no I have only used the Scarlett 2i2.
I never did bother to hook it up to a different laptop/pc.  It is definitely NOT the "O" key, or Offset mode.
I am convinced it's the interface.

Alex - You have a point about the footer.  I guess it's actually kind of ignorant to ask for help and not have that info available.  I don't mind when other ppl do it but, I don't want all that crap at the bottom of everything I say.  Will be sure to post a more thorough description of my rig next time I ask for help though.
But I am pretty much done with the Pan issue. I've tried it on different DAWs.  
I might try the driver boost thing.  But I generally stay away from those type of apps.
Will also try the AUD.ini file.
I'm using Scarlett 2i2.  It doesn't support Mix Control.  And no firewire.
I was mainly posting back because my other CPU Spike issue seems to be resolved.  
I had to turn off Read/Write Caching.  

Thanks again everyone.  Will post back when I find something definite about the panning issue.

>  I don't want all that crap at the bottom of everything I say.
 
Fair enough, but it's really useful for us. When people come into the forums and start having similar symptoms we can see the similarities straight away. It also saves us time searching through a thread and allows us to always think about your particular system every time we respond. Finally a forum member might recognise a known issue with particular hardware and bingo just by reading your footer. Cheers...
 
> But I generally stay away from those type of apps.
Same here, this was the exception though, I understand the reluctance, just be careful how you install it and all will be fine. This will at least be a good way of auditing your PC, you can choose to have drivers installed automatically, or go and get any outstanding drivers yourself if you so wish.
 
So you are on Focusrite USB 2 Driver-2.4 I assume: http://uk.focusrite.com/d...s?product=Scarlett+2i2
 
And windows update :) Often there are USB fixes for instance (not that it should solve your particular issue).