Have you tried to install Reaper and see if you get the same problems?

If it works in Reaper, I would be knocking on Cakewalks door, especially since EMU says they can't recreate the problem ....

Sounds like the Octa-Capture might well be a viable alternative - especially as I could get a second one in the future to expand it as you have done.  Let's see what a couple of days moaning on a few forums brings - by the sounds of it, unless I manage to obtain the EMU 1616M PCI driver source code and fix it myself (not likely!), nothing is going to improve...   Thanks for info!

Bub


Have you tried to install Reaper and see if you get the same problems?

If it works in Reaper, I would be knocking on Cakewalks door, especially since EMU says they can't recreate the problem ....

I believe I did try this with Reaper - although, you'll have to forgive my uncertainty, I've been through soooo many changes and iterations of configuration on my PC I'm starting to lose track of them - perhaps I should keep a diary
 
Might be worth reminding myself later with a quick test...  cheers.

I was having problems with my firewire which is TI chipset it was unable to work with my Focusrite.

I bought a PCIe firewire card and it still did not work I had to go back to my trusty PCI slot which enables it to work effectively. So I would say that the PCI slot is long from being dead.

I also thought that moving to Win 7 x64 would mean the end of the line for my EMU-1616m. But the Beta Vista x64 drivers (2.30.00) work well in my case, to my pleasant surprise. I can confirm the following:

After almost 3 months of moderate use (ASIO mode), I'm not experiencing:

1] BSOD's while arming/disarming tracks or changing input sources
2] Silent outputs after rewind from record state


But I am experiencing the following:

1] 'Scribble Strip' track names (PatchMix DSP) are no longer appearing in the ASIO input names in Sonar

My needs are pretty straightforward and I will keep this interface until it dies on me. In the meantime, I'm saving up for when that time comes.

Alegria

After almost 3 months of moderate use (ASIO mode), I'm not experiencing:

1] BSOD's while arming/disarming tracks or changing input sources
2] Silent outputs after rewind from record state

Very interesting - I wonder if you've been incredibly lucky, or whether there is actually some kind of configuration issue that the EMU just does not like on my PC that is not present on yours.  I do note that you are using Beta Vista x64 drivers - are these different to the Windows 7 64 bit drivers I wonder?  Worth a go I guess...   thanks for the input!

Sorry for potentially misleading you Spencil. They are labelled:

E-MU PCI/PCIe Windows 7 Beta Driver - June 2010 (0404/1212M/1616/1616M/1820/1820M)

available here:

http://connect.creativelabs.com/emu/default.aspx

The second item in the download list. Not sure why I mentionned Vista??!! 

in device manager look at whats sharing IRQ's in control panel / view by IRQ.. you might find that is causing the BSOD's also , thats what less than / equals are caused by a lot of the time. you need to get it to go on another IRQ , switch it to another pci slot etc.. OR disable anything conflicting / sharing.. if it vanishs after.. thats more than probably your cause. also if you have anything plugged in say SPDIF wise thats reliant on a clock that can also trip things up if it drops sync.

I can not help with the EMU thing, but i had a M-Audio 10/10 on my W7 64 machine,
BSOD was driving me nuts. Tried all the help i was given, and nothing changed.
Got a Roland Quad-Capture, and all went away.
I feel for your problem and hope you get it sorted.
Good luck mate.

Fog


in device manager look at whats sharing IRQ's in control panel / view by IRQ.. you might find that is causing the BSOD's also , thats what less than / equals are caused by a lot of the time. you need to get it to go on another IRQ , switch it to another pci slot etc.. OR disable anything conflicting / sharing.. if it vanishs after.. thats more than probably your cause. also if you have anything plugged in say SPDIF wise thats reliant on a clock that can also trip things up if it drops sync.

I have one USB hub sharing an IRQ with the E-MU, but that was also the case under XP, and it wasn't a problem. Disabling the USB hub driver made no improvement in any case.


I do have the E-MU slaved to an external clock via ADAT from my QS8. I also suspected this might be a problem, but, again, it wasn't a problem under XP, and switching back to the internal clock on the E-MU did not eliminate any of the issues, including BSODs. 


Clearly the E-MU stuff is working better for some than for others, which suggests a certain sensitivity to the environment in which it's installed. But plenty of folks who had no trouble under XP have had issues suddenly crop up in Win7 x64, which tells me Creative/E-MU need to address this "sensitivity", whatever it is.