what's the "current" livido?

hi all,

in prep for piksel05, i've re-started development of gst-livido (livido in gstreamer wrapper, see
http://0xdf.com/?p=47), and am wondering, is there any livido version around that could be considered
current? the one from svn://dyne.org/livido seems to have various problems in livido.h, with symbols
being used before being declared and such. should i report these troubles? or is there a more current version?

in hope for some consolidation,
-dan

--

-- 
http://0xDF.com/
http://iterative.org/

_______________________________________________
piksel-dev mailing list
piksel-dev <at> bek.no
http://plot.bek.no/mailman/listinfo/piksel-dev
http://www.piksel.org

Re: what's the "current" livido?

daniel fischer wrote:

>hi all,
>
>in prep for piksel05, i've re-started development of gst-livido (livido in gstreamer wrapper, see
http://0xdf.com/?p=47), and am wondering, is there any livido version around that could be considered
current? the one from svn://dyne.org/livido seems to have various problems in livido.h, with symbols
being used before being declared and such. should i report these troubles? or is there a more current version?
>
>in hope for some consolidation,
>-dan
>
>
>  
>
Hi Dan,
nice to hear from you again, and to learn that gstreamer will have a 
livido wrapper ! It will be interesting if the mplayer developers start 
using livido (as I suspect they might). The current livido spec is here:

http://livido.dyne.org/trac.cgi/wiki/TechnicalSpecCurrent

Niels and I have been discussing this over the last few months.

Today I will make some more changes following our latest discussions,
and Niels has some final updates to the palette list.

In the next few days we will release our 1.0 proposal, and then we will
rewrite livido.h to the new spec. After this we will have updated sample
host/plugin code.

Re: what's the "current" livido?

salsaman <salsaman <at> xs4all.nl> (on Mon, 26 Sep 2005 16:07:38 +0200):

  > Everything should be complete by piksel, and we can there spend a day
  > going through the spec together.

that's cool then, i'll be patient ;) we'll see what i can do in advance (i hoped to have gst-livido in a running
state when i arrive to be able to do some filters there, but it's ok this way too. i'm not running out of work ;)

looking forward to meeting you during piksel. i hope this year the discussions will result in a usable
compromise, it is needed!

-dan

--

-- 
http://0xDF.com/
http://iterative.org/

_______________________________________________
piksel-dev mailing list
piksel-dev <at> bek.no
http://plot.bek.no/mailman/listinfo/piksel-dev
http://www.piksel.org

License/copyright for spec documentation

Hi people,
For the livido spec itself, it should be free (in every sense) for use 
by all of course. We already decided our reference implementation 
livido.h would be LGPL, and I think all the (optional) livido utility 
libraries should be too.

I don't think we discussed the license/copyright for the livido spec 
documentation now on livido.dyne.org ?

I was going to suggest we use the GNU Documentation License, but that 
allows modification, and I don't think we really want/need 100 competing 
versions of livido around the net !

What we need is something that allows for free 
distribution/use/implementation of the spec, but without unauthorised 
changes. Perhaps a CC no-modify license ?

As for the copyrights for the spec, perhaps we could donate these to the 
FSF/FSF Europe ? It seems only fair since so many developers who benefit 
from the GPL have been involved. Can we arrange something like that ?

(This implies of course that to get future changes added we would have 
to go through FSF Europe, which I kind of like.)

Cheers,
Gabriel.

_______________________________________________
piksel-dev mailing list
piksel-dev <at> bek.no

Re: License/copyright for spec documentation

On Wed, 28 Sep 2005, salsaman wrote:

> Hi people,
> For the livido spec itself, it should be free (in every sense) for use by all 
> of course. We already decided our reference implementation livido.h would be 
> LGPL, and I think all the (optional) livido utility libraries should be too.
>
> I don't think we discussed the license/copyright for the livido spec 
> documentation now on livido.dyne.org ?
>
> I was going to suggest we use the GNU Documentation License, but that allows 
> modification, and I don't think we really want/need 100 competing versions of 
> livido around the net !
>
> What we need is something that allows for free 
> distribution/use/implementation of the spec, but without unauthorised 
> changes. Perhaps a CC no-modify license ?
>
> As for the copyrights for the spec, perhaps we could donate these to the 
> FSF/FSF Europe ? It seems only fair since so many developers who benefit from 
> the GPL have been involved. Can we arrange something like that ?
>
> (This implies of course that to get future changes added we would have to go 
> through FSF Europe, which I kind of like.)
>
>
>
>
> Cheers,

