guitar distorts when recording OD

My audio is distorting in playback when I record guitar - not clean guitar, but OD.   Recording vocals, acoustic guitar or clean guitar is fine.   It's just when I record with a little gain on my guitar.

Thanks!
Greg

kristoffer
Umm... How many tracks do you have when it starts do distort? 
 
Or does it happen at a blank project? 
How does your CPU level look like? (in Sonar)
DPC latency? 

I have about a dozen songs that are nearly finished except for lead guitar, which I am currently trying to record.   Each song has anywhere from 15-20 tracks.   I have not tried recording audio on a blank project.
I don't have a visible CPU gadget, so I don't know yet.  I'll have to check it today.
I have not yet checked DPC latency.
 
Thanks!
Greg

Thanks!
 
Greg

I don't have the CPU meter showing.  I have to go into Task Manager.   But I just checked my CPU, and it consistently runs under 10% - more around 5% and under.   So that's not the problem.   I did install new drivers for the Quad-Capture this morning but haven't recorded anything yet.   So we'll see..
 
Thanks!
Greg

I'm still learning everything
 
Greg

I guess you might have some driver issues or something, try the DPC latency checker. 
 
do it right away 

The below tweaks, are referenced from the following thread: http://forum.cakewalk.com/The-Sonar-x64Windows-7-x64-Install-Tweaks-Compatibility-Thread-m1862515.aspx
 
Did you disable core-parking for Windows 7?
 
"- Core Parking:  Is a new features in Windows 7 that may be very handy for laptop computers, but not very convenient for systems where high performance is needed at all times.  You can google it if you want to learn more about it.  But, to disable it, you'll need to do the following (skip this if you're not comfortable editing the Registry): 
  
Go to Regedit and find the following key (use the "Find..." command under "Edit" to make this easier): 
  
0cc5b647-c1df-4637-891a-dec35c318583 
  
Within this key, change the values called "Value Min" and "ValueMax" to 0.  You'll have to find the key a few times (press F3) and adjust the values each time.  The number of instances depends on the number of power profiles in your system.  When you're done, do a cold shutdown/power on. 
   
[Thanks to TomG and sky60234 for providing this awesome tweak]
"
 
And using the Unified Preferences view, in the SONAR configuration file, did you try setting the ThreadSchedulingModel section at both 1 and 2?
 
"9- Sonar Tweaks: 
* Improved Multi-Core load balancing  [From Noel's SONAR 8.3 Log] 
  
Since all systems are not made equal we decided to make this new scheduling mode configurable. 
From the help file, the new aud.ini option to control this is: 
  
ThreadSchedulingModel=<0 - 2>  
Type Integer  
Default 1 
  
This variable goes in the [Wave] section and controls the interaction of the main audio thread and worker threads on multiprocessor systems when the Use Multiprocessing Engine option is enabled. Depending on the system, a particular model may result in less glitching and better overall performance. The values are as follows: 
  
............0 = Same as previous versions of SONAR. 
............1 = (default) Better thread balance. Model is more efficient and can provide cycles for other tasks. 
............2 = Additional worker thread is created. This may result in improvement with Quad processor systems or higher. Not recommended for Dual processor systems."
 
To change in SONAR X series, open Unified Preferences view, and under Audio>Configuration File (Advanced view), look on the right and find the section "ThreadSchedulingModel". Change the number to 1 or 2. Check which one works best for you.
 
Also, I would advise, if you are using any softsynths or effects (except any used when recording the Lead guitar), bounce them to audio, to free up any cpu power you can free up.
 
After making the above tweaks, run your project and see how it goes?

Take your time.
 
Get some relaxation.
 
When you feel clear headed, go ahead and try to troubleshoot the problem, again. Back off when needed and repeat the process.
 
I tried to be detailed with how to do some things I posted.
 
If you have some unclearness with some of the terms, such as "bounce to audio," search the SONAR Help or SONAR Reference manual for "bouncing tracks," "Freeze," "Real Time Bounce," and "Fast Bounce." It may help.
 
Also, ask more questions, if that will be more helpful to you.
 
You will be OK, just hang in there.

So I decided to try and record guitar direct.   Sound is better, but the volume is really loud during playback.   I have the Volume knob on the Quad-Capture at 9 o'clock.  The signal is not hot at all.   The wave form is small, but during playback it's just loud.
 
Anyway, I checked the driver settings on the Quad-Capture. 
ASIO buffer size is 256.
Sample rate is 44100
It's set for Low latency.
There is an unchecked box that says "Use ASIO Direct Monitor"
Under "Windows Sound Setting" there is another unchecked box that says "Match with the ASIO sample rate."
 
Do these settings seem right?    I uninstalled the old drivers for the QuadCapture and installed new ones, so I don't know if there needs to be some kind of audio adjustment (?) that's causing the volume level to be so loud during playback.
 

I had same issue long for long time and finally fixed after installing windows 8. I never had the problem when my pc was running win xp . After I upgraded to vista 64 and win 7 64bit with i7 processor still have the same problem. I had to deal with this issue for a long time and it was so Embarrassing specially in front of my clients because it usually ends up to restart the pc. After upgrading to win 8 and sonar x3d problems almost solved and i can say %95 is better. I think because win 8 is using all the cores compare to win 7 and some how sonar x3d matches itself with this ability more better.
The other thing is make sure all the plugins you have on your daw are 64 bit compatible and try to get the latest update.
 

If one track is louder than the others you might have it directed to your outputs instead of the Master bus, Check each tracks output. 

hmmm. if your DPC latency seems stable (as your description clearly says actually) it should not be an driver issue. 
Did you run Sonar, with the projects, with DPC running? 

greg54
Thanks, Cactus Music! 
 
I did the DPS latency checker, and the "absolute maximum" was 188.   I ran it for about 5-10 minutes, and it said, "This machine should be able to handle real-time streaming of audio and/or video without drop-outs."
 
I don't have my recording computer hooked up to the internet, so I never get updates.  Could that possibly be an issue?
And could the problem also be my interface?  

I'm making an effort to address the main problem you posted about in this thread, the CPU issue.
 
Probably the most significant things you can do, now after running the DPC Latency Checker, to help the strained CPU issue are:
 
- Disable core-parking, if not already done (see post #15 on how to do that.)
- In some cases, being up to date on important and recommended Windows updates can improve your system's performance, so it wouldn't hurt to be up to date with windows update. 
- Freeze softsynths or bounce to audio tracks with effects (if you are not currently recording on the tracks with softsynths and effects, they can be frozen or bounced to audio.)
- Raise the ASIO latency buffer for project playback
 
The things listed above are things to do that will allow for less strain on your CPU.
 
For playback and record performance, your audio interface, the Quad-capture is good to go, according to a good number of user reports here in the forums. If you want to make a purchase that will relieve the strain on your CPU even more, purchase another CPU. A faster and more powerful CPU will make a significant difference. I would recommend a core i7 920 or something faster or with more cores.

Disabling the core-parking seemed a bit over my head.  I'll have to go through that when I feel a bit more confident.
I'll freeze synth tracks and get updates for windows 7.    Then I'll see what happens and go from there.
You want me to raise the ASIO latency buffer from 256, where it is currently?
Thanks for your help!
Greg