The present disclosure relates to image and video coding and decoding.
Digital video accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.
The present disclosure discloses techniques for the signaling of general constraint information (GCI) that can be used by video encoders and decoders to perform video encoding, decoding, or processing.
In one example aspect, a video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a syntax structure in a profile-tier-level syntax structure is after a syntax element, wherein the syntax structure comprises information related to general constraint information (GCI) for the bitstream, and wherein the syntax element indicates a level to which an output layer set associated with the profile-tier-level syntax structure conforms.
In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a byte alignment syntax in a general constraint information (GCI) syntax structure is after one or more GCI reserved fields, wherein the byte alignment syntax indicates whether a current position in the bitstream is an integer multiple of 8 bits from a position of a first bit in the bitstream, and wherein the GCI syntax structure comprises GCI related syntax elements.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a syntax structure in a profile-tier-level syntax structure is after an indication of level information, wherein the syntax structure comprises information related to general constraint information (GCI), and wherein the indication of level information specifies an interoperability indicator.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein rule specifies that a syntax element in a profile-tier-level syntax structure indicates whether a general constraint information (GCI) syntax structure is included in the profile-tier-level syntax structure.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a byte alignment syntax is excluded from a general constraint information (GCI) syntax structure that is present in the profile-tier-level syntax structure, wherein the byte alignment syntax indicates whether a current position in the bitstream is an integer multiple of 8 bits from a position of a first bit in the bitstream, and wherein the GCI syntax structure comprises a GCI related syntax element.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a general constraint information (GCI) syntax structure is immediately before a byte alignment checking condition in a profile-tier-level syntax structure, wherein the GCI syntax structure comprises GCI related syntax elements, and wherein the byte alignment checking condition checks whether a current position in the bitstream is an integer multiple of 8 bits from a position of a first bit in the bitstream.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a number of a plurality of reserved constraint bits associated with a general constraint information (GCI) syntax element is included in the bitstream.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies that a general constraint information (GCI) syntax element is included at a beginning of a GCI syntax structure, wherein the GCI syntax element indicates whether one or more GCI syntax elements are included in the GCI syntax structure.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies a constraint on a syntax element, wherein the syntax element corresponds to a bit depth used for representing the video in the bitstream.
In yet another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more pictures and a bitstream of the video according to a rule, wherein the rule specifies a constraint on a syntax element, wherein the syntax element corresponds to a chroma format of the video.
In yet another example aspect, a video encoder apparatus is disclosed. The video encoder comprises a processor configured to implement above-described methods.
In yet another example aspect, a video decoder apparatus is disclosed. The video decoder comprises a processor configured to implement above-described methods.
In yet another example aspect, a computer readable medium having code stored thereon is disclose. The code embodies one of the methods described herein in the form of processor-executable code.
These, and other, features are described throughout the present disclosure.
Section headings are used in the present disclosure for ease of understanding and do not limit the applicability of techniques and embodiments disclosed in each section only to that section. Furthermore, H.266 terminology is used in some description only for ease of understanding and not for limiting scope of the disclosed techniques. As such, the techniques described herein are applicable to other video codec protocols and designs also.
This disclosure is related to video coding technologies. Specifically, it is about syntax designs for signaling of general constraints information (GCI) in video coding. The ideas may be applied individually or in various combination, to any video coding standard or non-standard video codec that supports multi-layer video coding, e.g., the being-developed Versatile Video Coding (VVC).
Video coding standards have evolved primarily through the development of the well-known International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) and International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) standards. The ITU-T produced H.261 and H.263, ISO/IEC produced Moving Picture Experts Group (MPEG)-1 and MPEG-4 Visual, and the two organizations jointly produced the H.262/MPEG-2 Video and H.264/MPEG-4 Advanced Video Coding (AVC) and H.265/HEVC standards. Since H.262, the video coding standards are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized. To explore the future video coding technologies beyond HEVC, the Joint Video Exploration Team (JVET) was founded by Video Coding Experts Group (VCEG) and MPEG jointly in 2015. Since then, many new methods have been adopted by JVET and put into the reference software named Joint Exploration Model (JEM). The JVET meeting is concurrently held once every quarter, and the new coding standard is targeting at 50% bitrate reduction as compared to HEVC. The new video coding standard was officially named as Versatile Video Coding (VVC) in the April 2018 JVET meeting, and the first version of VVC test model (VTM) was released at that time. As there are continuous effort contributing to VVC standardization, new coding techniques are being adopted to the VVC standard in every JVET meeting. The VVC working draft and test model VTM are then updated after every meeting. The VVC project is now aiming for technical completion (FDIS) at the July 2020 meeting.
In AVC and HEVC, the spatial resolution of pictures cannot change unless a new sequence using a new SPS starts, with an IRAP picture. VVC enables picture resolution change within a sequence at a position without encoding an IRAP picture, which is always intra-coded. This feature is sometimes referred to as reference picture resampling (RPR), as the feature needs resampling of a reference picture used for inter prediction when that reference picture has a different resolution than the current picture being decoded.
The scaling ratio is restricted to be larger than or equal to 1/2 (2 times downsampling from the reference picture to the current picture), and less than or equal to 8 (8 times upsampling). Three sets of resampling filters with different frequency cutoffs are specified to handle various scaling ratios between a reference picture and the current picture. The three sets of resampling filters are applied respectively for the scaling ratio ranging from 1/2 to 1/1.75, from 1/1.75 to 1/1.25, and from 1/1.25 to 8. Each set of resampling filters has 16 phases for luma and 32 phases for chroma which is same to the case of motion compensation interpolation filters. Actually the normal motion compensation (MC) interpolation process is a special case of the resampling process with scaling ratio ranging from 1/1.25 to 8. The horizontal and vertical scaling ratios are derived based on picture width and height, and the left, right, top and bottom scaling offsets specified for the reference picture and the current picture.
Other aspects of the VVC design for support of this feature that are different from HEVC include: i) The picture resolution and the corresponding conformance window are signaled in the PPS instead of in the SPS, while in the SPS the maximum picture resolution is signaled. ii) For a single-layer bitstream, each picture store (a slot in the DPB for storage of one decoded picture) occupies the buffer size as required for storing a decoded picture having the maximum picture resolution.
Scalable video coding (SVC, sometimes also just referred to as scalability in video coding) refers to video coding in which a base layer (BL), sometimes referred to as a reference layer (RL), and one or more scalable enhancement layers (ELs) are used. In SVC, the base layer can carry video data with a base level of quality. The one or more enhancement layers can carry additional video data to support, for example, higher spatial, temporal, and/or signal-to-noise (SNR) levels. Enhancement layers may be defined relative to a previously encoded layer. For example, a bottom layer may serve as a BL, while a top layer may serve as an EL. Middle layers may serve as either ELs or RLs, or both. For example, a middle layer (e.g., a layer that is neither the lowest layer nor the highest layer) may be an EL for the layers below the middle layer, such as the base layer or any intervening enhancement layers, and at the same time serve as a RL for one or more enhancement layers above the middle layer. Similarly, in the Multiview or three dimensional (3D) extension of the HEVC standard, there may be multiple views, and information of one view may be utilized to code (e.g., encode or decode) the information of another view (e.g., motion estimation, motion vector prediction and/or other redundancies).
In SVC, the parameters used by the encoder or the decoder are grouped into parameter sets based on the coding level (e.g., video-level, sequence-level, picture-level, slice level, etc.) in which they may be utilized. For example, parameters that may be utilized by one or more coded video sequences of different layers in the bitstream may be included in a video parameter set (VPS), and parameters that are utilized by one or more pictures in a coded video sequence may be included in a sequence parameter set (SPS). Similarly, parameters that are utilized by one or more slices in a picture may be included in a picture parameter set (PPS), and other parameters that are specific to a single slice may be included in a slice header. Similarly, the indication of which parameter set(s) a particular layer is using at a given time may be provided at various coding levels.
Thanks to the support of reference picture resampling (RPR) in VVC, support of a bitstream containing multiple layers, e.g., two layers with standard definition (SD) and high definition (HD) resolutions in VVC can be designed without the need any additional signal-processing-level coding tool, as upsampling needed for spatial scalability support can just use the RPR upsampling filter. Nevertheless, high-level syntax changes (compared to not supporting scalability) are needed for scalability support. Scalability support is specified in VVC version 1. Different from the scalability supports in any earlier video coding standards, including in extensions of AVC and HEVC, the design of VVC scalability has been made friendly to single-layer decoder designs as much as possible. The decoding capability for multi-layer bitstreams are specified in a manner as if there were only a single layer in the bitstream. E.g., the decoding capability, such as DPB size, is specified in a manner that is independent of the number of layers in the bitstream to be decoded. Basically, a decoder designed for single-layer bitstreams does not need much change to be able to decode multi-layer bitstreams. Compared to the designs of multi-layer extensions of AVC and HEVC, the high level syntax (HLS) aspects have been significantly simplified at the sacrifice of some flexibilities. For example, an IRAP AU is required to contain a picture for each of the layers present in the CVS.
AVC, HEVC, and VVC specify parameter sets. The types of parameter sets include SPS, PPS, APS, and VPS. SPS and PPS are supported in all of AVC, HEVC, and VVC. VPS was introduced since HEVC and is included in both HEVC and VVC. APS was not included in AVC or HEVC but is included in the latest VVC draft text.
SPS was designed to carry sequence-level header information, and PPS was designed to carry infrequently changing picture-level header information. With SPS and PPS, infrequently changing information need not to be repeated for each sequence or picture, hence redundant signaling of this information can be avoided. Furthermore, the use of SPS and PPS enables out-of-band transmission of the important header information, thus not only avoiding the need for redundant transmissions but also improving error resilience.
VPS was introduced for carrying sequence-level header information that is common for all layers in multi-layer bitstreams.
APS was introduced for carrying such picture-level or slice-level information that needs quite some bits to code, can be shared by multiple pictures, and in a sequence there can be quite many different variations.
In the latest VVC draft text, the general profile, tier, level syntax and semantics are as follows:
general_profile_idc
general_tier_flag
general_level_idc
ptl_num_sub_profiles
general_sub_profile_idc[ i ]
ptl_sublayer_level_present_flag[ i ]
ptl_alignment_zero_bit
sublayer_level_idc[ i ]
A profile_tier_level( ) syntax structure provides level information and, optionally, profile, tier, sub-profile, and general constraints information.
When the profile_tier_level( ) syntax structure is included in a VPS, the OlsInScope is one or more OLSs specified by the VPS. When the profile_tier_level( ) syntax structure is included in an SPS, the OlsInScope is the OLS that includes only the layer that is the lowest layer among the layers that refer to the SPS, and this lowest layer is an independent layer.
general_profile_idc indicates a profile to which OlsInScope conforms as specified in Annex A. Bitstreams shall not contain values of general_profile_idc other than those specified in Annex A. Other values of general_profile_idc are reserved for future use by ITU-T|ISO/IEC.
general_tier_flag specifies the tier context for the interpretation of general_level_idc as specified in Annex A.
general_level_idc indicates a level to which OlsInScope conforms as specified in Annex A. Bitstreams shall not contain values of general_level_idc other than those specified in Annex A. Other values of general_level_idc are reserved for future use by ITU-T|ISO/IEC.
general_non_packed_constraint_flag
general_frame_only_constraint_flag
general_non_projected_constraint_flag
general_one_picture_only_constraint_flag
intra_only_constraint_flag
max_bitdepth_minus8_constraint_idc
max_chroma_format_constraint_idc
single_layer_constraint_flag
all_layers_independent_constraint_flag
no_ref_pic_resampling_constraint_flag
no_res_change_in_clvs_constraint_flag
one_tile_per_pic_constraint_flag
pic_header_in_slice_header_
one_slice_per_pic_constraint_flag
one_subpic_per_pic_constraint_flag
no_qtbtt_dual_tree_intra_constraint_flag
no_partition_constraints_override_
no_sao_constraint_flag
no_alf_constraint_flag
no_ccalf_constraint_flag
no_joint_cbcr_constraint_flag
no_mrl_constraint_flag
no_isp_constraint_flag
no_mip_constraint_flag
no_ref_wraparound_constraint_flag
no_temporal_mvp_constraint_flag
no_sbtmvp_constraint_flag
no_amvr_constraint_flag
no_bdof_constraint_flag
no_dmvr_constraint_flag
no_cclm_constraint_flag
no_mts_constraint_flag
no_sbt_constraint_flag
no_lfnst_constraint_flag
no_affine_motion_constraint_flag
no_mmvd_constraint_flag
no_smvd_constraint_flag
no_prof_constraint_flag
no_bcw_constraint_flag
no_ibc_constraint_flag
no_ciip_constraint_flag
no_gpm_constraint_flag
no_ladf_constraint_flag
no_transform_skip_constraint_flag
no_bdpcm_constraint_flag
no_weighted_prediction_constraint_flag
no_palette_constraint_flag
no_act_constraint_flag
no_lmcs_constraint_flag
no_cu_qp_delta_constraint_flag
no_chroma_qp_offset_constraint_flag
no_dep_quant_constraint_flag
no_sign_data_hiding_constraint_flag
no_mixed_nalu_types_in_pic_
no_trail_constraint_flag
no_stsa_constraint_flag
no_rasl_constraint_flag
no_radl_constraint_flag
no_idr_constraint_flag
no_cra_constraint_flag
no_gdr_constraint_flag
no_aps_constraint_flag
gci_alignment_zero_bit
gci_num_reserved_bytes
general_non_packed_constraint_flag equal to 1 specifies that there shall not be any frame packing arrangement SEI messages present in the bitstream of the OlsInScope. general_non_packed_constraint_flag equal to 0 does not impose such a constraint.
JVET-S0050 and JVET-S0127 both proposes to add a presence flag, in the PTL syntax structure, to specifies the presence of the GCI syntax structure in the in the PTL syntax structure, with the only difference being that the following is done in S0050 and not done in S0127: S0050 adds byte alignment in the PTL syntax structure immediately after the GCI syntax structure, when present, to make sure that general_level_idc starts at a byte-aligned position in the PTL syntax structure, and consequently removed the byte alignment inside the GCI syntax structure. The JVET-S0050 syntax changes are as follows, wherein parts that have been added or modified are bolded, underlined and italicized, e.g., “using A ”, and some of the deleted parts are italicized with strikethrough, e.g., “based on A and B”.
gci_present_flag
u(1)
if( gci_present_flag )
while( !byte_aligned( ) )
ptl_alignment_zero_bit
f(1)
The JVET-S0127 syntax changes are as follows:
general_constraint_info_present_flag
u(1)
if( general_constraint_
info_present_flag )
JVET-S0092 only changes the GCI syntax structure itself. It moves the GCI extension length indicator (gci_num_reserved_bytes) from last to first (gci_num_constraint_bytes) in the GCI syntax structure to enable skip signaling of the GCI fields. The value of gci_num_reserved_bytes shall be equal to either 0 or 9.
The S0092 syntax changes are as follows:
gci_num_constraint_bytes
u(8)
if( gci_num_constraint_bytes > 8 )
{
}
Here are some comparisons regarding the different approaches:
The existing designs for signaling of the CGI fields need to spend more bits than needed.
To solve the above problems and some other problems not mentioned, methods as summarized below are disclosed. The items should be considered as examples to explain the general concepts and should not be interpreted in a narrow way. Furthermore, these items can be applied individually or combined in any manner.
Below are some example embodiments for some of the aspects summarized above in this Section, which can be applied to the VVC specification. The changed texts are based on the latest VVC text in JVET-S0152-v3. Most relevant parts that have been added or modified are bolded, underlined and italicized, e.g., “using A ”, and some of the deleted parts are italicized with strikethrough, e.g., “based on A and B”.
This embodiment is for item 1 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
gci_present_flag
u(1)
if( gci_present_flag )
general_constraint_info( )
And the semantics are changed as follows:
The syntax structure general_constraint_info( ) is changed as follows:
And the semantics are changed as follows:
gci_num_reserved_b specifies the number of the reserved constraint b. The value of gci_num_reserved_b shall be 0. Other values of gci_num_reserved_b are reserved for future use by ITU-T|ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification.
gci_reserved_b[i] may have any value. Its presence and value do not affect decoder conformance to profiles specified in this version of this Specification. Decoders conforming to this version of this Specification shall ignore the values of all the gci_reserved_b[i] syntax elements.
This embodiment is for item 2 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
And the semantics are changed as follows:
This embodiment is for item 3 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
And the semantics are changed as follows:
In one example, alternatively, furthermore, the syntax structure general_constraint_info( ) is changed as follows:
And the semantics are changed as follows:
gci_num_reserved_b specifies the number of the reserved constraint b. The value of gci_num_reserved_b shall be 0. Other values of gci_num_reserved_b are reserved for future use by ITU-T|ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification.
gci_reserved_b[i] may have any value. Its presence and value do not affect decoder conformance to profiles specified in this version of this Specification. Decoders conforming to this version of this Specification shall ignore the values of all the gci_reserved_b[i] syntax elements.
This embodiment is for item 4 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
general_profile_idc
general_tier_flag
u(1)
And the semantics are changed as follows:
This embodiment is for item 5 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
The syntax structure general_constraint_info( ) is changed as follows:
u(1)
general_non_packed_constraint_flag
general_frame_only_constraint_flag
general_non_projected_constraint_flag
general_one_picture_only_
constraint_flag
intra_only_constraint_flag
max_bitdepth_minus8_constraint_idc
max_chroma_format_constraint_idc
single_layer_constraint_flag
all_layers_independent_constraint_flag
no_ref_pic_resampling_constraint_flag
no_res_change_in_clvs_constraint_flag
one_tile_per_pic_constraint_flag
pic_header_in_slice_header_
constraint_flag
one_slice_per_pic_constraint_flag
one_subpic_per_pic_constraint_flag
no_qtbtt_dual_tree_intra_
constraint_flag
no_partition_constraints_
override_constraint_flag
no_sao_constraint_flag
no_alf_constraint_flag
no_ccalf_constraint_flag
no_joint_cbcr_constraint_flag
no_mrl_constraint_flag
no_isp_constraint_flag
no_mip_constraint_flag
no_ref_wraparound_constraint_flag
no_temporal_mvp_constraint_flag
no_sbtmvp_constraint_flag
no_amvr_constraint_flag
no_bdof_constraint_flag
no_dmvr_constraint_flag
no_cclm_constraint_flag
no_mts_constraint_flag
no_sbt_constraint_flag
no_lfnst_constraint_flag
no_affine_motion_constraint_flag
no_mmvd_constraint_flag
no_smvd_constraint_flag
no_prof_constraint_flag
no_bcw_constraint_flag
no_ibc_constraint_flag
no_ciip_constraint_flag
no_gpm_constraint_flag
no_ladf_constraint_flag
no_transform_skip_constraint_flag
no_bdpcm_constraint_flag
no_weighted_pred_constraint_flag
no_palette_constraint_flag
no_act_constraint_flag
no_lmcs_constraint_flag
no_cu_qp_delta_constraint_flag
no_chroma_qp_offset_constraint_flag
no_dep_quant_constraint_flag
no_sign_data_hiding_constraint_flag
no_mixed_nalu_types_
in_pic_constraint_flag
no_trail_constraint_flag
no_stsa_constraint_flag
no_rasl_constraint_flag
no_radl_constraint_flag
no_idr_constraint_flag
no_cra_constraint_flag
no_gdr_constraint_flag
no_aps_constraint_flag
f(1)
And the semantics are changed as follows:
gci_num_reserved_b specifies the number of the reserved constraint b. The value of gci_num_reserved_b shall be 0. Other values of gci_num_reserved_b are reserved for future use by ITU-T|ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification.
gci_reserved_b[i] may have any value. Its presence and value do not affect decoder conformance to profiles specified in this version of this Specification. Decoders conforming to this version of this Specification shall ignore the values of all the gci_reserved_b[i] syntax elements.
This embodiment is for item 6 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
general_profile_idc
general_tier_flag
if( profileTierPresentFlag
) {
gci
_present_flag
u(1)
if( gci
_present_flag
)
general
_constraint_info( )
{
while( !byte
_aligned
( ) )
ptl
_alignment_zero_bit
f(1)
And the semantics are changed as follows:
The syntax structure general_constraint_info( ) is changed as follows:
And the semantics are changed as follows:
gci_num_reserved_b specifies the number of the reserved constraint b. The value of gci_num_reserved_b shall be 0. Other values of gci_num_reserved_b are reserved for future use by ITU-T|ISO/IEC and shall not be present in bitstreams conforming to this version of this Specification.
gci_reserved_b[i] may have any value. Its presence and value do not affect decoder conformance to profiles specified in this version of this Specification. Decoders conforming to this version of this Specification shall ignore the values of all the gci_reserved_b[i] syntax elements.
This embodiment is for item 7 and its sub-items.
The syntax structure profile_tier_level( ) is changed as follows:
general_profile_idc
general_tier_flag
general_level_idc
if( profileTierPresentFlag
)
gci
_present_flag
u(1)
if( gci
_present_flag
)
general
_constraint_info
( )
while( !byte
_aligned
( ) )
ptl
_alignment_zero_bit
f(1)
And the semantics are changed as follows:
The system 1000 may include a coding component 1004 that may implement the various coding or encoding methods described in the present disclosure. The coding component 1004 may reduce the average bitrate of video from the input 1002 to the output of the coding component 1004 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 1004 may be either stored, or transmitted via a communication connected, as represented by the component 1006. The stored or communicated bitstream (or coded) representation of the video received at the input 1002 may be used by the component 1008 for generating pixel values or displayable video that is sent to a display interface 1010. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.
Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or Displayport, and so on. Examples of storage interfaces include serial advanced technology attachment (SATA), peripheral component interconnect (PCI), integrated drive electronics (IDE) interface, and the like. The techniques described in the present disclosure may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.
Video source 112 may include a source such as a video capture device, an interface to receive video data from a video content provider, and/or a computer graphics system for generating video data, or a combination of such sources. The video data may comprise one or more pictures. Video encoder 114 encodes the video data from video source 112 to generate a bitstream. The bitstream may include a sequence of bits that form a coded representation of the video data. The bitstream may include coded pictures and associated data. The coded picture is a coded representation of a picture. The associated data may include sequence parameter sets, picture parameter sets, and other syntax structures. I/O interface 116 may include a modulator/demodulator (modem) and/or a transmitter. The encoded video data may be transmitted directly to destination device 120 via I/O interface 116 through network 130a. The encoded video data may also be stored onto a storage medium/server 130b for access by destination device 120.
Destination device 120 may include an I/O interface 126, a video decoder 124, and a display device 122.
I/O interface 126 may include a receiver and/or a modem. I/O interface 126 may acquire encoded video data from the source device 110 or the storage medium/server 130b. Video decoder 124 may decode the encoded video data. Display device 122 may display the decoded video data to a user. Display device 122 may be integrated with the destination device 120, or may be external to destination device 120 which be configured to interface with an external display device.
Video encoder 114 and video decoder 124 may operate according to a video compression standard, such as the High Efficiency Video Coding (HEVC) standard, Versatile Video Coding (VVC) standard and other current and/or further standards.
Video encoder 200 may be configured to perform any or all of the techniques of this disclosure. In the example of
The functional components of video encoder 200 may include a partition unit 201, a prediction unit 202 which may include a mode select unit 203, a motion estimation unit 204, a motion compensation unit 205 and an intra prediction unit 206, a residual generation unit 207, a transform unit 208, a quantization unit 209, an inverse quantization unit 210, an inverse transform unit 211, a reconstruction unit 212, a buffer 213, and an entropy encoding unit 214.
In other examples, video encoder 200 may include more, fewer, or different functional components. In an example, prediction unit 202 may include an intra block copy (IBC) unit. The IBC unit may perform prediction in an IBC mode in which at least one reference picture is a picture where the current video block is located.
Furthermore, some components, such as motion estimation unit 204 and motion compensation unit 205 may be highly integrated, but are represented in the example of
Partition unit 201 may partition a picture into one or more video blocks. Video encoder 200 and video decoder 300 may support various video block sizes.
Mode select unit 203 may select one of the coding modes, intra or inter, e.g., based on error results, and provide the resulting intra- or inter-coded block to a residual generation unit 207 to generate residual block data and to a reconstruction unit 212 to reconstruct the encoded block for use as a reference picture. In some example, Mode select unit 203 may select a combination of intra and inter prediction (CIIP) mode in which the prediction is based on an inter prediction signal and an intra prediction signal. Mode select unit 203 may also select a resolution for a motion vector (e.g., a sub-pixel or integer pixel precision) for the block in the case of inter-prediction.
To perform inter prediction on a current video block, motion estimation unit 204 may generate motion information for the current video block by comparing one or more reference frames from buffer 213 to the current video block. Motion compensation unit 205 may determine a predicted video block for the current video block based on the motion information and decoded samples of pictures from buffer 213 other than the picture associated with the current video block.
Motion estimation unit 204 and motion compensation unit 205 may perform different operations for a current video block, for example, depending on whether the current video block is in an I slice, a P slice, or a B slice.
In some examples, motion estimation unit 204 may perform uni-directional prediction for the current video block, and motion estimation unit 204 may search reference pictures of list 0 or list 1 for a reference video block for the current video block. Motion estimation unit 204 may then generate a reference index that indicates the reference picture in list 0 or list 1 that contains the reference video block and a motion vector that indicates a spatial displacement between the current video block and the reference video block. Motion estimation unit 204 may output the reference index, a prediction direction indicator, and the motion vector as the motion information of the current video block. Motion compensation unit 205 may generate the predicted video block of the current block based on the reference video block indicated by the motion information of the current video block.
In other examples, motion estimation unit 204 may perform bi-directional prediction for the current video block, motion estimation unit 204 may search the reference pictures in list 0 for a reference video block for the current video block and may also search the reference pictures in list 1 for another reference video block for the current video block. Motion estimation unit 204 may then generate reference indexes that indicate the reference pictures in list 0 and list 1 containing the reference video blocks and motion vectors that indicate spatial displacements between the reference video blocks and the current video block. Motion estimation unit 204 may output the reference indexes and the motion vectors of the current video block as the motion information of the current video block. Motion compensation unit 205 may generate the predicted video block of the current video block based on the reference video blocks indicated by the motion information of the current video block.
In some examples, motion estimation unit 204 may output a full set of motion information for decoding processing of a decoder.
In some examples, motion estimation unit 204 may not output a full set of motion information for the current video. Rather, motion estimation unit 204 may signal the motion information of the current video block with reference to the motion information of another video block. For example, motion estimation unit 204 may determine that the motion information of the current video block is sufficiently similar to the motion information of a neighboring video block.
In one example, motion estimation unit 204 may indicate, in a syntax structure associated with the current video block, a value that indicates to the video decoder 300 that the current video block has the same motion information as the another video block.
In another example, motion estimation unit 204 may identify, in a syntax structure associated with the current video block, another video block and a motion vector difference (MVD). The motion vector difference indicates a difference between the motion vector of the current video block and the motion vector of the indicated video block. The video decoder 300 may use the motion vector of the indicated video block and the motion vector difference to determine the motion vector of the current video block.
As discussed above, video encoder 200 may predictively signal the motion vector. Two examples of predictive signaling techniques that may be implemented by video encoder 200 include advanced motion vector prediction (AMVP) and merge mode signaling.
Intra prediction unit 206 may perform intra prediction on the current video block. When intra prediction unit 206 performs intra prediction on the current video block, intra prediction unit 206 may generate prediction data for the current video block based on decoded samples of other video blocks in the same picture. The prediction data for the current video block may include a predicted video block and various syntax elements.
Residual generation unit 207 may generate residual data for the current video block by subtracting (e.g., indicated by the minus sign) the predicted video block(s) of the current video block from the current video block. The residual data of the current video block may include residual video blocks that correspond to different sample components of the samples in the current video block.
In other examples, there may be no residual data for the current video block for the current video block, for example in a skip mode, and residual generation unit 207 may not perform the subtracting operation.
Transform processing unit 208 may generate one or more transform coefficient video blocks for the current video block by applying one or more transforms to a residual video block associated with the current video block.
After transform processing unit 208 generates a transform coefficient video block associated with the current video block, quantization unit 209 may quantize the transform coefficient video block associated with the current video block based on one or more quantization parameter (QP) values associated with the current video block.
Inverse quantization unit 210 and inverse transform unit 211 may apply inverse quantization and inverse transforms to the transform coefficient video block, respectively, to reconstruct a residual video block from the transform coefficient video block. Reconstruction unit 212 may add the reconstructed residual video block to corresponding samples from one or more predicted video blocks generated by the prediction unit 202 to produce a reconstructed video block associated with the current block for storage in the buffer 213.
After reconstruction unit 212 reconstructs the video block, loop filtering operation may be performed reduce video blocking artifacts in the video block.
Entropy encoding unit 214 may receive data from other functional components of the video encoder 200. When entropy encoding unit 214 receives the data, entropy encoding unit 214 may perform one or more entropy encoding operations to generate entropy encoded data and output a bitstream that includes the entropy encoded data.
The video decoder 300 may be configured to perform any or all of the techniques of this disclosure. In the example of
In the example of
Entropy decoding unit 301 may retrieve an encoded bitstream. The encoded bitstream may include entropy coded video data (e.g., encoded blocks of video data). Entropy decoding unit 301 may decode the entropy coded video data, and from the entropy decoded video data, motion compensation unit 302 may determine motion information including motion vectors, motion vector precision, reference picture list indexes, and other motion information. Motion compensation unit 302 may, for example, determine such information by performing the AMVP and merge mode.
Motion compensation unit 302 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used with sub-pixel precision may be included in the syntax elements.
Motion compensation unit 302 may use interpolation filters as used by video encoder 20 during encoding of the video block to calculate interpolated values for sub-integer pixels of a reference block. Motion compensation unit 302 may determine the interpolation filters used by video encoder 200 according to received syntax information and use the interpolation filters to produce predictive blocks.
Motion compensation unit 302 may use some of the syntax information to determine sizes of blocks used to encode frame(s) and/or slice(s) of the encoded video sequence, partition information that describes how each macroblock of a picture of the encoded video sequence is partitioned, modes indicating how each partition is encoded, one or more reference frames (and reference frame lists) for each inter-encoded block, and other information to decode the encoded video sequence.
Intra prediction unit 303 may use intra prediction modes for example received in the bitstream to form a prediction block from spatially adjacent blocks. Inverse quantization unit 304 inverse quantizes, i.e., de-quantizes, the quantized video block coefficients provided in the bitstream and decoded by entropy decoding unit 301. Inverse transform unit 305 applies an inverse transform.
Reconstruction unit 306 may sum the residual blocks with the corresponding prediction blocks generated by motion compensation unit 302 or intra-prediction unit 303 to form decoded blocks. If desired, a deblocking filter may also be applied to filter the decoded blocks in order to remove blockiness artifacts. The decoded video blocks are then stored in buffer 307, which provides reference blocks for subsequent motion compensation/intra prediction and also produces decoded video for presentation on a display device.
The following solutions show example embodiments of techniques discussed in the previous section (e.g., items 1-9).
A listing of solutions preferred by some embodiments is provided next.
Another listing of solutions preferred by some embodiments is provided next.
Yet another listing of solutions preferred by some embodiments is provided next.
In the present disclosure, the term “video processing” may refer to video encoding, video decoding, video compression or video decompression. For example, video compression algorithms may be applied during conversion from pixel representation of a video to a corresponding bitstream representation or vice versa. The bitstream representation (or simply, the bitstream) of a current video block may, for example, correspond to bits that are either co-located or spread in different places within the bitstream, as is defined by the syntax. For example, a macroblock may be encoded in terms of transformed and coded error residual values and also using bits in headers and other fields in the bitstream.
The disclosed and other solutions, examples, embodiments, modules and the functional operations described in this disclosure can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this disclosure and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this disclosure can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and compact disc, read-only memory (CD ROM) and digital versatile disc read-only memory (DVD-ROM) disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
While the present disclosure contains many specifics, these should not be construed as limitations on the scope of any subject matter or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular techniques. Certain features that are described in the present disclosure in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in the present disclosure should not be understood as requiring such separation in all embodiments.
Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in the present disclosure.
This application is a continuation of U.S. application Ser. No. 18/073,700, filed on Dec. 2, 2022, which is a continuation of International Patent Application No. PCT/US2021/035366 filed on Jun. 2, 2021, which claims the priority to and benefits of U.S. Provisional Patent Application No. 63/033,689 filed on Jun. 2, 2020. All the aforementioned patent applications are hereby incorporated by reference in their entireties.
Number | Date | Country | |
---|---|---|---|
63033689 | Jun 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 18073700 | Dec 2022 | US |
Child | 18511565 | US | |
Parent | PCT/US2021/035366 | Jun 2021 | US |
Child | 18073700 | US |