Finish initial review of chapter 4 to 6
This commit is contained in:
1 parent
ba6b505983
commit
8d252f0dbd
21 files changed
+567
-493
No files matched your search
@@ -77,9 +77,12 @@ The spatial and temporal complexity of these video sequences was measured by usi
|
||||
The values of \ac{si} and \ac{ti} calculated for the test sequences are shown in the Table~\ref{TableTestSequences} (see second column).
|
||||
|
||||
For the simulation carried out in this study the HM reference software, version $16.2$, was used \cite{HEVCReferenceSoftware162}.
|
||||
The sequences were encoded with an \ac{idr} period of $16$ frames and all the coding modes enabled, following two recommended configurations: Low-Delay (P-frames with 4 references frames) and Random-Access (B-frames with 2 reference frames in each list)~\cite{HEVCCommonTests2012}.
|
||||
In order to achieve high quality images for all coded sequences (i.e., \ac{psnr} around 40 dB) different bitrates were used, as listed in Table~\ref{TableTestSequences}.
|
||||
The sequences were encoded with an \ac{idr} period of $16$ frames and all the coding modes enabled, following two recommended configurations: \ac{ld}, i.e., P-frames with 4 references frames, and \ac{ra}, i.e., B-frames with 2 reference frames in each list~\cite{HEVCCommonTests2012}.
|
||||
These prediction structures cover the use of P-frames and hierarchical B-frames~\cite{H264ScalableOverviewSep2007}, which are commonly used in HEVC streaming~\cite{RealTimeHEVC2016}.
|
||||
In order to achieve high quality images for all coded sequences (i.e., \ac{psnr} around 40 dB) different bitrates were used, as listed in Table~\ref{TableTestSequences}. The filtering operations were disabled at slices boundaries in order to keep the slices self-contained.
|
||||
Moreover, the ratio of inter-coded blocks of each coded sequence using the default coding parameters is also shown in the third column of the table to illustrate the predictions distribution.
|
||||
|
||||
|
||||
%The following bitrates were selected to achieve high quality (i.e., around 40 dB): 1.0 Mbits/s (Kendo), 1.5 Mbits/s (Book Arrival), 4.0 Mbits/s (BQSquare, Park Scene and Race Horses) and 12.0 Mbits/s (People on Street).
|
||||
% At the decoder side, error concealment is based on motion compensation from previously decoded frames.
|
||||
% The motion field of a missing frame is obtained applying \ac{mv} extrapolation from the two closest neighbours.
|
||||
@@ -100,7 +103,7 @@ In the first set of experiments the impact of the maximum \ac{cu} size in the de
|
||||
Table~\ref{Table3:Quality_BlockSize} shows the average \ac{psnr} obtained for the three test conditions and for four different packet loss ratios. Results for the error-free scenario shows a consistent quality increase as the maximum \ac{cu} size increases, up to a maximum of 1.41 dB for the Tennis sequence when comparing the maximum \ac{cu} size of $64\times64$ with $16\times16$.
|
||||
This confirms the principle used by the \ac{hevc} standard, that allowing larger coding units lead to higher coding efficiency, achieving a maximum of 1.41~dB for the Tennis sequence which has the higher \ac{ti} parameter (see Table~\ref{TableTestSequences}). Moreover, it is also noticeable that sequences with higher amount of inter-coded blocks take less advantage of the larger \acs{cu}, by the results of the BQSquare sequence (i.e., highest ratio of inter-coded blocks and lowest quality gain in the error-free case).
|
||||
Overall, comparing the results for the error-free and data loss cases it is noticeable that similar quality gains are obtained, which are achieved due to the superior coding efficiency of larger \acs{cu}. In most of the cases the quality gains slightly decrease for increasing \acs{plr}.
|
||||
Therefore, one may conclude that the error robustness of \ac{hevc} streams is not affected by limiting the maximum \ac{cu} size. \HERE
|
||||
Therefore, one may conclude that the error robustness of \ac{hevc} streams is not affected by limiting the maximum \ac{cu} size. \todo{Complete discussion of partition unit size}
|
||||
|
||||
|
||||
%Results for the case of data loss indicate that using larger coding units leads to higher video quality.
|
||||
@@ -168,7 +171,7 @@ Figure~\ref{Figure3:QualityvsIntra} shows the average decoded video quality (\ac
|
||||
Results in the figure indicate that as the distance between intra frames increases, the decoded video quality significantly decreases.
|
||||
The quality decreasing is especially noticeable for intra periods higher than 32 frames, indicating that temporal distances greater than approximately one second are not suitable for video streaming under error-prone conditions.
|
||||
When a high temporal distance between intra frames is used, the quality decreasing is more noticeable in the People On Street and BQSquare sequences, which have higher spatial complexity (see values for \ac{si}), leading to a reduction of 13 dB and 14 dB, respectively. As spatial complexity increases the encoder rely more on temporal predictions making the bitstream more prone to error propagation.
|
||||
\HERE
|
||||
\todo{Complete discussion of intra refreshing}
|
||||
|
||||
One should also note from the results of Figure~\ref{Figure3:QualityvsIntra} that using a small distance between intra frames is not always more efficient.
|
||||
Since intra frames require higher amount of bits, the overall coding efficiency is reduced, resulting in an overall quality that decreases even in data loss conditions.
|
||||
@@ -193,7 +196,8 @@ In this sub-section the amount of bits per slice is evaluated, in order to evalu
|
||||
|
||||
Figure~\ref{Figure3:SlicePartitioning} shows the average \ac{psnr} for three difference slice partitioning modes and different \acs{plr}.
|
||||
The first mode uses a single slice per frame, corresponding to the case where slice partitioning is disabled.
|
||||
The two remaining are characterised by a different amount of bits per slice, namely 1200 and 2400 bytes per slice, respectively. In these two cases each frame has a variable number of slices. \HERE
|
||||
The two remaining are characterised by a different amount of bits per slice, namely 1200 and 2400 bytes per slice, respectively. In these two cases each frame has a variable number of slices.
|
||||
\todo{Complete discussion of slice partitioning}
|
||||
|
||||
Results reveals a clear impact of the slice partitioning on the error robustness of the \ac{hevc}, as the quality degradation as the \ac{plr} increases varies for each scheme.
|
||||
Firstly it is clearly notice the disadvantage of using a single slice per frame as it leads to the lower quality when comparing the test cases studied. This is due to the lack of refresh points within a frame, resulting in loss events that affects the whole frame which will propagate to the subsequent inter predicted frames.
|
||||
@@ -258,14 +262,14 @@ Figure~\ref{Figure3:PSNRvsFrameErrorFreeConc} illustrates the error propagation,
|
||||
The results show that when the \ac{tmvp} mode is enabled, the loss of Frame \#6 leads to significant reduction in the reconstruction quality of the subsequent frames.
|
||||
% This is true even for sequences with low motion activity as per Table~\ref{tab:sequences}.
|
||||
On the contrary, when the temporal \ac{mv} candidate is disabled, the motion information on subsequent frames is not affected by the loss of a single frame and significantly higher quality is achieved. This is the effect of breaking the temporal dependencies between \acs{mv}, which prevents erroneous \acs{mv} to propagate throughout the set of dependent frames.
|
||||
%This is more noticeable in the Low-Delay configuration because more error propagation occurs in P-frames and several frames are affected until an intra frame is decoded (refresh point).
|
||||
%This is more noticeable in the \ac{ld} configuration because more error propagation occurs in P-frames and several frames are affected until an intra frame is decoded (refresh point).
|
||||
|
||||
\begin{figure}[!t]
|
||||
\centering
|
||||
\renewcommand{\FIGSIZE}{0.76\textwidth}
|
||||
% \includegraphics[width=\FIGSIZE,page=2]{\HEVCRobustnessEvaluation/PSNRvsFrameSingleFrameTMVP}
|
||||
\input{./031_ErrorResilienceEvaluation/QualityEvaluation/PSNRvsFrameSingleFrameTMVP}
|
||||
\caption{Error propagation for Kendo sequence when Frame~\#6 is lost for the Low-Delay configuration.}
|
||||
\caption{Error propagation for Kendo sequence when Frame~\#6 is lost for the \ac{ld} configuration.}
|
||||
\label{Figure3:PSNRvsFrameErrorFreeConc}
|
||||
\end{figure}
|
||||
|
||||
@@ -273,11 +277,11 @@ On the contrary, when the temporal \ac{mv} candidate is disabled, the motion inf
|
||||
In order to further evaluate the impact of the temporal \ac{mv} dependencies on the error propagation, the \ac{hevc} streams were subject to random packet losses.
|
||||
Table~\ref{Table3:AvgPSNRWithoutTMVP} presents the average quality results, measured using the \ac{psnr}.
|
||||
As expected, the results indicate that in error-free conditions higher quality is achieved by enabling the \ac{tmvp} candidate, since higher compression efficiency is obtained because more \ac{mv} predictors are used.
|
||||
This is true for all both test conditions, \emph{i.e.}, both Low-Delay and Random-Access.
|
||||
However, in the presence of errors, the video quality significantly decreases due to low error robustness when temporal \ac{mv} candidates are used. Alternatively, average quality up to 5.17 dB of \ac{psnr} when the temporal \ac{mv} predictors are disabled is achieved in the Low-Delay configuration.
|
||||
This is true for all both test conditions, \emph{i.e.}, both \ac{ld} and \ac{ra}.
|
||||
However, in the presence of errors, the video quality significantly decreases due to low error robustness when temporal \ac{mv} candidates are used. Alternatively, average quality up to 5.17 dB of \ac{psnr} when the temporal \ac{mv} predictors are disabled is achieved in the \ac{ld} configuration.
|
||||
The results also show that the negative impact of using temporal \ac{mv} dependencies is smaller when B-frames are used. For the Random-Access, the average gain of disabling the \ac{tmvp} is 0.78 dB.
|
||||
%This also confirms the previous results of Figure~\ref{Figure3:PSNRvsFrameErrorFreeConc}.
|
||||
A higher negative impact is obtained when only P-frames are used (Low-Delay), since subsequent frames are temporally closer, leading to more accurate temporal \ac{mv} candidates.
|
||||
A higher negative impact is obtained when only P-frames are used (\ac{ld} configuration), since subsequent frames are temporally closer, leading to more accurate temporal \ac{mv} candidates.
|
||||
Moreover, the results also indicate that for higher loss ratios the negative impact of using the \ac{tmvp} does not increase as both configuration are subject to high quality degradation.
|
||||
|
||||
\begin{table}[!t]
|
||||
@@ -383,7 +387,7 @@ However, reducing the temporal dependencies of the \acs{mv} using the proposed m
|
||||
|
||||
\begin{table}[tbp]
|
||||
\centering
|
||||
\caption{Bjontegaard's average \ac{psnr} (dB) differences for all sequences tested at different frame loss conditions.} \label{Table3:AverageResultsProposed}
|
||||
\caption{BD-PSNR (dB) differences for all sequences tested at different frame loss conditions.} \label{Table3:AverageResultsProposed}
|
||||
\input{031_ErrorResilienceEvaluation/DynamicTmvp/TableDynamicTMVPPSNR.tex}
|
||||
\end{table}
|
||||
|
||||
|
||||
Reference in new issue
Block a user