On 15 October 2013 21:52, Michael Müller michael@fds-team.de wrote:
The most similar way to Windows would be to completely rewrite the current implementation of the VMR9 as VMR7 using DirectDraw, which would take a lot of time and most probably end up in having a lot of duplicate code. I am wondering whether using d3d9 for VMR7 would also be an acceptable solution. We could move all the d3d9 related stuff to a separate file so that VMR7.c and VMR9.c only offer the version specific interfaces and use the same code internally. This shouldn't be a big problem since the differences between the VMR7 and VMR9 interfaces are often only very small. Though it would not completely fit the behavior of windows.
I'm not very familiar with quartz / VMR, but I guess the main question would be how applications can tell the difference between a d3d9 and a ddraw implementation. On the other hand, the amount of d3d9 specific code in vmr9.c looks pretty manageable at first sight.