Re: Sound error: Could not initialize DirectSoundCapture

[Jakob Bohm]

On 2020-12-15 12:46, kazusanosuke_kaz wrote:

Dear all!

I appreciate your kindness.
After all, I could hear the nostalgic startup sound by sb16 emulation.
I'm relieved to hear the error is harmless.


There still remains another problem.
Sometimes I can hear the sound, sometimes I can't. It is unclear what causes 
this behavior.
I have never been distressed in this way by actual machines, actual sb16 ISAPnP 
or other sound devices.

There still remains yet another problem.
FPU's benchmark score(1) is equivalent to classic pentium @ 30Mhz.
On the other hand, the score of integer instructions is equivalent to classic 
pentium @ 166Mhz,
The window system is so slow as you can see the movement to open a tree of 
Explorer, default file manager of windows 98. I wonder if it's becouse of the 
CPU emulation. It seems SSE is not used, vt-x doesn't work. The scores are far 
from them when I use VirtualBox using vt-x.
(1) I used HDBench, the most famous software in Japan when people use windows 
98 on actual machines.

Please note that CPU emulation via VT-x on a Windows Host machine
requires installing and using the Intel HAXM accellerator, which
acts as the device driver for accessing VT-x (similar to what the
kvm kernel module does on Linux).


These problems are not urgent or important.
Just FYI


thanks,
--
Yasuhide Omori



Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded

Re: Sound error: Could not initialize DirectSoundCapture

[kazusanosuke_kaz]

Dear all!

I appreciate your kindness.
After all, I could hear the nostalgic startup sound by sb16 emulation.
I'm relieved to hear the error is harmless.


There still remains another problem.
Sometimes I can hear the sound, sometimes I can't. It is unclear what causes 
this behavior.
I have never been distressed in this way by actual machines, actual sb16 ISAPnP 
or other sound devices.

There still remains yet another problem.
FPU's benchmark score(1) is equivalent to classic pentium @ 30Mhz.
On the other hand, the score of integer instructions is equivalent to classic 
pentium @ 166Mhz,
The window system is so slow as you can see the movement to open a tree of 
Explorer, default file manager of windows 98. I wonder if it's becouse of the 
CPU emulation. It seems SSE is not used, vt-x doesn't work. The scores are far 
from them when I use VirtualBox using vt-x.
(1) I used HDBench, the most famous software in Japan when people use windows 
98 on actual machines.

These problems are not urgent or important.
Just FYI


thanks,
-- 
Yasuhide Omori

Re: Sound error: Could not initialize DirectSoundCapture

[Lukas Straub]

On Mon, 7 Dec 2020 15:57:33 +0100
Jakob Bohm  wrote:

