mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
59750fe4c7
* Update release number to 121.
Github Issues:
* Add missing `structextends` attribute in `vk.xml` for
slink:VkPhysicalDevicePipelineExecutablePropertiesFeaturesKHR (public
issue 1018).
* Change attributes of flink:vkCmdCopyAccelerationStructureNV,
flink:vkCmdWriteAccelerationStructuresPropertiesNV,
flink:vkCmdBuildAccelerationStructureNV, and flink:vkCmdTraceRaysNV to
require that these commands execute outside renderpasses (public issue
1021).
* Add an issue to the `<<VK_EXT_buffer_device_address>>` appendix
discussing the introduction of new names and aliasing by equivalent old
names (public pull request 1024).
Internal Issues:
* Protect the `VK_KHR_sampler_mirror_clamp_to_edge` extension with
asciidoctor conditionals, and remove it from the core-only specification
builds, where it had previously been force-included in the Makefile. It
is now treated like any other extension (internal issue 1776).
* Edit some asciidoctor anchor names starting with `features-features-` to
just start with `features-`, since the old chapters was split into 3
pieces. There are still some mild naming inconsistencies with anchors
which may be addressed in the future (internal issue 1792).
* Add `KHR` alias for the non-suffixed extension token
ename:VK_SAMPLER_ADDRESS_MODE_MIRROR_CLAMP_TO_EDGE, for compatibility
with naming rules for extensions (internal issue 1796).
* Clarify requirements for external memory in NOTEs for
sname:VkExternalMemoryBufferCreateInfo, and valid usage statements for
flink:vkBindBufferMemory, slink:VkBindBufferMemoryInfo,
flink:vkBindImageMemory, and slink:VkBindImageMemoryInfo (internal merge
request 3301).
* Make extension version numbers in `vk.xml` and extension appendices
consistent. In a few cases, we could not recover history at this
granularity, and left the summary of a version's change undefined
(internal merge request 3323).
* Fix invocation of `CodeInlineMacro` in the Ruby extension backing the
`code:` macro, which was delegating to the wrong base class (internal
merge request 3331).
* Modify `reg.py` to do a better job of recognizing equivalent <enum>
definitions.
* Add a `sortorder` attribute to XML feature and extension tags.
New Extensions
* `<<VK_AMD_device_coherent_memory>>`
64 lines
2.2 KiB
Plaintext
64 lines
2.2 KiB
Plaintext
include::meta/VK_EXT_hdr_metadata.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2018-12-19
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Courtney Goeltzenleuchter, Google
|
|
|
|
This extension defines two new structures and a function to assign SMPTE
|
|
(the Society of Motion Picture and Television Engineers) 2086 metadata and
|
|
CTA (Consumer Technology Association) 861.3 metadata to a swapchain.
|
|
The metadata includes the color primaries, white point, and luminance range
|
|
of the mastering display, which all together define the color volume that
|
|
contains all the possible colors the mastering display can produce.
|
|
The mastering display is the display where creative work is done and
|
|
creative intent is established.
|
|
To preserve such creative intent as much as possible and achieve consistent
|
|
color reproduction on different viewing displays, it is useful for the
|
|
display pipeline to know the color volume of the original mastering display
|
|
where content was created or tuned.
|
|
This avoids performing unnecessary mapping of colors that are not
|
|
displayable on the original mastering display.
|
|
The metadata also includes the pname:maxContentLightLevel and
|
|
pname:maxFrameAverageLightLevel as defined by CTA 861.3.
|
|
|
|
While the general purpose of the metadata is to assist in the transformation
|
|
between different color volumes of different displays and help achieve
|
|
better color reproduction, it is not in the scope of this extension to
|
|
define how exactly the metadata should be used in such a process.
|
|
It is up to the implementation to determine how to make use of the metadata.
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_HDR_METADATA_EXT
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkXYColorEXT
|
|
* slink:VkHdrMetadataEXT
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkSetHdrMetadataEXT
|
|
|
|
=== Issues
|
|
|
|
1) Do we need a query function?
|
|
|
|
*PROPOSED*: No, Vulkan does not provide queries for state that the
|
|
application can track on its own.
|
|
|
|
2) Should we specify default if not specified by the application?
|
|
|
|
*PROPOSED*: No, that leaves the default up to the display.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-12-27 (Courtney Goeltzenleuchter)
|
|
- Initial version
|
|
* Revision 2, 2018-12-19 (Courtney Goeltzenleuchter)
|
|
- Correct implicit validity for VkHdrMetadataEXT structure
|