GNOME Bugzilla – Bug 582462
souphttpsrc should set caps for "audio/L16" mime_type
Last modified: 2009-05-21 22:33:34 UTC
If an http server streams raw audio as described in RFC 2586[1], a decodebin2 element connected after souphttpsrc in a pipeline is unable to guess the type of media being streamed. This could be solved by adding special support for "audio/L16" mimetype: it should set the caps appropriately on the outgoing buffer(s) once it detects the said mimetype. Will provide a patch soon since this is very important in UPnP/DLNA world where I live now a days. :) [1] http://www.faqs.org/rfcs/rfc2586.html
Created attachment 135028 [details] [review] souphttpsrc: Rename icy_caps to src_caps Making way for next (real) patch.
Created attachment 135029 [details] [review] souphttpsrc: Set caps for audio/L16 content-type When "Content-Type" header is "audio/L16", we need to set the caps on the outgoing buffers so that downstream elements can have means to detect the stream type and handle it appropriately. Tested with HTTP stream provided by pulse-audio's http module (git master).
This seems reasonable to me
Should i commit?
Fine by me, and I haven't seen anyone else objecting :)
(In reply to comment #5) > Fine by me, and I haven't seen anyone else objecting :) > Done! Thanks for your quick review.
Don't forget to set your target milestone when closing bugs...