On Sunday 06 January 2008, Danny Pansters wrote:
> IMHO both xine and gstreamer were piss-poor choices for the a/v backend,
> they should have built their own infrastructure around ffmpeg instead which
> in any event is the *real* a/v engine that eventually gets used, would have
> left the multimedia backend framework basically up to themselves, possibly
> manpower shortage was the main reason for this?

Manpower, and the desire *not* to write a mm backend, but only the 80% 
solution (common functionality, no specialized needs) KDE API for the 
majority of KDE applications. It's always been a stated goal of the KDE4 MM 
framework *not* to impinge on the space where people who know what they're 
doing and who have specific needs to do MM with ffmpeg.

Ah, and arts has left a bad taste in the mouth.


-- 
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd

Reply via email to