brundlefly

forkol


I have an 1820 m working under Windows 7, with ASIO.  It was a bit fiddley to get setup, but it's working, pretty much.

Patchmix is a pain in the butt, but very flexible.

I'm sorry if you have done these steps, but just want to check.

1) Do you either have or created an strip for ASIO?  Mine is named ASIO 31/32.  I think it was setup this way.
2) Then make sure in the Audio tabs that EMU ASIO is selected
3) Finally, as part of PatchMix (sorry, not in front of me right now), is a virtual 'patch-bay'  You have to take the output from the strip and assign it to the output you want to get the audio out of.  For example, if I want the headphone output, then I had to assign it to the headphone output from the main mix.  You will have to do the same with whatever outputs you want to use.

However, the same issue that I have as you in regards to trying to get a low latency....Mine is setup to about 10ms, and it's not laggy, but for some reason I can't set it too much lower, then I get motarboating and dropout....and I don't get why that is...I've seen some folks report they can get 2.5 ms....but that was probably the XP drivers.

Hope this helps.  I can also look at my exact setup at home and let you know exactly what the setup is.

FWIW, I have an 1820m working in ASIO mode under Win7 x64 with the beta drivers and a 2ms buffer (5.9ms total RTL). The overall performance is identical to what I got under XP x86, except for the following:


1. I/O names on the Drivers tab in SONAR are generic In/Out 1-32, rather than showing the friendly names entered in the Patchmix strips and only for ports actually used in PatchMix session. Friendly naming in SONAR helps, but old projects have to have their bus I/O assignments re-established because they don't recognize them as being the same device.


2. I sometimes get a BSOD caused by HA10KX2K.SYS (a Creative/E-Mu driver). I have not been able find a recipe to reproduce it on demand.


3. When I rewind after recording, input echoed tracks go silent, and I have to cycle the audio engine to re-open the ports. Stopping recording with R before stopping the transport avoids the problem because rewinding from playback state works fine.


I had all these same issues using the Vista x64 driver under Win7; the Win7 beta drivers made absolutely no improvement for me. Since I had none of these problems with XP x86 on the same hardware, I attribute all these issues to the x64 drivers, though #3 seems also to be an interoperability problem with SONAR as I do not see this in Studio One. And I haven't used S1 enough to know whether the BSOD problem exists there, too.

brundlefly

For me with my 1616m I can get it to BSOD by randomly arming and disarming a track.  Keep doing it enough times and it will eventually blue screen with this file: HA10KX2K.SYS.  This only happens to me in Windows 7 64 bit.  Never had this problem in 32 bit.

I can't get it consistently by doing that, but arming/disarming is one of the actions that tends to cause them. Pretty much anything that changes the status of the interface can cause it. The thing that bothers me is some other 1820m users on Win7 x64 report they never get BSODs. 


When you were still 32-bit, was that also Win7 or was it XP or Vista? I've been wondering whether going to 32-but Win7 x86 would solve the problem. And do you also see the problem with input-echoed tracks going silent on rewind after recording?