it's much much simpler to have a single executable to run to cover as much surface as possible, rather than having to list every possible module out there.
OK, that's a good point. I'll close this MR and raise a new one to put these tests under `mf/tests`.
I feel that because they are from the same era it might be easier to go this way rather than through MF?
I already have POC working with MF; it's not too bad, apart from the memory copies.
It depends on how much data copy we mean.
Unfortunately it is the entire RGB frame; and twice. Once on the way in and once on the way out. I could always write a `IMFMediaBuffer` wrapper instead. I will have to do that for `IMediaBuffer` if I use `IMediaObject` anyway. But do you think option 1. or 3. is better? If your changes will be in soon, then I guess it's not worth implementing that interface in winegstreamer. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10709#note_137301