[gst-devel] IEC958 caps

Arun Raghavan arun.raghavan at collabora.co.uk
Tue Oct 12 15:39:43 CEST 2010


On Mon, 2010-10-11 at 22:11 -0500, pl bossart wrote:
[...]
> So the question is: how does one go about extending capabilities? Can
> I just go ahead and define new fields, eg "audio/x-iec958,
> payload=<val>", using the values defined by the IEC or CEA standards?
> Or do I need a new cap per format such as "audio/x-iec958-eac3"? Or
> are the capabilities listed somewhere in some central location to
> ensure consistency?

Extending the caps by adding a field for the payload type seems to make
the most sense to me. Then when the API becomes available, alsasink can
do a probe and update its sinkpad caps, presumably much in the way that
v4l2sink does now.

Just my 2p. :)

-- Arun





More information about the gstreamer-devel mailing list