Open lazzarello opened 2 years ago
Hi,
I've just released a new version to the stable channel. Can I request that you update, move your modified launch
script aside so that the snap copies a new one over and try running the vm again to see if the audio issues are fixed?
What happened?
With these sound settings from the launch shell script, sound from the VM was audible but had an unstable clock, which both changed the speed of music playing with a regular tempo and produced frequent audible clicks.
Using the same disk image for a VM created through virt-manager (both are backed by kvm/qemu) with the following setting played sound as I would expect.
The only difference I could see is when the qemu "pulse native" device connects to the pulse graph, its buffer size is much lower (about 4x lower) when played out of the same sound device as the virt-manager buffer (which is about 4300 samples, so pretty long). I do not know how to control this value and it seems virt-manager just has a different default? I'm not really sure.
What should have happened?
The virtual audio device from clouds qemu device should play sound the same way as the virt-manger audio device. Both are backed by the same pulseaudio server.
Output of
snap info clouds
Output of
snap connections clouds
Output of
snap version
Relevant log output
No response
Teminal output of app
No response