| Age | Commit message (Collapse) | Author |
|---|
|
Otherwise output buffer and segment would not be serialized as expected
|
|
|
|
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/784>
|
|
|
|
|
|
This was broken by the rewrite, receiving gaps on the main pad
should let the position progress, reset timeouts and keep the main
pad active.
This picks the simplest solution, transforming gap events into GAP
buffers and letting them go through chain(), this achieves the desired
effect.
|
|
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/780>
|
|
We don't need all those.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/780>
|
|
Keeping the upload-part-retry-duration & complete-upload-retry-duration
properties changes the semantics in comparison to their usage in
rusotos3sink. Deprecate these two properties and add a warning while
making them noop.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/759>
|
|
Now that migration to AWS SDK is complete, rename directory and
references to aws/AWS SDK.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/759>
|
|
Rename all the elements to use aws prefix now but still register a
backwards compat element factory.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/759>
|
|
Now that all elements are migrated to AWS SDK drop the rusoto
dependencies.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/759>
|
|
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/759>
|
|
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/759>
|
|
See https://github.com/clap-rs/clap/issues/3822
|
|
|
|
|
|
|
|
|
|
|
|
Add new properties so that user can specify output raw audio and/or
video format of fallback stream (output of testsrc or still image)
|
|
We shouldn't leave the used clock ID around. Otherwise, we might never
schedule a new timeout from an inactive pad if the active pad doesn't
get a buffer.
|
|
Dedupe the code and use the function that does the exact same thing.
|
|
|
|
Those are not reliable either.
|
|
|
|
For instance when dealing with a variable framerate media stream,
input media buffers may not hold a duration, in which case we try
to calculate one by waiting for the following buffer.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/765>
|
|
We could otherwise busy loop in aggregate forever when the meta
sink pad received EOS.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/765>
|
|
`schedule_timeout` can synchronously call `handle_timeout` and change the
active pad. We need to update `is_active` afterwards.
After calling `schedule_timeout` with `end_running_time`, we used to
assume there was no pad switch and reset `switched_pad` immediately. If
the pad actually got switched, this would make us miss a sticky events
update.
|
|
|
|
Convenient tracer to dump all the existing pipelines when receiving the
SIGUSR1 Unix signal.
|
|
|
|
|
|
On unclean input, PTS/DTS might go backwards a bit and in those cases
calculate a duration of 0 instead of panicking.
|
|
accumulated durations
Durations might accumulate rounding errors and streams might not
actually start at the same time. For that reason also start with the
stream that has the lowest timestamp.
|
|
|
|
This allows muxing even if some streams are sparse or have big gaps.
|
|
|
|
This variant supports H264/5, JPEG, alaw, mulaw and G726.
|
|
|
|
PTS/DTS might go backwards if the input is borderline broken but that
shouldn't cause a panic.
|
|
The RTP depayloader base class does not take care of this in any way and
it has to be done manually.
|
|
|
|
|
|
|
|
|
|
Not yet exposed from the element.
|
|
multiple streams
|
|
Instead of declaring them to be in the `tfhd` but not writing them into
the `tfhd` but also not the `trun`.
|
|
As described in issue #200, we hold the srcpad's stream lock in some
situations where we notify the `active-pad` property.
If there's a handler installed it will most likely attempt to read the
property, which had to take the `state` lock. Another thread could
already be holding this lock and attempting to obtain the srcpad's
stream lock. This resulted in a deadlock.
To avoid this, move the `active_sinkpad` field into its own Mutex, which
we never hold for long.
Fixes: https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/issues/200
|
