Re: [PATCH v12 0/7] MR4449: winegstreamer: WMReader compressed output

[Yuxuan Shui (＠yshui)]

On Tue Mar 12 14:10:01 2024 +0000, Alfred Agrell wrote:
> Yes, that certainly would explain your symptoms, and why I never saw
> those issues. That's why Proton has a beta period, isn't it? Sounds like
> an easy fix, easier than comparing media types.
> Code duplication certainly has drawbacks, but I don't think we can blame
> me or WineHQ for this one; if you fork an active codebase, you get merge
> conflicts, and sometimes even behavioral conflicts like this. We can't
> let a fork constrain upstream development, can we? The safest way to
> avoid such trouble is get your code upstreamed.
> The stream order is indeed not guaranteed; as long as the input video
> bytestream is the same, I'm trusting that the stream order is also the same.
> Maybe that's naive of me, maybe it is indeed safe. I didn't check.
> I didn't mean to pass blame, so sorry if I came across as accusing. Information you provided helped me figure out the bug, so thanks again for that! And thank you for taking take to respond!

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/4449#note_64497