Re: mm framework
Enrico Weigelt <[email protected]>
| Newsgroups | gmane.comp.multimedia.media-api |
|---|---|
| Message-ID | <[email protected]> |
* Christian HJ Wiesner <[email protected]> [2003-12-29 15:41:25 +0100]: Hi folks, <snip> > 1. UCI ( Universal Codec Interface ) : http://uci.sf.net ; Alex 'Foogod' It seems to be a good starting point, but its missing some points, i.e. an archicture for module building and dynamic loading vs static linking. All a codec/driver developer should have to do is to write its code and a small descriptor file, which contains a lists of source files per codec, external dependencies, some descriptive text and some other meta information. The rest should be completely done by the framework's build system. As the smallest functional unit we would have a module. Multiple module may be linked together to a library, which may be loaded on call. But modules also may be linked statically into a application. A module provides one or more services, which may be queried. Each service class has its own interface structure, which is derived from a base interface to allow identification. But this all belongs into a lower layer, where the codec api sits on top of. What we have to consider on the design of an audio api are exact latency measurements, especially if we're gonna work w/ networked audio. At least we need something like timestamps (which go against ntp-synced rtcs) cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT services phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [email protected] cellphone: +49 174 7066481 --------------------------------------------------------------------- Diese Mail wurde mit UUCP versandt. http://www.metux.de/uucp/