GNOME Bugzilla – Bug 659139
gstpad: make some debug traces more useful
Last modified: 2011-09-16 11:12:45 UTC
Created attachment 196612 [details] [review] gstpad: make some debug traces more useful
What is GST_BUFFER_CAPS() is NULL ?
You can have buffers with NULL caps (without being a bug elsewhere) ?
Created attachment 196654 [details] [review] gstpad: make some debug traces more useful
> You can have buffers with NULL caps (without being a bug elsewhere) ? Yes, that just means "same as previous buffer". The first buffer must have caps though (and really, all buffers *should* have caps, still..). There's also the case of e.g. filesrc or souphttpsrc or so which don't put caps on buffers and leave downstream to typefind them. I've changed it so that it just doesn't mention the type if the buffer has NULL caps, I don't think putting "[NULL caps]" in the log will add much information (but more noise, IMHO). commit 91c217c714ceb052cecdbab61f48a1e3fb9955f7 Author: Vincent Penquerc'h <vincent.penquerch@collabora.co.uk> Date: Thu Sep 15 13:20:15 2011 +0100 pad: make some debug traces more useful https://bugzilla.gnome.org/show_bug.cgi?id=659139 PS: when you attach an updated patch, please make sure to check the right boxes for 'Obsoletes: [ ] previous patch'