virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-23 12:43:46 +02:00
Code Issues Releases Activity

* adding Michael's explanation to the FAQ

Browse Source 
Originally committed as revision 3411 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Roman Shaposhnik 2004-08-23 19:48:41 +00:00
parent 26efc54e4a
commit f2fe8752ab
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/faq.texi
View File

@ -14,7 +14,7 @@
ffmpeg development is now concentrated on the codec and format ffmpeg development is now concentrated on the codec and format
handling. New developments broke ffserver, so don't expect it to work handling. New developments broke ffserver, so don't expect it to work
correctly. It is planned to fix it ASAP. correctly. If you have time and experience, please help us fix it.
@section I cannot read this file although this format seems to be suppored by ffmpeg. @section I cannot read this file although this format seems to be suppored by ffmpeg.
@ -46,6 +46,12 @@ The same system is used for the other image formats.
No. FFmpeg only supports open source codecs. Windows DLLs are not No. FFmpeg only supports open source codecs. Windows DLLs are not
portable, bloated and often slow. portable, bloated and often slow.
@section Why do I see a slight quality degradation with multithreaded MPEG* encoding ?
For multithreaded MPEG* encoding, the encoded slices must be independent,
otherwise thread n would practically have to wait for n-1 to finish, so its
quite logic that there is a small reduction of quality, this is not a bug
@section How can I read from the standard input or write to the standard output ? @section How can I read from the standard input or write to the standard output ?
Use @file{-} as filename. Use @file{-} as filename.