GNOME Bugzilla – Bug 734970
codecparser: h264: Use proper bit_reader api while parsing buffering_period SEI
Last modified: 2014-08-21 13:02:11 UTC
Created attachment 283694 [details] [review] codecparser: h264: Use proper bit_reader api while parsing buffering_period SEI Use proper bit_reader api for parsing initial_cpb_removal_delay and initial_cpb_remvoal_delay_offset fields of buffering_period SEI messages.
Are you sure this is right? Is the length of these parameters not dynamic?
e.g. see GstH264HRDParams; and also what libav does.
Actually nevermind, I misread something.
The initial_cpb_removal_delay and initial_cpb_removal_delay_offset fields have length in bits given by initial_cpb_removal_delay_length_minus1 + 1. Here the initial_cpb_removal_delay_length_minus2 is a 5 bit field. And even the default value is 23. So we should use READ_UINT32 macro .
Yes, sorry. Pushed, thanks: commit e93551d5b0e08eac5fd9ad899bf814cb8d349bd6 Author: Sreerenj Balachandran <sreerenj.balachandran@intel.com> Date: Sun Aug 17 01:42:05 2014 +0300 codecparser: h264: Use proper bit_reader api while parsing buffering_period SEI https://bugzilla.gnome.org/show_bug.cgi?id=734970