GNOME Bugzilla – Bug 583487
automatic missing codec search
Last modified: 2009-05-25 07:59:48 UTC
Just like totem does, it would be nice if PiTiVi could plug into the codec manager thing to offer installing codecs if the user lacks some of them.
We do have missing-codec support. Did you try an unsupported file and it didn't pop up the missing-codec distribution system ?
No, the automatic codec discovery thing doesn't seem to work at all, according to user testimonials yesterday and the testing I just did (removing gst plugins bad/ugly and importing an mp3 file). All that pitivi will do is spit the usual: "URI :/home/jeff/foobar.mp3 Problème :Impossible de déterminer la durée du fichier. Informations supplémentaires :Cette séquence semble être codée dans un format qui n'accepte pas l'accès aléatoire."
Created attachment 135229 [details] [review] fix
commit a35296da01913969a163f0b614df122104c28d6b Author: Alessandro Decina <alessandro.d@gmail.com> Date: Sat May 23 12:44:42 2009 +0200 Workaround to make the missing-plugin API work when using decodebin2. Decodebin2 commits its state change to PAUSED before posting missing-plugin messages. The workaround consists in manually popping messages off the bus before doing our internal check for missing plugins. Fixes #583487.
Tried with today's pitivi on jaunty after removing the bad/ugly plugins, and I still don't get a codec install popup. I just get the same pitivi error: URI:/home/jeff/Musique/Pulse.mp3 Problem:Could not establish the duration of the file. Extra information:This clip seems to be in a format which cannot be accessed in a random fashion.
Jeff, could you provide us with a GST_DEBUG=2 PITIVI_DEBUG=5 debug log ?
You're seeing a different issue. A decoder is being plugged (ffmpeg?) but it fails to answer a DURATION query.
ok, so it is fixed. Re-closing bug :)