Re: License/copyright for spec documentation

>
>
> On Wed, 28 Sep 2005, salsaman wrote:
>
>> Hi people,
>> For the livido spec itself, it should be free (in every sense) for use
>> by all
>> of course. We already decided our reference implementation livido.h
>> would be
>> LGPL, and I think all the (optional) livido utility libraries should be
>> too.
>>
>> I don't think we discussed the license/copyright for the livido spec
>> documentation now on livido.dyne.org ?
>>
>> I was going to suggest we use the GNU Documentation License, but that
>> allows
>> modification, and I don't think we really want/need 100 competing
>> versions of
>> livido around the net !
>>
>> What we need is something that allows for free
>> distribution/use/implementation of the spec, but without unauthorised
>> changes. Perhaps a CC no-modify license ?
>>
>> As for the copyrights for the spec, perhaps we could donate these to the
>> FSF/FSF Europe ? It seems only fair since so many developers who benefit
>> from
>> the GPL have been involved. Can we arrange something like that ?
>>

Re: License/copyright for spec documentation

salsaman <at> xs4all.nl wrote:

>
>
>The first stage is to put the spec document under a CC non-change,
>attribution license, allow distribution, for commercial use license,
>listing all the contributors as copyright holders.
>
>  
>
http://creativecommons.org/licenses/by-nd/2.5/

For the livido spec document.

>If everyone agrees on this then we can discuss at piksel transferring
>copyright to FSF Europe.
>
>
>Gabriel.
>
>
>  
>

_______________________________________________
piksel-dev mailing list
piksel-dev <at> bek.no
http://plot.bek.no/mailman/listinfo/piksel-dev
http://www.piksel.org

Babl at piksel?

I was initially hoping to release 1.0 of babl at piksel, this won't
happen due to too much work at my day job, as well as hacking focus
being diverted at the moment.

I won't make it to piksel, but I have a slight glimmer of hope that
babl itself will be present in some form.

Babl is a framework providing an expandable vocabulary to describe
pixel formats, (sometimes known as palettes) as well as reference
conversions between all expressible pixel formats.

More information can be found on the babl website http://pippin.gimp.org/babl/

The reference conversions are slow, but AFAIK accurate. Babl also
provides the ability to register optimized conversion functions, that
are checked against the reference versions when a chain of conversions
between two formats -- a BablFishPath -- is constructed.
http://pippin.gimp.org/babl/BablFishPath.html shows the current
shortcut coverage.

Babl currently lacks the ability to properly handle chroma sub
sampling and dithering but is otherwise feature complete.

Any comments on the API and further optimization extensions / changes
to the vocabulary used is welcome.

/pippin

--
«The future is already here. It's just not very evenly distributed»

Re: Babl at piksel?

Øyvind Kolås wrote:
> Babl is a framework providing an expandable vocabulary to describe
> pixel formats, (sometimes known as palettes) as well as reference
> conversions between all expressible pixel formats.

> Any comments on the API and further optimization extensions / changes
> to the vocabulary used is welcome.

That is a very cool api.

Martin

_______________________________________________
piksel-dev mailing list
piksel-dev <at> bek.no
http://plot.bek.no/mailman/listinfo/piksel-dev
http://www.piksel.org

Re: Babl at piksel?

Øyvind Kolås wrote:

>I was initially hoping to release 1.0 of babl at piksel, this won't
>happen due to too much work at my day job, as well as hacking focus
>being diverted at the moment.
>
>I won't make it to piksel, but I have a slight glimmer of hope that
>babl itself will be present in some form.
>
>Babl is a framework providing an expandable vocabulary to describe
>pixel formats, (sometimes known as palettes) as well as reference
>conversions between all expressible pixel formats.
>
>More information can be found on the babl website http://pippin.gimp.org/babl/
>
>The reference conversions are slow, but AFAIK accurate. Babl also
>provides the ability to register optimized conversion functions, that
>are checked against the reference versions when a chain of conversions
>between two formats -- a BablFishPath -- is constructed.
>http://pippin.gimp.org/babl/BablFishPath.html shows the current
>shortcut coverage.
>
>Babl currently lacks the ability to properly handle chroma sub
>sampling and dithering but is otherwise feature complete.
>
>Any comments on the API and further optimization extensions / changes
>to the vocabulary used is welcome.
>
>/pippin
>