Log of /xvidcore/src/motion/estimation_bvop.c
Parent Directory
Revision
1.1.2.5 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Wed Nov 19 12:24:25 2003 UTC (19 years, 10 months ago) by
syskin
Branch:
dev-api-4
Changes since
1.1.2.4: +143 -112 lines
Diff to
previous 1.1.2.4
, to
branch point 1.1
SearchData revised - not longer constant across checkcandidates, but keeps search results in self - no pointers and redirections. All checkcandidates are faster now.
Revision
1.1.2.4 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Sun Nov 16 15:32:37 2003 UTC (19 years, 10 months ago) by
edgomez
Branch:
dev-api-4
Changes since
1.1.2.3: +3 -1 lines
Diff to
previous 1.1.2.3
, to
branch point 1.1
Valgrind reported lot of unitialized reads. These unitialized reads
helped sysKin finding three bugs:
- ZeroMacroblock did not reset the cbp field. So for some skipped
blocks, a test was done on the cbp value...
- MEanalysis was using wrong mvs from the current bvop (unitialized
or just wrong in current context). That's because in devapi3,
bframes used to share the same mvs array wheras now, it's one array
a bvop.
- Collocated skipped MBs for a bvop didn't reset mvs[0] and b_mvs[0].
Revision
1.1.2.3 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Sun Nov 9 20:47:14 2003 UTC (19 years, 10 months ago) by
edgomez
Branch:
dev-api-4
Changes since
1.1.2.2: +2 -2 lines
Diff to
previous 1.1.2.2
, to
branch point 1.1
* transfer_8to16_sub2_(c|mmx|xmm|3dne) write back the compensated
result to current frame pointer.
* transfer_8to16_sub2_mmx uses proper rounding (a+b+1)/2. The +1
operation was missing.
* Blocks skipped in bframes must be compensated for psnr computing.
Revision
1.1
Wed Sep 10 22:18:59 2003 UTC (20 years ago) by
edgomez
Branch:
MAIN
Branch point for:
dev-api-4
FILE REMOVED
file estimation_bvop.c was initially added on branch dev-api-4.
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.