Solved Sharing Audio in Linuxulator

I'm running Google Chrome on linuxulator to take classes online and noticed that audio will won't work if another browser on freebsd audio is playing so had to exit that browser to release the audio device.

Since I'm running the audio driver below:

pcm0: <Realtek ALC889A (Internal Analog 3.1/2.0)> (play/rec) default
pcm1: <Realtek ALC889A (Rear Analog)> (play/rec)
pcm2: <Realtek ALC889A (Rear Digital)> (play/rec)
pcm3: <Realtek ALC889A (Rear Analog Mic)> (rec)

It doesn't seem to support virtual channels (vchans) and I've been reading that creating an audio server isn't viable on freebsd. The audio system between freebsd and linuxulator doesn't seem to be shared as it's either one or the other so base from what I can tell I would need to get a usb audio interface to setup a shared audio between the two environments.

If anyone also experiences this issue you can share your thoughts of how it went for you.
 
I have trenched into the waters dive deep into the audio subsystems swimming across from pulseaudio (got that to work using dsp4 new hardware and pulse-oss layer) to sndio (sound suddenly stops) then virtual oss (got that working) but after some time has passed I stripped all of these away to pure OSS. Chromium will require dsp device to be created to play the sound and we added ALSA config on Chrome to point into the setting file for the fallback.
 
Assuming you are using pulseaudio, you can just share the freebsd socket (make sure it's readable) and place it on ${XDG_RUNTIME_DIR}/pulse/native on the the compat/linux chroot, that should work.
 
Assuming you are using pulseaudio, you can just share the freebsd socket (make sure it's readable) and place it on ${XDG_RUNTIME_DIR}/pulse/native on the the compat/linux chroot, that should work.
I'm using OSS native on freebsd and disabled pulseaudio from starting so I can start with the basics for audio playback.
 
I am now stopping my obsession over the audio with the linux-chrome being able to feed the audio streams on the same speaker chromium is using. It is time to settle and not further intrude on adjusting the tunable settings that I overdid causing audio stutters from cpu bound tasks.
 
I am now stopping my obsession over the audio with the linux-chrome being able to feed the audio streams on the same speaker chromium is using. It is time to settle and not further intrude on adjusting the tunable settings that I overdid causing audio stutters from cpu bound tasks.
That's crazy talk.
 
Back
Top