- 28 Mar, 2011 7 commits
-
-
Stefano Sabatini authored
Make the mp wrapper accept the syntax mp=filter=params as alternative to mp=filter:params. The alternative syntax is sligthly more readable and should simplify copy&paste of MPlayer filter strings to the mp filter.
-
Stefano Sabatini authored
Change position of the fade filter description, put it between drawtext and fifo descriptions.
-
Stefano Sabatini authored
-
Stefano Sabatini authored
-
Reimar Döffinger authored
-
Reimar Döffinger authored
avcodec_thread_init currently doesn't do anything at all with pthreads enabled.
-
Michael Niedermayer authored
-
- 27 Mar, 2011 12 commits
-
-
Michael Niedermayer authored
* newdev/master: ac3enc: Add codec-specific options for writing AC-3 metadata. NOT MERGED: Remove arrozcru URL from documentation sndio support for playback and record Conflicts: doc/faq.texi doc/general.texi Merged-by: Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
Fixes issue2632 if interl=1 is used or the automatic interlace detection is enabled and works. This has the advantage compared to the patch in issue2632 that it causes no speed loss and it also works when scaling is used. The disadvantage is that interlacing autodetection does not yet work very well it seems. This is the same method mplayer uses Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Aurelien Jacobs authored
Signed-off-by: Aurelien Jacobs <aurel@gnuage.org>
-
Stefano Sabatini authored
In draw_glyphs(), draw glyphs in dtext->expanded_text rather than in dtext->text. Fix crash if a strftime() sequence is used.
-
Stefano Sabatini authored
-
Justin Ruggles authored
-
Stefano Sabatini authored
This is more consistent with the terminology adopted by the aspect filter names.
-
Stefano Sabatini authored
-
Ramiro Polla authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Brad authored
Signed-off-by: Anton Khirnov <anton@khirnov.net>
-
Michael Niedermayer authored
* newdev/master: dsputil: allow to skip drawing of top/bottom edges. Split fate-psx-str-v3 into a video-only and audio-only test. Conflicts: libavcodec/dsputil.c libavcodec/mpegvideo.c libavcodec/snow.c libavcodec/x86/dsputil_mmx.c Merged-by: Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 26 Mar, 2011 21 commits
-
-
Philip Langdale authored
Signed-off-by: Philip Langdale <philipl@overt.org>
-
Philip Langdale authored
Signed-off-by: Philip Langdale <philipl@overt.org>
-
Philip Langdale authored
This reverts commit e44073ca.
-
Philip Langdale authored
This reverts commit 4ab57cff.
-
Philip Langdale authored
This reverts commit f968ef92.
-
Philip Langdale authored
-
Philip Langdale authored
As previously discussed, the CrystalHD hardware treats some PAFF clips different from others; even when input fields are always in separate packets, the hardware might return a single fieldpair for one clip and individual fields for another. Given the bogus flags set by the hardware, it is impossible to distinguish these two cases without knowing about the current picture and the next one. The hardware can usually provide the picture number of the next picture and when that is available, we can detect the two cases. When it is not available, we have to guess - and find out later if we were right or wrong. With this change, clips will play correctly unless they are PAFF where individual fields are returned *and* no next picture number is available. Generally speaking, the incorrect cases arise in the first couple of seconds of a clip as the delay calibration takes place. Once that's set, things work fine.
-
Philip Langdale authored
As previously discussed, the CrystalHD hardware returns exceptionally useless information about interlaced h.264 content - to the extent that it's not possible to distinguish MBAFF and PAFF content until it's too late. This change introduces use of the h264_parser to help bridge the gap; it can indicate if the input data is PAFF fields or not. With this clarity, some of heuristics can be removed from the code, making this less convoluted. Finally, I found an MBAFF clip that acts like non h.264 content so I had to make allowances for that. Note that I still cannot distinguish between two forms of PAFF, where the hardware either returns individual fields or a field-pair. It's not clear that there's even a spec relevant difference between the two forms, as opposed to hardware ideosyncracies.
-
Alexander Strange authored
-
Ronald S. Bultje authored
-
Ilya authored
strtol could return negative values, leading to various error messages, mainly "non-monotonically increasing dts".
-
Nicolas George authored
Currently, only S16 quad, 5.1 and 7.1 are implemented. Implementing support for other formats/layouts and capture should be straightforward. 7.1 support by Carl Eugen Hoyos.
-
Stefano Sabatini authored
Provide a non-NULL AVFormatParameters structure to av_open_input_file() in open_input_file(). This is required because otherwise av_open_input_file() will allocate and use a new format context, discarding the options set in the provided format context.
-
Stefano Sabatini authored
-
Stefano Sabatini authored
The function was only used in opt_sample_fmt() for listing the sample formats. Move list_fmts() functionality directly into opt_sample_fmt(). Als fix the warning: ffmpeg.c: In function ‘opt_audio_sample_fmt’: ffmpeg.c:2877: warning: passing argument 1 of ‘list_fmts’ from incompatible pointer type cmdutils.h:163: note: expected ‘void (*)(char *, int, int)’ but argument is of type ‘char * (*)(char *, int, enum AVSampleFormat)’
-
Reimar Döffinger authored
-
Peter Ross authored
-
Peter Ross authored
-
Peter Ross authored
-
Peter Ross authored
-
Peter Ross authored
-