[Smenelian]

Anyone have confirmed working audio interfaces that run in XP/Vista/7 x64? I have a Phonic Firefly that I've tried with XP and 7 and it doesn't work with either even though drivers exist.

[Harmony]

M-Audio ProFire 2626 and M-Audio FastTrack Pro working fine under Win 7 64 bit (and XP 32 bit).

Under Win 7, try other non Win 7 drivers, e.g. Vista drivers. They seem to work well with my interfaces.

[conyeezy]

i can vouch for most m-audio and e-mu hardware

[zircon]

Presonus interfaces work in XP64.

[Scrap McNapps]

Echo Audiofire Series
Edirol FA Series
RME Fireface Series
Most of Presonus stuff is working
Steinberg's audio interfaces are working as well.

[djpretzel]

Originally Posted by Harmony

M-Audio ProFire 2626 and M-Audio FastTrack Pro working fine under Win 7 64 bit (and XP 32 bit).

Under Win 7, try other non Win 7 drivers, e.g. Vista drivers. They seem to work well with my interfaces.

Really? No occasional BSODs or anything? I've been having really intermittent crashes - once a week, in some cases, and I just conclusively narrowed it down to the ProFire 610 beta drivers.

[Harmony]

Originally Posted by djpretzel

Really? No occasional BSODs or anything? I've been having really intermittent crashes - once a week, in some cases, and I just conclusively narrowed it down to the ProFire 610 beta drivers.

The only problems I've had have been related to trying to get 32 bit plugins to run correctly, but that's more of a 64 bit SONAR issue. My two M-Audio interfaces have worked problem-free. I'm using the Beta drivers on both now, but for the first few days I used the Vista 64 SP2 driver for the ProFire 2626 and it worked fine too.

Wonder what you're doing that's different than me? How did you trace the cause of the crashes to the interface drivers?

Also, the Win7 drivers for our interfaces are now out of Beta and have been officially released. Maybe the new ones will work better for you.

[Level 99]

Lexicon Lambda worked just fine under Vista and Win7, both 32-bit and 64-bit flavors. One irritating thing about Win7 is that, even under the "Performance" power config, it still has selective USB suspension (or something to that effect) enabled. So my Lambda would randomly power off and I'd not be able to power it back on without a disconnect-and-reconnect. Once that's disabled, everything's golden. If you've been having similar issues, I'd suggest checking that out.

I'll get a report on how Win7 64-bit likes the PodXT drivers sometime this week, hopefully.

[Harmony]

Originally Posted by Level 99

One irritating thing about Win7 is that, even under the "Performance" power config, it still has selective USB suspension (or something to that effect) enabled. So my Lambda would randomly power off and I'd not be able to power it back on without a disconnect-and-reconnect. Once that's disabled, everything's golden. If you've been having similar issues, I'd suggest checking that out.

OMG! If the same goes for firewire, maybe that's what has been happening with the ProFire 2626. If I leave the computer on for 30 mins or so without doing anything, the interface goes into a standby mode and I need to power on/power off to get it back. I thought it was just an annoying "feature" of the interface, but maybe it's this. I honestly don't remember whether or not it happened in XP.

[djpretzel]

Originally Posted by Harmony

The only problems I've had have been related to trying to get 32 bit plugins to run correctly, but that's more of a 64 bit SONAR issue. My two M-Audio interfaces have worked problem-free. I'm using the Beta drivers on both now, but for the first few days I used the Vista 64 SP2 driver for the ProFire 2626 and it worked fine too.

Wonder what you're doing that's different than me? How did you trace the cause of the crashes to the interface drivers?

Also, the Win7 drivers for our interfaces are now out of Beta and have been officially released. Maybe the new ones will work better for you.

Heh... well, it's still 2.05, but it might be a newer build. Out of curiosity, how much RAM do you have?

I traced the BSOD cause by actually downloading the damn Windows debugging tool and debugging symbols and seeing that the root cause was a driver issue stemming from the audiodg.exe process. Also, some guy in the M-audio forums is having the same problem, with the same config, and had the exact same BSOD error codes (APC_INDEX_MISMATCH and a fault in wdf01000.sys)... for now, I've switched back to my USB Yamaha mixer, as I can't have random BSODs on a machine I use for work...