> On 07/12/2020 15:13, Peter Maydell wrote:
> > On Mon, 7 Dec 2020 at 13:56, kazusanosuke_kaz
> >  wrote:  
> >> Hi, all!
> >>
> >> I've just installed qemu to my PC, Windows 8.1(x64) with Core i5-4670 / 
> >> MSI MS-7817(OnBoard Sound) / GeForce GT 640
> >> Windows 98SE was successfully installed on qemu, but sound device doesn't 
> >> work ...
> >>
> >> "C:\Program Files\qemu\qemu-system-i386.exe" -device sb16 -m 512 
> >> Windows98SE.qcow2
> >> dsound: Could not initialize DirectSoundCapture
> >> dsound: Reason: No sound driver is available for use, or the given GUID is 
> >> not a valid DirectSound device ID  
> > (I don't use Windows, but here are some suggestions based on
> > reading the source code.)
> >  
> >> Even though I choose another soundhw, the result is all the same  
> > That's because this error message is not related to what sound
> > hardware is being given to the guest. It's the QEMU DirectSound
> > audio backend complaining that when it asked the host Windows
> > for a sound-input device (ie a microphone or similar) it got
> > an error back. (Specifically, the IDirectSoundCapture_Initialize()
> > call failed.) So the warnings are basically saying "sound input
> > to QEMU is not going to work", and they'll be printed for any
> > kind of sound hardware you give to the guest (sb16, ac97, ...).
> >
> > That said, looking at the code I think that the DirectSound
> > backend attempts to continue even if audio input doesn't work.
> > So if you only care about audio output, in theory these warnings
> > should be harmless.
> >
> > You could try some of the suggestions in this stack overflow
> > post:
> > https://stackoverflow.com/questions/55601413/how-to-fix-could-not-initialize-directsoundcapture-in-android-studio
> > (effectively "plug in a microphone" or "enable some windows-internal
> > input device") to see if they help. If that makes the warnings
> > go away and also makes sound output start working, then there
> > might be a bug in the QEMU code that is supposed to handle
> > "input doesn't work but proceed with output anyway". If the
> > warnings go away but sound output still doesn't work, then
> > the output problem is not related to the warnings.  
> I sometimes use Windows, and the only time I tried a qemu on Windows,
> I could not find any working sound option, and all the help and error
> messages were useless, suggesting things that weren't explained, listing
> options that didn't work etc.
> 
> Someone on the team needs to clean up sound support in the prebuilt
> Windows binaries that are linked to from qemu.org.
> 
> 

CC'ing Stefan Weil, maintainer for windows hosts.


-- 



pgp7V16CqQ0MN.pgp
Description: OpenPGP digital signature

Re: Sound error: Could not initialize DirectSoundCapture

[Peter Maydell]

On Mon, 7 Dec 2020 at 14:58, Jakob Bohm  wrote:
> I sometimes use Windows, and the only time I tried a qemu on Windows,
> I could not find any working sound option, and all the help and error
> messages were useless, suggesting things that weren't explained, listing
> options that didn't work etc.
>
> Someone on the team needs to clean up sound support in the prebuilt
> Windows binaries that are linked to from qemu.org.

Perhaps so. Unfortunately very few people on the QEMU
dev team use Windows at all; Linux is by far the best supported
host OS. If anybody is interested in trying to improve the
sound situation on Windows hosts we'd be happy to review patches.

thanks
-- PMM

Re: Sound error: Could not initialize DirectSoundCapture

[Jakob Bohm]

On 07/12/2020 15:13, Peter Maydell wrote:

On Mon, 7 Dec 2020 at 13:56, kazusanosuke_kaz
 wrote:

Hi, all!

I've just installed qemu to my PC, Windows 8.1(x64) with Core i5-4670 / MSI 
MS-7817(OnBoard Sound) / GeForce GT 640
Windows 98SE was successfully installed on qemu, but sound device doesn't work 
...

"C:\Program Files\qemu\qemu-system-i386.exe" -device sb16 -m 512 
Windows98SE.qcow2
dsound: Could not initialize DirectSoundCapture
dsound: Reason: No sound driver is available for use, or the given GUID is not 
a valid DirectSound device ID

(I don't use Windows, but here are some suggestions based on
reading the source code.)


Even though I choose another soundhw, the result is all the same

That's because this error message is not related to what sound
hardware is being given to the guest. It's the QEMU DirectSound
audio backend complaining that when it asked the host Windows
for a sound-input device (ie a microphone or similar) it got
an error back. (Specifically, the IDirectSoundCapture_Initialize()
call failed.) So the warnings are basically saying "sound input
to QEMU is not going to work", and they'll be printed for any
kind of sound hardware you give to the guest (sb16, ac97, ...).

That said, looking at the code I think that the DirectSound
backend attempts to continue even if audio input doesn't work.
So if you only care about audio output, in theory these warnings
should be harmless.

You could try some of the suggestions in this stack overflow
post:
https://stackoverflow.com/questions/55601413/how-to-fix-could-not-initialize-directsoundcapture-in-android-studio
(effectively "plug in a microphone" or "enable some windows-internal
input device") to see if they help. If that makes the warnings
go away and also makes sound output start working, then there
might be a bug in the QEMU code that is supposed to handle
"input doesn't work but proceed with output anyway". If the
warnings go away but sound output still doesn't work, then
the output problem is not related to the warnings.

I sometimes use Windows, and the only time I tried a qemu on Windows,
I could not find any working sound option, and all the help and error
messages were useless, suggesting things that weren't explained, listing
options that didn't work etc.

Someone on the team needs to clean up sound support in the prebuilt
Windows binaries that are linked to from qemu.org.


--
Jakob Bohm, CIO, partner, WiseMo A/S. http://www.wisemo.com 

Transformervej 29, 2860 Soborg, Denmark. direct: +45 31 13 16 10 


This message is only for its intended recipient, delete if misaddressed.
WiseMo - Remote Service Management for PCs, Phones and Embedded

Re: Sound error: Could not initialize DirectSoundCapture

[Peter Maydell]

On Mon, 7 Dec 2020 at 13:56, kazusanosuke_kaz
 wrote:
>
> Hi, all!
>
> I've just installed qemu to my PC, Windows 8.1(x64) with Core i5-4670 / MSI 
> MS-7817(OnBoard Sound) / GeForce GT 640
> Windows 98SE was successfully installed on qemu, but sound device doesn't 
> work ...
>
> "C:\Program Files\qemu\qemu-system-i386.exe" -device sb16 -m 512 
> Windows98SE.qcow2
> dsound: Could not initialize DirectSoundCapture
> dsound: Reason: No sound driver is available for use, or the given GUID is 
> not a valid DirectSound device ID

(I don't use Windows, but here are some suggestions based on
reading the source code.)

> Even though I choose another soundhw, the result is all the same

That's because this error message is not related to what sound
hardware is being given to the guest. It's the QEMU DirectSound
audio backend complaining that when it asked the host Windows
for a sound-input device (ie a microphone or similar) it got
an error back. (Specifically, the IDirectSoundCapture_Initialize()
call failed.) So the warnings are basically saying "sound input
to QEMU is not going to work", and they'll be printed for any
kind of sound hardware you give to the guest (sb16, ac97, ...).

That said, looking at the code I think that the DirectSound
backend attempts to continue even if audio input doesn't work.
So if you only care about audio output, in theory these warnings
should be harmless.

You could try some of the suggestions in this stack overflow
post:
https://stackoverflow.com/questions/55601413/how-to-fix-could-not-initialize-directsoundcapture-in-android-studio
(effectively "plug in a microphone" or "enable some windows-internal
input device") to see if they help. If that makes the warnings
go away and also makes sound output start working, then there
might be a bug in the QEMU code that is supposed to handle
"input doesn't work but proceed with output anyway". If the
warnings go away but sound output still doesn't work, then
the output problem is not related to the warnings.

thanks
-- PMM