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 668341 - [0.11] unable to mux into Matroska
[0.11] unable to mux into Matroska
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.11.x
Other Linux
: Normal normal
: 0.11.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 668665 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-01-20 13:06 UTC by Christian Fredrik Kalager Schaller
Modified: 2012-02-18 23:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Fredrik Kalager Schaller 2012-01-20 13:06:08 UTC
Getting the following from Transmageddon when trying to create a matroska file with Vorbis and Theora

GStreamer-CRITICAL **: gst_value_set_bitmask: assertion `GST_VALUE_HOLDS_BITMASK (value)' failed
sys:1: Warning: g_value_init: assertion `value != NULL' failed

GStreamer-CRITICAL **: gst_value_set_bitmask: assertion `GST_VALUE_HOLDS_BITMASK (value)' failed

GStreamer-CRITICAL **: gst_event_has_name: assertion `GST_IS_EVENT (event)' failed

GStreamer-CRITICAL **: gst_event_has_name: assertion `GST_IS_EVENT (event)' failed

GStreamer-CRITICAL **: gst_event_has_name: assertion `GST_IS_EVENT (event)' failed

GStreamer-CRITICAL **: gst_event_has_name: assertion `GST_IS_EVENT (event)' failed

GStreamer-CRITICAL **: gst_event_has_name: assertion `GST_IS_EVENT (event)' failed

GStreamer-CRITICAL **: gst_event_has_name: assertion `GST_IS_EVENT (event)' failed
Comment 1 Christian Fredrik Kalager Schaller 2012-01-20 13:07:59 UTC
GST_DEBUG log:

http://www.linuxrising.org/files/misc/matroskadebug.txt.bz2
Comment 2 Vincent Penquerc'h 2012-01-24 12:03:36 UTC
Works for me with latest 0.11 and latest Transmageddon.
I tried to convert your gravity.mpg test file to a Matroska/Vorbis/Theora ouput.
Can you check if you still get the issue with 0.11 git ?
Comment 3 Vincent Penquerc'h 2012-01-24 13:10:31 UTC
Wait - it'd probably been using 0.10, even as I installed 0.10.
How to you tell Transmegeddon to switch between 0.10 and 0.11 ?
Comment 4 Christian Fredrik Kalager Schaller 2012-01-26 09:09:04 UTC
You have to use the 0.11 branch of Transmageddon, but Slomo worked on this yesterday and fixed some of the issues involved. Errors gone, but 0 byte file created atm., using gst-launch test pipeline:

gst-launch-0.11 -v filesrc location=/home/cschalle/Videos/output.ogg ! decodebin name="decode" decode. ! videoflip ! videoconvert ! theoraenc ! queue name="video" ! matroskamux name=mux ! filesink location=/tmp/output2.mkv decode. ! queue name="audio" ! audioconvert ! audioresample ! audiorate ! vorbisenc ! mux.
Comment 5 Christian Fredrik Kalager Schaller 2012-01-26 09:11:48 UTC
*** Bug 668665 has been marked as a duplicate of this bug. ***
Comment 6 Vincent Penquerc'h 2012-01-26 11:05:46 UTC
Is this the repo at git://git.gnome.org/transmageddon ?
I don't see a 0.11 branch here:

$ git branch -a
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/gtk3
  remotes/origin/master

Is this only showing a subset of branches or have I got the wrong repo ?
Comment 7 Christian Fredrik Kalager Schaller 2012-01-26 11:37:18 UTC
Sorry for confusion, the 0.11 branch is the GTK3 branch
Comment 8 Sebastian Dröge (slomo) 2012-01-26 14:01:54 UTC
This is fixed in 0.11 now