[Bug 673699] New: [ges] [encodebin] [pitivi] Setting video-only or audio-only encoding profiles as rendering settings does not always work
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Sat Apr 7 11:47:09 PDT 2012
https://bugzilla.gnome.org/show_bug.cgi?id=673699
GStreamer | gst-python | git
Summary: [ges] [encodebin] [pitivi] Setting video-only or
audio-only encoding profiles as rendering settings
does not always work
Classification: Platform
Product: GStreamer
Version: git
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: gst-python
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: nekohayo at gmail.com
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
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.
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list