After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796831 - composition: Output one single segment "per seek"
composition: Output one single segment "per seek"
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-editing-services
unspecified
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-07-18 16:59 UTC by Thibault Saunier
Modified: 2018-11-03 12:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
composition: Output one single segment "per seek" (19.67 KB, patch)
2018-07-18 17:00 UTC, Thibault Saunier
none Details | Review
composition: Output one single segment "per seek" (20.21 KB, patch)
2018-09-08 20:35 UTC, Thibault Saunier
accepted-commit_now Details | Review

Description Thibault Saunier 2018-07-18 16:59:55 UTC
See commit message.
Comment 1 Thibault Saunier 2018-07-18 17:00:02 UTC
Created attachment 373087 [details] [review]
composition: Output one single segment "per seek"

Instead of pushing a segment per new stack, output one single segment
that represents the whole duration of the composition. We now
retimestamp everything inside that segment using buffer PTS running
time.

The main goal of doing so is to avoid having the encoder drainning on
new segments which, with some encoders, leads to the introduction of
a few "silent" samples, meaning hicups/blips/blops.
Comment 2 Thibault Saunier 2018-09-08 20:35:42 UTC
Created attachment 373569 [details] [review]
composition: Output one single segment "per seek"

Instead of pushing a segment per new stack, output one single segment
that represents the whole duration of the composition. We now
retimestamp everything inside that segment using buffer PTS running
time.

The main goal of doing so is to avoid having the encoder drainning on
new segments which, with some encoders, leads to the introduction of
a few "silent" samples, meaning hicups/blips/blops.
Comment 3 Nicolas Dufresne (ndufresne) 2018-09-09 15:22:53 UTC
Review of attachment 373569 [details] [review]:

While I'm not fan of the encoder behaviour with segments, I think this change do make sense. The composition endup making the upper layer look like a single stream, not leaking the upstream complexity into the downstream elements. This change basically makes the stream time match the rendering (the output), instead of jumping around. I think it will make the nlecomposition much less of a special case, and help prevent later regressions.
Comment 4 Thibault Saunier 2018-09-09 15:34:22 UTC
I have found a big regression in that patch and am working on it :-)
Comment 5 GStreamer system administrator 2018-11-03 12:54:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-editing-services/issues/40.