Log of /xvidcore/src/image/image.c
Parent Directory
Revision
1.26.2.12 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Fri Dec 12 08:19:13 2003 UTC (20 years, 5 months ago) by
chl
Branch:
dev-api-4
Changes since
1.26.2.11: +12 -13 lines
Diff to
previous 1.26.2.11
, to
branch point 1.26
I thought I had commited this days or weeks ago?!?
Colorspace fix, internal format is YCrCb==CSP_I420
CSP_USER is YCrCb with arbitrary pointers and strides for Luma and Chroma
Revision
1.26.2.11 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Wed Nov 5 16:15:47 2003 UTC (20 years, 6 months ago) by
edgomez
Branch:
dev-api-4
Changes since
1.26.2.10: +15 -14 lines
Diff to
previous 1.26.2.10
, to
branch point 1.26
Patch from syskin.
* This patch avoids calling setedges and interpolate for uneeded cases:
- setedges is only called once per frame.
- interpolate is called only when the previous rounding
was different from the one needed.
* Interpolation has been optimized a bit for qpel case, we do the
hv pass down to top to use the cache more efficiently (hope so).
Revision
1.26.2.5 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Thu May 22 16:35:55 2003 UTC (21 years ago) by
edgomez
Branch:
dev-api-4
Changes since
1.26.2.4: +1 -1 lines
Diff to
previous 1.26.2.4
, to
branch point 1.26
Removed this annoying \n from DPRINTF output. DPRINTF behaves
now like usual printf.
Just for fun, i decided to exercice my regexp skills:
for i in `find . -name "*.c"` ; do
sed s/'\(DPRINTF(XVID_DEBUG.*\)"\([^"]\+[^\\][^n]\)"\(.*\)$'/'\1"\2\\n"\3'/g $i > $i.tmp;
mv $i.tmp $i
done
Nice isn't it ? It just adds a \n to every DPRINTF call that
was relying on old behavior (automatic trailing \n).
Revision
1.26.2.4 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Sat May 17 13:36:18 2003 UTC (21 years ago) by
suxen_drol
Branch:
dev-api-4
Changes since
1.26.2.3: +1 -1 lines
Diff to
previous 1.26.2.3
, to
branch point 1.26
* dynamic bvop decision stats bug fixed
* added runtime debug level option. this only only activated when _DEBUG is defined.
level is specified globaly, via "xvid_glb_init_t.debug" and XVID_DEBUG_xxx defines.
references to previous DPRINTF_LEVEL_xxx's have been replaced throughout libxvidcore
* futher bitrate zone fixes for plugin_2pass2.c
* removed old ratecontrol.c from msvc project
* xvid_encraw.c specifc:
* added "-max_key_interval integer" option
* renamed -debug to -vop_debug
* added "-debug integer" option, which sets xvid_gbl_init_t.debug field
* s/length/len/ status line
* vfw specific:
* zone/bitrate typos fixed ("you eediot")
* renamed "debug" regkey to "vop_debug"
* added "debug" regeky and textbox which sets xvid_gbl_init_t.debug field
Revision
1.26.2.3 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Thu Apr 10 13:05:54 2003 UTC (21 years, 1 month ago) by
edgomez
Branch:
dev-api-4
Changes since
1.26.2.2: +3 -3 lines
Diff to
previous 1.26.2.2
, to
branch point 1.26
2003-04-10 GMT Edouard Gomez <ed.gomez@free.fr> patch-14
Summary:
Removed all ABS() macros.
Revision:
xvidcore--devapi4--1.0--patch-14
All ABS macros have been replace with their stdlib.h/math.h
equivalent. This gives a 33% overall speedup for the plain C encoder,
while the ia32 one seems to suffer a small speed loss. However this
speed loss is very small and it seems it depends on the CPU type as
the abs/fabs usage is impacting badly on sad functions but impacting
well on interpolate functions ... weird inst'it ?
modified files:
src/bitstream/mbcoding.c src/global.h src/image/image.c
src/motion/motion_comp.c src/motion/motion_est.c
src/motion/sad.c src/prediction/mbprediction.c
src/utils/mbtransquant.c src/xvid.c
Revision
1.4 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue Mar 26 11:16:08 2002 UTC (22 years, 2 months ago) by
h
Branch:
MAIN
Changes since
1.3: +76 -20 lines
Diff to
previous 1.3
interlacing support - slow (MBDecideFieldDCT()), buggy (p-frames), incomplete (field motion prediction)
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.