this is not optimized or anything (that is easy to add just use the existing unscaled converters if possible ...)
Originally committed as revision 22236 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale
(r15249) to sws_scale() too (until now, it only was in sws_scale_ordered())
Originally committed as revision 21887 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale
Since mplayer always define CONFIG_GPL, this commit should not change
anything for mplayer.
Originally committed as revision 21699 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale
Patch by Victor Paesa <wzrlpy@arsystel.com>
Original thread:
Date: Aug 31, 2006 7:15 PM
Subject: [Ffmpeg-devel] [PATCH] Add sws_getCachedContext() to swscale library
Originally committed as revision 19667 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale
MMX2 code, because the HAVE_ defines do not have sane values here if
runtime cpudetection is used. Hopefully fixes runtime cpudetection
breakage from r19339.
Originally committed as revision 19374 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale
the +-1 issue is limited to >2tap vertical filters, so bilinear upscale was unaffected
the new code is sometime faster sometimes slower but the difference is significant (~20%) so its optional and enabled with arnd=1
Originally committed as revision 19177 to svn://svn.mplayerhq.hu/mplayer/trunk/libswscale
once when the scaler is initialized, instead of building them and freeing
them over and over. This gives massive performance improvements.
patch by Alan Curry, pacman*at*TheWorld*dot*com
Originally committed as revision 17589 to svn://svn.mplayerhq.hu/mplayer/trunk/postproc
patch replaces '()' for the correct '(void)' in function
declarations/prototypes which have no parameters. The '()' syntax tell
thats there is a variable list of arguments, so that the compiler cannot
check this. The extra CFLAG '-Wstrict-declarations' shows those cases.
Comments about a similar patch applied to ffmpeg:
That in C++ these mean the same, but in ANSI C the semantics are
different; function() is an (obsolete) K&R C style forward declaration,
it basically means that the function can have any number and any types
of parameters, effectively completely preventing the compiler from doing
any sort of type checking. -- Erik Slagter
Defining functions with unspecified arguments is allowed but bad.
With arguments unspecified the compiler can't report an error/warning
if the function is called with incorrect arguments. -- Måns Rullgård
Originally committed as revision 17567 to svn://svn.mplayerhq.hu/mplayer/trunk/postproc
- Fixed PlanarToNV12Wrapper() and made it handle NV21.
- Added yuv2nv12XinC() to handle software scaling.
- Added NV12/NV21 handling to various places.
- Removed NV12 from vf_hue and vf_spp as they don't look like they can
actually handle it.
Originally committed as revision 14716 to svn://svn.mplayerhq.hu/mplayer/trunk/postproc