"brundlefly"
which tells me Creative/E-MU need to address this "sensitivity", whatever it is.

Don't hold your breath. I don't see that happening, period. 

Alegria

"brundlefly"

which tells me Creative/E-MU need to address this "sensitivity", whatever it is.

Don't hold your breath. I don't see that happening, period. 

Netiher do I. That's why I wrote, "Bottom line is I think we are all going to have to give up on these interfaces, because E-MU has officially stopped supporting them" in my first post. 

Have you tried to reset the emu? There's a button in pathchmix.
Have you reinstalled the driver and patchmix? They need to be installed in a specific order - I forget which is first. Most folks can run the 2.1 with win 7 in 64bit without any problems. Uninstall then reinstall - should be working.

"drumr"
They need to be installed in a specific order - I forget which is first.

EMU drivers first, then Patchmix.

There is one thing that can be tried as a test of what might be wrong with an ASIO driver: after starting Sonar, fire up the task manager and use it to set sonar's CPU affinity to just one of your CPUs**. If that stops the problem, there's a good bet that the ASIO driver has a multiple-CPU race condition.

It is even possible that some DAW software DOESN'T exhibit the race condition, but not because that DAW is "better", just "different" in how it accesses the ASIO API.

(** Right-click on Sonar's image name and click on "set affinity ..." then uncheck all but one CPU. Naturally, this is not a good workaround because it uses only allows Sonar to use one CPU.)

The problem I have in troubleshooting this is that I can sometimes go weeks without a BSOD. If the troubleshooting step badly compromises performance, it's just not feasible to try.

lowdown, thats worrying for me as I was hoping to chuck my 1010LT into a w7 / 64 machine when it's built... I've already had to dump an m-audio ozone because of their inability to write decent w7/64 drivers (they were told the issues 3 months later , still none working drivers) 2 revision. TBH if I have to drop them, it wouldn't surprise me.

sounds like memory problems

if companies can't be bothered to test / write proper drivers is the problem.. memory "mess ups" would show up far easily and are easily checked with a Live CD with memtest on...as for pci > pci-e.. check the bandwidth improvements. you might as we be comparing usb1 to usb2..

Spencil Splodge


Out of curiousity, Guitarpima, how is the Roland Octa-Capture?  I've looked at this one before and it looks nice - what kind of latency do you get in Sonar X1 (how low can you go)?

At 24/44.1, I get 1.1ms at 48 samples. At 96khz it is a little slower at 9? samples. I never bothered to check the latency. I have a project at 96 I plan on mixing some more on and I'll let you know.