| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
_set_output_state returns a reference to the codec state.
CID #1212170
|
|
|
|
| |
CID #1212158
|
|
|
|
| |
CID #1212164
|
|
|
|
|
|
| |
CID #1212139
CID #1212140
CID #1212141
|
|
|
|
|
|
| |
By making it go through the error path that takes care of cleanups
CID #1212168
|
|
|
|
|
|
| |
It does not makes sense and asserts.
Based on 7f9aac386fd5d5921c80100889a5f212c0148a88 from gst-plugins-base.
|
| |
|
|
|
|
| |
An atomic is enough, they can only be set once.
|
|
|
|
|
|
| |
This is not needed anymore if the gst_pad_link checks nothing.
This reverts commit a303375a3f5c12e97ca8bf50b5a93ce8652faf23.
|
| |
|
| |
|
|
|
|
|
| |
We're a subclass, so we can just take the object lock and iterate the list
directly.
|
|
|
|
| |
Process it like downstream getcaps
|
| |
|
|
|
|
|
| |
It was already the case, now be more explicit about that, and remove useless
lock/ref/unlock/unref dances.
|
|
|
|
| |
Simplifies the code
|
|
|
|
| |
NULL is valid GList
|
|
|
|
| |
A reconfigure could trigger a change of contents instead of just reconfiguring the internal element
|
| |
|
|
|
|
|
|
| |
Remove trailing empty line from commit bfdc54395238c04fc6e5b51880c2d706f33e9011
https://bugzilla.gnome.org/show_bug.cgi?id=729614
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=721685
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729614
|
|
|
|
|
|
| |
Signed-off-by: Sanjay NM <sanjay.nm@samsung.com>
https://bugzilla.gnome.org/show_bug.cgi?id=729614
|
| |
|
|
|
|
|
|
| |
Also allow disabling the timeout by setting it to 0.
https://bugzilla.gnome.org/show_bug.cgi?id=726156
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=726802
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729200
|
|
|
|
|
|
|
| |
They are very confusing for people, and more often than not
also just not very accurate. Seeing 'last reviewed: 2005' in
your docs is not very confidence-inspiring. Let's just remove
those comments.
|
| |
|
|
|
|
|
|
|
|
| |
This should not harm regular files, since those are the last 4 bytes of
a normal file.
This allows to handle playback of concatenated mpeg-ps files. Seeking and
duration reporting is still wrong though.
|
|
|
|
| |
CID 1204274
|
|
|
|
|
|
|
|
|
| |
Testing mpegversion when mpegaudioversion was likely meant.
Similar tests in sys/androidmedia/gstamcaudiodec.c also test
mpegaudioversion with the same conditional code.
Coverity 206071
|
|
|
|
|
|
|
|
|
|
| |
If framerate is unknown, we write the maximum framerate
allowed for this profile/level:
https://tools.ietf.org/html/draft-ietf-avt-rtp-vc1-06#section-6.1
http://wiki.multimedia.cx/index.php?title=VC-1#Setup_Data_.2F_Sequence_Layer
Coverity 1139694
|
|
|
|
|
|
| |
Use a placeholder value in that case, it's better than crashing.
Coverity 1139697
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This component is dereferenced, and later code checking for
NULL in particular cases implies it can be NULL. This likely
does not fix the coverity warning as it was seeing another
path setting component to NULL explicitely, but this was
spotted by looking at:
Coverity 1139736
Which is actually OK from what I can see since the actual
dereference of the explicit NULL pointer will not happen
if the condition that led to the NULL pointer assignment
is met, since the assignment and defeference have mutually
exclusive tests.
|
|
|
|
| |
Coverity 1139622
|
|
|
|
|
|
|
|
| |
Detect resolution changes on key frames, and propagate the resulting
caps to the src pad. Only the uncompressed data chunk is decoded, so
avoid using the new VP8 bitstream parsing library for now.
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
|
|
|
|
|
|
| |
Avoid possible division-by-zero while deriving the presentation timestamp
of the buffer. The base class will take care of any interpolation needs.
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=710855
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Search in current pending values first. For CBR streams we can very
easily end up having just one initial observations and then nothing
else (since the bitrate doesn't change).
* Use one group whether we are in that group *OR* if there is only
one group.
* If the group to use isn't closed (points are being accumulated in the
PCROffsetCurrent), use the latest data available for calculation
* If in the unlikelyness that all of this *still* didn't produce more
than one data point, just return the initial offset
|
|
|
|
|
|
|
|
|
|
| |
While the calculation done in these macros will work with 64bit
integers, they will fail if working with 32bit integers.
Force the scaling up to solve that.
This amazingly didn't introduce major issues up to now, but resulted
in bogus values in debug logs.
|
|
|
|
|
|
|
| |
Doing a hard flush on the packetizer will drop all observations, which
will eventually break push-based seeking (with BYTES segment) since
we won't know where to seek to anymore (new data would always be
considered as the beginning of the stream).
|
|
|
|
|
|
|
|
| |
We want to check whether the rate is different. We check changes in
numerator *and* denominator.
CID #1139631
CID #1139642
|
|
|
|
|
|
| |
And properly cleanup/reset the segment before returning on errors
CID #206012
|
|
|
|
|
|
|
| |
a guint will always smaller or equal to the maximum value it can
contain
CID #206049
|
|
|
|
|
|
|
|
|
| |
Also unref buffers on error, as it seems to be done in one, but
not all, error paths.
The NULL pointer part is Coverity 206112
https://bugzilla.gnome.org/show_bug.cgi?id=727889
|
| |
|
|
|
|
|
|
|
| |
packet_buffer has already been cleared in all code paths leading
to this point.
CID #1199696
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=727894
|
|
|
|
|
|
|
| |
Turns out glib aborts on allocation failure, so this is pointless.
We'll just ignore Coverity warnings on such constructs.
This reverts commit d347809a82e24057302f948269392e76aaacea10.
|