From Fedora Project Wiki
(Initial feature)
 
No edit summary
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
<!-- Self Contained or System Wide Change Proposal?
Use this guide to determine to which category your proposed change belongs to.
Self Contained Changes are:
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
* limited scope changes without the impact on other packages/rest of the distribution
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
System Wide Changes are:
* changes that does not fit Self Contained Changes category touching
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
* changing system defaults
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
-->
= VA-API 1.0.0 =
= VA-API 1.0.0 =


== Summary ==
== Summary ==
This change is about upgrading {{package|libva}} and others to version 2.0. This change affects several video players as there are both API and ABI changes.
This change is about upgrading {{package|libva}} and others to version 2.x. This change affects several multimedia players as there are both API and ABI changes.
This will allow some VA-API backends to be updated, improving support for recent hardware.
This will allow some VA-API backends to be updated, improving support for recent hardware.


== Owner ==
== Owner ==
* Name: [[User:kwizart| Nicolas Chauvet]]
* Name: [[User:kwizart| Nicolas Chauvet]]
* Email: kwizart@fedoraproject.org
* Email: kwizart - at - fedoraproject.org
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/113 #113]
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
-->
* Product: Workstation
* Product: Spins / Workstation
* Responsible WG:
* Responsible WG: Desktop


== Current status ==
== Current status ==
Line 48: Line 26:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1547062 #1547062]


== Detailed Description ==
== Detailed Description ==


