From 59b218e4106e1c6fbf0477fbed2ab0675ed83ce6 Mon Sep 17 00:00:00 2001 From: Alexey Safronov Date: Fri, 7 Aug 2020 00:59:26 +0300 Subject: [PATCH] Fix wrong profile. Fix issue #102 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e4ccfe6..41244d6 100644 --- a/README.md +++ b/README.md @@ -681,7 +681,7 @@ If we skip the first synchronization marker we can decode the **first byte** to For instance the first byte after the synchronization marker is `01100111`, where the first bit (`0`) is to the field **forbidden_zero_bit**, the next 2 bits (`11`) tell us the field **nal_ref_idc** which indicates whether this NAL is a reference field or not and the rest 5 bits (`00111`) inform us the field **nal_unit_type**, in this case, it's a **SPS** (7) NAL unit. -The second byte (`binary=01100100, hex=0x64, dec=100`) of an SPS NAL is the field **profile_idc** which shows the profile that the encoder has used, in this case, we used the **[constrained high-profile](https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Profiles)**, it's a high profile without the support of B (bi-predictive) slices. +The second byte (`binary=01100100, hex=0x64, dec=100`) of an SPS NAL is the field **profile_idc** which shows the profile that the encoder has used, in this case, we used the **[high profile](https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Profiles)**. Also the third byte contains several flags which determine the exact profile (like constrained or progressive). But in our case the third byte is 0x00 and therefore the encoder has used just high profile. ![SPS binary view](/i/minimal_yuv420_bin.png "SPS binary view")