[gst-devel] jpegparse element
marc.leeman at gmail.com
Mon May 18 12:12:18 CEST 2009
> > Wim committed some work in rtpjpegpay a couple weeks ago. I had a
> > simular issue you probl have; but I used a quick decode/encode trick to
> > get the correct caps; before reconfiguring the pipeline again.
> Probably not :-) I get a stream of concatenated JPEG frames without any
> muxing, and I need to mux it into a matroska file. So the 4K souphttpsrc
> buffers have to become buffers containing 1 JPEG frame. I could indeed do a
> jpegdec-enc chain of the whole stream, but that would be quite expensive (for
> 100 parallel streams...).
Hey, that is *exactly* what I'm doing!
No, not really; I was re-payloading MJPEG/RTP and rtpjpegpay was
requiring more extensive caps than those that came from rtpjpegdepay.
So I added a dirty jpegdec ! jpegenc to get the full caps and once I got
those from a typefind; I reconfigured the pipeline to remove the
Full recoding would indeed be expensive and silly. Wim updated
rtpjpegpay to get the required params from the stream instead of from
One Bell System - it sometimes works.
crichton 2.6.26 #1 PREEMPT Tue Jul 29 21:17:59 CDT 2008 GNU/Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the gstreamer-devel