- #KIGB UNABLE TO RECORD SOUND DRIVERS#
- #KIGB UNABLE TO RECORD SOUND DRIVER#
- #KIGB UNABLE TO RECORD SOUND CODE#
It may be of some help - but no guarantees: This ought to be in the Knowlegebase, but the indexing of that appears to be a law unto itself, and I simply can't find it - well, not in the short time I looked before starting to lose the will to live, anyway. Since it's not so easy to reference, I'll just reproduce the whole thing here - I'm sure Ron won't mind. I don't have Windows 7 here, so I can't comment personally, but I did find a part of a blog from Ron Day about this, in connection with both Audition and Soundbooth. So if you can't find an easy way to make it work then you'll have to wait for somebody who has to say how they did it, I'm afraid. What I have no idea of though is how, if it has, this has changed in W7.
#KIGB UNABLE TO RECORD SOUND DRIVERS#
This was exactly what I said about Vista, which most people now admit was demonstrably true - it sucks big time for audio.īut also, I'd have to say that not being able to record a 'what you hear' option doesn't actually have anything to do with the drivers as such, but is simply a routing issue within the OS. But, as I've argued before, any OS that gets in the way of an already operating setup should be viewed as the offender, not the existing SW. You have to bear in mind that what ASIO does is to punch a large hole through the OS so that it can get directly at your sound device without being 'mediated' by the OS - well, as far as possible anyway you have to reckon that the sound device is still 'seen' by the system, so it's not completely hands-off. I can't say unequivocally that it isn't - Audition uses an ASIO interface, and whilst that's known to work fine with XP, it's also quite possible that it doesn't behave exactly the same with W7. The obvious candidate is Windows Sounds - have you turned them off?ītw: could this be a compatibility issue that is the fault of audition rather than windows 7 圆4 or my sound driver?
The other thing that's just occurred to me is that if the device can't be opened, something else has grabbed it.
#KIGB UNABLE TO RECORD SOUND DRIVER#
Alternatively, if you think you are using ASIO then check to see if there's an updated driver from Creative - but if you are already using the latest one and it's not working, try ASIO4ALL as a stopgap and complain to Creative. It carries out the same function as the Audition one (converts WDM to ASIO and vice versa), and generally works pretty well. The one thing that might work if all else fails is the (free) ASIO4ALL driver - this is much more likely to have been updated for Windows 7 and also gives better error reporting.
But, if you've installed the correct driver for the card, you won't have been using the same one that sound recorder uses, so it doesn't actually prove very much, I'm afraid - Audition uses ASIO and sound recorder uses the internal WDM one. You've done the basic check I would have suggested already (sound recorder), so this sounds very much like the Audition driver is not liking your sound device for some reason. Unusual - but this is Windows 7, which wasn't around when AA3.0 was developed and technically isn't supported (although generally reports are good). I've tried using the Sound Recorder program that comes with Windows 7 圆4 and that records fine.
#KIGB UNABLE TO RECORD SOUND CODE#
But when I click the record button, I get an error message titled "Adobe Default Windows Sound Driver" error code FF9-5-0044 "device could not be opened".
0 kommentar(er)
