VIt's where I instinctively looked
Hmake a new section, sound utilities
H
Tlol
VI mean, by Bazzite's definition so is VLC.
Hwhat is vlc not at this point 
RIs :testing for OLED currently up to date with kernel modules/configs from stock Steam OS in regards to audio system/handling?
I reinstalled stock Steam OS today on my OLED in order to see whether my issues with distorted audio are related strictly to Bazzite or it is a Valve's issue.
Well, it turns out audio is 100% fine on stock Steam OS.
Now I reinstalled back stock Bazzite (:testing branch rebase + setup with Bazzite portal) and my audio issues are once again back - occasional crackling and from very little to frequent audio stutters/distortions (imagine if somebody had 'playback speed' knob and would turn it down below 100% by a random value for a randomised fraction of second every ~second). Additional strange thing is that for most games it seems 'mostly' fine (although still happens if you listen carefully to the speakers) - however, it is very noticeable in rhythm games, when almost immediately you can notice that audio goes out of sync with prompts on the screen (due to those issues) - and the longer stage goes, the more out of sync it gets. This makes rhythm games unplayable on Bazzite whereas it's fine on stock SteamOS.
I reinstalled stock Steam OS today on my OLED in order to see whether my issues with distorted audio are related strictly to Bazzite or it is a Valve's issue.
Well, it turns out audio is 100% fine on stock Steam OS.
Now I reinstalled back stock Bazzite (:testing branch rebase + setup with Bazzite portal) and my audio issues are once again back - occasional crackling and from very little to frequent audio stutters/distortions (imagine if somebody had 'playback speed' knob and would turn it down below 100% by a random value for a randomised fraction of second every ~second). Additional strange thing is that for most games it seems 'mostly' fine (although still happens if you listen carefully to the speakers) - however, it is very noticeable in rhythm games, when almost immediately you can notice that audio goes out of sync with prompts on the screen (due to those issues) - and the longer stage goes, the more out of sync it gets. This makes rhythm games unplayable on Bazzite whereas it's fine on stock SteamOS.
RI apologise for bugging ppl again with this, but this issue is really annoying me, seems to happen only on Bazzite itself and I can't seem to find any other person which would report such issue (maybe I haven't searched well enough)
KKernel and configs are 1:1, there may be some pipewire changes needed still
KI have the crackling audio on resume from sleep, but no issues with growing delays
RAre pipewire/wireplumber configs from /usr/share (which, from what I understand, are config templates) show values which are default when no system/user config is present?
KRight
RBecause if so, then indeed there are some differences from what I looken into between Steam Os from today and Bazzite
RThough it's a bit suprising, since if https://forum.manjaro.org/t/howto-troubleshoot-crackling-in-pipewire/82442 is to be believed, changes from valve's configs should actually make issues (if they happen) worse.
Manjaro Linux Forum
Difficulty: ★★☆☆☆ This tutorial will help you get rid of crackling/popping issues in PipeWire and PipeWire-Pulse, as well as replace PulseAudio with PipeWire. Note: This guide was written for pipewire with pipewire-media-session, not wireplumber, if you have wireplumber installed some of the configs will be at different locations, under differ...
RI'll gather those config templates from both and try to diff them to see differences.
JOn bazzite-deck-gnome, or any -gnome image for that matter, Discover Overlay will not start due to GNOME mutter not supporting the Layered Shell protocol used by
discover-overlay on Wayland.
KThere's an optional work around that will launch it anyway, but it's a default disabled for the time being
KCan enable it in /etc/default if you want to try it out
JI'll check it out and report back, thanks.
T-nokmods is deprecated for Bazzite right? Someone has asked me if it will forever stay on F38Tim assuming it relies heavily on kernel modules
KAll base images are nokmods now, Bazzite only comes with kmods atm
LOk dumb question but maybe im missing something if i wanted to attempt to fix the syntax warning the net.py file of waydroid is producing how can i save the modified file so waydroid will use it so i can test it? As apparently /usr/lib/waydroid is read only..
ADon’t let go
AWhen is the next bazzite buzz coming
Tlol im not sure yet. i just put out #9 not too long ago
Tthere's a few things in
:testing that, when ready to be in latest, i will probably talk about
KYou can't
KThe syntax error it's warning about it is in var
AOkies
LAh ok
AIma try some games next week on the ally in bazzite
AUsing the decky loader plugin as well
LSo wait is that warning actually something wrong with waydroid or is it something to do with bazzite that its complaining about?
KIt's complaining about a config file that lives in var having a syntax error
KThat's why I was saying delete /var/Waydroid and try relaunching on the newest build
LThe ujust reset script doesn't do that though right?
LBecause I've tried to delete it and it's always telling me that /var/waydroid "no such file or directory" so um is it not located at /var/waydroid ?
Jis installation on an oled borked? installs fine but this is all i get after a reboot
Mgive it a solid 5 minutes
Jnot blinking, just solid, almost seems like grub is stuck trying to boot the kernel
Jwill do, just wasn't sure if it was booting but doing first time setup or borked, figured if it was the former i would be able to see services if i hit b like on my lcd
KShould have a message on screen, and a logo
KUnless this is the stable image
KThen just wait, only testing has the needed changes for display from a cold boot
Myeah I think this is what happens if you install from the iso
Mrebase to testing doesn’t have the issue
Mbut I’ve done it a couple times so the install iso does work
Jmy first attempt was changing the grub entry in the iso to pull directly from testing, and i had the same result
Jthe picture i took was on stable but testing was the same thing
