On Mon Sep 25 12:50:03 2023 +0000, Alfred Agrell wrote:
changed this line in [version 2 of the diff](/wine/wine/-/merge_requests/3938/diffs?diff_id=71612&start_sha=bd76cbe404176a0a952c424ad5fa7c46e052c28d#1db08ec81aafecfe3bd575cfcd57f9db6a4bfb1b_243_243)
I'm not sure, but I think maybe it could handle the format change from the caller side? Calling `wg_transform_set_output_format` with the new format if the change is no-op from the quartz PoV?
For reference, I've stripped the default values for these properties on input, in 59dedf2754650bd84ffa7d10c94f83b97198fed2, to let decoders decide what their values should be and avoid forcing a colorspace conversion in videoconvert.
Then we might be interested to expose them to the client side at some point, MF has some attributes to represent colorimetry information, but I don't know if AM_MEDIA_TYPE has something for it as well.