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 686181 - [pitivi] After an async discovery is done, emit a signal with missing codecs to install
[pitivi] After an async discovery is done, emit a signal with missing codecs ...
Product: GStreamer
Classification: Platform
Component: gst-editing-services
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 721640 (view as bug list)
Depends on:
Blocks: 686182
Reported: 2012-10-15 21:13 UTC by Jean-François Fortin Tam
Modified: 2018-11-03 12:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Jean-François Fortin Tam 2012-10-15 21:13:05 UTC
GES will need to do the clip discovery for us, maintain the list of clips in a given project's library, but it should also tell us what codecs are missing so we can trigger the gstreamer codec installation dialog (if that thing still exists).
Comment 1 Jean-François Fortin Tam 2013-01-30 17:36:13 UTC
There is now a "error-loading-asset" signal in GESProject, but the problem is that it does not give us a "details" string to pass to GSt pbutils install plugins async.
Comment 2 Jean-François Fortin Tam 2013-12-17 03:53:39 UTC
In addition to the signal problem, GES might need a feature to tell it "okay the codecs for this asset and this asset have been installed, re-discover them in-place".
Comment 3 Thibault Saunier 2013-12-17 08:25:22 UTC
We mostly have the code for that in the proxy editing branch it is and around, we should cherry pick that code and add a:

    gboolean ges_asset_reload (GESAsset *asset);

method that makes use of that infrastructure.
Comment 4 Thibault Saunier 2014-11-24 22:35:53 UTC
*** Bug 721640 has been marked as a duplicate of this bug. ***
Comment 5 GStreamer system administrator 2018-11-03 12:51:46 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to'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: