> Since two (or more) players work, I don't think the problem is in the > host. ;-) More data: If I start mplayer, then a guest VBox (winxp),
I agree. > sound works simultaneously for both the VBox and one or more mplayer > instances on the host. Additionally, if I stop the mplayer instances, > while the VBOx guest is still running, I am able to restart mplayer > instances and hear audio. HOWEVER, if I start the guest VBox first, > then mplayer wont start unless I disable audio, but audio continues to > work on the VBox. I suspect that VBox is doing some sort of audio > locking on startup, and it only takes complete control (full locking?) > if it can, otherwise it "shares" (sorry for my complete lack > specificity wrt alsa mixing) Yes, something like that. The strange thing is that in my case VirtualBox behaves like any other ALSA client (after selecting ALSA driver in the configuration). It works just like mplayer, amarok or anything else (and obeys the /etc/asound.conf and .asoundrc properly). But I don't have much experience with ALSA to guess what might be wrong. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
