Alexandros Frantzis (@afrantzis) commented about dlls/winewayland.drv/wayland_pointer.c:
> process_wayland.zwp_relative_pointer_manager_v1,
> pointer->wl_pointer);
> zwp_relative_pointer_v1_add_listener(pointer->zwp_relative_pointer_v1,
> - &relative_pointer_v1_listener, NULL);
> + &relative_pointer_v1_listener, &accum);
Let's place the accumulated x and y values in wayland_pointer, since it's really a per-pointer state (currently per-process since we have a single pointer).
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7806#note_101263
On Thu Apr 17 07:54:50 2025 +0000, Rémi Bernon wrote:
> Have you tried GstVideoTimeCodeMeta / do you know what it does?
No, I didn't look at that. But taking a look now, it looks like it might be good for Video PTS/DTS, but wouldn't work for audio. I'm not sure for duration either.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7623#note_101244
On Wed Apr 16 08:20:27 2025 +0000, Brendan McGrath wrote:
> Oops (again). I just tried using the `preserve_timestamps` boolean and
> it doesn't work. The `timestamp/x-wg-transform` is a flag that lets
> `video_decoder.c` know that an input timestamp has been provided (and
> that it should use it). It will otherwise fall back to the behavior
> defined by `provide_timestamps`.
> But if we want to get rid of the need for the GUID, I guess we could
> move the existing logic in `video_decoder.c` (for generating our own
> timestamp) in to `wg_transform.c`.
Hmm, I'm not sure that moving timestamp generation to the unix side is better. Can't we simply fill the sample timestamps from the input provided timestamps instead of the GStreamer-generated timestamps we don't really care about?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7623#note_101242