- 13 Oct, 2018 8 commits
-
-
Nicolas Dufresne authored
Otherwise we may endup pushing incomplete caps. This patch isn't ready yet, as it will merge PPS/SPS/VPS in the same GstBuffer. This is valid as per current definition of alignment=nal, but is also a behaviour change. It's also weird, since it only merge these for the first set.
-
Nicolas Dufresne authored
As we no longer accumulate 2 NALs before producing any data, we may endup with the case where we have completly parsed the frame data and then get called on handle_frame(). This was triggering the assertion current_off < size, as the current offset was equal to the size. Handle this just like we'd do in other case, like broken NAL etc.
-
Nicolas Dufresne authored
There is some code to fixup broken stream that uses the SEI location, this code is meant to locate SUFFIX SEI only. This should prevent unwanted side effect if SUFFIX SEI is used.
-
Nicolas Dufresne authored
This add a feature that existed in h264parse already, which is the insertion of AUD NAL whenever these are missing. This simplify the detection of frame start and also allow producing valid MPEG TS files.
-
Nicolas Dufresne authored
We no longer add latency when doing AU->AU, AU->NAL and NAL->NAL parsing.
-
Nicolas Dufresne authored
-
Nicolas Dufresne authored
Waiting for the next NAL increases the latency. If alignment=nal/au has been negotiated, assumes the the buffer contains a complete NAL and don't except a second start-code. This way, nal -> nal, au -> au and au -> nal no longer introduce latency. As a side effect, the collect_pad() function was not able to poke at the following NAL. This call is now moved before processing the NAL, so it's looking at the current NAL before it's ingested into the parser state in order to dermin if the end of an AU has been reached. The AUD injection state as been adapted to support this.
-
Nicolas Dufresne authored
When we inject a NAL in the bitstream before another one, make sure to pass both DTS and PTS. Also make sure to transfer the DISCONT flag properly.
-
- 11 Sep, 2018 12 commits
-
-
Apply the commit ef71b617 See also https://bugzilla.gnome.org/show_bug.cgi?id=742212 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply commits 0c04e004, bf0d9523 and a0876aa7 to h265parse. See also https://bugzilla.gnome.org/show_bug.cgi?id=766803 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 48a1f279 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 69c09c38 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 9b50a12b https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 14f6fcdb https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 7d44a51b See also https://bugzilla.gnome.org/show_bug.cgi?id=732203 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Direct applying the commit 7bb6443b. This could fix also unexpected nal dropping when nonzero "config-interval" is set. (e.g., gst-launch-1.0 videotestsrc ! x265enc key-int-max=30 ! h265parse config-interval=30 ! avdec_h265 ! videoconvert ! autovideosink) Similar to the h264parse, have_{vps,sps,pps} variables will be used for deciding on when to submit updated caps or not, and rather mean "have new SPS/PPS to be submitted?" See also https://bugzilla.gnome.org/show_bug.cgi?id=732203 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Adopt h264parse's _collect_nal() behavior. See also commit 5601c875 and https://bugzilla.gnome.org/show_bug.cgi?id=732154 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 36a2acae https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
Apply the commit 10ffa089 https://bugzilla.gnome.org/show_bug.cgi?id=754124
-
- 12 Apr, 2018 1 commit
-
-
Fix following assertion failure GStreamer-CRITICAL **: gst_structure_remove_field: assertion 'IS_MUTABLE (structure)' failed https://bugzilla.gnome.org/show_bug.cgi?id=795032
-
- 05 Mar, 2018 2 commits
-
-
Those profiles have been introduced in version 2 of the HEVC spec (A.3.5). https://bugzilla.gnome.org/show_bug.cgi?id=793876
-
We used to have the same enum to represent H265 profiles and idc values. Those are no longer the same with extension profiles defined from version 2 of the spec. Split those enums so the semantic of each is clearer and we'll be able to add extension profiles to GstH265Profile. Also add gst_h265_profile_tier_level_get_profile() to retrieve the GstH265Profile from the GstH265ProfileTierLevel. It will be used to implement the detection of extension profiles. https://bugzilla.gnome.org/show_bug.cgi?id=793876
-
- 02 Mar, 2018 1 commit
-
-
Nicolas Dufresne authored
This reverts commit 93d29e80.
-
- 24 Jan, 2018 1 commit
-
-
This information could be used for example to pick a decoder supporting a specific chroma and/or bit depth, like 4:2:2 10 bits. It can also be used to inform earlier decoder about the format it is about to decode. https://bugzilla.gnome.org/show_bug.cgi?id=792039
-
- 24 Nov, 2017 1 commit
-
-
Guillaume Desmottes authored
When input is not in byte-stream format there is no need to wait for the first buffer before setting src caps. We already have all the information from the input codec_data. This allow us to already configure downstream elements allowing them, for example, to already allocate their internal buffers as they know the format of the input they are about to receive. Same change as the one I just did in h264parse. https://bugzilla.gnome.org/show_bug.cgi?id=790709
-
- 22 Nov, 2017 1 commit
-
-
Guillaume Desmottes authored
Try prioritizing downstream's caps over upstream's if possible so the parser can configured in "passthrough" if possible and save it from doing useless conversions. Exact same change as the one I just did in h264parse. https://bugzilla.gnome.org/show_bug.cgi?id=790628
-
- 18 May, 2017 1 commit
-
-
Sebastian Dröge authored
-
- 12 May, 2017 1 commit
-
-
Vincent Penquerc'h authored
-
- 26 Nov, 2016 1 commit
-
-
Sebastian Dröge authored
Error out properly instead. https://bugzilla.gnome.org/show_bug.cgi?id=775130
-
- 23 Nov, 2016 1 commit
-
-
- 26 Sep, 2016 1 commit
-
-
- 30 May, 2016 1 commit
-
-
Scott D Phillips authored
vps/sps/pps id's are not required to be used contiguously. https://bugzilla.gnome.org/show_bug.cgi?id=766891
-
- 25 Apr, 2016 1 commit
-
-
Sebastian Dröge authored
Don't put level=0 into the caps, it confuses other elements. https://bugzilla.gnome.org/show_bug.cgi?id=765538
-
- 24 Mar, 2016 1 commit
-
-
- 17 Mar, 2016 1 commit
-
-
Aleksander Wabik authored
The parser handles the downstream force-key-unit event incorrectly, it tries to parse it as an upstream force-key-unit event, does not check the return value, and then uses uninitialized memory in "all_headers" boolean variable. https://bugzilla.gnome.org/show_bug.cgi?id=763793
-
- 11 Mar, 2016 1 commit
-
-
Sreerenj Balachandran authored
Create temporary ParseFrame and copy the nal size buffer region for each nal unit like we did for h264. https://bugzilla.gnome.org/show_bug.cgi?id=763494
-
- 04 Feb, 2016 1 commit
-
-
Matthew Waters authored
h265 versions of the following commits: f352691a try the current caps before querying downstream 72bc7d7f increase caps equality check for no codec_data https://bugzilla.gnome.org/show_bug.cgi?id=761014
-
- 25 Jan, 2016 2 commits
-
-
Vineeth TM authored
When sps data is NULL, the buffer allocated and mapped is not being freed. In this scenario there is no need to allocate the buffer as we are supposed to return NULL. https://bugzilla.gnome.org/show_bug.cgi?id=761070
-
Vineeth TM authored
While setting caps, codec_data buffer is mapped, but not being unmapped leading to memory leaks. https://bugzilla.gnome.org/show_bug.cgi?id=761070
-