OverClocked ReMix...

Harmony · #11 11-18-2009, 06:29 AM

Quote:

Originally Posted by djpretzel

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).

Quote:

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?

djpretzel · #12 11-18-2009, 07:21 PM

Quote:

Originally Posted by Harmony

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/...diodg-exe.aspx

Harmony · #13 11-18-2009, 07:33 PM

Quote:

Originally Posted by djpretzel

http://blogs.msdn.com/larryosterman/...diodg-exe.aspx

Yeah, 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?

Harmony · #14 11-19-2009, 05:49 AM

(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.

Pope · #15 11-19-2009, 09:14 AM

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.

Level 99 · #16 11-19-2009, 12:44 PM

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?

Harmony · #17 11-19-2009, 05:13 PM

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.

Level 99 · #18 03-10-2010, 12:21 PM

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.

Palpable · #19 03-10-2010, 01:04 PM

Quote:

Originally Posted by Level 99

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.