- Apr 07, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Apr 06, 2017
-
-
Edward Hervey authored
AudioSpecifigConfig is used in a variety of AAC streams but was being parsed differently. Instead, make everyone use the same parsing. * Remove unused 'bits' field (it was always set to 0 if present) * Add proper GAConfig parsing (to know the number of samples per frame if present). Fixes wrong rate/channels configuration in streams coming from qtdemux https://bugzilla.gnome.org/show_bug.cgi?id=780966
-
- Apr 05, 2017
-
-
Nicolas Dufresne authored
The previous patch was using %llu for 64bits printf, which is 32bit specific. We also trace the latency in time human readable form now.
-
Without a specified framerate from the sink, the decoder frame interval should be set using the framerate of the encoded video stream. Therefore, the v4l2object should be able to change the framerate on the output if the V4L2 device accepts it. This is also necessary for mem2mem encoders so that their bitrate calculation code may work correctly and they may report the correct frame duration on the capture queue. https://bugzilla.gnome.org/show_bug.cgi?id=779466
-
If the duration of the v4l2object is GST_CLOCK_TIME_NONE, because the sink did not specify a framerate in the caps and the driver accepts the framerate, the decoder element uses GST_CLOCK_TIME_NONE to calculate and set the element latency. While this is a bug of the capture driver, the decoder element should not use the invalid duration to calculate a latency, but print a warning instead. https://bugzilla.gnome.org/show_bug.cgi?id=779466
-
The correct behaviour of anything stuck in the ->render() function between ->unlock() and ->unlock_stop() is to call gst_base_sink_wait_preroll() and only return an error if this returns an error, otherwise, it must continue where it left off! https://bugzilla.gnome.org/show_bug.cgi?id=774945
-
Jan Schmidt authored
At least output an element warning on the bus when we encounter a frame format GStreamer doesn't currently support.
-
- Apr 04, 2017
-
-
Edward Hervey authored
According to ISO/IEC:14496-2:2009 , in the case of HE-AACv2 (audioObjecType 29) parametric stereo is used (a single mono track is used and then transformations are applied to it to provide a stereo output). We therefore report two channels in the case where there is one reported in the audioChannelConfiguration. Fixes the various issues where a demuxer would report two channels, but then the parser would say there's only one channel, and then the decoder would output two channels.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
last_buf is the one we're going to write next, not buf. As such we should check timestamps against that one if there is one to select the earliest pad. Also remember the currently selected pad in the very beginning when storing the first last_buf. This both solves some edge cases where not the correct next pad was selected corresponding to the target interleave.
-
Sebastian Dröge authored
-
- Apr 03, 2017
-
-
Edward Hervey authored
This is an update of d78d5896 We still exit as early as possible in case of non-ok/non-unlinked combined flow, but we first make sure that we update the internal position variables. This ensures that if upstreams "ignores" the flow return (and carries on pushing), we don't end up processing data with completely bogus variables/positions.
-
- Mar 31, 2017
-
-
Douglas Bagnall authored
If self->channel_positions == NULL (which seems unlikely), self->default_channels_ordering_map will be used unintialised. We avoid that by keeping track of the channel_mask, which is set when the ordering map is initialised. https://bugzilla.gnome.org/show_bug.cgi?id=780331
-
Douglas Bagnall authored
When there are more than 64 channels, we don't want to exceed the bounds of the ordering_map buffer, and in these cases we don't want to rempa at all. Here we avoid doing that. https://bugzilla.gnome.org/show_bug.cgi?id=780331
-
- Mar 28, 2017
-
-
Thibault Saunier authored
It is avalaible in meson 0.36 which is now are requirement
-
Thibault Saunier authored
-
Thibault Saunier authored
-
Thibault Saunier authored
-
- Mar 27, 2017
-
-
Sebastian Dröge authored
The mdat generally does not start at offset 0, we have to include the size of the moof and whatever else was in front of the mdat.
-
Sebastian Dröge authored
CID 1403262
-
- Mar 24, 2017
- Mar 23, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Mar 22, 2017
-
-
Enrique Ocaña González authored
TFDTs with time 0 are being ignored since commit 1fc3d42f. They're mistaken with the case of not having TFDT, but those two cases must be distinguished in some way. This patch passes an extra boolean flag when the TFDT is present. This is now the condition being evaluated, instead of checking for 0 time. https://bugzilla.gnome.org/show_bug.cgi?id=780410
-
Sebastian Dröge authored
If we have multiple tracks with timecodes, or it's not the first track that has timecodes, or not the first buffer, we already started a chunk for media data. We now need to "close" that chunk because we wrote data for the timecode track and a new chunk has to be started for the original track the next time it has data.
-
Sebastian Dröge authored
There could be multiple video tracks with timecodes.
-
- Mar 21, 2017
-
-
Jan Schmidt authored
Similar to what was done in adaptivedemux, ignore seek events we've already handled - such as when they are received on every srcpad of files with lots of streams.
-
Sebastian Dröge authored
Otherwise mdatleft will have a value calculated from the initial mdatsize minus the parts of the stream that we saw, which is not including all the parts of the stream that might've been skipped.
-
- Mar 20, 2017
-
-
-
George Kiagiadakis authored
Mostly explaining the difference between rtprtxqueue and rtprtxsend.
-
- Mar 18, 2017
-
-
Nicolas Dufresne authored
It didn't match between AutoMake and Meson, and the Meson name didn't math the plugin name (video4linux2).
-
- Mar 17, 2017
-
-
-
Vincent Penquerc'h authored
This reverts commit 29b80768, while fixing the original breaking tests/check/pipelines/flacdec.
-
Vincent Penquerc'h authored
This breaks gst-validate on the build server (though not locally), and a unit test, and I can't run unit tests right now for some unrelated reason. This reverts commit 0747b56f.
-
- Mar 16, 2017
-
-
George Kiagiadakis authored
This debug statement is meant to print the time since the last (early) RTCP transmission, not the last regular RTCP transmission (which also happens to be set a few lines above to current_time, so the debug output is just confusing)
-
George Kiagiadakis authored
This is printed too often (for every chained buffer!) and just clutters the logs.
-
-