#
✕ nick:chadmed
#asahi-dev · 2024-04-15 06:50
chadmedah yeah that makes more sense
#asahi-dev · 2024-03-30 12:59
chadmedwhile this doesnt matter for our use case since we need it to be a string anyway, it's not a very good general use API
#asahi-dev · 2024-03-30 12:58
chadmedfor some reason we can retrieve the named section as a parsed string value successfully, but trying to return it via push_luajson() causes it to misbehave
#asahi-dev · 2024-03-30 12:57
chadmedthe one thing left is wrangling the lua api: https://gitlab.freedesktop.org/chadmed/wireplumber/-/blob/sw-dsp/from-disk/modules/module-lua-scripting/api/api.c?ref_type=heads#L1640
#asahi-dev · 2024-03-30 12:56
chadmedhttps://gitlab.freedesktop.org/chadmed/wireplumber/-/tree/sw-dsp/from-disk?ref_type=heads okay this branch works
#asahi-dev · 2024-03-30 12:09
chadmedyup that was the issue
#asahi-dev · 2024-03-30 11:52
chadmedahhh section.name has to be a parsed spa-json string -.-
#asahi-dev · 2024-03-30 11:25
chadmedso we need to guard all that recursive crap underneath
#asahi-dev · 2024-03-30 11:25
chadmedthe idea is to not do that, and parse the entire file as a value with a specified key name in WpProperties
#asahi-dev · 2024-03-30 11:24
chadmedthe issue there is that without guarding behind if (as_section) it will try to parse the first token as a key then look for a value off that key
#asahi-dev · 2024-03-30 11:23
chadmedthats what i had initially without the strdup
#asahi-dev · 2024-03-30 11:16
chadmedlet me try and fix the lua side first
#asahi-dev · 2024-03-30 11:16
chadmedhmm okay
#asahi-dev · 2024-03-30 11:12
chadmedaha ive narrowed it down to the lua api
#asahi-dev · 2024-03-30 11:09
chadmedthe only issue im having now is that the parser returns an empty json object to me
#asahi-dev · 2024-03-30 11:06
chadmedthe original function also just assigns a string to section.name via wp_spa_json_parse_string(tmp)
#asahi-dev · 2024-03-30 08:37
chadmedfixed it happy days
#asahi-dev · 2024-03-30 08:32
chadmedhmph its glib clearing the pointer to the object
#asahi-dev · 2024-03-30 08:13
chadmedmixi: well thats embarrassing :p thanks
#asahi-dev · 2024-03-29 05:04
chadmedoh for fucks sake they changed the matching behaviour from AND to OR
#asahi-dev · 2024-03-29 04:26
chadmedso we're almost ready for the cutover
#asahi-dev · 2024-03-29 04:26
chadmedcurrently main is (mostly) working with wireplumber 0.5.x
#asahi-dev · 2024-03-29 04:24
chadmedso im basically just going to say no more 1.x backports after so-and-so date and time
#asahi-dev · 2024-03-29 04:24
chadmedbut obviously i cant keep doing this forever and supporting new devices across both is a PITA
#asahi-dev · 2024-03-29 04:24
chadmedcurrent plan for asahi-audio is for main to continue tracking upstream wireplumber developments and maintain a 0.4.x compat branch which will continue to be tagged out as 1.x releases
#asahi-dev · 2024-03-29 04:23
chadmednot officially supporting wireplumber 0.4.x at all after a certain point
#asahi-dev · 2024-03-29 04:09
chadmeddoes anyone have any objections if i put a hard limit on asahi-audio 1.x backports?
#asahi-dev · 2024-03-26 12:54
chadmedso i think theres some give and take here
#asahi-dev · 2024-03-26 12:54
chadmedinserting yourself as a crucial part of the linux desktop supply chain while still being officially unstable then deciding to completely and utterly break virtually every single consumer of your api between versions is not very neighbourly
#asahi-dev · 2024-03-26 12:50
chadmedlets go that works
#asahi-dev · 2024-03-26 12:47
chadmedi guess we could reapply the commit as a desperate measure?
#asahi-dev · 2024-03-26 12:40
chadmedim actually quite miffed i got as far as hiding the real node again and loading the graph before i realised the API was gone :p
#asahi-dev · 2024-03-26 12:11
chadmedporting work to 0.5 is cancelled until further notice
#asahi-dev · 2024-03-26 12:11
chadmeddbf8204cf94e2eae6eab458731e29269ec370343
#asahi-dev · 2024-03-26 11:02
chadmedwe're back to 2022 square 1...
#asahi-dev · 2024-03-26 11:02
chadmedturns out they just didnt bother to port the dsp policy to the new scheme at all so it straight up doesnt work
#asahi-dev · 2024-03-26 11:02
chadmedthis wireplumber stuff is extremely extremely extremely broken
#asahi-dev · 2024-03-25 12:17
chadmedok so we can port the custom asahi policy stuff we did for limiting the available sample rates but the DSP selection and loading stuff is still lua
#asahi-dev · 2024-03-25 11:41
chadmedoh and apparently that's the only thing thats broken with wp 0.5
#asahi-dev · 2024-03-25 11:38
chadmedffs they changed how nodes are named _again_
#asahi-dev · 2024-03-24 09:39
chadmedbut the colours are fine and frames are pushed to the plane correctly
#asahi-dev · 2024-03-24 09:39
chadmedodd issue when scaling the viewport or trying to enter fullscreen mode but unclear whether that's vlc/weston being odd or us
#asahi-dev · 2024-03-24 09:37
chadmedwell planar 420 seems to just work when done "properly" :p
#asahi-dev · 2024-03-24 08:05
chadmedunfortunately i think kwin still just doesnt support overlay planes at all except for cursor in any case, so ill have to throw weston on j314
#asahi-dev · 2024-03-24 08:04
chadmedhopefully kwin behaves the same. either way i am forcing sw cursors at the moment so it shouldnt explode _too_ hard
#asahi-dev · 2024-03-24 08:04
chadmedlast time i had a play with it weston ignored the 2 overlay planes i instantiated because they were not _CURSOR
#asahi-dev · 2024-03-24 07:56
chadmeddamage and repaint doesnt clear them
#asahi-dev · 2024-03-24 07:56
chadmedjanneg: that makes sense. i assume the persistent black panels are probably a gpu bug then
#asahi-dev · 2024-03-21 11:18
chadmedbuys a few more jbod cages for an asahi gitlab
#asahi-dev · 2024-03-21 11:07
chadmedergh ffs asahi-audio ended up in The Stack

plus ›