• SONAR
  • Problems with dropouts, clicking etc, with FocusRight Scarlet 6i6
2014/07/13 22:04:58
Kroneborge
Hi,
 
I recently got built a new computer, so I could no longer use my old EMU 1820m (no more PCI slot).  It didn't take me long to realize that my extra sound blaster xi-fi wasn't going to cut it (I had purchased it for playing games).  So I figured I would give the FocusRight Scarlet a try based on the reviews here.
 
So in installed the Scarlet, but I was still getting drop outs, and crackling.  Some helpful people pointed out that I was using ASIO4All drivers (even though I don't recall installing them).  I tried deleting, but still problems.  So I did a fresh install.  
 
That seemed to work, I was making music all day, then suddenly problems again.  Note I was multi tasking, also watching some flash videos on groove 3 etc.  
 
Now back to popping and crakling.  I've tried restarting my computer, and hitting restore factory setting on the Scarlet mix panel (not that I had changed any of them).
 
Any ideas?  I can't do a fresh install every day.  
 
Link to pics of my setup.
 
https://www.dropbox.com/sh/mm23ejqskjqrjn1/AAA1XeFl0-KdazqShi53V-xaa
 
Thanks,
2014/07/13 22:43:57
robert_e_bone
I believe your ASIO Buffer size is too big for recording purposes, and your Sonar-reported latency values are pretty high.
 
Try adjusting that ASIO setting down to around 3-5 milliseconds - starting with 5 milliseconds perhaps, and if that works make it 4, then if that works OK make it 3.
 
Also, if you have ANY effects loaded, please list which specific ones there are - by name - as some of these can also cause latency problems, on top of your settings being too high, as noted above.
 
After you get your ASIO buffer value set to a lower value, try hitting 'E' on your computer keyboard, which will temporarily bypass any effects.  Then see if that helps too, and post back.  (hitting 'E' again will turn the effects back on, by the way).  :)
 
So, first try the interface settings, then list your effects, by name, then try bypassing them to see if that works, as a test.
 
Bob Bone
 
2014/07/13 22:49:33
Splat
To be clear you have removed all trace of ASIO4ALL I hope?

+1 Bob... His suggestion first. You could also try disabling Intel Speedstep in the BIOS. Assuming you are running the latest mix control software?
2014/07/13 23:04:44
Kroneborge
So this is weird, I loaded my other project, and things seem to be going fine.  The project I'm having problems with though is actually the smaller project, and all of the same instruments are in the bigger project.
 
The smaller project just has 4 Play instances, and 1 instance of EWQL Silver.  Also, one Lexicon PCM reverb, that's it.
 
I tired setting latency to 5ms, no help.  I also tried deleting the reverb, as well as hitting E, no difference.
 
Maybe the project somehow got corrupted?  The other project has about 2-3 times as much going on with no problems.
 
Also, yes ASIO4ALL is totally gone, fresh install.
 
Also, system specs
 
I-7 4830,  24 gigs of ram, EVGA GTX 760,  
 
 
2014/07/13 23:08:48
Kroneborge
Actually, it looks like I spoke to soon, I went from the smaller project, back to the large, and dropouts.
 
Then I restart, and it seems like it's playing...
 
 
2014/07/13 23:48:01
robert_e_bone
I have to get some sleep - been up for 20 hours.  I will look at your thread first thing in the morning, and will stay with this until we get it figured out.
 
Bob Bone
 
2014/07/14 08:34:52
fireberd
Run the DPC Latency Checker (if you have Windows 7) and see what it shows.  If it shows everything is OK then you can eliminate the PC and work on the Focusrite interface.  But, if it shows system problems then that is where you need to focus on. 
 
If your new system has a Gigabyte motherboard, did you happen to install EasyTune6?  If you did, get rid of it immediately as it can cause all kinds of dropout problems.  If its another motherboard and it has some similar system monitor/tuning program dump that and see what happens. 
 
http://www.thesycon.de/deu/latency_check.shtml
2014/07/14 11:06:44
robert_e_bone
1.  I indicated between 3-5 milliseconds on the ASIO settings for the interface, and it looks like you may have only changed it to 5 MS, which might still need to come down.  Again, PLEASE adjust it down to 4 ms, and if doesn't help, then try 3 ms, and post back.
 
2.  Try increasing the MIDI Playback Buffers ('Prepare Using nnn' buffers in Edit>Preferences>MIDI>Playback and Recording), from 250 up to 500 ms, and see if that helps.
 
3.  Please post the Sonar-reported latency values again after making your adjustments to the ASIO Buffer settings, as well - thanks.
 
Bob Bone
 
 
2014/07/14 11:13:35
robert_e_bone
At this point, I too would like to see the results of a running of DPC Latency Checker, with Sonar not running during the test, to make sure your system itself is not the culprit.  (some background service or device driver - that sort of thing).
 
You can get DPC Latency Checker here:
 
You just launch it and let it run for a few minutes, and it will scroll across the detected DPC latency values, and if you see red spikes, there is something running on your system that needs to be looked at.  Remember, run it without Sonar running.
 
Also, do you have, by chance, a Wi-Fi adapter on this particular computer?
 
Lastly, you indicated 4 instances of 'Play'.  What specifically is that referring to?
 
Bob Bone
 
2014/07/14 11:43:25
Kroneborge
Ok, I will give those a try tonight.  "Play" is the VST from East West Quantum Leap, it's used to run Hollywood Strings and other sample libraries.
 
Thanks,
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account