quibb


"Just wanted to let you know that it is your Focusrite..."
 
Lol. Focusrite rocks, even with the firewire interface . Stable as a rock here.
However...
That was after I went back to the 2.2 driver...  Too many midi glitches with 3.0.
 
FWIW...While I agree with what's already been discussed, when it comes to pops and clicks I always start with my audio interface driver - either update or re-install.
 
V

Totally agree


2 Focusrite interfaces here- one uses Firewire, the other USB. Never had a single problem with either of them

Colin, 

I'm going to be a pain here, but didn't Noel once state that setting the processor scheduling to background services was no longer necessary with W7 ? 

I have mine unchecked and am running a with zero problems.

Cheers,
Jerry

guylemec

I have reverted to non-legacy drivers and all seems ok; I have emailed Focusrite for their advice on which way I should go in this matter. 

Reply from Focusrite:
The legacy FireWire drivers were only required for MixControl 2.4. Now that MixControl 3.0 is released, this should not be necessary. If you can connect using the standard FireWire driver, then please use it, as MixControl 3.0 is not designed for use with the legacy driver.

joakes


Colin, 

I'm going to be a pain here, but didn't Noel once state that setting the processor scheduling to background services was no longer necessary with W7 ? 

I have mine unchecked and am running a with zero problems.

Cheers,
Jerry

You might be right Jerry - this was as communicated to me by Focusrite

As you say, if you don't have any problems, leave well alone

John


Well Freddie a great summery. I would add that now what are meant as tweaks as such are for the most part user preference. As you say you really don't need to do much on a modern OS unless you have special needs such as on a laptop.  

Thanks my friend!

The process scheduler algorithm- Once for all I will attempt to set this straight!
It shall be set to PROGRAM in Windows Vista, Windows 7, Windows 8 and later...


In XP and NT the kernel may change the priority level of a thread depending on its I/O and CPU usage and whether it is interactive (i.e. accepts and responds to input from humans), raising the priority of interactive and I/O bounded processes and lowering that of CPU bound processes, to increase the responsiveness of interactive applications. The scheduler was modified in Windows Vista, Windows 7, Windows 8 to use the cyckle counter register of modern processors to keep track of exactly how many CPU cycles a thread has executed, rather than just using an interval-timer interrupt routine. Windows Vista, Windows 7, Windows 8 also uses a priority scheduler for the I/O queue so that disk defragmenters and other such programs don't interfere with foreground operations.
 
 
Dispatch lock has also been fixed that improve multitasking and multimedia in Windows 7 and later... But that is another story.

Here you can see a video that explain more what is under the hood in Windows 7 and later.
It also explain how they cracked the Dispatch lock.


http://channel9.msdn.com/Shows/Going+Deep/Mark-Russinovich-Inside-Windows-7


Windows 8
http://www.extremetech.com/computing/138177-under-the-hood-of-windows-8-or-why-desktop-users-should-upgrade-from-windows-7

So guylemec, after all that, Focusrite says DON'T use the legacy driver? OK.