Log of /xvidcore/src/prediction/mbprediction.c
Parent Directory
Revision
1.18 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue Nov 22 10:23:01 2005 UTC (17 years, 6 months ago) by
suxen_drol
Branch:
MAIN
CVS Tags:
release-1_1_0,
release-1_1_0_final,
release-1_1_1-final,
release-1_1_2,
release-1_1_3,
release-1_1_3-final,
release-1_2_0,
release-1_2_2,
tag-branching-1_2_0
Branch point for:
release-1_1-branch,
release-1_2-branch
Changes since
1.17: +12 -12 lines
Diff to
previous 1.17
cleanings in code spotted by sparse (ed dot gomez at free dot fr>
Revision
1.17 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue Sep 13 12:12:15 2005 UTC (17 years, 9 months ago) by
suxen_drol
Branch:
MAIN
Changes since
1.16: +79 -0 lines
Diff to
previous 1.16
Field interlaced decoding, contributed by Christoph Kuehnel
decoder.c
=========
- Some new defines for DIV
- <decoder_mb_decode> modified: had wrong address offsets for interlaced
- <decoder_mbinter_field> = new function for interlaced
- <get_motion_vector_interlaced> = new function for interlaced motion vector prediction
- <decoder_pframe> modified so that it differs between frame and field prediction
global.h
========
- For field motion prediction MACORBLOCK has new member that is the average of
field1 and field2 motion vector = <mvs_avg>
xvid.c
======
- For field predicted macroblocks we need new field oriented transfer functions.
For colour calculations they may only process 4 lines (one field from the colour
macroblock that is 8x8). So I introduced 4 new function pointers:
<transfer8x4_copy, interpolate8x4_ ...)
mbcoding.c
==========
- _DEBUG code; index is checked against 64
interpolate8x8.[c,h,asm]
===========================
- New 8x4 functions
mbpredicition.[c,h]
===============
- New function <get_pmv2_interlaced> for interlaced prediciton according to spec
mem_transfer.[c,h,asm]
==============
- New 8x4 function
Revision
1.13.2.6 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Thu May 22 16:36:07 2003 UTC (20 years ago) by
edgomez
Branch:
dev-api-4
Changes since
1.13.2.5: +3 -3 lines
Diff to
previous 1.13.2.5
, to
branch point 1.13
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.13.2.5 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Sat May 17 13:36:56 2003 UTC (20 years ago) by
suxen_drol
Branch:
dev-api-4
Changes since
1.13.2.4: +3 -3 lines
Diff to
previous 1.13.2.4
, to
branch point 1.13
* 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.13.2.4 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Thu Apr 10 13:05:54 2003 UTC (20 years, 2 months ago) by
edgomez
Branch:
dev-api-4
Changes since
1.13.2.3: +7 -5 lines
Diff to
previous 1.13.2.3
, to
branch point 1.13
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.7.2.1 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Sat Jan 4 06:14:33 2003 UTC (20 years, 5 months ago) by
suxen_drol
Branch:
dev-api-3
Changes since
1.7: +1 -4 lines
Diff to
previous 1.7
global.h macro cleanup
cpu_detection cleanup, XVID_CPU_ASM added
sse2 stuff enabled, femms now utilized
Revision
1.2 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Thu Mar 28 20:57:25 2002 UTC (21 years, 2 months ago) by
edgomez
Branch:
MAIN
CVS Tags:
xvidcore
Changes since
1.1: +75 -55 lines
Diff to
previous 1.1
Big patch, use it with care (tests done with GNU/Linux) :
- Trivial warnings in encoder.c line 282 ret1 = ret 2 = 0;
- Lot of "New line at end of file missing" warnings fixed (gcc3)
- All 2d arrays have been turned into 1d arrays
To force alignment of matrices on stack, use DECLARE_ALIGNED_MATRIX
(read portab.h)
Win32 users should give feedback.
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.
