FIREWIRE W7 Question please...

Does anybody know if there is a reason why I can't run an RME FF800 without getting digital clicks while running X3, opening browser windows or just plain moving the mouse.
I'm chasing my tail for a solution & it's lucky I have no hair to start with!

Thanx for the prompt reply Mike.
 
I have posted a couple of similar threads (amidst trying to resolve this) along the lines....
 
My"glitch" has to do with "ANY" mouse movement at all in the track pane on playback. 
No amount of buffer or tweaking can prevent it. Was using Logitech cordless laser mouse & tried same brand usb....still get audio skip.
FW driver, graphics card...all rolled back/updated...digital GLITCH!
&
 
One project that is playing up only has 4 audio tks with very little else...does EXACTLY that.
Trying drivers etc with no luck...Pro Channel not on.
Here's a kicker...I opened the Sonar demo file (12 x audio tks) ...playing as we speak & can't get it to skip a beat..pardon the pun.
 
 
Since then it's a matter of on playback a FREQUENT digital CLIK, that I can emulate while opening a browser for eg.
 
I recently upgraded to W7 & it's a nightmare. It's got to be operator error (read ME) but I've tried most. 
 
Is FF driver ver 3.080 with hardware 2.77 right for a start?
 
Appreciate your input ++++

Jinxy, What graphics card are you using?

Check out a thread that I started not too long ago regarding similar issues. The nightmare of FireWire versus graphics cards is real. I'm living in it right now.

Surely, it's not the mouse... I'm using a Logitech Anywhere MX™ laser mouse ( I have a glass desktop and require a laser) and have never had an issue with it.. excepting that I wore out the buttons on the first one and replaced it with another one. Love that mouse.. 
 
I'm using a MOTU connected via  firewire and having no issues either. RME is known for high-quality drivers too, so it's unlikely that it could be drivers unless they are installed incorrectly.
 
What I suspect is that you've got some sort of a systems issue - possibly background processes that are eating up protected high-priority CPU time. A mouse tends to exacerbate issues with high priority processes if they are overrunning their expected time, which I believe might be your case.
 
I'd suggest as a start to take a look at the "DPC latency checker application". If there's an issue with latency, this application will indicate it. A more advanced application is "LatencyMon", which can also indicate which process are offennding - but it is a bit more technical for some.
 
A google search on the above terms will give you places where you can find out more information about these applications and where to download them.

It's a start...

Nightmare empathy?
 
Never heard of that one before.. but it sounds like a cool name for a band....

Thanx all....doin a re jig as suggested.
 
I know yur waiting with baited breath...ie another newbie!
 
DON'T join my band SUperG...better things to do ! :)
 

2:43AM
Jinxy, What graphics card are you using?

Check out a thread that I started not too long ago regarding similar issues. The nightmare of FireWire versus graphics cards is real. I'm living in it right now.

I'm thinking graphics as well.
 
a) update to latest graphics drivers
b) update from dell for latest chipset drivers
c) Part of optimizations for audio in any Windows is reducing visual aspects. Look at optimizing for performance more than visuals.
d) evaluating fw, I did plenty bios changes, not allowing core parking, removing dynamic overclocking and things like that. I also reverted to legacy fw drivers in W7 - and machine worked much more smooth.
 
Even back in XP I had such issues, not using FW, but opening popup menues made a click in audio. Removing shadows on popup menues fixed it.
 
So a workaround might be to change visual aspects of W7.

Q for Mike...
X3 reporting roundtrip latency 49.6ms @ 1024 samples...is that NOT good?
There's a lag when I hit the PLAY transport?

If you've got lag etc - that gives a flashback to fw cable?
 
Not much trension/bend in cable is needed to cause malfunction in fw. Connectors are really old technology and very poor design.
 
In my case I worked a full evening troubleshooting until I found that table pressed cable a tiny bit towards the wall, that was enough.
 
I could even see cpu going up and down by pressing the cable in different directions. It may be that simple.