Alternatives to DirectSound for Host Audio Driver
Posted: 18. Sep 2008, 16:52
I have been exploring an issue I have had with VirtualBox since I first migrating my virtual platforms from VMWare a couple of weeks ago. In VMWare, my sound performance was excellent, and I could stream media, listen to local music files, and watch videos without any noticeable performance degradation when compared with that of my host.
However, I have had issues with VirtualBox's sound emulation from day one. Initially, I had slight choppiness from time to time, particularly when I was doing things on my host at the same time as listening to sound from the guest. I also had issues of the guest's audio support being "lost" when I switched from full screen view to a windowed view.
I did some research and found what I believe to be at hand. Windows Vista no longer provides a hardware level view of the sound device to the DirectSound API. Thus, all calls made through DirectSound and now emulated through another layer, the WASAPI component new to Vista. Articles I've came across directly mention this as a notable limitation that could degrade performance in certain applications.
I am just curious as to what type of solutions might be out there, or perhaps to suggest that VirtualBox look into a direction that allows a more direct approach towards sound production from the guest that avoids this additional layer of emulation. It seems as if on Vista, it would be more advantageous to directly utilized the WASAPI rather than rely on DirectSound, which just leverages WASAPI in the first place.
Has anyone else had similar performance problems with using the sound in their guests when using a Vista host? I have posted this under a similar thread, but the purpose of this thread is primarily to suggest a movement in a different direction, to allow for an alternative host driver selection for Vista machines.
However, I have had issues with VirtualBox's sound emulation from day one. Initially, I had slight choppiness from time to time, particularly when I was doing things on my host at the same time as listening to sound from the guest. I also had issues of the guest's audio support being "lost" when I switched from full screen view to a windowed view.
I did some research and found what I believe to be at hand. Windows Vista no longer provides a hardware level view of the sound device to the DirectSound API. Thus, all calls made through DirectSound and now emulated through another layer, the WASAPI component new to Vista. Articles I've came across directly mention this as a notable limitation that could degrade performance in certain applications.
I am just curious as to what type of solutions might be out there, or perhaps to suggest that VirtualBox look into a direction that allows a more direct approach towards sound production from the guest that avoids this additional layer of emulation. It seems as if on Vista, it would be more advantageous to directly utilized the WASAPI rather than rely on DirectSound, which just leverages WASAPI in the first place.
Has anyone else had similar performance problems with using the sound in their guests when using a Vista host? I have posted this under a similar thread, but the purpose of this thread is primarily to suggest a movement in a different direction, to allow for an alternative host driver selection for Vista machines.