05:40 <mrvictorywin> How can I disable or modify the default DSP (digital sound processing) on macOS? The asahi-audio github page mentions macOS uses DSP to improve sound quality and Linux should also use DSP to match macOS. I have an Intel Mac (MB Air early 2015 running Arch) and audio quality on Linux is worse than macOS. I'm trying to find if the cause is lack of DSP or sth else ie. HDA commands.

08:01 <cy8aer> mrvictorywin: Asahi linux uses a DSP like macOS not _the_ DSP of macOS. Apple laptops have 2 or more speakers which have their own digital analogue converters. The DSP provides the crossovers like in old HIFI speakers. They also adjust the frequency spectra of the loudspeakers (Asahi as straight a frequency response as possible, macOS with more boom). Asahi also uses psychoacoustic effects to boost the bass and there is a limiter to avoid speaker...

08:01 <cy8aer> ... damages. Sound on linux laptops is a general problem and may be adapted from the asahi solution for other laptops. Since the macOS DSP has nothing to do with the asahi DSP, there is unfortunately nothing you can do for the Linux sound on the macOS side. And the DSPs are software, no hardware!

08:30 <cy8aer> Components involved implement the sound in asahi: asahi-scripts, alsa-ucm-conf-asahi, speakersafetyd, bankstown (lv2). For the speakers (we have three mics and beam forming is needed) there is another lv2 plugin triforce. These components are heavily using pipewire and wireplumber. More infos at https://github.com/AsahiLinux/asahi-audio

10:37 <mrvictorywin> cy8aer: my goal by disabling DSP is to understand if it fixes the issues ie. buzzing I have on Linux. I basically want to see if I turn off DSP on macOS whether the audio output becomes similar to Linux. If it does then I can rule out driver problems.

10:43 <cy8aer> mrvictorywin: ah I see.

10:51 <chadmed> mrvictorywin: in case you read the logs, you cant turn off the dsp on macos'

12:16 <chadmed> sooooo sam_ and/or leio re getting asahi enabled upstream

12:16 <chadmed> will i just make a PR against the live ebuild with what we're currently doing in the overlay?

12:17 <chadmed> sorry that wasnt particularly clear, i mean mesa asahi (incl. honeykrisp)

13:49 <leio> chadmed: probably, if you beat me to it ;) but I don't know what kernel bits I need to match uapi

13:50 <leio> (to test)

13:51 <jannau> leio: asahi-wip but not tags for a while

16:33 <mrvictorywin> Another question: how can I get the count of tweeters / woofers on either linux or macos? This repo: https://github.com/davidjo/snd_hda_macbookpro supports setting up 4 channels for 2 tweeters & 2 woofers but idk if I need a 4 channel setup as my mac has a different audio device (cs4208)

16:42 <sam_> chadmed: sounds good

16:42 <flokli> chadmed: hmmh, I'm trying to debug why asahi-audio doesn't seem to properly do the microphone thing on my NixOS machine (J413). I poked around at `wpctl status` and `wpctl inspect`, as well as running pipewire/wireplumber with more debug being enabled, and it looks like api.alsa.path is not hw:AppleJ314,1 or hw:AppleJ314HPAI,0 (or I'm looking in the wrong place).

16:42 <sam_> chadmed: as long as it's upstream -- I wouldn't expect Matt to necessarily merge it if it's not yet

16:42 <sam_> chadmed: he may be open to a draft PR to discuss stuff

16:42 <flokli> wpctl inspect says alsa.card_name = "MacBook Air J413" and api.alsa.path = "hw:0"

16:44 <flokli> is there multiple api.alsa.path that can be matched on, and if so, how do I see which ones exist?

16:47 <jannau> sam_: it's merged https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33984

20:43 <n3ph> I am currently compiling non-stop and have a look on `powertop` in parallel. Why do I see so much idle state, or might it be inaccurate? https://pastebin.com/rExjX6MY

20:48 <chadmed> flokli: if the api alsa path is hw:0 and not J314HPAI then something is wrong