<br><br><div class="gmail_quote">2010/9/1 Tim-Philipp Müller <span dir="ltr"><<a href="mailto:t.i.m@zen.co.uk">t.i.m@zen.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div><div></div><div class="h5">On Wed, 2010-09-01 at 12:34 +0200, Julien Isorce wrote:<br> <br> > If my X11 settings are 32 bpp then an annoying thing is that running<br> > "gst-launch-0.10 videotestsrc ! "video/x-raw-rgb, bpp=16, depth=16" !<br> > ximagesink" gives me an error from videotestsrc but I think the error<br> > should come from ximagesink.<br> ><br> > In ximagesink::gst_ximagesink_getcaps, the xcontext->caps is setup to<br> > bpp=32 and depth=24, so I think at this point it should check that<br> > this is not compatible with the required caps from my capfilter.<br> ><br> > The error is:<br> > "videotestsrc0 : Could not negotiate format"<br> > and I think it should be:<br> > "ximagesink0 : Could not negotiate format"<br> ><br> > Any comment ?<br> <br> </div></div>Well, yes. We should find a way to report errors like this better, no<br> doubt. Currently there's no way to communicate error state to the<br> upstream element that drives the pipeline and eventually errors out<br> though, it just knows the flow return and that's that. I think there's a<br> bug about this somewhere in bugzilla, but can't find it right now. Feel<br> free to file a new one.<br> <br> Cheers<br> <font color="#888888"> -Tim<br></font></blockquote><div><br></div><div>Hi,</div><div>Could you suggest me a tittle for bugzilla ? So we can find it easier. And in core or base ? </div></div>Julien