Originally created by @ghost on GitHub (Aug 20, 2021).
Currently pipewire can see the pulseeffects sound, which requires a codec (visit pr 72). But what about audio over the virtual ethernet? Set up could include rtsp to broadcast over the virtual ethernet and pipeline to pipewire. If so, would it be too latent?
Originally created by @ghost on GitHub (Aug 20, 2021).
Currently pipewire can see the pulseeffects sound, which requires a codec (visit pr 72). But what about audio over the virtual ethernet? Set up could include rtsp to broadcast over the virtual ethernet and pipeline to pipewire. If so, would it be too latent?
@sickcodes commented on GitHub (Aug 20, 2021):
Network is fast tbh since we use vmxnet3 so I don't think the latency will be affected.
Maybe some type of ASIO mac thing? Tbh I haven't used audio before inside the VM.
Passing thru /dev/snd allegedly works, or sound card, but this answer looks pretty sufficient: https://stackoverflow.com/questions/51859636/docker-sharing-dev-snd-on-multiple-containers-leads-to-device-or-resource-bu
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ghost on GitHub (Aug 20, 2021).
Currently pipewire can see the pulseeffects sound, which requires a codec (visit pr 72). But what about audio over the virtual ethernet? Set up could include rtsp to broadcast over the virtual ethernet and pipeline to pipewire. If so, would it be too latent?
@sickcodes commented on GitHub (Aug 20, 2021):
Network is fast tbh since we use vmxnet3 so I don't think the latency will be affected.
Maybe some type of ASIO mac thing? Tbh I haven't used audio before inside the VM.
Passing thru /dev/snd allegedly works, or sound card, but this answer looks pretty sufficient: https://stackoverflow.com/questions/51859636/docker-sharing-dev-snd-on-multiple-containers-leads-to-device-or-resource-bu