3hhh

This could partially be fixed via [my script](https://github.com/3hhh/xtalk). Only partially as the first incorrect MIDI event happens ~10ms before the choke, the second ~5ms and I only want to delay...

Btw increasing the sense time helped with this issue. However it caused worse rim detection, so that I dropped the change again.

No. Let's say you have encrypted containers (encrypted files with other files inside) inside a VM (usually `sys-usb` on some USB drive). Then `qcrypt` can attach those to other VMs...

> Ok so an analogy would be if i have my files in truecrypt type container on a usb drive i plug it in and then qcrypt detects its been...

On 12/29/23 12:24, Marek Marczykowski-Górecki wrote: > Can you check what pulled in pipewire in dom0? I don't see it neither system updated from 4.1 nor in a fresh install....

So far I couldn't fix dom0 audio with either `pulseaudio` or `pipewire` & `pipewire-pulseaudio` installed. In both cases `pavucontrol` shows no VMs except for the dom0 audio devices. `ps aux|grep...

On 12/29/23 16:50, Marek Marczykowski-Górecki wrote: > If pacat processes are there, they should connect to pipewire/pulseaudio, if they can't it means relevant daemon isn't running. See systemctl commands I...

Looks like there's some more affected users: https://forum.qubes-os.org/t/upgraded-to-4-2-and-audio-no-longer-works/23130/14 Any debugging hints why those `pacat-simple-vchan` instances don't show up in `pavucontrol` would be much appreciated. Unfortunately the journal doesn't have any...

> However it looks like it's missing its configuration? I noticed that `/etc/pulse/qubes-default.pa` exists in VMs, but not in dom0. However adding it in dom0 didn't help.

Hm interesting: Using my old 4.1 `debian-11` template makes audio work for the VMs using that template (those VMs then come up in dom0 `pavucontrol` as well). So I apparently...