Xv is not direct rendered so it's not a meaningful comparision.
The question is when it will be more like OpenGL, with separate
libXvMC and libXvMCcore. I've not really given the implementation
much thought, and I'm not convinced that the DRI example is a
correct one. To do things correctly you'd want to be able to
handle multiple heads using different drivers, which is something
I suspect the DRI OpenGL implementation cannot do.
Currently, the assumed decoder implementation is one that
links to libXvMC and dlopens the vendor-specific library like
my mpeg2play demo does. This isn't much different from how
you'd ideally want things to work, though you'd want the
dlopen part to be handled transparently by libXvMC.
Mark.
On Fri, 16 Jan 2004, Alex Deucher wrote:
> What does the future hold for XvMC? I've been playing around with the
> open source savageXvMC lib that S3/VIA released. As I understand it
> now, you have to explicitly link you application with the particular
> XvMC lib you want to use. Are there any plans to make this more like
> Xv? That way apps could just link against libXvMC.so.1 or whatever and
> be able to use whatever XvMC support is available. There are getting
> to be quite a few XvMC inplementations available. what is needed to
> move this forward?
>
> XvMC support:
> i810/15 (open source)
> savage (open source)
> via (open and closed libs)
> nvidia (closed libs)
> ati (closed libs)
>
> Alex
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus
> _______________________________________________
> Devel mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