<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Updating to VA-API 1.0.0 will allow to fix and clean-up issues with the API as sum-up in this upstream topic [https://github.com/intel/libva/issues/72 VA-API 1.0.0]:
 
*  fix errors in API/data structure definition, e.g. [https://github.com/intel/libva/issues/32 01org#32]
*  add new features, e.g. [https://github.com/intel/libva/issues/69 01org#69],
*  deprecate some useless API/data structures, e.g. libva-tpi, libva-egl.
* provide other improvement, e.g. use portable type to define data structure.
 
All packages using {{package|libva}} will be rebuilt to take into account the new API/ABI. Futhermore, the intel backend will be updated along (not provided by Fedora).
Others VA-API backend such the AMD and NVIDIA backend provided by Fedora within {{package|mesa-dri-drivers}} will work as appropriate.
Bridges between VA-API and VDPAU will continue to be supported , this is:
* {{package|libva-vdpau-driver}} which allows to use the VA-API enabled players with VDPAU backend (such as NVIDIA binary driver).
* {{package|libvdpau-va-gl}} which allows to use the VDPAU API enabled players with VA-API backends (such as intel driver).


== Benefit to Fedora ==
== Benefit to Fedora ==


Fedora will provide a better multimedia experience on recent hardware.
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->


== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
Update and rebuild packages that depend on {{package|libva}}. DONE


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Verify that everything is working as appropriate or report issue upstream. TESTING IN PROGRESS.
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Other developers: N/A
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/7285 #7285]
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


* Trademark approval: N/A (not needed for this Change)
* List of deliverables: N/A
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
 
* Policies and guidelines: N/A
 
* Trademark approval: N/A


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
Users should update to the more recent version provided in repositories.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.  
* Hardware that are fully supported in Fedora:
AMD with {{package|mesa-dri-drivers}} installed
* Hardware that are fully supported in Fedora, but requires additional firmware
NVIDIA with {{package|mesa-dri-drivers}} installed and nouveau video firmware extracted from the NVIDIA binary driver.
* Hardware that requires package provided by third party repository.
Intel HD graphics hardwares require a separate libva-intel-driver package that need to be installed. This VA-API backend can be downloaded from a single purpose f28-free-drivers repository provided by the RPM Fusion project.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
* vainfo should output the VA-API backend capabilities for your hardware


A good "how to test" should answer these four questions:
* totem with {{package|gstreamer1-vaapi}} installed should play the video with less CPU usage than when VAAPI backend is disabled.
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Users use less CPU resources when playing certain videos with VA-API enabled players.
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
N/A
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Contingency Plan ==
== Contingency Plan ==
 
* If a Fedora application trigger any un-acceptable  regression with VA-API, this application will be built with VA-API support disabled until the VA-API support can be restored.
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
* Contingency mechanism:  
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: N/A (not a System Wide Change)
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Blocks release? N/A  
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? None
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* https://github.com/intel/libva/issues/72
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
Line 137: Line 101:
-->
-->


[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF28]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 143: Line 107:
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->


<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SelfContainedChange]]
<!-- [[Category:SystemWideChange]] -->

Latest revision as of 15:08, 2 March 2018

VA-API 1.0.0

Summary

This change is about upgrading Package-x-generic-16.pnglibva and others to version 2.x. This change affects several multimedia players as there are both API and ABI changes. This will allow some VA-API backends to be updated, improving support for recent hardware.

Owner

  • Name: Nicolas Chauvet
  • Email: kwizart - at - fedoraproject.org
  • Release notes ticket: #113
  • Product: Spins / Workstation
  • Responsible WG: Desktop

Current status

Detailed Description

Updating to VA-API 1.0.0 will allow to fix and clean-up issues with the API as sum-up in this upstream topic VA-API 1.0.0:

  • fix errors in API/data structure definition, e.g. 01org#32
  • add new features, e.g. 01org#69,
  • deprecate some useless API/data structures, e.g. libva-tpi, libva-egl.
  • provide other improvement, e.g. use portable type to define data structure.

All packages using Package-x-generic-16.pnglibva will be rebuilt to take into account the new API/ABI. Futhermore, the intel backend will be updated along (not provided by Fedora). Others VA-API backend such the AMD and NVIDIA backend provided by Fedora within Package-x-generic-16.pngmesa-dri-drivers will work as appropriate. Bridges between VA-API and VDPAU will continue to be supported , this is:

  • Package-x-generic-16.pnglibva-vdpau-driver which allows to use the VA-API enabled players with VDPAU backend (such as NVIDIA binary driver).
  • Package-x-generic-16.pnglibvdpau-va-gl which allows to use the VDPAU API enabled players with VA-API backends (such as intel driver).

Benefit to Fedora

Fedora will provide a better multimedia experience on recent hardware.

Scope

  • Proposal owners:

Update and rebuild packages that depend on Package-x-generic-16.pnglibva. DONE

Verify that everything is working as appropriate or report issue upstream. TESTING IN PROGRESS.

  • Other developers: N/A
  • Release engineering: #7285
  • List of deliverables: N/A
  • Policies and guidelines: N/A
  • Trademark approval: N/A

Upgrade/compatibility impact

Users should update to the more recent version provided in repositories.

How To Test

  • Hardware that are fully supported in Fedora:

AMD with Package-x-generic-16.pngmesa-dri-drivers installed

  • Hardware that are fully supported in Fedora, but requires additional firmware

NVIDIA with Package-x-generic-16.pngmesa-dri-drivers installed and nouveau video firmware extracted from the NVIDIA binary driver.

  • Hardware that requires package provided by third party repository.

Intel HD graphics hardwares require a separate libva-intel-driver package that need to be installed. This VA-API backend can be downloaded from a single purpose f28-free-drivers repository provided by the RPM Fusion project.

  • vainfo should output the VA-API backend capabilities for your hardware
  • totem with Package-x-generic-16.pnggstreamer1-vaapi installed should play the video with less CPU usage than when VAAPI backend is disabled.

User Experience

Users use less CPU resources when playing certain videos with VA-API enabled players.

Dependencies

N/A

Contingency Plan

  • If a Fedora application trigger any un-acceptable regression with VA-API, this application will be built with VA-API support disabled until the VA-API support can be restored.
  • Contingency mechanism:
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A
  • Blocks product? None

Documentation

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/VA-API_1.0.0&oldid=512021"