It seems VBox sets audio device correctly to PulseAudio for new devices.
This issue concerned only machines created before Karmic installation
and just moved with other configuration files.
I'm marking it invalid.
** Changed in: virtualbox-ose (Ubuntu)
Status: New => Invalid
--
Terrible
(ok, don't bother to answer here, I asked a question:
https://answers.launchpad.net/questions/86831)
--
Terrible sound in VirtualBox (both OSE and mainstream)
https://bugs.launchpad.net/bugs/451688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
BTW: as far as I know, if an application wants to use ALSA, it's tricked
and really uses a virtual device which really outputs its sound to
PulseAudio. So it seems there is a huge problem with efficiency of this
virtual device, am I right? Otherwise even setting ALSA as a sound
output shouldn't cau
*Yawn*. I should have already know that. As usual, VirtualBox defaulted
to ALSA; changing it to PulseAudio fixed the problem.
It seems like a very common issue shared by many programs. How are those
poor usual Ubuntu users supposed to know they have to manually switch
alsa to pulse in 1/2 their ap
** Description changed:
Binary package hint: virtualbox-ose
My VirtualBox instance started to have terrible 'hoarse' sound under my
guest Windows XP. After I installed Karmic (at 09 X 2009) it was OK, but
it got spoilt after a period of time. Reinstalling guest additions
didn't help.
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33682051/Dependencies.txt
** Attachment added: "LsMod.txt"
http://launchpadlibrarian.net/33682055/LsMod.txt
** Attachment added: "ProcEnviron.txt"
http://launchpadlibrarian.net/33682056/ProcEnviron.txt
** Attachment
