#asahi-dev · 2023-02-24 14:51
dsharshakovbut maybe that can be left for later#asahi-dev · 2023-02-24 14:51
dsharshakovAFAIK also possible to offload just because of why not, even if it's just some spdif encoded format#asahi-dev · 2023-02-24 14:47
dsharshakovnot just 7.1 which is handled by HDMI PCM#asahi-dev · 2023-02-24 14:47
dsharshakovI mean stuff like Atmos apparently only existing in compressed forms (pass bitstream to the AV receiver which decodes metadata to render sound objects)#asahi-dev · 2023-02-24 14:45
dsharshakovMany modern TVs should have that sort of thing, and macOS is likely to take advantage of that (since no immersive audio is possible with PCM only)#asahi-dev · 2023-02-24 14:44
dsharshakovSomething to attach and trace with to see how it's handled#asahi-dev · 2023-02-24 14:43
dsharshakovNo RE sample like supporting TV to test?#asahi-dev · 2023-02-24 14:42
dsharshakovSPDIF-like data offloading. Apparently driver has something to do with that#asahi-dev · 2023-02-24 14:42
dsharshakovSNDRV_PCM_FMTBIT_IEC958_SUBFRAME_LE or something like this#asahi-dev · 2023-02-24 14:40
dsharshakovmight also be architecturally important#asahi-dev · 2023-02-24 14:40
dsharshakovprofile-wise, have you checked passthrough modes on HDMI (Dolby TrueHD, DTS, other codec bitstreamed directly to AV receiver)?#asahi-dev · 2023-02-24 14:38
dsharshakovYes, idk how PA handles devices without UCM and how does it treat HDMI#asahi-dev · 2023-02-24 14:37
dsharshakovALSA Card Profile, yes, it's implemented by PW#asahi-dev · 2023-02-24 14:37
dsharshakovAnd UCM is optional in that mix (maybe can be avoided), ACP can handle that just fine#asahi-dev · 2023-02-24 14:35
dsharshakovbut at least we (PW) shouldn't check for it being an HDA device. ALSA and PA might be different though#asahi-dev · 2023-02-24 14:35
dsharshakovfirst link#asahi-dev · 2023-02-24 14:34
dsharshakov> The ELD format is specific to HDA Intel sound cards#asahi-dev · 2023-02-24 14:34
dsharshakovso apparently it's reported in some non-ordinary way but uses that ELD#asahi-dev · 2023-02-24 14:33
dsharshakovfound by brief ripgrepping#asahi-dev · 2023-02-24 14:33
dsharshakovhttps://gitlab.freedesktop.org/pipewire/pipewire/-/blob/da21cfa93c892dc7d7cd6894771ae50b4c55a1fa/spa/plugins/alsa/acp/alsa-util.c#L1857 https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/da21cfa93c892dc7d7cd6894771ae50b4c55a1fa/spa/plugins/alsa/acp/acp.c#L886#asahi-dev · 2023-02-24 14:31
dsharshakovalright, found some, will link in a sec#asahi-dev · 2023-02-24 14:31
dsharshakov> maybe the sound servers have special-cased support for hdmi#asahi-dev · 2023-02-24 14:28
dsharshakovwell, nothing related here. but I clearly remember seeing monitor name in say pw-dump's#asahi-dev · 2023-02-24 14:27
dsharshakovWait, you said your DCP audio driver isn't using ASoC, didn't you?#asahi-dev · 2023-02-24 14:27
dsharshakovhttps://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/codecs/hda/hdmi.conf#asahi-dev · 2023-02-24 14:25
dsharshakovDo existing UCM configs implement something similar#asahi-dev · 2023-02-24 14:24
dsharshakovvc4 uses ASoC and viewing through it doesn't seem to show anything related to feeding EDID data to snd_*#asahi-dev · 2023-02-24 14:20
dsharshakovMaybe see how vc4 or others solve this (not having HDA)#asahi-dev · 2023-02-24 14:18
dsharshakovAnd Radeon is being an HDA device. Unsure about the exact mechanisms#asahi-dev · 2023-02-24 14:17
dsharshakovAMDGPU shows monitor name#asahi-dev · 2023-02-24 14:17
dsharshakovit's more expected to see display name from EDID there, not the port type#asahi-dev · 2023-02-24 14:16
dsharshakovMaybe it's better to create it dynamically with the monitor name in place, since desktop HDMI audio does the same (IIRC being snd-hda-intel inside)#asahi-dev · 2023-01-18 09:17
dsharshakovAlright#asahi-dev · 2023-01-18 09:16
dsharshakovI've seen misspells and spaces being used#asahi-dev · 2023-01-18 09:16
dsharshakovbtw, what's the proper way of naming a person without mentioning them on IRC?#asahi-dev · 2023-01-18 09:14
dsharshakovAnd basically everyone else here#asahi-dev · 2023-01-18 09:13
dsharshakovYes. Nice to know markan adheres to such a philosophy to make users safe :)#asahi-dev · 2023-01-18 09:13
dsharshakovAlright. Thanks guys for speaker protection studies: maybe we can enable those in some 2-3 months#asahi-dev · 2023-01-18 09:11
dsharshakovUX: yeah, will get covered. As I said, I just need to get to it...#asahi-dev · 2023-01-18 09:11
dsharshakovSo expect userspace to be harsh, users are quite eager to make everything glitch#asahi-dev · 2023-01-18 09:10
dsharshakovYou can also make PW DSP glitch by setting low quantum etc#asahi-dev · 2023-01-18 09:10
dsharshakovI answered to povik's "hide speakers to be safe"#asahi-dev · 2023-01-18 09:09
dsharshakovUCM2 as well #asahi-dev · 2023-01-18 09:08
dsharshakovAnd anyway, you mustn't rely on WirePlumber to prevent users from accessing speakers. They should be able to safely push DC bias, square waves and whatever they want, kernel + speakersafetyd should prevent frying the machine. PipeWire is there to ease and enrich, not to protect#asahi-dev · 2023-01-18 09:05
dsharshakovWe should not bikeshed about that config format, don't let it be another cpuidle. Rule matching should suffice, UCM2 does the same#asahi-dev · 2023-01-18 09:04
dsharshakovWell, node hiding should be enough for our use cases. Not enough to store the config universally in repos yet#asahi-dev · 2023-01-18 09:03
dsharshakovActually loading the filter by rules causes debates due to config structure #asahi-dev · 2023-01-18 09:03
dsharshakovI need to finish at least wireplumber.hide prop as the first step#asahi-dev · 2023-01-18 09:02
dsharshakov* dsharshakov should finish old branches instead of creating new projects...#asahi-dev · 2023-01-18 09:00
dsharshakovIt's hard to catch