On Wed, Nov 04, 2026 at 02:46:43PM -0700, Thomas Frohwein wrote: > On Wed, 4 Nov 2026 18:20:00 +0100 > Antoine Jacoutot <[email protected]> wrote: > > > > > This is a fairly small and simple midi program you can use to > > > > test by just putting in a few notes: > > > > > > > > https://timm-schmidt.com/software/simplemidi/#download > > > > > > > > Extracted with unzip(1), Then ran: > > > > > > > > $ cd simpleMidi-windows-x86_64 > > > > $ pipewire & > > > > $ wine simpleMidi.exe > > > > > > > > Putting in a few notes, the distorted, crackling sound can be > > > > heard. Not sure about simpler reproducers; can't find something > > > > built into wine to test audio playback. > > > > > > > > I don't use pipewire or pulseaudio otherwise. If other consumers > > > > of pulseaudio don't have this problem, like it sounds from your > > > > email, then we will have to look at the wine pulseaudio > > > > backend... > > > > > > Use this workaround for now. > > > I will fix pipewire config later on. > > > > > > PULSE_LATENCY_MSEC=60 wine simpleMidi.exe > > > > This works for me: > > This fixes it indeed. I went ahead and committed it. As a bonus, I > would like to point out that with this new setup, the previously > observed noticeable audio lag in wine seems to be resolved. > > What's the recommended way for users to ensure a running pipewire > service? `pipewire &` in .xsession? (asking because I'm anticipating > "no audio" reports about wine and possibly other ports without some > hints...)
Is users are running under a desktop manager, pipewire will be started automatically throug /etc/xdg/autostart/pipewire.desktop. Otherwise it needs to be started manually through .xsession or some other way. /usr/local/bin/pipewire & is all that's needed.
