summaryrefslogtreecommitdiff
path: root/gst/videoparsers
AgeCommit message (Collapse)AuthorFilesLines
2018-09-10h265parse: Fix periodic SPS/PPS sending work after a seekSeungha Yang1-1/+5
Apply the commit ef71b61 See also https://bugzilla.gnome.org/show_bug.cgi?id=742212 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Add support insert parameter set per IDRSeungha Yang2-112/+132
Apply commits 0c04e00, bf0d952 and a0876aa to h265parse. See also https://bugzilla.gnome.org/show_bug.cgi?id=766803 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Don't discard first AU delimiterSeungha Yang1-0/+6
Apply the commit 48a1f27 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Consider SEI NALU as "HEADER" packetsSeungha Yang1-0/+1
Apply the commit 69c09c3 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Don't unref buffer that was unreffed just a few lines before alreadySeungha Yang1-1/+0
Apply the commit 9b50a12 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Reset the parser information when caps changesSeungha Yang1-19/+36
Apply the commit 14f6fcd https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Fix collection of access units to preserve config headersSeungha Yang1-2/+9
Apply the commit 7d44a51 See also https://bugzilla.gnome.org/show_bug.cgi?id=732203 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Improve conditions for skipping NAL unitsSeungha Yang1-14/+36
See also https://bugzilla.gnome.org/show_bug.cgi?id=732203 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Introduce new state tracking variablesSeungha Yang2-1/+33
Direct applying the commit 7bb6443. 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
2018-09-10h265parse: Fix and optimize NAL collection functionSeungha Yang1-3/+3
Adopt h264parse's _collect_nal() behavior. See also commit 5601c87 and https://bugzilla.gnome.org/show_bug.cgi?id=732154 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Unref/replace force_key_unit_event in gst_h265_parse_resetSeungha Yang1-1/+1
Apply the commit 36a2aca https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-09-10h265parse: Copy over DISCONT flag from input buffersSeungha Yang2-0/+14
Apply the commit 10ffa08 https://bugzilla.gnome.org/show_bug.cgi?id=754124
2018-04-25Meson: Generate pc file for all plugins in badXavier Claessens1-0/+1
https://bugzilla.gnome.org/show_bug.cgi?id=794568
2018-04-25h264parse: add constrained and progressive profilesGuillaume Desmottes1-1/+9
Those profiles have been added in the version 2012-01 and 2011-06 of the AVC spec. https://bugzilla.gnome.org/show_bug.cgi?id=794127
2018-04-11h265parse: Make caps writable before modifying themSeungha Yang1-2/+4
Fix following assertion failure GStreamer-CRITICAL **: gst_structure_remove_field: assertion 'IS_MUTABLE (structure)' failed https://bugzilla.gnome.org/show_bug.cgi?id=795032
2018-03-21h264parse: reset internal 'state' variable properlyBrendan Shanks1-0/+1
Reset the internal 'state' variable when the parser is started, fixes errors when parser is being re-used. https://bugzilla.gnome.org/show_bug.cgi?id=794537
2018-03-05h265parse: add support for 'Format range extensions profiles'Guillaume Desmottes1-0/+40
Those profiles have been introduced in version 2 of the HEVC spec (A.3.5). https://bugzilla.gnome.org/show_bug.cgi?id=793876
2018-03-05h265parser: decouple GstH265Profile and GstH265ProfileIDCGuillaume Desmottes1-14/+18
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
2018-03-02Revert "h265parse: early set src caps when input not byte-stream"Nicolas Dufresne1-4/+0
This reverts commit 93d29e80300f566b7a8e7d86beecb578fe03821c.
2018-03-02Revert "h264parse: early set src caps when input is avc"Nicolas Dufresne1-5/+0
This reverts commit 5ac886d85aab4b919f84fb80e2d1ef36dc8e647d.
2018-01-24h26{4,5}parse: expose chroma format and bit depth in capsGuillaume Desmottes2-0/+56
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
2017-12-07h264parse: make caps writable before modifying themTim-Philipp Müller1-2/+4
https://bugzilla.gnome.org/show_bug.cgi?id=790628
2017-11-25h263parse: Add debug log for more annexes when plustypeStian Selnes1-0/+6
2017-11-24h265parse: early set src caps when input not byte-streamGuillaume Desmottes1-0/+4
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
2017-11-24h264parse: early set src caps when input is avcGuillaume Desmottes1-0/+5
When input is in AVC 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. https://bugzilla.gnome.org/show_bug.cgi?id=790709
2017-11-22h265parse: put downstream caps first if possible on sink capsGuillaume Desmottes1-14/+21
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
2017-11-22h264parse: put downstream caps first if possible on sink capsGuillaume Desmottes1-14/+21
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. https://bugzilla.gnome.org/show_bug.cgi?id=790628
2017-07-21tsmux/tsdemux: Add support for JPEG2000Aaron Boxer2-2/+2
Based on patches by Milos Seleceni. https://bugzilla.gnome.org/show_bug.cgi?id=753323
2017-07-17jpeg2000parse: support 2-component imagesAaron Boxer1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=784797
2017-07-17jpeg2000parse: initial support for JP2 formatAaron Boxer1-4/+7
This is a simple way of supporting JP2 : we treat is as JPC, and throw away header info. https://bugzilla.gnome.org/show_bug.cgi?id=767546
2017-07-17jpeg2000parse: Parse colorimetry, interlace-mode, field-order, ↵Aaron Boxer1-7/+38
multiview-mode and chroma-site https://bugzilla.gnome.org/show_bug.cgi?id=753323
2017-07-10jpeg2000parse: allow parsing when current caps are nullAaron Boxer1-41/+69
In this case, we assume that the format is jpc, and we infer the color space from the number of components. This allows the parser to process a jpc disk file coming from a filesrc element. https://bugzilla.gnome.org/show_bug.cgi?id=783291
2017-06-07jpeg2000parse: parse RSIZ capabilities and put profile/level into the capsAaron Boxer2-7/+150
The RSIZ capabilities tag stores the JPEG 2000 profile. In the case of broadcast profiles, it also stores the broadcast main level, which specifies the bit rate. https://bugzilla.gnome.org/show_bug.cgi?id=782337
2017-05-18h265parse: Fix calculation of codec_data buffer sizeSebastian Dröge1-2/+1
2017-05-16Remove plugin specific static build optionNicolas Dufresne1-1/+0
Static and dynamic plugins now have the same interface. The standard --enable-static/--enable-shared toggle are sufficient.
2017-05-12h265parse: fix caps leak in renegotiationVincent Penquerc'h1-1/+3
2017-05-12h264parse: fix caps leak in renegotiationVincent Penquerc'h1-1/+3
2017-05-12jpeg2000parse: fix negotiation with j2c and jpc both allowed upstreamVincent Penquerc'h1-4/+88
If upstream supports both, but downstream supports only jpc, j2c would have been selected as the first in the caps. https://bugzilla.gnome.org/show_bug.cgi?id=782221
2017-04-12docs: Port all docstring to gtk-doc markdownThibault Saunier1-3/+3
2017-03-08h264parse: frame->buffer can't be NULL in pre_push_frame()Sebastian Dröge1-2/+1
CID 1402118
2017-03-08h264parse: fix some failures in testcasesHyunjun Ko1-4/+10
Move logic of judgement whether or not to insert AU Delimiter before draining. Besides, aud_needed flag is reset to TRUE when skip. https://bugzilla.gnome.org/show_bug.cgi?id=736213
2017-03-07h264parse: insert AU delimiter only in case of byte-streamHyunjun Ko2-5/+54
Inserts AU delimeter by default if missing au delimeter from upstream. This should be done only in case of byte-stream format. Note that: We have to compensate for the new bytes added for the AU, otherwise insertion of PPS/SPS will use wrong offsets and overwrite wrong data. Also mark the AU delimiter blob const, and use frame->out_buffer for storing the output to keep baseparse assumptions valid. Original-Patch-By: Michal Lazo <michal.lazo@mdragon.org> Helped by Sebastian Dröge <sebastian@centricular.com> https://bugzilla.gnome.org/show_bug.cgi?id=736213
2017-02-27h264parse: Include `interlace-mode` in capsThibault Saunier1-0/+8
Those are the rules: In the SPS: * if frame_mbs_only_flag=1 => all frame progressive * if frame_mbs_only_flag=0 => field_pic_flag defines if each frame is progressive or interlaced, thus the mode is 'mixed' in GStreamer terms. https://bugzilla.gnome.org/show_bug.cgi?id=779309
2016-12-28mpeg4videoparse: determine intra of frame at frame parse timeMark Nauwelaerts2-11/+16
... rather than when determining when to end the frame. The opportunity to do so might not come when forced to drain, and it seems nicer anyway to do so at parse wrapup time.
2016-11-26h264parse: Fix indentationSebastian Dröge1-2/+2
2016-11-26h265parse: Fix assertion when encountering an invalid NALUSebastian Dröge1-2/+4
Error out properly instead. https://bugzilla.gnome.org/show_bug.cgi?id=775130
2016-11-26h264parse: Fix assertion when encountering an invalid NALUSebastian Dröge1-2/+4
Error out properly instead. https://bugzilla.gnome.org/show_bug.cgi?id=775130
2016-11-23h265parse: Ensure codec_data has the required size when reading number of ↵Sebastian Dröge1-1/+9
NAL arrays https://bugzilla.gnome.org/show_bug.cgi?id=774896
2016-11-23h264parse: Ensure codec_data has the required size when reading number of SPSSebastian Dröge1-0/+4
https://bugzilla.gnome.org/show_bug.cgi?id=774896
2016-11-18vc1parse: Mark pad as needing reconfiguration again if it failedSebastian Dröge1-2/+12
And return FLUSHING instead of NOT_NEGOTIATED on flushing pads. https://bugzilla.gnome.org/show_bug.cgi?id=774623
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-24 23:12:04 +0000