Re: [FFmpeg-devel] [PATCH 3/3] avcodec/cbs_h2645: rename macros to read and write fields with custom range of values

2019-04-28 Thread James Almer
On 4/28/2019 8:19 PM, Mark Thompson wrote: > On 17/04/2019 03:56, James Almer wrote: >> These are more in line with the new ones introduced in the previous commit. >> >> Signed-off-by: James Almer >> --- >> No more i() macro :p >> >> Figured I'd leave all the byte and checksum fields using the

Re: [FFmpeg-devel] [PATCH 3/3] avcodec/cbs_h2645: rename macros to read and write fields with custom range of values

2019-04-28 Thread Mark Thompson
On 17/04/2019 03:56, James Almer wrote: > These are more in line with the new ones introduced in the previous commit. > > Signed-off-by: James Almer > --- > No more i() macro :p > > Figured I'd leave all the byte and checksum fields using the custom range > macro, to have the explicit hex

Re: [FFmpeg-devel] [PATCH 3/3] avcodec/cbs_h2645: rename macros to read and write fields with custom range of values

2019-04-17 Thread James Almer
On 4/16/2019 11:56 PM, James Almer wrote: > @@ -164,9 +164,9 @@ static int FUNC(profile_tier_level)(CodedBitstreamContext > *ctx, RWContext *rw, > > for (i = 0; i < max_num_sub_layers_minus1; i++) { > if (current->sub_layer_profile_present_flag[i]) { > -us(2,

[FFmpeg-devel] [PATCH 3/3] avcodec/cbs_h2645: rename macros to read and write fields with custom range of values

2019-04-16 Thread James Almer
These are more in line with the new ones introduced in the previous commit. Signed-off-by: James Almer --- No more i() macro :p Figured I'd leave all the byte and checksum fields using the custom range macro, to have the explicit hex values visible. That's why they were not changed in the first