Searched refs:PPS (Results 1 – 15 of 15) sorted by relevance
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_KHR_video_decode_h265.adoc | 23 …* APIs allowing to specify H.265 video, sequence, and picture parameter sets (VPS, SPS, PPS) to be…
24 …pecific to the decoded picture, including references to previously stored VPS, SPS, and PPS entries
132 …* H.265 PPS entries are identified using a triplet of `sps_video_parameter_set_id`, `pps_seq_param…
134 …PPS key. This is needed because a PPS is not uniquely identified by its ID and the ID of the paren…
136 The H.265/HEVC video compression standard always requires a VPS, SPS, and PPS, hence the applicatio…
158 The active VPS, SPS, and PPS (sourced from the bound video session parameters object) are identifie…
278 .maxStdPPSCount = ... // PPS capacity
303 // parse and populate PPS parameters
461 === RESOLVED: How should PPS entries be identified?
463 The H.265 picture parameter set syntax only includes the PPS ID (`pps_pic_parameter_set_id`) and th…
[all …]
|
| D | VK_KHR_video_decode_h264.adoc | 23 …* APIs allowing to specify H.264 sequence and picture parameter sets (SPS, PPS) to be stored in vi…
24 …tion specific to the decoded picture, including references to previously stored SPS and PPS entries
147 …* H.264 PPS entries are identified using a pair of `seq_parameter_set_id` and `pic_parameter_set_i…
149 The H.264/AVC video compression standard always requires an SPS and PPS, hence the application has …
180 The active SPS and PPS (sourced from the bound video session parameters object) are identified by t…
312 .maxStdPPSCount = ... // PPS capacity
333 // parse and populate PPS parameters
|
| D | VK_KHR_video_queue.adoc | 257 … H.265/HEVC standards require sequence and picture parameter sets (SPS and PPS) that apply to mult…
261 …ific (e.g. in case of H.264/AVC picture parameter sets the key consists of an SPS and PPS ID pair).
|
| /hardware/google/aemu/host-common/include/host-common/ |
| D | H264NaluParser.h | 64 PPS = 8, enumerator
|
| /hardware/google/aemu/host-common/ |
| D | H264NaluParser.cpp | 108 if (currNaluType != H264NaluParser::H264NaluType::PPS) { in checkPpsFrame()
|
| D | MediaVideoToolBoxVideoHelper.cpp | 135 case H264NaluType::PPS: in decode()
295 || H264NaluType::PPS == H264NaluParser::getFrameNaluType(frame, szBytes, nullptr) in parseOneFrame()
320 if (naluType == H264NaluType::SPS || naluType == H264NaluType::PPS) { in parseOneFrame()
|
| D | MediaH264DecoderVideoToolBox.cpp | 349 if (naluType != H264NaluType::SPS && naluType != H264NaluType::PPS && in decodeFrameInternal()
371 case H264NaluType::PPS: in decodeFrameInternal()
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | video_encode_h264_extensions.adoc | 334 object supports storing H.264 SPS/PPS parameter sets that may: be later
349 * pname:maxStdPPSCount is the maximum number of PPS parameters that the
375 * pname:stdPPSCount is the number of PPS provided in pname:pStdPPSs.
381 Each element of the array must: have a unique H.264 SPS-PPS ID pair.
406 Parameters Object that is being updated, SPS-PPS IDs
409 with a particular SPS-PPS IDs cannot: be replaced nor updated
412 template, the array's parameters with the same SPS-PPS IDs as the ones
415 SPS/PPS parameters must: comply with the limits specified in
|
| D | video_decode_h264_extensions.adoc | 30 <<decode-h264-active-pps,active PPS>> specifying the <<decode-h264-pps,
321 H.264 Picture Parameter Sets (PPS)::
327 code:pic_parameter_set_id is used as the key of the PPS entry;
367 PPS>> entries the created sname:VkVideoSessionParametersKHR can:
393 <<decode-h264-pps,H.264 PPS>> entries to add.
510 <<decode-h264-pps,PPS>> identified by the key specified by the pair
|
| D | video_decode_h265_extensions.adoc | 33 <<decode-h265-active-pps,active PPS>> specifying the <<decode-h265-pps,
376 H.265 Picture Parameter Sets (PPS)::
385 as the key of the PPS entry;
430 PPS>> entries the created sname:VkVideoSessionParametersKHR can:
460 <<decode-h265-pps,H.265 PPS>> entries to add.
598 <<decode-h265-pps,PPS>> identified by the key specified by the triplet
|
| D | video_encode_h265_extensions.adoc | 474 * pname:stdPPSCount is the number of PPS elements in pname:pStdPPSs.
499 have a unique H.265 VPS-SPS-PPS ID tuple
503 Parameters Object that is being updated, VPS-SPS-PPS IDs
506 with a particular VPS-SPS-PPS IDs must: not be replaced nor updated
509 template, the array's parameters with the same VPS-SPS-PPS IDs as the
512 VPS/SPS/PPS parameters must: comply with the limits specified in
|
| D | video_extensions.adoc | 1728 <<decode-h264-pps,H.264 PPS>> entries, as follows:
1774 <<decode-h265-pps,H.265 PPS>> entries, as follows:
1848 <<decode-h264-pps,H.264 PPS>> entries to add to the created video
1894 <<decode-h265-pps,H.265 PPS>> entries to add to the created video
2069 * The <<decode-h264-pps,H.264 PPS>> entries specified in
2085 * The <<decode-h265-pps,H.265 PPS>> entries specified in
|
| /hardware/interfaces/wifi/supplicant/1.0/ |
| D | ISupplicantStaNetwork.hal | 569 * Set PPS MO ID for this network.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | glossary.adoc | 2090 PPS::
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/ |
| D | ChangeLog.adoc | 2833 should obtain the IDs indirectly from the associated PPS picture
2834 parameters based on the picture parameter and slice header PPS IDs.
|