survey: KDE Multimedia API (or framework)
Christian Fredrik Kalager Schaller
christian at fluendo.com
Sat Dec 11 10:02:10 GMT 2004
While not officially a standard I guess libavcodec, which is part of
ffmpeg, has established itself as sort of a de-facto API for codec
developers (as most projects like Xine, GStreamer and VideoLan utilize
it.) Main problem with it is of course that ffmpeg community has so far
been relatively unresponsive on unbundling/liberating libavcodec from
the rest of ffmpeg.
On Fri, 2004-12-10 at 19:25 +0000, Charles Samuels wrote:
> On Friday 2004 December 10 07:05 pm, Matthias Kretz wrote:
> > Hi,
> > as some of you already know, I'm writing a "Requirements & Specification"
> > at Uni (for a software engineering internship) for KDE multimedia in KDE 4.
> > To get a broader perspective on what the requirements really are I want to
> > know from you what you think the KDE Multimedia API (or framework) should
> > provide.
> Hi Matthias,
> Your message reminds me that I've made a minor discovery:
> The open source world needs a standard codec interface. It can be C and
> crappy (as is by implication.. cough). This would allow us to have any API
> we want for ourselves.
> The problem is getting various open source developers to agree on something
> like this. :)
> kde-multimedia mailing list
> kde-multimedia at kde.org
More information about the kde-multimedia