search for: libmcf

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

...rface into FLAC once Alex Stewart is about to fix the specs and has a stable libuci running to allow testing of the codec interface against it. Steve is 'MCF chief engineer' ( ;-) and the backbone of MCF, and we are all anxiously waiting on him to freeze and document MCF-1 specs and update libmcf then. We have first alpha test files with MP2/3/PCM audio and uncompressed RGB video in them, and first dshow and JMF based MCF parsers for them. At the same time i am trying to motivate Cyrius to start looking into using UCI codecs from Virtualdub ( as alternative to VfW/ACM ), so that movies wit...

Josh Coalson wrote: > --- engdev <engdev@ozemail.com.au> wrote: > >>Hi, >> >>Has there been any progress on the ACM for FLAC >>that was being looked at by Steve Lhomme? > > > Haven't heard anything here about it for a long time. Sorry, I sent my reply to engdev privately (because there's no good reply to). In short I haven't worked on

...to contribute suggestions to the UCI-Devel maillist. > Thank you all for your kind consideration, > -alex 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 imple...

...have left the MCF project because of incompatibilities of our work with the project goals defined by the founder of MCF ( TMF ), Lasse 'Tronic' Karkainen, especially with respect to the latest specs Steve had been writing and documenting here http://matroska.sourceforge.net/specs/ ( replace libmcf with libmatroska, will be updated soon ) . Tronic himself could not be actively participating on the project lately, due to the fact that his courses at university didnt leave him much time to do so. Steve and myself have been developing the project further, and now we find ourselves in the situat...

...have left the MCF project because of incompatibilities of our work with the project goals defined by the founder of MCF ( TMF ), Lasse 'Tronic' Karkainen, especially with respect to the latest specs Steve had been writing and documenting here http://matroska.sourceforge.net/specs/ ( replace libmcf with libmatroska, will be updated soon ) . Tronic himself could not be actively participating on the project lately, due to the fact that his courses at university didnt leave him much time to do so. Steve and myself have been developing the project further, and now we find ourselves in the situat...

...rmat is passing Round 1 soon (see spec for more details). But now Tronic is back and don't want MCF to become that format I worked on. And since I consider it fills all past missing gaps in the specs and is far superior in expandability, I don't want that format to die. There is also a libmcf library already existing that I coded 90% a while back. And since MCF and Matroska are twins this code will be used for libmatroska, and I think we'll be able to parse/create Matroska files quite fast (we're only missing UCI then). > "Step one: Achieve something. Step two: toot...

...rmat is passing Round 1 soon (see spec for more details). But now Tronic is back and don't want MCF to become that format I worked on. And since I consider it fills all past missing gaps in the specs and is far superior in expandability, I don't want that format to die. There is also a libmcf library already existing that I coded 90% a while back. And since MCF and Matroska are twins this code will be used for libmatroska, and I think we'll be able to parse/create Matroska files quite fast (we're only missing UCI then). > "Step one: Achieve something. Step two: toot...