[FFmpeg-devel] DVBSUBS and TXTSUBS

JULIAN GARDNER joolzg at btinternet.com
Tue May 22 21:30:27 CEST 2012

> From: Michael Niedermayer <michaelni at gmx.at>
>To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org> 
>Sent: Tuesday, 22 May 2012, 19:19
>Subject: Re: [FFmpeg-devel] DVBSUBS and TXTSUBS
>On Tue, May 22, 2012 at 06:52:54PM +0200, Clément Bœsch wrote:
>> On Tue, May 22, 2012 at 04:45:43PM +0200, Michael Niedermayer wrote:
>> > On Fri, May 18, 2012 at 07:43:51AM +0100, JULIAN GARDNER wrote:
>> > > I was wondering what the current situation is with regards to the decode chain, is there any point in my re-porting my "HARD SUBS" to the current git, we are still using 33000 on channels that need burned in subtitles.
>> > > 
>> > > I was also looking at getting subtitles working but the source would be teletext, a simple txt decoder, just for the subtitle pages.
>> > 
>> > i think there where no major changes, but maybe ubitux, iive or some
>> > other subtitle experts could comment ?
>> > 
>> This comment from Nicolas in the Trac summarizes pretty well the
>> situation: https://ffmpeg.org/trac/ffmpeg/ticket/1305#comment:2
>> Now that things seem to calm down with the audio in lavfi, we might want
>> to consider working again on subtitles to do the burning in lavfi (and
>> various other changes).
>> But before I start working on "architecture" stuff like this, I'd like to
>> check if Libav won't plan to rewrite everything differently in a few
>> months, like they did for the audio processing, audio filtering and now
>> writers in ffprobe.
>i can tell you already now libav will probably
>but why is this a problem ?
>Code and design is written in ffmpeg to the best of our abilities.
>We are human and not everything will be perfect. "Libav" will take
>our code a few month later and change it randomly (while loosing some
>names from copyright statements).
>Some of these changes will be improvments, some
>will be just equivalent changes and some will be worse.
>We will merge the ones that are better and the ones that are equivalent
>to keep differences small.
>This certainly isnt perfect and manpower could be used more efficiently
>but libav is working for ffmpeg and they have no choice at all.
>Whenever they do something better than we i switch to their code.
>Whenever they are worse i dont
>So, its not that bad IMO
>OTOH if we stop working on some part and just leave it to libav, do
>you really think quality will be at the same level ?

Well if you guys want any help from me, especially dvbsub and txtsubs then just drop me a line, i would love to be able to move our encoders to newer builds than 33000


More information about the ffmpeg-devel mailing list