https://bugs.winehq.org/show_bug.cgi?id=38278
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- Inasmuch as this is a wmvcore metabug:
I've been thinking briefly about this, and I think there are two interesting options for implementing wmvcore:
* Build it on top of mfplat. This seems to be a relatively good fit, but the mfplat API is ugly.
* Built it directly on top of the winegstreamer API (i.e. wg_*). The API there is better designed (or at least malleable) and could easily be exported. Inasmuch as it's relatively similar to mfplat, it'd be a good fit for wmvcore as well. On the other hand, introducing another internal API surface may not be warmly received.
I think we want to do one of these, though. We probably don't want to use quartz, not just because the quartz API is ugly and an uglier fit for wmvcore, but also because the quartz asfreader is internally supposed to use wmvcore. And of course we don't want to duplicate the GStreamer backend yet again.