Please find below a brief summary of the progress Collabora have made last week on Pipewire and Weston/Wayland.
PipeWireGeorge:
- Continued work on simplifying some WirePlumber API to align with recent PipeWire changes
- Continued writing API documentation for the changed API
- Was watching closely Julian's work on the fade in/out feature that he is implementing on PipeWire,
providing feedback
Julian:
- Fixed audio glitches when testing fade in/out with adapter-control example
- Made the new channelmix control port configurable
- Created channelmix control port MR on pipewire master for review
Weston / Wayland
- added some additional debug information for the qtwayland panel issue to qtwayland people, but so far not
much progress on the qtwayland debugging process.
But in the same time, found a potential work-around which seems to solve the display panel issue and currently
trying to validate all other uses cases: homescreen just uses two panels, trying to make sure all of them work.
Ideally this should behave correctly on both older qtwayland version (the one found on AGL image) and newer
ones (5.12, or even 5.13). It seems that the panel initilization does not have the correct surface size (the order
seems to suggest that race in qtwayland), which results in some of the panels being incorrectly set to invalid
x and y position. Delaying the moment this happens, at commit time, would allow to retrieve the panels surface size correctly
and assign proper x and y values, which in turn results in proper display of the panel.
This could could have a side effect for normal windows, as the panel initizalition part took care of
making sure that the normal surfaces have the correct size(s) as well. Trying to valide all the use case here (all panels
being activated/set) as to make sure the solution handle correctly all cases.
- Re-worked a bit the yocto recipes as to use the testing WIP repositories of normal clients. This has been merged, as
well as the patch that switches to xdg-shell-v6, instead of ivi-shell. Once the compositor patches land as well,
people can/could try to test it using agl-compositor distro feature.
- started to do some normal builds (that is, using current homescreen/windowmanager) to figure out what else could be helpful
for the compositor/new homescreen to handle. One particular use case seems to be some kind of notitifcation from windows
not currently activated/switched to, which should deliver some message to the client shell (homescreen). I should get back to
this once I push a solution for the qtwayland issue.
Kind regards,
Nick
_._,_._,_
Links:
You receive all messages sent to this group.
View/Reply Online (#8064) |
Reply To Group
| Reply To Sender
|
Mute This Topic
| New Topic
Your Subscription |
Contact Group Owner |
Unsubscribe
[list-automotive-discussions82@xxxxxxxxxxx]
_._,_._,_
