On Fri Sep 13 08:05:59 2024 +0000, Ziqing Hui wrote:
> Will these only be implemented on top of winedmo or the winegstreamer
> version will also migrate to it?
I'm thinking to implement these with winedmo, while keeping the redirection to the winegstreamer backend as default.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6430#note_82101
On Fri Sep 13 08:05:43 2024 +0000, Ziqing Hui wrote:
> one minor question: why this module is called wine**dmo**, from the
> above comments, it sounds more like wineffmpeg.
I found wineffmpeg to be awkward and didn't like the name, the libraries we use aren't even named ffmpeg but libavformat, libavcodec,... Then, there's an existing msdmo, and winedmo sounded nicer. DMOs (and now MFTs but only a few are pure MFTs, most are dual DMO-MFT objects) are the building blocks of all the windows multimedia components.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/6442#note_82100