[haiku-commits] Re: Aw: Re: haiku: hrev47086 - in src: kits/media servers/media
- From: Julian Harnath <julian.harnath@xxxxxxxxxxxxxx>
- To: <haiku-commits@xxxxxxxxxxxxx>
- Date: Wed, 2 Apr 2014 19:35:39 +0200
Stephan AÃmus <superstippi@xxxxxx> schrieb:
> The performance concerns are rather
> pointless, given that all that will most likely ever happen from here
> on
> is the ffmpeg plugin getting fixes and supporting more and more
> formats.
> Why would there ever be additional codec plugins anymore?
*cough cough* :-)
I'm actually planning about adding some more plugins. Some time ago I
started work on a de/muxer plugin for Ogg (work on that was then
preempted though and has been sleeping since). My plan is to, over
time, create media kit plugins for at least the most important open-
source container and codec formats (such as Ogg, Matroska on the
container side, things like Vorbis and Theora on the codec side). The
idea would be to use the "native" plugins with higher priority, and for
anything that they don't support, fall back to ffmpeg.
I know that some people will view that as a waste of time, "why do
that, just use ffmpeg for it all". But then, we could always say that...
still, many thing in Haiku got their own implementations instead of
using $(popular_opensource_lib).
Personally I find it a bit sad too that we only ship the ffmpeg plugin
and the other "native" plugins we had before are not on the image
anymore. In a way, I sense a controversy coming up once I propose to
add new plugins for things which are already supported by ffmpeg...
If the view is really "nothing more than ffmpeg is needed" then that
poses the question: why even have the plugin interface at all, we could
just as well link ffmpeg into the media services.
--
So long, jua
Other related posts:
