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 796871 - Basic tutorial 8 (appsrc/appsink): Should directly write data from need-data signal
Basic tutorial 8 (appsrc/appsink): Should directly write data from need-data ...
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: documentation
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-07-25 07:43 UTC by Sebastian Dröge (slomo)
Modified: 2018-11-03 11:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2018-07-25 07:43:45 UTC 
Currently it schedules an idle source on the mainloop from need-data and stops that idle source from enough-data. This causes people to copy this pattern everywhere while it is usually not needed at all.

In real applications there are usually two options that make sense:

1) Directly push into the appsrc from some thread where the data is available anyway

2) Use the need-data signal to produce the data and push it into the appsrc. It's called from the basesrc thread so that's exactly where it makes sense to produce the data
Comment 1 GStreamer system administrator 2018-11-03 11:04:19 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-docs/issues/17.