Please find below a brief summary of the progress Collabora have made last week on Pipewire and Weston/Wayland.
PipeWireGeorge:
- Investigated how to implement volume ramping & crossfade and helped Julian to start working on it
- Analyzed issues related to the state management of the application streams and started a discussion
upstream at https://gitlab.freedesktop.org/pipewire/pipewire/issues/205
- Started looking at simplifying some WirePlumber API to align with recent PipeWire changes
Julian:
- Finished updating wireplumber to use the new pipewire API
- Ensured wireplumber and its unit test work as expected with latest pipewire API changes
- Started implementing pipewire audio fade in/out feature using control ports on the channelmix node
Weston / Wayland
Marius:
- Conversion of navigation-demo and launcher sort-of done. All the apps have either hard-coded
width/height in QML and need to use the screen's width/height instead (as to use the
width/height from the configure event sent by the compositor). Otherwise applications will
get an invalid size from the compositor = try to commit with a surface different than that
of the buffer, will result in a protocol error. Will probably add some documentation about it.
This took a bit more than exepected on the navigation-demo due to the fact the main QML didn't have
any width/height specifying for the main application.
Launcher application uses libhomescreen and alg-service-homescreen which in turn talk to afm-main
to retrieve list of runnables. As I wasn't aware of that until recently, resorted to use my own
wrappers to chat directly with afm-main and retrieve runnables apps.
- Launching applications as agl-driver is possible using the correct
urn:AGL:permission:afm:system:widget:start in config.xml. The same as agl-service-homescreen.
- Started to look into agl-service-homescreen / libhomescreen / homescreen itself to allow binding
of the agl-shell in agl-service-homescreen, provide wrappers in libhomescreen and call it from
homescreen. Initial comments from meeting discussions result in the fact these have to be exported such that
other applications are able to call into.
As we're using wayland objects (wl_surface/wl_output) not sure at this stage if these can be "serialized"
correctly or not over the JSON proto. Boolean like of functions or functions taking strings as args
should be easy to add. I should be able to have a working PoC and determine what can be done this week.
- In the midst of cleaning up agl-compositor code for submission over gerrit.
Needs a bit of clean-up and dead-code removal.
Kind regards,
Nick
_._,_._,_
Links:
You receive all messages sent to this group.
View/Reply Online (#8022) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
_._,_._,_
