[gst-devel] float caps

[Andy Wingo]

On Thu, 05 Feb 2004, Thomas Vander Stichele wrote:

> Hi,
> 
> > > This obviously requires converters (floatconvert, ntoone, oneton (this
> > > one needs to work with float, too), int2float, float2int and maybe
> > > buffer-frames-adapt).
> > 
> > Well, ok. You have int2float and float2int (which maybe can be done with
> > audioconvert). I'll take the hit and have oneton (which should either be
> > called one2n or one-to-n) and ntoone be necessary for dsp pipelines
> > (damn you ;). Then we're OK, except for buffer-frames-adapt, which I
> > hope is never necessary, ever.
> 
> I'm trying to grok wingo's street slang.  I'm not hip to the kid's lingo
> these days :)

Sorry, I'll try to contain myself ;) Also my opinions are changing. I've
been corrupted to the dark side of audioconvert, I think. So for a
'normal' pipeline, with a hypothetical vorbisfloat element, you can
have:

filesrc ! vorbisfloat ! audioconvert ! audiosink

And for a DSP app that reads some data stored in int, you have:

intsrc ! audioconvert ! one-to-n ! ... dsp ...

And a DSP app writing int data to an audio sink,

... dsp ... ! n-to-one ! audioconvert ! intsink.

This requires some cleverness in the (de)interleaving plugins regarding
caps, and a couple more chain functions in audioconvert. Also I think
this can make int2float and float2int die, as without the interleaving
code they're pretty trivial. Does this sound sane?

Regards,

Wingo.