Ticket #9205 (new defect) — at Version 4

Opened 8 years ago

Last modified 5 years ago

Could not initialize DirectSoundCapture

Reported by: dark_overload Owned by:
Component: audio Version: VirtualBox 4.0.10
Keywords: HostAudioNotResponding Cc:
Guest type: Linux Host type: Windows

Description (last modified by sunlover) (diff)

I have tried everything to get virtualbox to stop giving me this error, but nothing works. Below is the relevant section of the log for a test VM I created with all default settings just to test this bug.

00:00:00.765 Audio: Trying driver 'dsound'. 00:00:00.810 DSound: Could not initialize DirectSoundCapture 00:00:00.812 Audio: set_record_source ars=0 als=0 (not implemented) 00:00:00.812 AC97: WARNING: Unable to open PCM IN! 00:00:00.812 AC97: WARNING: Unable to open PCM MC! 00:00:00.812 VM: Raising runtime error 'HostAudioNotResponding' (fFlags=0x0) 00:00:00.812 Console: VM runtime error: fatal=false, errorID=HostAudioNotResponding message="Some audio devices (PCM_in, PCM_mic) could not be opened. Guest applications generating audio output or depending on audio input may hang. Make sure your host audio device is working properly. Check the logfile for error messages of the audio subsystem"

Change History

comment:1 Changed 8 years ago by dark_overload

Further testing shows that using HD audio causes only PCM_in to fail, and SB16 doesnt give errors.

comment:2 Changed 8 years ago by dark_overload

Scratch that, the log still shows "Could not initialize DirectSoundCapture"

comment:3 Changed 6 years ago by Tomer

The following website seems to explain this issue and provide a solution to the problem:

Last edited 6 years ago by Tomer (previous) (diff)

comment:4 Changed 5 years ago by sunlover

  • Description modified (diff)

We think we fixed this problem. Here is a test build:

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use