The disclosed subject matter relates to video coding and decoding, and more specifically, to the signaling of reference picture resampling with resampling picture size indication.
Video coding and decoding using inter-picture prediction with motion compensation has been known. Uncompressed digital video can consist of a series of pictures, each picture having a spatial dimension of, for example, 1920×1080 luminance samples and associated chrominance samples. The series of pictures can have a fixed or variable picture rate (informally also known as frame rate), of, for example 60 pictures per second or 60 Hz. Uncompressed video has significant bitrate requirements. For example, 1080p60 4:2:0 video at 8 bit per sample (1920×1080 luminance sample resolution at 60 Hz frame rate) requires close to 1.5 Gbit/s bandwidth. An hour of such video requires more than 600 GByte of storage space.
One purpose of video coding and decoding can be the reduction of redundancy in the input video signal, through compression. Compression can help reducing aforementioned bandwidth or storage space requirements, in some cases by two orders of magnitude or more. Both lossless and lossy compression, as well as a combination thereof can be employed. Lossless compression refers to techniques where an exact copy of the original signal can be reconstructed from the compressed original signal. When using lossy compression, the reconstructed signal may not be identical to the original signal, but the distortion between original and reconstructed signal is small enough to make the reconstructed signal useful for the intended application. In the case of video, lossy compression is widely employed. The amount of distortion tolerated depends on the application; for example, users of certain consumer streaming applications may tolerate higher distortion than users of television contribution applications. The compression ratio achievable can reflect that: higher allowable/tolerable distortion can yield higher compression ratios.
A video encoder and decoder can utilize techniques from several broad categories, including, for example, motion compensation, transform, quantization, and entropy coding, some of which will be introduced below.
Historically, video encoders and decoders tended to operate on a given picture size that was, in most cases, defined and stayed constant for a coded video sequence (CVS), Group of Pictures (GOP), or a similar multi-picture timeframe. For example, in MPEG-2, system designs are known to change the horizontal resolution (and, thereby, the picture size) dependent on factors such as activity of the scene, but only at I pictures, hence typically for a GOP. The resampling of reference pictures for use of different resolutions within a CVS is known, for example, from ITU-T Rec. H.263 Annex P. However, here the picture size does not change, only the reference pictures are being resampled, resulting potentially in only parts of the picture canvas being used (in case of downsampling), or only parts of the scene being captured (in case of upsampling). Further, H.263 Annex Q allows the resampling of an individual macroblock by a factor of two (in each dimension), upward or downward. Again, the picture size remains the same. The size of a macroblock is fixed in H.263, and therefore does not need to be signaled.
Changes of picture size in predicted pictures became more mainstream in modern video coding. For example, VP9 allows reference picture resampling and change of resolution for a whole picture. Similarly, certain proposals made towards VVC (including, for example, Hendry, et. al, “On adaptive resolution change (ARC) for VVC”, Joint Video Team document JVET-M0135-v1, Jan. 9-19, 2019, incorporated herein in its entirety) allow for resampling of whole reference pictures to different-higher or lower-resolutions. In that document, different candidate resolutions are suggested to be coded in the sequence parameter set and referred to by per-picture syntax elements in the picture parameter set.
In an embodiment, there is provided a method of decoding an encoded video bitstream using at least one processor, the method including obtaining a flag indicating that a conformance window is not used for reference picture resampling; based on the flag indicating that the conformance window is not used for the reference picture resampling, determining whether a resampling picture size is signaled; based on determining that the resampling picture size is signaled, determining a resampling ratio based on the resampling picture size; based on determining that the resampling picture size is not signaled, determining the resampling ratio based on an output picture size; and performing the reference picture resampling on a current picture using the resampling ratio.
In an embodiment, there is provided a device for decoding an encoded video bitstream, the device including at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: obtaining code configured to cause the at least one processor to obtain a flag indicating that a conformance window is not used for reference picture resampling; first determining code configured to cause the at least one processor to, based on the flag indicating that the conformance window is not used for the reference picture resampling, determine whether a resampling picture size is signaled; second determining code configured to cause the at least one processor to, based on determining that the resampling picture size is signaled, determine a resampling ratio based on the resampling picture size; third determining code configured to cause the at least one processor to, based on determining that the resampling picture size is not signaled, determine the resampling ratio based on an output picture size; and performing code configured to cause the at least one processor to perform the reference picture resampling on a current picture using the resampling ratio.
In an embodiment, there is provided a non-transitory computer-readable medium storing instructions, the instructions including: one or more instructions that, when executed by one or more processors of a device for decoding an encoded video bitstream, cause the one or more processors to: obtain a flag indicating that a conformance window is not used for reference picture resampling; based on the flag indicating that the conformance window is not used for the reference picture resampling, determine whether a resampling picture size is signaled; based on determining that the resampling picture size is signaled, determining a resampling ratio based on the resampling picture size; based on determine that the resampling picture size is not signaled, determining the resampling ratio based on an output picture size; and perform the reference picture resampling on a current picture using the resampling ratio.
Further features, the nature, and various advantages of the disclosed subject matter will be more apparent from the following detailed description and the accompanying drawings in which:
In
A streaming system may include a capture subsystem (213), that can include a video source (201), for example a digital camera, creating a for example uncompressed video sample stream (202). That sample stream (202), depicted as a bold line to emphasize a high data volume when compared to encoded video bitstreams, can be processed by an encoder (203) coupled to the camera (201). The encoder (203) can include hardware, software, or a combination thereof to enable or implement aspects of the disclosed subject matter as described in more detail below. The encoded video bitstream (204), depicted as a thin line to emphasize the lower data volume when compared to the sample stream, can be stored on a streaming server (205) for future use. One or more streaming clients (206, 208) can access the streaming server (205) to retrieve copies (207, 209) of the encoded video bitstream (204). A client (206) can include a video decoder (210) which decodes the incoming copy of the encoded video bitstream (207) and creates an outgoing video sample stream (211) that can be rendered on a display (212) or other rendering device (not depicted). In some streaming systems, the video bitstreams (204, 207, 209) can be encoded according to certain video coding/compression standards. Examples of those standards include ITU-T Recommendation H.265. Under development is a video coding standard informally known as Versatile Video Coding or VVC. The disclosed subject matter may be used in the context of VVC.
A receiver (310) may receive one or more codec video sequences to be decoded by the decoder (210); in the same or another embodiment, one coded video sequence at a time, where the decoding of each coded video sequence is independent from other coded video sequences. The coded video sequence may be received from a channel (312), which may be a hardware/software link to a storage device which stores the encoded video data. The receiver (310) may receive the encoded video data with other data, for example, coded audio data and/or ancillary data streams, that may be forwarded to their respective using entities (not depicted). The receiver (310) may separate the coded video sequence from the other data. To combat network jitter, a buffer memory (315) may be coupled in between receiver (310) and entropy decoder/parser (320) (“parser” henceforth). When receiver (310) is receiving data from a store/forward device of sufficient bandwidth and controllability, or from an isosychronous network, the buffer (315) may not be needed, or can be small. For use on best effort packet networks such as the Internet, the buffer (315) may be required, can be comparatively large and can advantageously of adaptive size.
The video decoder (210) may include a parser (320) to reconstruct symbols (321) from the entropy coded video sequence. Categories of those symbols include information used to manage operation of the decoder (210), and potentially information to control a rendering device such as a display (212) that is not an integral part of the decoder but can be coupled to it, as was shown in
The parser (320) may perform entropy decoding/parsing operation on the video sequence received from the buffer (315), so to create symbols (321).
Reconstruction of the symbols (321) can involve multiple different units depending on the type of the coded video picture or parts thereof (such as: inter and intra picture, inter and intra block), and other factors. Which units are involved, and how, can be controlled by the subgroup control information that was parsed from the coded video sequence by the parser (320). The flow of such subgroup control information between the parser (320) and the multiple units below is not depicted for clarity.
Beyond the functional blocks already mentioned, decoder 210 can be conceptually subdivided into a number of functional units as described below. In a practical implementation operating under commercial constraints, many of these units interact closely with each other and can, at least partly, be integrated into each other. However, for the purpose of describing the disclosed subject matter, the conceptual subdivision into the functional units below is appropriate.
A first unit is the scaler/inverse transform unit (351). The scaler/inverse transform unit (351) receives quantized transform coefficient as well as control information, including which transform to use, block size, quantization factor, quantization scaling matrices, etc. as symbol(s) (321) from the parser (320). It can output blocks comprising sample values, that can be input into aggregator (355).
In some cases, the output samples of the scaler/inverse transform (351) can pertain to an intra coded block; that is: a block that is not using predictive information from previously reconstructed pictures, but can use predictive information from previously reconstructed parts of the current picture. Such predictive information can be provided by an intra picture prediction unit (352). In some cases, the intra picture prediction unit (352) generates a block of the same size and shape of the block under reconstruction, using surrounding already reconstructed information fetched from the current (partly reconstructed) picture (358). The aggregator (355), in some cases, adds, on a per sample basis, the prediction information the intra prediction unit (352) has generated to the output sample information as provided by the scaler/inverse transform unit (351).
In other cases, the output samples of the scaler/inverse transform unit (351) can pertain to an inter coded, and potentially motion compensated block. In such a case, a Motion Compensation Prediction unit (353) can access reference picture memory (357) to fetch samples used for prediction. After motion compensating the fetched samples in accordance with the symbols (321) pertaining to the block, these samples can be added by the aggregator (355) to the output of the scaler/inverse transform unit (in this case called the residual samples or residual signal) so to generate output sample information. The addresses within the reference picture memory form where the motion compensation unit fetches prediction samples can be controlled by motion vectors, available to the motion compensation unit in the form of symbols (321) that can have, for example X, Y, and reference picture components. Motion compensation also can include interpolation of sample values as fetched from the reference picture memory when sub-sample exact motion vectors are in use, motion vector prediction mechanisms, and so forth.
The output samples of the aggregator (355) can be subject to various loop filtering techniques in the loop filter unit (356). Video compression technologies can include in-loop filter technologies that are controlled by parameters included in the coded video bitstream and made available to the loop filter unit (356) as symbols (321) from the parser (320), but can also be responsive to meta-information obtained during the decoding of previous (in decoding order) parts of the coded picture or coded video sequence, as well as responsive to previously reconstructed and loop-filtered sample values.
The output of the loop filter unit (356) can be a sample stream that can be output to the render device (212) as well as stored in the reference picture memory for use in future inter-picture prediction.
Certain coded pictures, once fully reconstructed, can be used as reference pictures for future prediction. Once a coded picture is fully reconstructed and the coded picture has been identified as a reference picture (by, for example, parser (320)), the current reference picture (358) can become part of the reference picture buffer (357), and a fresh current picture memory can be reallocated before commencing the reconstruction of the following coded picture.
The video decoder 210 may perform decoding operations according to a predetermined video compression technology that may be documented in a standard, such as ITU-T Rec. H.265. The coded video sequence may conform to a syntax specified by the video compression technology or standard being used, in the sense that it adheres to the syntax of the video compression technology or standard, as specified in the video compression technology document or standard and specifically in the profiles document therein. Also necessary for compliance can be that the complexity of the coded video sequence is within bounds as defined by the level of the video compression technology or standard. In some cases, levels restrict the maximum picture size, maximum frame rate, maximum reconstruction sample rate (measured in, for example megasamples per second), maximum reference picture size, and so on. Limits set by levels can, in some cases, be further restricted through Hypothetical Reference Decoder (HRD) specifications and metadata for HRD buffer management signaled in the coded video sequence.
In an embodiment, the receiver (310) may receive additional (redundant) data with the encoded video. The additional data may be included as part of the coded video sequence(s). The additional data may be used by the video decoder (210) to properly decode the data and/or to more accurately reconstruct the original video data. Additional data can be in the form of, for example, temporal, spatial, or SNR enhancement layers, redundant slices, redundant pictures, forward error correction codes, and so on.
The encoder (203) may receive video samples from a video source (201) (that is not part of the encoder) that may capture video image(s) to be coded by the encoder (203).
The video source (201) may provide the source video sequence to be coded by the encoder (203) in the form of a digital video sample stream that can be of any suitable bit depth (for example: 8 bit, 10 bit, 12 bit, . . . ), any colorspace (for example, BT.601 Y CrCB, RGB, . . . ) and any suitable sampling structure (for example Y CrCb 4:2:0, Y CrCb 4:4:4). In a media serving system, the video source (201) may be a storage device storing previously prepared video. In a videoconferencing system, the video source (203) may be a camera that captures local image information as a video sequence. Video data may be provided as a plurality of individual pictures that impart motion when viewed in sequence. The pictures themselves may be organized as a spatial array of pixels, wherein each pixel can comprise one or more sample depending on the sampling structure, color space, etc. in use. A person skilled in the art can readily understand the relationship between pixels and samples. The description below focusses on samples.
According to an embodiment, the encoder (203) may code and compress the pictures of the source video sequence into a coded video sequence (443) in real time or under any other time constraints as required by the application. Enforcing appropriate coding speed is one function of Controller (450). Controller controls other functional units as described below and is functionally coupled to these units. The coupling is not depicted for clarity. Parameters set by controller can include rate control related parameters (picture skip, quantizer, lambda value of rate-distortion optimization techniques, . . . ), picture size, group of pictures (GOP) layout, maximum motion vector search range, and so forth. A person skilled in the art can readily identify other functions of controller (450) as they may pertain to video encoder (203) optimized for a certain system design.
Some video encoders operate in what a person skilled in the are readily recognizes as a “coding loop”. As an oversimplified description, a coding loop can consist of the encoding part of an encoder (430) (“source coder” henceforth) (responsible for creating symbols based on an input picture to be coded, and a reference picture(s)), and a (local) decoder (433) embedded in the encoder (203) that reconstructs the symbols to create the sample data a (remote) decoder also would create (as any compression between symbols and coded video bitstream is lossless in the video compression technologies considered in the disclosed subject matter). That reconstructed sample stream is input to the reference picture memory (434). As the decoding of a symbol stream leads to bit-exact results independent of decoder location (local or remote), the reference picture buffer content is also bit exact between local encoder and remote encoder. In other words, the prediction part of an encoder “sees” as reference picture samples exactly the same sample values as a decoder would “see” when using prediction during decoding. This fundamental principle of reference picture synchronicity (and resulting drift, if synchronicity cannot be maintained, for example because of channel errors) is well known to a person skilled in the art.
The operation of the “local” decoder (433) can be the same as of a “remote” decoder (210), which has already been described in detail above in conjunction with
An observation that can be made at this point is that any decoder technology except the parsing/entropy decoding that is present in a decoder also necessarily needs to be present, in substantially identical functional form, in a corresponding encoder. For this reason, the disclosed subject matter focusses on decoder operation. The description of encoder technologies can be abbreviated as they are the inverse of the comprehensively described decoder technologies. Only in certain areas a more detail description is required and provided below.
As part of its operation, the source coder (430) may perform motion compensated predictive coding, which codes an input frame predictively with reference to one or more previously-coded frames from the video sequence that were designated as “reference frames.” In this manner, the coding engine (432) codes differences between pixel blocks of an input frame and pixel blocks of reference frame(s) that may be selected as prediction reference(s) to the input frame.
The local video decoder (433) may decode coded video data of frames that may be designated as reference frames, based on symbols created by the source coder (430). Operations of the coding engine (432) may advantageously be lossy processes. When the coded video data may be decoded at a video decoder (not shown in
The predictor (435) may perform prediction searches for the coding engine (432). That is, for a new frame to be coded, the predictor (435) may search the reference picture memory (434) for sample data (as candidate reference pixel blocks) or certain metadata such as reference picture motion vectors, block shapes, and so on, that may serve as an appropriate prediction reference for the new pictures. The predictor (435) may operate on a sample block-by-pixel block basis to find appropriate prediction references. In some cases, as determined by search results obtained by the predictor (435), an input picture may have prediction references drawn from multiple reference pictures stored in the reference picture memory (434).
The controller (450) may manage coding operations of the video coder (430), including, for example, setting of parameters and subgroup parameters used for encoding the video data.
Output of all aforementioned functional units may be subjected to entropy coding in the entropy coder (445). The entropy coder translates the symbols as generated by the various functional units into a coded video sequence, by loss-less compressing the symbols according to technologies known to a person skilled in the art as, for example Huffman coding, variable length coding, arithmetic coding, and so forth.
The transmitter (440) may buffer the coded video sequence(s) as created by the entropy coder (445) to prepare it for transmission via a communication channel (460), which may be a hardware/software link to a storage device which would store the encoded video data. The transmitter (440) may merge coded video data from the video coder (430) with other data to be transmitted, for example, coded audio data and/or ancillary data streams (sources not shown).
The controller (450) may manage operation of the encoder (203). During coding, the controller (450) may assign to each coded picture a certain coded picture type, which may affect the coding techniques that may be applied to the respective picture. For example, pictures often may be assigned as one of the following frame types:
An Intra Picture (I picture) may be one that may be coded and decoded without using any other frame in the sequence as a source of prediction. Some video codecs allow for different types of Intra pictures, including, for example Independent Decoder Refresh Pictures. A person skilled in the art is aware of those variants of I pictures and their respective applications and features.
A Predictive picture (P picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most one motion vector and reference index to predict the sample values of each block.
A Bi-directionally Predictive Picture (B Picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most two motion vectors and reference indices to predict the sample values of each block. Similarly, multiple-predictive pictures can use more than two reference pictures and associated metadata for the reconstruction of a single block.
Source pictures commonly may be subdivided spatially into a plurality of sample blocks (for example, blocks of 4×4, 8×8, 4×8, or 16×16 samples each) and coded on a block-by-block basis. Blocks may be coded predictively with reference to other (already coded) blocks as determined by the coding assignment applied to the blocks' respective pictures. For example, blocks of I pictures may be coded non-predictively or they may be coded predictively with reference to already coded blocks of the same picture (spatial prediction or intra prediction). Pixel blocks of P pictures may be coded non-predictively, via spatial prediction or via temporal prediction with reference to one previously coded reference pictures. Blocks of B pictures may be coded non-predictively, via spatial prediction or via temporal prediction with reference to one or two previously coded reference pictures.
The video coder (203) may perform coding operations according to a predetermined video coding technology or standard, such as ITU-T Rec. H.265. In its operation, the video coder (203) may perform various compression operations, including predictive coding operations that exploit temporal and spatial redundancies in the input video sequence. The coded video data, therefore, may conform to a syntax specified by the video coding technology or standard being used.
In an embodiment, the transmitter (440) may transmit additional data with the encoded video. The video coder (430) may include such data as part of the coded video sequence. Additional data may comprise temporal/spatial/SNR enhancement layers, other forms of redundant data such as redundant pictures and slices, Supplementary Enhancement Information (SEI) messages, Visual Usability Information (VUI) parameter set fragments, and so on.
Recently, compressed domain aggregation or extraction of multiple semantically independent picture parts into a single video picture has gained some attention. In particular, in the context of, for example, 360 coding or certain surveillance applications, multiple semantically independent source pictures (for examples the six cube surface of a cube-projected 360 scene, or individual camera inputs in case of a multi-camera surveillance setup) may require separate adaptive resolution settings to cope with different per-scene activity at a given point in time. In other words, encoders, at a given point in time, may choose to use different resampling factors for different semantically independent pictures that make up the whole 360 or surveillance scene. When combined into a single picture, that, in turn, requires that reference picture resampling is performed, and adaptive resolution coding signaling is available, for parts of a coded picture.
Below, a few terms will be introduced that will be referred to in the remainder of this description.
Sub-Picture may refer to a, in some cases, rectangular arrangement of samples, blocks, macroblocks, coding units, or similar entities that are semantically grouped, and that may be independently coded in changed resolution. One or more sub-pictures may form a picture. One or more coded sub-pictures may form a coded picture. One or more sub-pictures may be assembled into a picture, and one or more sub pictures may be extracted from a picture. In certain environments, one or more coded sub-pictures may be assembled in the compressed domain without transcoding to the sample level into a coded picture, and in the same or other cases, one or more coded sub-pictures may be extracted from a coded picture in the compressed domain.
Reference Picture Resampling (RPR) or Adaptive Resolution Change (ARC) may refer to mechanisms that allow the change of resolution of a picture or sub-picture within a coded video sequence, by the means of, for example, reference picture resampling. RPR/ARC parameters henceforth refer to the control information required to perform adaptive resolution change, that may include, for example, filter parameters, scaling factors, resolutions of output and/or reference pictures, various control flags, and so forth.
In embodiments coding and decoding may be performed on a single, semantically independent coded video picture. Before describing the implication of coding/decoding of multiple sub pictures with independent RPR/ARC parameters and its implied additional complexity, options for signaling RPR/ARC parameters shall be described.
Referring to
Classes of RPR/ARC parameters may include:
Henceforth, the description assumes the coding of a finite set of up/downsample factors (the same factor to be used in both X and Y dimension), indicated through a codeword. That codeword may be variable length coded, for example using the Ext-Golomb code common for certain syntax elements in video coding specifications such as H.264 and H.265. One suitable mapping of values to up/downsample factors can, for example, be according to Table 1:
Many similar mappings could be devised according to the needs of an application and the capabilities of the up and downscale mechanisms available in a video compression technology or standard. The table could be extended to more values. Values may also be represented by entropy coding mechanisms other than Ext-Golomb codes, for example using binary coding. That may have certain advantages when the resampling factors were of interest outside the video processing engines (encoder and decoder foremost) themselves, for example by MANEs. It should be noted that, for situations where no resolution change is required, an Ext-Golomb code can be chosen that is short; in the table above, only a single bit. That can have a coding efficiency advantage over using binary codes for the most common case.
The number of entries in the table, as well as their semantics, may be fully or partially configurable. For example, the basic outline of the table may be conveyed in a “high” parameter set such as a sequence or decoder parameter set. In embodiments, one or more such tables may be defined in a video coding technology or standard, and may be selected through for example a decoder or sequence parameter set.
Below is described how an upsample/downsample factor (ARC information), coded as described above, may be included in a video coding technology or standard syntax. Similar considerations may apply to one, or a few, codewords controlling up/downsample filters. See below for a discussion when comparatively large amounts of data are required for a filter or other data structures.
As shown in
In the same or another embodiment, the signaling of ARC parameters can follow a detailed example as outlined in
As shown in
Referring to
When adaptive resolution is in use, in this example, coded is an output resolution in units of samples (613). The numeral 613 refers to both output_pic_width_in_luma_samples and output_pic_height_in_luma_samples, which together can define the resolution of the output picture. Elsewhere in a video coding technology or standard, certain restrictions to either value can be defined. For example, a level definition may limit the number of total output samples, which could be the product of the value of those two syntax elements. Also, certain video coding technologies or standards, or external technologies or standards such as, for example, system standards, may limit the numbering range (for example, one or both dimensions must be divisible by a power of 2 number), or the aspect ratio (for example, the width and height must be in a relation such as 4:3 or 16:9). Such restrictions may be introduced to facilitate hardware implementations or for other reasons, and are well known in the art.
In certain applications, it can be advisable that the encoder instructs the decoder to use a certain reference picture size rather than implicitly assume that size to be the output picture size. In this example, the syntax element reference_pic_size_present_flag (614) gates the conditional presence of reference picture dimensions (615) (again, the numeral refers to both width and height).
Finally, shown is a table of possible decoding picture width and heights. Such a table can be expressed, for example, by a table indication (num_dec_pic_size_in_luma_samples_minus1) (616). The “minus1” can refer to the interpretation of the value of that syntax element. For example, if the coded value is zero, one table entry is present. If the value is five, six table entries are present. For each “line” in the table, decoded picture width and height are then included in the syntax (617).
The table entries presented (617) can be indexed using the syntax element dec_pic_size_idx (602) in the tile group header, thereby allowing different decoded sizes—in effect, zoom factors—per tile group.
Certain video coding technologies or standards, for example VP9, support spatial scalability by implementing certain forms of reference picture resampling (signaled quite differently from the disclosed subject matter) in conjunction with temporal scalability, so to enable spatial scalability. In particular, certain reference pictures may be upsampled using ARC-style technologies to a higher resolution to form the base of a spatial enhancement layer. Those upsampled pictures could be refined, using normal prediction mechanisms at the high resolution, so to add detail.
Embodiments discussed herein can be used in such an environment. In certain cases, in the same or another embodiment, a value in the NAL unit header, for example the Temporal ID field, can be used to indicate not only the temporal but also the spatial layer. Doing so may have certain advantages for certain system designs; for example, existing Selected Forwarding Units (SFU) created and optimized for temporal layer selected forwarding based on the NAL unit header Temporal ID value can be used without modification, for scalable environments. In order to enable that, there may be a requirement for a mapping between the coded picture size and the temporal layer is indicated by the temporal ID field in the NAL unit header.
In an embodiment, a conformance window size may be signaled in a PPS. The conformance window parameters may be used for calculating the resampling ratio, when the conformance window size of the reference picture is different from that of the current picture. A decoder may need to recognize the conformance window size of each picture, to determine whether the resampling process is needed.
In an embodiment, the scale factor for reference picture resampling (RPR) may be calculated based on the output widths and output heights, which may be derived from the conformance window parameters, between the current picture and the referenced picture. This may allow the scaling factor to be calculated more exactly, compared to using the decoded picture size. This may work well for most video sequences, which the output picture size is almost identical to the decoded picture size, with small padded regions.
However, this may also cause various issues. For example, when a conformance window size is quite different from the decoded picture size with large offset values, for immersive media applications (e.g. 360 cubemap, stereoscopic, point cloud), the calculation of scaling factor based on the conformance window size may not guarantee the quality of inter-prediction with different resolutions. In extreme cases, the collocated region of the current CU in a reference picture may not be present. When RPR is used for scalability with multi-layers, the conformance window offsets may not be used for calculation of referenced region across layers. Note that the referenced region of each directly dependent layer ma be explicitly signaled in PPS-extension, in HEVC Scalability Extension (SHVC). When a sub-bitstream targeting a specific region (sub-picture) is extracted from the entire bitstream, the conformance window size is not matched with the picture size at all. Note that the conformance window parameters can not be updated as long as the parameters are used for scaling calculation, once the bitstream is encoded.
Based on the above potential problems, the calculation of the scaling factors based on the conformance window size may have corner cases, for which alternative parameters are required. As a fallback, when the conformance window parameters may not be used for calculation of scaling factors, it is proposed to signal reference region parameters that can be used to calculate scaling for RPR and Scalability.
In an embodiment, referring to
In an embodiment, still referring to
In an embodiment, a flag may be present in a PPS, or another parameter set, and may indicate whether or not the resampling picture size (width and height) are explicitly signaled in a PPS, or another parameter set. If the resampling picture size parameters are explicitly signaled, the resampling ratio between the current picture and the reference picture may be calculated based on the resampling picture size parameters.
In an embodiment, referring to
In an embodiment, use_conf_win_for_rpr_flag equal to 1 may indicate that resampling_pic_width_in_luma_samples and resampling_pic_height_in_luma_samples are not present.
In an embodiment, resampling_pic_width_in_luma_samples may specify the width of each reference picture referring to the PPS in units of luma samples, for resampling. resampling_pic_width_in_luma_samples may not be equal to 0, may be an integer multiple of Max(8, MinCbSizeY), and may be less than or equal to pic_width_max_in_luma_samples.
In an embodiment, resampling_pic_height_in_luma_samples may specify the height of each reference picture referring to the PPS in units of luma samples, for resampling. resampling_pic_height_in_luma_samples may not be equal to 0 and may be an integer multiple of Max(8, MinCbSizeY), and may be less than or equal to pic_height_max_in_luma_samples.
When the syntax element resampling_pic_width_in_luma_samples is not present, the value of resampling_pic_width_in_luma_samples may be inferred to be equal to PicOutputWidthL.
When the syntax element resampling_pic_height_in_luma_samples is not present, the value of resampling_pic_height_in_luma_samples may be inferred to be equal to PicOutputHeightL.
In an embodiment, an example of a fractional interpolation process with the reference picture resampling may be processed as follows:
The variable fRefWidth may be set equal to the resampling_pic_width_in_luma_samples of the reference picture in luma samples.
The variable fRefHeight may be set equal to resampling_pic_height_in_luma_samples of the reference picture in luma samples.
The motion vector mvLX may be set equal to (refMvLX−mvOffset).
If cIdx is equal to 0, the scaling factors and their fixed-point representations may be defined according to Equation 1 and Equation 2 below:
hori_scale_fp=((fRefWidth<<14)+(resampling_pic_width_in_luma_samples>>1))/resampling_pic_width_in_luma_samples (Equation 1)
vert_scale_fp=((fRefHeight<<14)+(resampling_pic_height_in_luma_samples>>1))/resampling_pic_height_in_luma_samples (Equation 2)
In an embodiment, referring to
In an embodiment, ref_region_left_offset may specify the horizontal offset between the top-left luma sample of the reference region in the decoded picture. The value of ref_region_left_offset shall be in the range of −214 to 214−1, inclusive. When not present, the value of ref_region_left_offset may be inferred to be equal to conf_win_left_offset.
In an embodiment, ref_region_top_offset may specify the vertical offset between the top-left luma sample of the reference region in the decoded picture. The value of ref_region_top_offset shall be in the range of −214 to 214−1, inclusive. When not present, the value of ref_region_top_offset may be inferred to be equal to conf_win_right_offset.
In an embodiment, ref_region_right_offset may specify the horizontal offset between the bottom-right luma sample of the reference region in the decoded picture. The value of ref_layer_right_offset shall be in the range of −214 to 214−1, inclusive. When not present, the value of ref_region_right_offset may be inferred to be equal to conf_win_top_offset.
In an embodiment, ref_region_bottom_offset may specify the vertical offset between the bottom-right luma sample of the reference region in the decoded picture. The value of ref_layer_bottom_offset shall be in the range of −214 to 214−1, inclusive. When not present, the value of ref_region_bottom_offset[ref_loc_offset_layer_id[i] ] may be inferred to be equal to conf_win_bottom_offset.
The variables PicRefWidthL and PicRefHeightL may be derived as shown in Equation 3 and Equation 4, as shown below:
PicRefWidthL=pic_width_in_luma_samples−SubWidthC*(ref_region_right_offset+ref_region_left_offset) (Equation 3)
PicRefHeightL=pic_height_in_pic_size_units−SubHeightC*(ref_region_bottom_offset+ref_region_top_offset) (Equation 4
The variable fRefWidth may be set equal to PicRefWidthL of the reference picture in luma samples.
The variable fRefHeight may be set equal to PicRefHeightL of the reference picture in luma samples.
The motion vector mvLX may be set equal to (refMvLX−mvOffset).
If cIdx is equal to 0, the scaling factors and their fixed-point representations may be defined as shown in Equation 5 and Equation 6, as shown below:
hori_scale_fp=((fRefWidth<<14)+(PicRefWidthL>>1))/PicRefWidthL (Equation 5)
vert_scale_fp=((fRefHeight<<14)+(PicRefHeightL>>1))/PicRefHeight (Equation 6)
The top-left coordinate of the bounding block for reference sample padding (xSbIntL, ySbIntL) may be set equal to (xSb+(mvLX[0]>>4),ySb+(mvLX[1]>>4)).
For each luma sample location
refxSbL=(((xSb+ref_region_left_offset)<<4)+refMvLX[0])*hori_scale_fp (Equation 7)
refxL=((Sign(refxSb)*((Abs(refxSb)+128)>>8)+xL*((hori_scale_fp+8)>>4))+32)>>6 (Equation 8)
refySbL=(((ySb+ref_region_top_offset)<<4)+refMvLX[1])*vert_scale_fp (Equation 9)
refyL=((Sign(refySb)*((Abs(refySb)+128)>>8)+yL*((vert_scale_fp+8)>>4))+32)>>6 (Equation 10)
As shown in
As further shown in
If the second flag is determined to indicate that the resampling picture size is signaled (YES at block 920), process 900 may proceed to block 930 and then block 950. At block 930, process 900 may include determining a resampling ratio based on the resampling picture size.
If the second flag is determined to not indicate that the conformance window is used for reference picture resampling (NO at block 920), process 900 may proceed to block 940 and then block 950. At block 940, process 900 may include determining the resampling ratio based on an output picture size.
As further shown in
In an embodiment, the flag may be signaled in a picture parameter set.
In an embodiment, the resampling picture size may be signaled in the encoded video bitstream as at least one of a width of the resampling picture size and a height of the resampling picture size.
In an embodiment, the at least one of the width and the height may be signaled in a picture parameter set.
In an embodiment, the at least one of the width and the height may be expressed as a number of luma samples included in the at least one of the width and the height.
In an embodiment, the at least one of the width and the height may be determined based on at least one offset distance between a border of the current picture and a predetermined luma sample of a reference region.
In an embodiment, the at least one offset distance may be signaled in a picture parameter set.
In an embodiment, the at least one offset distance may include at least one from among a horizontal offset distance between a left border of the current picture and a top-left luma sample of the reference region, a vertical offset distance between a top border of the current picture and the top-left luma sample of the reference region, a horizontal offset distance between a right border of the current picture and a bottom-right luma sample of the reference region, and a vertical offset distance between a bottom border of the current picture and the bottom-right luma sample of the reference region.
Although
Further, the proposed methods may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits). In one example, the one or more processors execute a program that is stored in a non-transitory computer-readable medium to perform one or more of the proposed methods.
The techniques described above can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media. For example,
The computer software can be coded using any suitable machine code or computer language, that may be subject to assembly, compilation, linking, or like mechanisms to create code comprising instructions that can be executed directly, or through interpretation, micro-code execution, and the like, by computer central processing units (CPUs), Graphics Processing Units (GPUs), and the like.
The instructions can be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smartphones, gaming devices, internet of things devices, and the like.
The components shown in
Computer system 1000 may include certain human interface input devices. Such a human interface input device may be responsive to input by one or more human users through, for example, tactile input (such as: keystrokes, swipes, data glove movements), audio input (such as: voice, clapping), visual input (such as: gestures), olfactory input (not depicted). The human interface devices can also be used to capture certain media not necessarily directly related to conscious input by a human, such as audio (such as: speech, music, ambient sound), images (such as: scanned images, photographic images obtain from a still image camera), video (such as two-dimensional video, three-dimensional video including stereoscopic video).
Input human interface devices may include one or more of (only one of each depicted): keyboard 1001, mouse 1002, trackpad 1003, touch screen 1010 and associated graphics adapter 1050, data-glove, joystick 1005, microphone 1006, scanner 1007, camera 1008.
Computer system 1000 may also include certain human interface output devices. Such human interface output devices may be stimulating the senses of one or more human users through, for example, tactile output, sound, light, and smell/taste. Such human interface output devices may include tactile output devices (for example tactile feedback by the touch-screen 1010, data-glove, or joystick 1005, but there can also be tactile feedback devices that do not serve as input devices), audio output devices (such as: speakers 1009, headphones (not depicted)), visual output devices (such as screens 1010 to include cathode ray tube (CRT) screens, liquid-crystal display (LCD) screens, plasma screens, organic light-emitting diode (OLED) screens, each with or without touch-screen input capability, each with or without tactile feedback capability-some of which may be capable to output two dimensional visual output or more than three dimensional output through means such as stereographic output; virtual-reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted).
Computer system 1000 can also include human accessible storage devices and their associated media such as optical media including CD/DVD ROM/RW 1020 with CD/DVD or the like media 1021, thumb-drive 1022, removable hard drive or solid state drive 1023, legacy magnetic media such as tape and floppy disc (not depicted), specialized ROM/ASIC/PLD based devices such as security dongles (not depicted), and the like.
Those skilled in the art should also understand that term “computer readable media” as used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.
Computer system 1000 can also include interface(s) to one or more communication networks (1155). Networks can for example be wireless, wireline, optical. Networks can further be local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks to include global systems for mobile communications (GSM), third generation (3G), fourth generation (4G), fifth generation (5G), Long-Term Evolution (LTE), and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks commonly require external network interface adapters (1154) that attached to certain general purpose data ports or peripheral buses (1149) (such as, for example universal serial bus (USB) ports of the computer system 1000; others are commonly integrated into the core of the computer system 1000 by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). As an example, network 1055 may be connected to peripheral bus 1049 using network interface 1054. Using any of these networks, computer system 1000 can communicate with other entities. Such communication can be uni-directional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbus to certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces (1154) as described above.
Aforementioned human interface devices, human-accessible storage devices, and network interfaces can be attached to a core 1040 of the computer system 1000.
The core 1040 can include one or more Central Processing Units (CPU) 1041, Graphics Processing Units (GPU) 1042, specialized programmable processing units in the form of Field Programmable Gate Areas (FPGA) 1043, hardware accelerators 1044 for certain tasks, and so forth. These devices, along with Read-only memory (ROM) 1045, Random-access memory (RAM) 1046, internal mass storage such as internal non-user accessible hard drives, solid-state drives (SSDs), and the like 1047, may be connected through a system bus 1048. In some computer systems, the system bus 1048 can be accessible in the form of one or more physical plugs to enable extensions by additional CPUs, GPU, and the like. The peripheral devices can be attached either directly to the core's system bus 1048, or through a peripheral bus 1049. Architectures for a peripheral bus include peripheral component interconnect (PCI), USB, and the like.
CPUs 1041, GPUs 1042, FPGAs 1043, and accelerators 1044 can execute certain instructions that, in combination, can make up the aforementioned computer code. That computer code can be stored in ROM 1045 or RAM 1046. Transitional data can be also be stored in RAM 1046, whereas permanent data can be stored for example, in the internal mass storage 1047. Fast storage and retrieve to any of the memory devices can be enabled through the use of cache memory, that can be closely associated with one or more CPU 1041, GPU 1042, mass storage 1047, ROM 1045, RAM 1046, and the like.
The computer readable media can have computer code thereon for performing various computer-implemented operations. The media and computer code can be those specially designed and constructed for the purposes of the present disclosure, or they can be of the kind well known and available to those having skill in the computer software arts.
As an example and not by way of limitation, the computer system having architecture 1000, and specifically the core 1040 can provide functionality as a result of processor(s) (including CPUs, GPUs, FPGA, accelerators, and the like) executing software embodied in one or more tangible, computer-readable media. Such computer-readable media can be media associated with user-accessible mass storage as introduced above, as well as certain storage of the core 1040 that are of non-transitory nature, such as core-internal mass storage 1047 or ROM 1045. The software implementing various embodiments of the present disclosure can be stored in such devices and executed by core 1040. A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the core 1040 and specifically the processors therein (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM 1046 and modifying such data structures according to the processes defined by the software. In addition or as an alternative, the computer system can provide functionality as a result of logic hardwired or otherwise embodied in a circuit (for example: accelerator 1044), which can operate in place of or together with software to execute particular processes or particular parts of particular processes described herein. Reference to software can encompass logic, and vice versa, where appropriate. Reference to a computer-readable media can encompass a circuit (such as an integrated circuit (IC)) storing software for execution, a circuit embodying logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware and software.
While this disclosure has described several exemplary embodiments, there are alterations, permutations, and various substitute equivalents, which fall within the scope of the disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the disclosure and are thus within the spirit and scope thereof.
This application is a continuation of U.S. application Ser. No. 18/122,158, filed Mar. 16, 2023, which is a continuation of U.S. application Ser. No. 17/697,402, filed on Mar. 17, 2022, which is a continuation of U.S. application Ser. No. 17/022,727, filed on Sep. 16, 2020, which claims priority under 35 U.S.C. § 119 to U.S. Provisional Application No. 62/905,319, filed on Sep. 24, 2019, in the United States Patent & Trademark Office, the disclosure of each of which are incorporated herein by reference in their entirety.
Number | Date | Country | |
---|---|---|---|
62905319 | Sep 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 18122158 | Mar 2023 | US |
Child | 18431652 | US | |
Parent | 17697402 | Mar 2022 | US |
Child | 18122158 | US | |
Parent | 17022727 | Sep 2020 | US |
Child | 17697402 | US |