hakurei/internal/pipewire/client_test.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/internal/pipewire/client_test.go?h=develop2025-12-07T08:07:30Zinternal/pipewire: seq access method for consume2025-12-07T08:07:30ZOphestracat@gensokyo.uk2025-12-07T08:07:30Zurn:sha1:8cdd659239654aa2c18e392d5cde3c31da069b98
This improves readability as the offset is not immediately obvious.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: constants from pipewire/keys.h2025-12-04T18:27:30ZOphestracat@gensokyo.uk2025-12-04T18:27:22Zurn:sha1:d5509cc6e54282f048389d8dcfd731fa5a4f3b09
These are PipeWire spa_dict keys. Interestingly many keys in the sample are undefined and appear as magic strings in upstream source code.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: add json struct tags2025-11-27T16:33:32ZOphestracat@gensokyo.uk2025-11-27T16:33:32Zurn:sha1:cbe86dc4f02bc43d00fd362692a123549ad48efc
These match the names found in documentation.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: do not store spa_dict fields2025-11-27T16:25:18ZOphestracat@gensokyo.uk2025-11-27T16:25:18Zurn:sha1:d08a1081bd8131a2708f4cb934f060760371d114
This is effectively a poor man's slice, it is entirely unnecessary here and can be handled internally.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: store sample iovec continuously2025-11-27T15:35:10ZOphestracat@gensokyo.uk2025-11-27T15:34:32Zurn:sha1:72a2601d7461c0e2e24a3f97f19392dc30ee4c68
This removes the need for manual splitting. The understanding of the format is robust enough to allow this to happen anyway.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: shorten test data filenames2025-11-27T11:06:01ZOphestracat@gensokyo.uk2025-11-27T11:06:01Zurn:sha1:2bafde99e352ffec2e35a1e45aaf6c26bf864485
These were getting very annoying to type.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: additional Client::Info test case2025-11-26T07:28:57ZOphestracat@gensokyo.uk2025-11-26T07:27:46Zurn:sha1:a55c209099c96101288350043817c5dc50fdb158
This appears to add *one single entry* compared to the message before it. The inefficiency of this protocol is beyond imagination.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: additional Client::Info test case2025-11-26T07:17:38ZOphestracat@gensokyo.uk2025-11-26T07:17:38Zurn:sha1:10ff276da187868be1fa136ffd41ee2904c2cea8
This message follows the other Client::Info event before it. No idea why.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Client::Info2025-11-26T07:05:46ZOphestracat@gensokyo.uk2025-11-26T07:05:46Zurn:sha1:fd4d379b6777168c3251c85d153dbdf6b82f2b35
Everything is already supported, as usual.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Core::BoundProps2025-11-25T09:40:19ZOphestracat@gensokyo.uk2025-11-25T09:37:50Zurn:sha1:77f5b89a4180600179d4f0d1683b063b43372811
Very straightforward type, everything is already supported.
Signed-off-by: Ophestra <cat@gensokyo.uk>