Joshua wrote:I am also using a Firewire M-Audio 410 soundcard. I have tried all permutations and downloaded the beta. While I am no longer getting the error message, G-Force does not respond to any audio from my soundcard.
All this should be fixed w/ G-Force 3.6 (posted a few days ago), so everyone on this thread please post on how 3.6 does either way.
Unfortunately, 3.6 is still not responding to my M-Audio 410, sound card.
I'm running on Windows XP. To be sure of detection, I set the wave shape to zipperheads- there's no detection of the signal. I can hear the music and moniter the signal through my sound card software, but G-Force does not respond.
Anxiously awaiting full functionality, but patiently appreciative of your efforts,
Joshua wrote:Unfortunately, 3.6 is still not responding to my M-Audio 410, sound card.
I'm running on Windows XP. To be sure of detection, I set the wave shape to zipperheads- there's no detection of the signal. I can hear the music and moniter the signal through my sound card software, but G-Force does not respond.
Given that 3.6 addresses the M-Audio Audiophile 192 issues, I'm out of guesses. Considering that you can by a Soundblaster Audigy for less than $20 these days, that's probably the way to go. Unfortunately, we just don't have the time and the resources to buy every piece of pro audio hardware out there to troubleshoot what's going on. The drivers for pro hardware are usually pretty dodgy since they're typically only tested against standard industry apps.
In any case, I've added this issue to our internal bug tracker, so hopefully we can look into it further in the not too distant future.
May be a tad late now but i also recieved a similar error, one thing people should always make sure of is that in recording devices under sound options in windows is "Allow applications to take exclusive control of this device" For example, I had skype clashing with whitecap.
This was using 2 soundcards, i dont know if others had this problem but it fixed it for me, hope it helps!
