> Question: Who cares about Jim's problem? ^W^W^W^W^W^W^ Opps! ;-) What > I meant to say is: do you know if VBox tries to gain an exclusive lock > on /dev/dsp (or whatever), and if it doesn't get exclusivity does it do > something different and continue. As I mentioned before, if /dev/dsp is > in use (i.e. mplayer is running) when VBox starts, then VBox continues > to work as expected. However if VBox is started first, no other > application can play sound until the VBox guest is stopped/suspended.
My understanding about ALSA is that it doesn't use /dev/dsp at all. ALSA clients should use library functions to create sound. The one last thing I have in mind is to check what mplayer and VBox are saying about sound devices. Can you locate the relevant output in the case you run first mplayer and then vbox and then other way around ? Output on my system looks something like this: 1) When you run mplayer from command line, it should print info messages about sound system it uses. Mine prints something like this: alsa-init: using device default alsa: 48000 Hz/2 channels/4 bpf/72000 bytes buffer/Signed 16 bit Little Endian AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) 2) Vbox will print something like this in the log file: 00:00:04.338 Audio: Trying driver 'alsa'. 00:00:04.338 Audio: set_record_source ars=0 als=0 (not implemented) 00:00:04.412 ALSA: ADC frequency 44100Hz, period size 1024, buffer size 4096 00:00:04.415 ALSA: DAC frequency 44100Hz, period size 6000, buffer size 18000 Vladimir _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
