Re: Encoder-decoder interface question.

Hello Kondoros,

The UCI project does not want to be much more than a=20
simple encoder/decoder interface.  In particular it is
a stated goal that the interface be a very thin layer.
The only services provided by the layer are:
a) finding an appropriate codec for a format spec.
b) some common "trivial" format transforms [colorspace, etc.]
I would encourage you to look at the UCI specs and
let us know how it does or does not meet your
requirements: http://uci.sourceforge.net

Andrew Bachmann
[OpenBeOS Media Kit developer]

-----Original Message-----
From: Kondoros Attila <[email protected]>
Date: Thu, 17 Oct 2002 04:10:48 -0700 (PDT)

[snip]

Am I wasting my time or is there an interest in this=20
interface-around-tarkin thing? I know that that there=20
is some effort in the "UCI Project" but that wants to=20
be much more than a simple encoder/decoder=20
interface... Should I try to use "UCI Projects"'s
encoder/decoder interface? (I haven't checked on it
yet to see what it takes...). My interface is very 
thin and because of that I know that some things are 
missing from it,  and I should not invent another 
interface if there is one we should standardize on 
(UCI or something else anyone?).  

I'll gladly accept any critique, comment or idea you 
might have on this! If I'm missing something please 
let me know. Thanks.

Best Regards, 
 Kondoros Attila


--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to '[email protected]'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.