[gstreamer-bugs] [Bug 576322] cannot change caps inline to set samplerate

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=576322

  GStreamer | gst-plugins-base | Ver: 0.10.22

Stefan Kost (gstreamer, gtkdoc dev) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ensonic at sonicpulse.de




------- Comment #4 from Stefan Kost (gstreamer, gtkdoc dev)  2009-03-27 20:17 UTC -------
I can also confirm what tim said. Unfixed caps should (and for me) work fine. I
once had the problem that the caps I set on caps filter were constrained too
much and it resulted in warnings a bit unrelated at first. It looked like what
you have in comment #2. Othercaps are NULL. I would suggest to dump a pipeline
graph and look at the caps. Put a GST_DEBUG_BIN_TO_DOT_FILE_WITH_TS into your
pipeline bus error handler and run the app using GST_DEBUG_DUMP_DOT_DIR=$PWD
./myapp
Convert the dot files to pngs (dot -Tpng -oimage.png graph_lowlevel.dot) and
check the caps beein set on the pad-links.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=576322.