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 666198 - [0.11] basetransform issue in 0.11?
[0.11] basetransform issue in 0.11?
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.11.x
Other Linux
: Normal normal
: 0.11.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-12-14 20:16 UTC by Christian Fredrik Kalager Schaller
Modified: 2012-02-18 20:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
GST_DEBUG log (374.82 KB, application/x-bzip)
2011-12-14 20:16 UTC, Christian Fredrik Kalager Schaller
Details

Description Christian Fredrik Kalager Schaller 2011-12-14 20:16:11 UTC
Created attachment 203514 [details]
GST_DEBUG log

This could be a Transmageddon bug, but I have no idea what is going wrong here

** (transmageddon.py:23035): CRITICAL **: gst_video_rate_transform_caps: assertion `GST_CAPS_IS_SIMPLE (caps)' failed

(transmageddon.py:23035): GStreamer-CRITICAL **: gst_caps_is_subset: assertion `subset != NULL' failed
0:00:06.151903787 23035 0xb0c044c8 ERROR          basetransform gstbasetransform.c:517:gst_base_transform_transform_caps:<videorate0> transform_caps returned caps (NULL) which are not a real subset of the filter caps video/x-raw, width=(int)[ 1, 32767 ], height=(int)[ 1, 32767 ], pixel-aspect-ratio=(fraction)[ 1/2147483647, 2147483647/1 ], framerate=(fraction)30000/1001, format=(string){ I420, YV12, YUY2, UYVY, AYUV, RGBx, BGRx, xRGB, xBGR, RGBA, BGRA, ARGB, ABGR, RGB, BGR, Y41B, Y42B, YVYU, Y444, v210, v216, NV12, NV21, GRAY8, GRAY16_BE, GRAY16_LE, v308, Y800, Y16, RGB16, BGR16, RGB15, BGR15, UYVP, A420, RGB8_PALETTED, YUV9, YVU9, IYU1, ARGB64, AYUV64, r210 }

** (transmageddon.py:23035): WARNING **: videorate0: transform_caps returned caps which are not a real subset of the filter caps
Comment 1 Christian Fredrik Kalager Schaller 2012-01-06 13:22:27 UTC
Tested with current git master and this issue is gone, closing as fixed.