Smenelian Posted November 13, 2009 Share Posted November 13, 2009 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. Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 13, 2009 Share Posted November 13, 2009 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. Quote Link to comment Share on other sites More sharing options...
conyeezy Posted November 13, 2009 Share Posted November 13, 2009 i can vouch for most m-audio and e-mu hardware Quote Link to comment Share on other sites More sharing options...
zircon Posted November 13, 2009 Share Posted November 13, 2009 Presonus interfaces work in XP64. Quote Link to comment Share on other sites More sharing options...
Scrap McNapps Posted November 15, 2009 Share Posted November 15, 2009 Echo Audiofire Series Edirol FA Series RME Fireface Series Most of Presonus stuff is working Steinberg's audio interfaces are working as well. Quote Link to comment Share on other sites More sharing options...
djpretzel Posted November 17, 2009 Share Posted November 17, 2009 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. Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 17, 2009 Share Posted November 17, 2009 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. Quote Link to comment Share on other sites More sharing options...
Level 99 Posted November 17, 2009 Share Posted November 17, 2009 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. Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 17, 2009 Share Posted November 17, 2009 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. Quote Link to comment Share on other sites More sharing options...
djpretzel Posted November 18, 2009 Share Posted November 18, 2009 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... Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 18, 2009 Share Posted November 18, 2009 Heh... well, it's still 2.05, but it might be a newer build. Out of curiosity, how much RAM do you have?Yeah, I noticed the unchanged driver version right after I posted. I have 4GB installed, 3.12GB usable (stupid ASUS mobo randomly sucking up the rest). the root cause was a driver issue stemming from the audiodg.exe process.I can't find that process/service on my setup. The closest that I find are services AudioSrv and AudioEndpointBuilder, both running at start. Is there something that I'm missing? Quote Link to comment Share on other sites More sharing options...
djpretzel Posted November 18, 2009 Share Posted November 18, 2009 Yeah, I noticed the unchanged driver version right after I posted. I have 4GB installed, 3.12GB usable (stupid ASUS mobo randomly sucking up the rest). I can't find that process/service on my setup. The closest that I find are services AudioSrv and AudioEndpointBuilder, both running at start. Is there something that I'm missing? http://blogs.msdn.com/larryosterman/archive/2007/01/31/what-is-audiodg-exe.aspx Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 18, 2009 Share Posted November 18, 2009 http://blogs.msdn.com/larryosterman/archive/2007/01/31/what-is-audiodg-exe.aspxYeah, that's the same link I found when looking up this process. I'll check again when I get home, but that process wasn't in my task manager and I didn't see it in my running or stopped process. It was 2:30am, maybe I overlooked it. I didn't bother looking for the physical executable to see if it actually exists on my pc, but I'll try that when I get home too. What version of Win 7 are you using (I'm in Ultimate)? If it exists, have you disabled the mobo's integrated audio device? Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 19, 2009 Share Posted November 19, 2009 (double post) Alright, I found audiodg.exe, but it only runs when I route some of my outputs on the profire to any of the software returns. If I send everything through the onboard mixer, the way it was setup yesterday, audiodg doesn't run at startup. Quote Link to comment Share on other sites More sharing options...
Pope Posted November 19, 2009 Share Posted November 19, 2009 I'm running a Mackie Onyx Satellite FireWire audio interface in Windows 7 64 bit. I had to switch my FireWire driver to the legacy version to get it working, however. No big deal. I don't know if you can really buy these new anymore. From what I understand, the product was kind of a bomb for Mackie, despite being awesome. Quote Link to comment Share on other sites More sharing options...
Level 99 Posted November 19, 2009 Share Posted November 19, 2009 Alright, a bit of an update because I noticed one very important thing about Win 7 64-bit, Sonar 8 64-bit, and the Lexicon Lambda... I must've forgotten to switch my drivers from MME over to ASIO when I first got it all up and running. However, there are no detected audio interfaces when I switch to ASIO in Sonar. I'm not sure if this is an issue with Sonar, ASIO in-general on Win7 64-bit, or just the drivers I have installed with the Lambda AND my Creative X-Fi, but even ASIO4ALL is causing issues. More research needs to be done, and the Lambda drivers do not say they support Win7 yet, let alone 64-bit (they did, however, install just fine and the device does work in MME mode) but that no drivers are working in ASIO at all is disconcerting. Anyone have any idea about ASIO and Win7 64-bit? Quote Link to comment Share on other sites More sharing options...
Harmony Posted November 19, 2009 Share Posted November 19, 2009 I've used the ASIO drivers on my ProFire in Sonar 6 without issue, but I've switched back to my beloved WDM drivers. If the Lambda offers them, give them a shot. Quote Link to comment Share on other sites More sharing options...
Level 99 Posted March 10, 2010 Share Posted March 10, 2010 Alright, time for a bump. A most-frustrated bump. I recently decided to get back into Windows 7 64-bit to take advantage of the higher memory cap and increased performance in Sonar. This actually stemmed from a project bundle I got from Luiza for a song we're working on. It wouldn't open because I have two drum VSTs: the one I use, and the one that she also uses (I recently got the one she uses so the projects can be shared easier, amongst other things). Long story short: the project wouldn't open and kept crashing because of the memory usage exceeding the 2 gb limit. That's when I discovered the horrendous 64-bit support from Lexicon for their Alpha/Lambda/Omega line. Horrendous = there is no driver support for 64-bit. Well, at least none outside of the generic usb driver provided by microsoft, which is buggy at best and doesn't support ASIO at all. While searching for a new interface, I stumbled upon this site: http://rainrecording.com/windows-watch/ An incredible list of compatibility for audio interfaces with Windows Vista and 7, both 32-bit and 64-bit flavors. Definitely should be of use to people searching for compatible interfaces or seeing if theirs is compatible with an upgrade before they go through with the upgrade. In other news, does anyone want to buy a like-new Lexicon Lambda? Has everything except the box! Edit: also something interesting on the site. Look at how those expensive Waves plugins are not 64-bit compatible! Imagine being a professional musician or producer, buying Waves Mercury, and having it not work with your 64-bit DAW. Unbelievable. Quote Link to comment Share on other sites More sharing options...
Palpable Posted March 10, 2010 Share Posted March 10, 2010 That's when I discovered the horrendous 64-bit support from Lexicon for their Alpha/Lambda/Omega line. Horrendous = there is no driver support for 64-bit. Well, at least none outside of the generic usb driver provided by microsoft, which is buggy at best and doesn't support ASIO at all. Sorry to hear it, but good to know. I've contemplated switching to 64-bit, but knowing I'll need to get a new interface on top of the upgrade... I'll pass for now. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.