[Bug 647648] videorate: support for caps modifications in a running pipeline

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=647648
  GStreamer | gst-plugins-base | 0.10.32

--- Comment #4 from Nicola <lists at svrinformatica.it> 2011-06-30 18:29:26 UTC ---
Created an attachment (id=191051)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=191051)
test app that show the problem

Attached is a sample application, David I know this is not enough for you, I
hope some other developer can play with it and mark this bug as confirmed. The
app assume you have a v4l2src device and the fpsdisplay sink element. It start
this pipeline:

v4l2src ! videorate ! capsfilter name=vfps caps="video/xraw-yuv,framerate=2/1"
! fpsdisplaysink

when the pipeline go to play state start a timer that after 10 seconds change
the capsfilter with the following code:

    GstElement *vfps=gst_bin_get_by_name(GST_BIN(pipe),"vfps");
    GstCaps *new_caps;
//=gst_caps_from_string("video/x-raw-yuv,framerate=15/1");
    new_caps = gst_caps_new_simple("video/x-raw-yuv",
                               "framerate",GST_TYPE_FRACTION, 15, 1,
                               NULL);
    g_object_set(G_OBJECT (vfps),"caps",new_caps,NULL);
    gst_caps_unref(new_caps);
    gst_object_unref(vfps);

well, fpsdisplaysink will continue to show 2fps even after this change,

to compile the app use qmake && make

-- 
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.