Re: [gst-devel] float caps

[David S. <ds...@sc...>]

On Thu, Jan 22, 2004 at 05:28:29PM +0100, in...@pu... wrote:
> - If we allow the buffer-frames property to be 0 to mean undefined, dsp 
> elements could advertise [1 - MAX] in there templates if they want it fixed or 
> [0, MAX] if they don't care or even 0 if they require unfixed. As a bonus the 
> core would even automatically fixate to undefined behaviour.

You could also use buffer-frames={ "undefined", (int)[1-MAX] }.  I don't
necessarily recommend this, but it's possible.

> - If we split int2float and float2int each into two plugins, one doing channel 
> splitting/merging, the other doing the actual conversion, we could use 
> float2int and int2float with autoplugging. That would also solve the current 
> problems for the people that have been reporting them with int2float ! 
> float2int not working.

from a negotiation perspective, float2int and int2float are currently
_really_ painful.  They currently hold the record for most complicated
negotiation code that I've written.  Splitting the functionality into
a channel splitter/merger element would be a good idea.



dave...