taginject critical warnings (bug?)

[Andrés González]

Hi,

When setting running this pipeline:

gst-launch audiotestsrc num-buffers=100 ! taginject
tags="title=testsrc,artist=\"gstreamer\",license=\"CC by\",date=\"Mon
Apr 4 2011\"" ! vorbisenc ! oggmux ! filesink location=test2.ogg

The file is written and is playable, but
- The last metadata field is not written to the file,
- I get the following messages (Note: There are no warning messages when
three or less fields are given):


Estableciendo el conducto a PAUSA … (Setting pipeline to PAUSE...)
El conducto está PREPARÁNDOSE … (The pipeline is GETTING READY...)

(gst-launch-0.10:2137): GLib-GObject-CRITICAL **: g_value_dup_boxed:
assertion `G_VALUE_HOLDS_BOXED (value)' failed

** (gst-launch-0.10:2137): CRITICAL **: file gstvorbistag.c: line 591
(gst_tag_to_vorbis_comments): should not be reached
El conducto está PREPARADO … (the pipeline is READY ...)
Estableciendo el conducto a REPRODUCIENDO … (Setting pipeline to PLAYING...)
New clock: GstSystemClock
(etc)

Regards,
Andrés




_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Sebastian Dröge-7]

On Mon, 2011-04-04 at 10:16 +0200, Andrés González wrote:

> Hi,
>
> When setting running this pipeline:
>
> gst-launch audiotestsrc num-buffers=100 ! taginject
> tags="title=testsrc,artist=\"gstreamer\",license=\"CC by\",date=\"Mon
> Apr 4 2011\"" ! vorbisenc ! oggmux ! filesink location=test2.ogg
>
> The file is written and is playable, but
> - The last metadata field is not written to the file,
> - I get the following messages (Note: There are no warning messages when
> three or less fields are given):
>
>
> Estableciendo el conducto a PAUSA … (Setting pipeline to PAUSE...)
> El conducto está PREPARÁNDOSE … (The pipeline is GETTING READY...)
>
> (gst-launch-0.10:2137): GLib-GObject-CRITICAL **: g_value_dup_boxed:
> assertion `G_VALUE_HOLDS_BOXED (value)' failed
>
> ** (gst-launch-0.10:2137): CRITICAL **: file gstvorbistag.c: line 591
> (gst_tag_to_vorbis_comments): should not be reached
> El conducto está PREPARADO … (the pipeline is READY ...)
> Estableciendo el conducto a REPRODUCIENDO … (Setting pipeline to PLAYING...)
> New clock: GstSystemClock
> (etc)

I just fixed a similar bug:
http://cgit.freedesktop.org/gstreamer/gstreamer/commit/?id=eba33c1de11fc7fb63fb31a764d3c16698eea490

Because taginject uses gst_structure_from_string() that check doesn't
seem to trigger. Could you file a bug for this? The problem here is that
the date can't be parsed.

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Andrés González]

On 04/04/11 10:30, Sebastian Dröge wrote:

I just fixed a similar bug:
http://cgit.freedesktop.org/gstreamer/gstreamer/commit/?id=eba33c1de11fc7fb63fb31a764d3c16698eea490

Because taginject uses gst_structure_from_string() that check doesn't
seem to trigger. Could you file a bug for this? The problem here is that
the date can't be parsed.

I don't have much experience filing bugs, I hope this is right:

https://bugzilla.gnome.org/show_bug.cgi?id=646696

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel