2023-05-28
00:01chadmed i should check in on the pipewire situation re auto-selecting appropriate configurations
00:21barrowsx has joined #asahi-dev
00:22bgb has joined #asahi-dev
00:26brolin has quit [Ping timeout: 480 seconds]
00:43brolin has joined #asahi-dev
01:42barrowsx has quit [Quit: barrowsx]
02:00gabuscus has quit []
02:10brolin has quit [Ping timeout: 480 seconds]
02:12barrowsx has joined #asahi-dev
02:19bps has joined #asahi-dev
02:22gabuscus has joined #asahi-dev
02:32brolin has joined #asahi-dev
02:48bps has quit [Ping timeout: 480 seconds]
03:22brolin has quit [Ping timeout: 480 seconds]
03:50barrowsx has quit [Quit: barrowsx]
04:38derzahl has quit [Ping timeout: 480 seconds]
05:04derzahl has joined #asahi-dev
05:33dsharshakov has joined #asahi-dev
05:34dsharshakovIDENTIFY
05:34dsharshakovsorry
05:34dsharshakovHello chadmed! Yes, I've submitted a draft for permissions refactor, but it's utterly broken and WirePlumber masters don't have time to fix that
05:35dsharshakovHowever, I'm thinking of doing a simple "Load and route chain once device is discovered"
05:35chadmedi was going to test the rest of your patches today but i went down a config parsing rabbit hole that led nowhere instead :P
05:35dsharshakovYeah, now we have lower layers as an idiot protection, thus ones picking wrong sink wont make machine go boom boom
05:36dsharshakovWell, we want it for WP 0.4 probably, yea? Not waiting for 0.5
05:37dsharshakovLet me open g.fd.o, I have a draft branch I can remove permissions stuff (racy) from and rebase to some commit fresher than 1yr ago
05:37dsharshakovwill rebase and push to a sideways branch
05:37chadmedi dont think theres any particular rush (at least not on my end) so if upstream needs more time then thats no big deal
05:38chadmedwe have the benefit of being able to simply not release anything until its actually ready
05:38dsharshakovWP people tell me to do that for 0.5 but unsure when is that released
05:38dsharshakovIt should be loading fine once I toss out permissions
05:39dsharshakovBut I'm mainly developing on PipeWire (DSP libs, modules etc), WirePlumber is a bit hard to me
05:39chadmedbut like i said we can simply not release speaker support until all this stuff is in a healthy place
05:39chadmedyeah i was trying to avoid WP today but it seems like thats where they really want this stuff to go
05:39dsharshakovwe can start with !412 rebased since it should be safe to mess with PW in any way, yes?
05:40dsharshakovYes, we shouldn't hack a filter into ALSA plugin (the thing PW uses to output to ALSA). No other way other than module-filter-chain
05:41chadmedmy idea today was to try load a config fragment when the node is registered, using alsa.driver_name and alsa.card_name as the keys to find the right config file
05:42chadmedbut it doesnt like loading configs before all nodes have been registered and the context loaded
05:43dsharshakovWell, my WIP does the same I believe?
05:43dsharshakovah, I load the config at startup anyway, yes
05:43dsharshakovWe can't read files from Lua, at least in 0.4
05:44dsharshakovMaybe you or m_arcan can contact gkiagia (at Collabora, doing most WirePlumber work) to review and help with my permissions WIP to make a proper solution move forward
05:45dsharshakovoh, no way. session manager exists for that)
05:45dsharshakovyes, PW is just a framework session manager assembles into the desired config
05:46chadmedi think for now we just progress without the permissions stuff since we have the daemon set up in a way that should make all safety concerns go away
05:47chadmedso if the user wants to select the wrong sink then at least its not going to explode the machine
05:47dsharshakovyes, please do. I know they're busy, but 0.5 work is being really slow...
05:52dsharshakov`everything's been slow lately on most fronts everywhere` <-- why so? Seems everyone in Asahi is also busy
05:53dsharshakovchadmed: here you are https://gitlab.freedesktop.org/d3dx12.xx/wireplumber/-/commits/dsp-monitor-may-23
05:53dsharshakovnot tested at all, busy rn
05:53dsharshakovUse description from https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/412 to get started on configs. I'm unsure whether all of that is up to date enough...
05:54chadmedso when i install i just take that policy lua and copy the filter chain into it and fix the match statement?
05:54dsharshakovI suppose I gave you an appropriately formatted config for J314, but that probably changed
05:55dsharshakovpaste example from descr
05:55dsharshakovyes, then change matchers and insert an inlined FC description
05:56dsharshakovDrop `-- Used to hide streams` section, however, shouldn't do anything bad
05:56dsharshakovleave this essentially: table.insert (dsp_policy.policy.rules, { matches = { { { "media.class", "matches", "*/Sink" }, { "node.name", "=", "alsa_output.pci-0000_03_00.6.analog-stereo" } }, }, device_matches = { { { "device.name", "=", "alsa_card.pci-0000_03_00.6" } }, }, filter_chain = '{"media.name":"My DSP Speakers 2", "capture.props":{"node.virtual":false, "audio.channels":2,
05:58dsharshakovPing me if you need help with PW/WP, I am watching the IRC logs. May be busy, but will try to help as I can
05:59dsharshakov has quit [Quit: Page closed]
06:17dsharshakov has joined #asahi-dev
06:18dsharshakovSPA JSON (the permissive type PW uses)s is fine, just remove newlines
06:19dsharshakov has quit [Remote host closed the connection]
06:39gladiac has quit [Quit: k thx bye]
06:53dsharshakov has joined #asahi-dev
06:53dsharshakovYes, and I wasn't able to deduce the reason for filter chain rate switch bug (#2969 iirc) However, there's a reliable reproducer at the issue now. Please don't add more allowed rates or make the speaker output only support 48000 using PW props for now.
06:54chadmed has quit [Remote host closed the connection]
06:54chadmed has joined #asahi-dev
06:54dsharshakovWim said that didn't reproduce for him, but described method leads to clicks (audio interleaved with 0s) in almost 100% for me
06:55dsharshakovIn some weeks I might be able to dedicate time to that
06:55chadmedanyway what do i need to do to get this to install correctly? the only options i added were -Dlibdir and -Dprefix because gentoo
06:55dsharshakovWhat did you ask multirate convolver for?
06:55dsharshakovI build WP together with PW
06:56dsharshakovBut you can probably use your ordinary opts as you install WP on Gentoo, but give my branch as a source
06:56nicolas17 has quit [Quit: Konversation terminated!]
06:56chadmedwe have multiple rates because the resampling produced low quality, i have no intention to add more rates than we currently have (44, 48, 96, 192) because nothing else matters for desktop audio
06:57dsharshakovFor dev setup I checkout PW, run meson and it pulls WP and builds it. Then I can change wireplumber subproject (e.g. roll its git rev) and re-run ninja in PW dir
06:58dsharshakov`44, 48, 96, 192` <-- switching from 48k to 96k is affected in some cases. Let's stick to 48000 as a balanced option for non-pro tasks and then attempt to squash the bug. It lies somewhere in the graph management
06:59dsharshakovwell, weird. my system is a typical AMD laptop, no hardware specifics (Bluetooth also seems to be affected)
07:00dsharshakovEven if you try to pause, wait and play a 96k track in Elisa?
07:00dsharshakovThat (as described) is a solid reproducer
07:02dsharshakovthat didn't repro for me. Anyway, better keep that topic in https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2969 since that's not hw specific
07:02dsharshakovWe can switch to oftc-pipewire if you'd like, since we're pretty far from hw specials anyway
07:03dsharshakovPW is available on matrix as well
07:15dsharshakov has quit [Quit: Page closed]
07:28derzahl has quit [Ping timeout: 480 seconds]
08:14mkurz has quit [Ping timeout: 480 seconds]
08:30gladiac has joined #asahi-dev
08:36gladiac has quit [Quit: k thx bye]
08:37gladiac has joined #asahi-dev
08:48blazra has quit [Quit: The Lounge - https://thelounge.chat]
08:48blazra has joined #asahi-dev
09:26jeisom has quit [Quit: Leaving]
09:34___nick___ has joined #asahi-dev
09:35___nick___ has quit []
09:35chadmed has quit [Remote host closed the connection]
09:36chadmed has joined #asahi-dev
09:37___nick___ has joined #asahi-dev
09:42nsklaus has joined #asahi-dev
10:12roxfan has quit [Ping timeout: 480 seconds]
10:18gladiac has quit [Quit: k thx bye]
10:19marcanthat wasn't there before... DisplayPort MST support ganging up two dispexts (at a layer above the crossbar)?
10:20marcanit would make sense that dispext is in charge of the DP protocol so MST is implemented with a side channel with another dispext, while the dual pipe thing is for Thunderbolt only which uses discrete DP tunneled SST streams for multimonitor use cases.
10:21marcanwild guess though, it could also just be a tiling thing (but I thought we decided that was done with a single dispext)
10:55roxfan has joined #asahi-dev
11:07gladiac has joined #asahi-dev
11:10bps has joined #asahi-dev
11:23jannauwhat do you mean by latest firmware? 13.3 or 13.4? I suspect based on strings in the 13.3 kext (and on how apple advertises the feature) that 8k hdmi mode might need 2 dcp(ext)s
11:39jannauthinking of it it could be simply some cleanup of how they handle dual displays over thunderbolt and/or thunderbolt+dp-altmode
11:45jannauprobably not what I was seeing with my thunderbolt hub. 2 displays only worked when one of them was a downstream thunderbolt display. for any combination of 2 hdmi/dp/usb-c downstream displays it always used DP MST
12:08jonny1996 has joined #asahi-dev
12:33jonny1996 has quit [Ping timeout: 480 seconds]
12:55sventhat string could also “just” be a more generic multi stream display handling across multiple dcpext. That would be very weird though
12:57svenAt which layer is MST done in DP? Atcphy has some very low level PHY setting for DP but I think most of the protocol is handled inside DCP
14:43bps has quit [Ping timeout: 480 seconds]
14:49amarioguy has quit [Quit: Leaving]
15:01bps has joined #asahi-dev
15:36bgb has quit [Ping timeout: 480 seconds]
15:49bps has quit [Ping timeout: 480 seconds]
17:07derzahl has joined #asahi-dev
17:11lewurm- has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
17:11lewurm`` has joined #asahi-dev
17:37rustycrates has quit [Quit: Connection closed for inactivity]
17:49bps has joined #asahi-dev
18:07stipa has joined #asahi-dev
18:09bps has quit [Ping timeout: 480 seconds]
18:15stipa has quit [Remote host closed the connection]
18:29stipa has joined #asahi-dev
18:30brolin has joined #asahi-dev
18:38brolin has quit [Ping timeout: 480 seconds]
19:07kleist has joined #asahi-dev
19:30kleist has quit [Remote host closed the connection]
19:34brolin has joined #asahi-dev
20:02i509vcb has joined #asahi-dev
20:08mkurz has joined #asahi-dev
20:08___nick___ has quit [Ping timeout: 480 seconds]
20:29gladiac has quit [Quit: k thx bye]
21:21Deroy2112 has joined #asahi-dev
21:22Deroy2112 has quit [Remote host closed the connection]
21:50mkurz has quit [Read error: Connection reset by peer]
22:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
22:01yrlf has joined #asahi-dev