GNOME Bugzilla – Bug 673699
[ges] [encodebin] [pitivi] Setting video-only or audio-only encoding profiles as rendering settings does not always work
Last modified: 2013-03-16 12:47:33 UTC
In bug #590639, we added a trivial change in pitivi that basically only creates and adds the EncodingVideoProfile/EncodingAudioProfile to the EncodingContainerProfile depending on what the user selected or not. The result is three possible combinations: - Video+audio ("always" works) - Video only (sometimes fails) - Audio only (sometimes fails) Not only do we get scary failed assertions in the terminal, such as: GStreamer-CRITICAL **: Trying to dispose element tee2, but it is in PLAYING instead of the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. This problem may also be caused by a refcounting bug in the application or some element. ...but the render pipeline sometimes does not start/work *depending on the input codec of the files that are on the timeline*. For example, ogg{theora+vorbis} usually works (at least on my laptop, but not necessarily on my desktop) while mov{H.264+PCM} clips always seem to fail. For the sake of consistency during testing, I always rendered using the default settings/codec/muxer combo, that is ogg{dirac+flac}. I'm not sure if the bug is in pygst, encodebin, GES, or something else.
Screencast or it didn't happen: http://jeff.ecchi.ca/public/gstreamer-673699.webm In this video, initially I'm demonstrating with ogg theora as the input (which works), then replace it with a .MOV file (which fails).
Does this still happen with gst-python from master and pygi?
> Does this still happen with gst-python from master and pygi? No reply for 3 months, closing. Please re-open if this still happens with pygi, thanks.