Re: Re: An apology about the mass subscription to media-api list - and the reasons why .....
Enrico Weigelt <[email protected]>
| Newsgroups | gmane.comp.multimedia.media-api |
|---|---|
| Message-ID | <[email protected]> |
* Steve Lhomme <[email protected]> [2004-01-02 13:24:05 +0100]: <snip> > http://www.ordinateur-dj.org/overview.html hmm, somethings to mention: 1. we should not enforce threading - in many situations select()-loops perform much better (also many systems dont have MT) 2. GUI should not belong into the same process - better several processes (okay, that goes OT for media-api) 3. We should not limit to one fixed internal encoding/resolution. Better let all devices tell their supported formats and additional metric information for them. 4. How should speed modification work together w/ timestamps ? Are they also stretched ? How does the buffer management work then ? Some Ideas we should think about: 1. We have several kinds of devices. Some have only output, some only input. (thats not really correct, since they all do IO, but its not always in the scope of the api, but in the scope of the OS) 2. Latency of devices can vary. Each device must be able to tell the world, how much latency it has on some specific rate and encoding. 3. How could we implement frame skipping (like mplayer's -framedrop) ? 4. How to handle seeking ? 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/