FI just read PIPEWIRE_QUANTUM & PIPEWIRE_LATENCY is just for jack applications & Fedora doesn't have pipewire-jack
Ppipewire supports breaking up the config into as fine of chunks as you need in XDG config spec location
Phaven't personally had to touch it since it was at version 0.3.3 or something so a couple years back
Pbut it is quite intuitive, don't think the devs would have any issue modifying it globally (or just adding it to the setup for deck images)
FI would test this in my image for sure
Pfor clarification PIPEWIRE_LATENCY works with alsa, jack, and pipewire
Pit requests specific values, i think the issue here is more with the minimum allowed
FIt doesn't work for Firefox flatpak for me
it shows 2048 quantum
it shows 2048 quantum
Psome applications will request "the lowest i can get!" and that can cause issues 
Pfirefox is using pulseaudio
Fmakes sense
Rcopy /usr/share/pipewire/pipewire-pulse.conf.d/wine.conf to ~/.config/pipewire/pipewire-pulse.conf.d/
Open file there and change both values from 1024/48000 to 128/48000.
Open file there and change both values from 1024/48000 to 128/48000.
systemctl restart --user pipewire pipewire-pulse.service wireplumber.servicePwait, the buffer is too large?
Pthat's a first in my entire life LOL
Pyou can remove a lot of that config file after copying it over basically just leaving the skeleton of changes you actually make
Pmodule you're changing & the changes made
Pi had a peek in
/usror
:testing, perhapsRIt's on
:testing only currently suppossedlyPmhm
RPipewire on :latest is also 1.0.0?
Pyes, 1.0, just checked
Pah the file is already as fragmented as it can be. good stuff
RSo most probably that file hasn't shipped with package but was added explicitly there.
Pit has been added by the bazzite devs, not something that comes with pipewire normally
Hits here if you want it
https://github.com/ublue-os/bazzite/blob/testing/system_files/desktop/shared/usr/share/pipewire/pipewire-pulse.conf.d/wine.conf
https://github.com/ublue-os/bazzite/blob/testing/system_files/desktop/shared/usr/share/pipewire/pipewire-pulse.conf.d/wine.conf
GitHub
Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other h...
P1024 is an absolutely huge minimum so it's unsurprising that had some negative consequences
P20ms 
RIt was added 2 weeks ago
Pmaybe someone should poke around and see how low the OLED deck can go?
Pmin is only a minimum, after all
Pit's generally up to applications to ask for what they need
Pwould do it myself because i'm an elitist rhythm gamer on occasion but don't own the device 
RThis is the reason (minus 'elitist' part) of why this issue was bugging me so much.
RSo happy that I finally found root cause
Pelitist part is entirely a joke. i just like to tinker and get the best result in my personal use case
Mon nobara min-quantum is set to 32 across the board for OLED Deck from what i'm seeing in pw-dump
Mit was kind of odd, there was never any point that I can tell where Nobara had the same audio issues pop up as bazzite did, even though the OLED audio packages were aligned
RThat seems to also be the default on stock SteamOS
ROr rather, there are no config files at all on stock in /usr/share/pipewire iirc
RThough version shipped there is also older, 0.3.68 I think?
P/usr/share/pipewire should contain all the default configs, it was changed from /etc/pipewire yonks agoMyeah /etc is the override folder, so if you drop something in there it will default to that over the standard system config
KSee if this helps
KOr hurts
KAnd thanks for all the research you two
KAlways appreciated
SCan you dual boot bazzite on same drive?
