[Bug 655257] [camerabin2][design] Removing redundant options/elements

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=655257
  GStreamer | gst-plugins-bad | git

--- Comment #7 from Luciana Fujii <luciana at fujii.eti.br> 2011-08-02 03:27:44 UTC ---
Ok, there is one big difference between using image-capture-caps and
restriction on GstEncodingProfile and I just ran into it: restrictions only
apply when the encodebin has to encode the stream. When the stream is already
encoded, they don't go through the capsfilter.

I'm assuming here camerabin2 works with cameras that provide jpeg images, for
instance. I think that is true at least if you don't use wrappercamerabinsrc.
Correct me if I'm wrong.

This is easier to happen for image capture. So the pipeline is like this:

src ! capsfilter ! ( split name=s ! converters ! capsfilter ! encoder !
combiner name=c ) ! filesink
s. ! c.

If you want to restrict, for instance, resolution, it will only work for raw
streams if you set it on restriction. It would be tricky to set it using
image-capture-caps and not force to have only raw streams though. I think in
that case you can actually add the restriction directly to the
GstEncodingProfile to restrict the encoded stream (meaning, using caps like
"image/jpeg,width=x,height=y" to create the profile),

Anyway, I still think it is a good idea, but it would be good to make this
explicit in documentation, for those like me that don't realize this difference
at first. =]

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