Comentário enviado por darkstarfire
em 01/10/2012 - 23:27h:
Peço-lhe desculpas por qualquer mau(L) entendido, que por ventura ouve na hora de interpretar meu cometário anterior
Não gosto e não costumo causar flame... apenas fiz uma observação no meu comentário anterio conforme listo aqui "Obs: ou você está desinformado, ou então é maldade sua.", usei o termo "desinformado" pois o ffmpeg "http://ffmpeg.org/
" foi forcado no ano passado, dando origem ao libav "http://libav.org/
". Quanto ao termo "maldade sua" referia-me, caso você já soubesse da divisão do projeto ffmpeg e mesmo assim, seguindo o devs do libav, continuou aumentando o FUD.
Quanto a informação tirada do proprio pacote fornecido pela equipe do Debian, trata-se de um pequeno FUD, com um pouco de verdade, pois até a data da criação do pacote, ainda usava o nome "ffmpeg" linkado para o novo nome "avconv".
porque disse que era FUD? pois é isso mesmo FUD "*** THIS PROGRAM IS DEPRECATED ***" e pouco de verdade, se refere ao modo de compatibilidade para que os front end feitos para usar como base o "ffmpeg" podessem continuar funcionando...
sites para referência:
Obs: alguns textos tirados dos dois sites principais.
March 15, 2011
FFmpeg has been forked by some developers after their attempted takeover two months ago did not fully succeed. During these two months their repository was listed here as main FFmpeg repository. We corrected this now and list the actual main repository and theirs directly below. All improvements of their fork have been merged into the main repository already.
Sadly we lost a not so minor part of our infrastructure to the forking side. We are still in the process of recovering, but web, git and issue tracker are already replaced.
Readers who want to find out more about the recent happenings are encouraged to read through the archives of the FFmpeg development mailing list. There was also a bit of coverage on some news sites like here .
 Takeover: http://article.gmane.org/gmane.comp.video.ffmpeg.devel/123868
 GMANE FFmpeg development mailing list archive: http://dir.gmane.org/gmane.comp.video.ffmpeg.devel
 LWN.net Article: http://lwn.net/Articles/423702/
August 09 2011
Updated on 12.09.2011.
For consistency with our new name we have renamed ffplay to avplay, ffserver to avserver and ffprobe to avprobe. Their behavior is the same, just the names were changed.
With ffmpeg (the commandline tool) we decided to use this opportunity to fix some longstanding usability problems, which involves breaking compatibility. Therefore we have added a new tool named avconv which is based on ffmpeg, but has a different (hopefully more powerful and easier to use) syntax for some options. ffmpeg will be kept in its current state for some time, so no scripts or frontends using it will break. However it will not be developed further.
Differences between avconv and ffmpeg are:
The options placement is now strictly enforced! While in theory the options for ffmpeg should be given in [input options] -i INPUT [output options] OUTPUT order, in practice it was possible to give output options before the -i and it mostly worked. Except when it didn't - the behavior was a bit inconsistent. In avconv, it is not possible to mix input and output options. All non-global options are reset after an input or output filename.
All per-file options are now truly per-file - they apply only to the next input or output file and specifying different values for different files will now work properly (notably -ss and -t options).
All per-stream options are now truly per-stream - it is possible to specify which stream(s) should a given option apply to. See the Stream specifiers section in the avconv manual for details.
In ffmpeg some options (like -newvideo/-newaudio/...) are irregular in the sense that they're specified after the output filename instead of before, like all other options. In avconv this irregularity is removed, all options apply to the next input or output file.
-newvideo/-newaudio/-newsubtitle options were removed. Not only were they irregular and highly confusing, they were also redundant. In avconv the -map option will create new streams in the output file and map input streams to them. E.g. avconv -i INPUT -map 0 OUTPUT will create an output stream for each stream in the first input file.
The -map option now has slightly different and more powerful syntax:
Colons (':') are used to separate file index/stream type/stream index instead of dots. Comma (',') is used to separate the sync stream instead of colon.. This is done for consistency with other options.
It's possible to specify stream type. E.g. -map 0:a:2 creates an output stream from the third input audio stream.
Omitting the stream index now maps all the streams of the given type, not just the first. E.g. -map 0:s creates output streams for all the subtitle streams in the first input file.
Since -map can now match multiple streams, negative mappings were introduced. Negative mappings disable some streams from an already defined map. E.g. '-map 0 -map -0:a:1' means 'create output streams for all the stream in the first input file, except for the second audio stream'.
There is a new option -c (or -codec) for choosing the decoder/encoder to use, which allows to precisely specify target stream(s) consistently with other options. E.g. -c:v lib264 sets the codec for all video streams, -c:a:0 libvorbis sets the codec for the first audio stream and -c copy copies all the streams without reencoding. Old -vcodec/-acodec/-scodec options are now aliases to -c:v/a/s
It is now possible to precisely specify which stream should an AVOption apply to. E.g. -b:v:0 2M sets the bitrate for the first video stream, while -b:a 128k sets the bitrate for all audio streams. Note that the old -ab 128k syntax is deprecated and will stop working soon.
-map_chapters now takes only an input file index and applies to the next output file. This is consistent with how all the other options work.
-map_metadata now takes only an input metadata specifier and applies to the next output file. Output metadata specifier is now part of the option name, similarly to the AVOptions/map/codec feature above.
-metadata can now be used to set metadata on streams and chapters, e.g. -metadata:s:1 language=eng sets the language of the first stream to 'eng'. This made -vlang/-alang/-slang options redundant, so they were removed.
Presets in avconv are disabled, because only libx264 used them and presets for libx264 can now be specified using a private option -preset presetname.
-qscale option now uses stream specifiers and applies to all streams, not just video. I.e. plain -qscale number would now apply to all streams. To get the old behavior, use -qscale:v. Also there is now a shortcut -q for -qscale and -aq is now an alias for -q:a.
-vbsf/-absf/-sbsf options were removed and replaced by a -bsf option which uses stream specifiers. Use -bsf:v/a/s instead of the old options.
-itsscale option now uses stream specifiers, so its argument is only the scale parameter.
-intra option was removed, use -g 0 for the same effect.
-psnr option was removed, use -flags +psnr for the same effect.
-vf option is now an alias to the new -filter option, which uses stream specifiers.
-vframes/-aframes/-dframes options are now aliases to the new -frames option.
-vtag/-atag/-stag options are now aliases to the new -tag option.
Note that the avconv interface is not considered stable yet. More incompatible changes may come in the following weeks. We will announce here when avconv is stable.