How will applications determine whether VDPAU will work on their display 
or not?

Are there any plans for integrating this with any actual applications, 
or with gstreamer or other desktop video apps?

    -- Garrett

John Fischer wrote:
> Template Version: @(#)sac_nextcase %I% %G% SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        Video Decode and Presentation API for Unix (VDPAU)
>     1.2. Name of Document Author/Supplier:
>        Author:  John Martin
>     1.3  Date of This Document:
>       29 January, 2009
> 4. Technical Description
> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        Video Decode and Presentation API for Unix (VDPAU)
>     1.2. Name of Document Author/Supplier:
>        Author:  John Martin 
>     1.3  Date of This Document:
>       29 January, 2009
> 4. Technical Description
>
>    The Video Decode and Presentation API for Unix (VDPAU) is a development
>    and runtime environment which provides decode, post-processing, 
> compositing,
>    and display of compressed and uncompressed video streams.  It is not a
>    standalone video player but instead an environment which can be used
>    by video players and other video applications.  It also does not address
>    content protection.
>
>    The VDPAU API is initially defined and implemented by NVIDIA.
>    The implementation of libvdpau.so is a DSO frontend that can load
>    any vendor's backend driver.  libvdpau.so will be open sourced
>    with a MIT-X11 license and hosted by X.Org.
>
>    As of this writing, the VDPAU API provides the following features:
>      + GPU-accelerated decode of MPEG-1, MPEG-2, H.264, WMV-3 and VC-1
>        bitstreams
>      + Post-processing of decoded video, including temporal and
>        spatial deinterlacing, inverse telecine, and noise reduction
>      + Timestamp-based presentation of final video frames
>      + Compositing sub-picture, on-screen display, and other UI elements
>
>    It is important to note this is limited to GPU accelerated so
>    support depends on the hardware.  There is not a software fallback
>    path in VDPAU if the hardware does not support these features.
>    Also, even though VDPAU provides a large subset of the PureVideo HD
>    functionality delivered on Windows, there is no guarantee all
>    PureVideo features are (or will be) delivered on Solaris.
>
>    While the API will be classified as volatile for this document,
>    the plan is to maintain backward compatibility in future releases. 
>
>    Delivery will be in the existing SYSV package NVDAgraphics which
>    installs files in the following directories:
>
>       /usr/include/vdpau: VDPAU headers
>       /usr/lib:           VDPAU 32-bit libraries 
>       /usr/lib/amd64:     VDPAU 64-bit libraries 
>
>    The main web page for VDPAU is: 
>       http://http.download.nvidia.com/XFree86/vdpau/doxygen/html/index.html
>    This includes documentation for the API. Documentation is not part
>    of the package delivery for Solaris.
>
>    Support for VDPAU is provided by NVIDIA through their developer forum.
>
>    Bugtraq: nvidia/nvidia/other
>
> Interfaces Exported
> Interface                      Classification   Comments
> -----------------------------------------------------------------
> /usr/include/vdpau/vdpau.h     Volatile         Defined by NVIDIA
> /usr/include/vdpau/vdpau_x11.h Volatile         Defined by NVIDIA
> /usr/lib/libvdpau.so.1         Volatile         Defined by NVIDIA
> /usr/lib/libvdpau.so           Volatile         Defined by NVIDIA
> /usr/lib/amd64/libvdpau.so.1   Volatile         Defined by NVIDIA
> /usr/lib/amd64/libvdpau.so     Volatile         Defined by NVIDIA
>
> The libraries /usr/lib[/amd64]/libvdpau_nvidia.so.1 and
> /usr/lib[/amd64]/libvdpau_trace.so.1 are private objects
> and should not be linked in for normal application development. 
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               X
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               JDS - X
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>
>   


Reply via email to