Greetings all.. I'm sending this message out here because I suspect that some folks involved in this project might be interested in the following. If this is not the case (or this is not an appropriate forum for this sort of thing) I apologize in advance.. Project Announcement and Call for Participation ----------------------------------------------- The Universal Codec Interface (UCI) Project is aiming to create a consistent, well-designed, portable set of programming interfaces for multimedia applications and codecs to interface to one another on unix-like (and potentially other) operating systems. The UCI system is intended to provide an interface which is both consistent enough to allow easy ("plug and play") use of any codec by any application, while being flexible enough to allow sophisticated use of specialized codec features by applications designed to take more thorough advantage of certain codec implementations, or even to allow the user to control codec features of which the application itself may not be directly aware. It is not tied to any particular system or set of other libraries (such as graphical environments), and is intended to be lightweight and as efficient as possible so as not to get in the way of application/codec builders. We are interested in developing an interface which is well thought-out and meets all the needs of multimedia applications and codecs, both now and in the future. To this end, we are inviting (and encouraging) participation by any and all current multimedia developers or other interested parties, to provide input and feedback on developing UCI specifications, suggest features, contribute code, or simply keep up to date on the current state of the project. UCI is an Open-Source, Open-Spec, Peer-Directed project. Choice of licenses and related issues are still somewhat under discussion. Contributions and feedback in this area are welcome, as well. Everyone and anyone interested in contributing, knowledge, skills, critical thinking, or anything else that might be useful to this project is welcome! It is our hope that through the participation of a range of contributors from various backgrounds, we will build a system which is useful and effective for everyone's needs, and will significantly simplify the development of both platform-specific (linux, etc) and cross-platform multimedia software now and in the future. Those interested in the UCI project should visit the project web page at: http://uci.sourceforge.net/ A public UCI-Devel maillist is open to participation by everyone. To subscribe, point a web browser at: https://lists.sourceforge.net/lists/listinfo/uci-devel ..or simply send a subscription request to: uci-devel-request@lists.sourceforge.net We also have an NNTP gateway, web archives, and an IRC channel on FreeNode for discussing UCI development. More details can be found on the main project page. Some basic specifications and documentation as to the current direction of UCI development are available from the main project page. Please note that these "specifications" are preliminary and subject to change based on feedback from the larger multimedia community. If you see something that looks wrong, please feel free to contribute suggestions to the UCI-Devel maillist. Thank you all for your kind consideration, -alex
<alex@foogod.com> schrieb im Newsbeitrag news:20020924181444.H16854@firestar.foogod.com...> Greetings all.. I'm sending this message out here because I suspect thatsome> folks involved in this project might be interested in the following. Ifthis> is not the case (or this is not an appropriate forum for this sort ofthing) I> apologize in advance.. > Project Announcement and Call for Participation > ----------------------------------------------- > The Universal Codec Interface (UCI) Project is aiming to create aconsistent,> well-designed, portable set of programming interfaces for multimedia > applications and codecs to interface to one another on unix-like (and > potentially other) operating systems. > The UCI system is intended to provide an interface which is bothconsistent> enough to allow easy ("plug and play") use of any codec by anyapplication,> while being flexible enough to allow sophisticated use of specializedcodec> features by applications designed to take more thorough advantage ofcertain> codec implementations, or even to allow the user to control codec featuresof> which the application itself may not be directly aware. It is not tied toany> particular system or set of other libraries (such as graphicalenvironments),> and is intended to be lightweight and as efficient as possible so as notto get> in the way of application/codec builders. > We are interested in developing an interface which is well thought-out and > meets all the needs of multimedia applications and codecs, both now and inthe> future. To this end, we are inviting (and encouraging) participation byany> and all current multimedia developers or other interested parties, toprovide> input and feedback on developing UCI specifications, suggest features, > contribute code, or simply keep up to date on the current state of theproject.> UCI is an Open-Source, Open-Spec, Peer-Directed project. Choice oflicenses> and related issues are still somewhat under discussion. Contributions and > feedback in this area are welcome, as well. > Everyone and anyone interested in contributing, knowledge, skills,critical> thinking, or anything else that might be useful to this project iswelcome! It> is our hope that through the participation of a range of contributors from > various backgrounds, we will build a system which is useful and effectivefor> everyone's needs, and will significantly simplify the development of both > platform-specific (linux, etc) and cross-platform multimedia software nowand> in the future. > Those interested in the UCI project should visit the project web page at: > http://uci.sourceforge.net/ > A public UCI-Devel maillist is open to participation by everyone. To > subscribe, point a web browser at: > https://lists.sourceforge.net/lists/listinfo/uci-devel > We also have an NNTP gateway, web archives, and an IRC channel on FreeNodefor> discussing UCI development. More details can be found on the main project > page. > Some basic specifications and documentation as to the current direction ofUCI> development are available from the main project page. Please note thatthese> "specifications" are preliminary and subject to change based on feedbackfrom> the larger multimedia community. If you see something that looks wrong, > please feel free to contribute suggestions to the UCI-Devel maillist. > Thank you all for your kind consideration, > -alexHi folks, please allow me to raise the subject again. Anybody had the time to check http://uci.sf.net yet ? The MCF team meanwhile has decided to use UCI as the only codec interface to libmcf, at least for native MCF streams. There was also interest from the XviD team to use UCI, at least in addition to the currently existing VfW interface. A mplayer wrapper for UCI seems feasible and the OpenBeOS mediakit people show big interest to make UCI the new codec API for their opensource implementation of BeOS. Good input to UCI came from gstreamer people, especially Erik Walthinsen, its founder, and Thomas van der Stichelen. Could you consider to add a UCI interface to your codec ? IMHO we have a good chance to get some level of standardization in the opensource media world, we shouldnt miss it. Christian Sites : http://mcf.sourceforge.net http://sf.net/projects/mcf http://uci.sourceforge.net MCF mailing lists : news://news.gmane.org gmane.comp.video.mcf.general gmane.comp.video.mcf.devel gmane.comp.video.mcf.mplayer gmane.comp.video.mcf.announce gmane.comp.video.mcf.mpc gmane.comp.video.uci.devel Soon : www.corecodec.com
--- ChristianHJW <christianhjw@users.sourceforge.net> wrote:> Hi folks, > > please allow me to raise the subject again. Anybody had the time to > check > http://uci.sf.net yet ? > > The MCF team meanwhile has decided to use UCI as the only codec > interface to > libmcf, at least for native MCF streams. There was also interest from > the > XviD team to use UCI, at least in addition to the currently existing > VfW > interface. A mplayer wrapper for UCI seems feasible and the OpenBeOS > mediakit people show big interest to make UCI the new codec API for > their > opensource implementation of BeOS. Good input to UCI came from > gstreamer > people, especially Erik Walthinsen, its founder, and Thomas van der > Stichelen. > > Could you consider to add a UCI interface to your codec ? IMHO we > have a > good chance to get some level of standardization in the opensource > media > world, we shouldnt miss it.I haven't investigated UCI yet and even then I really don't have time to do an implementation. But, as of flac 1.0.4, there is a new library libOggFLAC which would probably be a good model for what you want to do, and the whole API has Doxygen-based docs (see http://flac.sf.net/api/index.html). libOggFLAC basically wraps the libFLAC encoders and decoders so that FLAC frames go into Ogg packets. Someone who knows UCI well could probably create a libUCIFLAC based on this code pretty easily. Josh __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/