- 21 Jun, 2016 27 commits
-
-
Anton Khirnov authored
This makes the code easier to read.
-
Anton Khirnov authored
This is a more appropriate place for this. H264Context.recovery_frame is shared between frame threads, so modifying it where it is right now is invalid.
-
Anton Khirnov authored
Going through the whole decoder initialization process for a slice we are not going to decode is unnecessary and potentially dangerous.
-
Anton Khirnov authored
It is always checked in the surrounding code, so this make sure we don't see a value from an old slice.
-
Anton Khirnov authored
This is a more appropriate place for it.
-
Anton Khirnov authored
-
Anton Khirnov authored
This should make it more clear that this function does not need any decoder-global state other than the parameter sets.
-
Anton Khirnov authored
The code does some weird casting to a 2-dimensional sub-array of ref2frm. This is not necessary, since only one dimension is needed there.
-
Anton Khirnov authored
Those are unused remnants of the old SVQ3 code.
-
Anton Khirnov authored
-
Anton Khirnov authored
This will prevent conflicts e.g. in code that deals with both h264 and hevc.
-
Anton Khirnov authored
The code does not depend on the h264 decoder anymore and only needs information from h264_ps
-
Anton Khirnov authored
-
Anton Khirnov authored
This field (which the spec calls max_num_ref_frames) must be less than or equal to MaxDpbFrames, which is at most 16.
-
Anton Khirnov authored
The PS parsing code is independent from the decoder, so it makes more sense for it to have its own separate header.
-
Anton Khirnov authored
The SVQ3 decoder has been decoupled from the H.264 decoder, so it can now use its own data type.
-
Anton Khirnov authored
Move the NAL unit types into it. This will allow to stop including the whole decoder-specific h264dec.h in some code that is unrelated to the decoder and only needs some enum values.
-
Anton Khirnov authored
This is more consistent with the naming of other decoders.
-
Anton Khirnov authored
Right now this code is mixed with selecting the next output frame. Move it to a separate function called from h264_field_start(), which is a more appropriate place for this.
-
Anton Khirnov authored
-
Anton Khirnov authored
This is a more appropriate place for it.
-
Anton Khirnov authored
Doing this after ff_thread_finish_setup() is called is invalid and can conflict with reads from the other thread.
-
Anton Khirnov authored
While the value of those variables will be constant for the whole frame, they are only used in two functions called from slice header decoding. Moving them to the per-slice context allows us to make the H264Context passed to slice_header_parse() constant.
-
Anton Khirnov authored
Copy them into the decoder-global context in field_start(). This avoids modifying the decoder-global context during bitstream parsing.
-
Anton Khirnov authored
Avoid unnecessary modification of the decoder-global state in per-slice code.
-
Anton Khirnov authored
There is no bitstream parsing in that block and messing with decoder-global state is not something that belongs into header parsing. Nothing else in this function depends on the value of current_slice, except for two validity checks. Those checks are also moved out of slice_header_parse().
-
Anton Khirnov authored
Replace the decoder-global nal_unit_type/nal_ref_idc variables with the per-NAL ones. The decoder-global ones still cannot be removed because they are used by hwaccels.
-
- 20 Jun, 2016 5 commits
-
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com> Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
-
Paul B Mahol authored
Signed-off-by:
Paul B Mahol <onemda@gmail.com> Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 18 Jun, 2016 1 commit
-
-
Jerome Martinez authored
Transparency is supported only by YUV and within specific bit depths.
-
- 17 Jun, 2016 5 commits
-
-
Martin Storsjö authored
The tests are inspired by similar tests for vp9 by Ronald Bultje. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Vittorio Giovara authored
This function needs to return false, or data in the additional tables will be skipped, and the decoder will not be able to decode frames associated with them.
-
Vittorio Giovara authored
Store data from each stsd in a separate extradata buffer, keep track of the stsc index for read and seek operations, switch buffers when the index differs. Decoder is notified with an AV_PKT_DATA_NEW_EXTRADATA packet side data. Since H264 supports this notification, and can be reset midstream, enable this feature only for multiple avcC's. All other stsd types (such as hvc1 and hev1) need decoder-side changes, so they are left disabled for now. This is implemented only in non-fragmented MOVs. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
- 16 Jun, 2016 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 14 Jun, 2016 1 commit
-
-
Diego Biurrun authored
-