summaryrefslogtreecommitdiffstats
path: root/libmpcodecs
diff options
context:
space:
mode:
authormichael <michael@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-06-06 10:34:45 +0000
committermichael <michael@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-06-06 10:34:45 +0000
commit9bf06dbc52cc6e92e82c0c1ea39a44f679efdccc (patch)
tree02253484bc350aae32b2c02232c8e517045825f5 /libmpcodecs
parent828cf9be9c3f45d2dc3f1396b0a160ec5feae47e (diff)
downloadmpv-9bf06dbc52cc6e92e82c0c1ea39a44f679efdccc.tar.bz2
mpv-9bf06dbc52cc6e92e82c0c1ea39a44f679efdccc.tar.xz
known issues and notes
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@18593 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'libmpcodecs')
-rw-r--r--libmpcodecs/vf_mcdeint.c27
1 files changed, 27 insertions, 0 deletions
diff --git a/libmpcodecs/vf_mcdeint.c b/libmpcodecs/vf_mcdeint.c
index cab8cef491..e54f39b0ae 100644
--- a/libmpcodecs/vf_mcdeint.c
+++ b/libmpcodecs/vf_mcdeint.c
@@ -16,6 +16,33 @@
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/
+
+/*
+Known Issues:
+* The motion estimation is somewhat at the mercy of the input, if the input
+ frames are created purely based on spatial interpolation then for example
+ a thin black line or another random and not interpolateable pattern
+ will cause problems
+ Note: completly ignoring the "unavailable" lines during motion estimation
+ didnt look any better, so the most obvious solution would be to improve
+ tfields or penalize problematic motion vectors ...
+
+* If non iterative ME is used then snow currently ignores the OBMC window
+ and as a result sometimes creates artifacts
+
+* only past frames are used, we should ideally use future frames too, something
+ like filtering the whole movie in forward and then backward direction seems
+ like a interresting idea but the current filter framework is FAR from
+ supporting such things
+
+* combining the motion compensated image with the input image also isnt
+ as trivial as it seems, simple blindly taking even lines from one and
+ odd ones from the other doesnt work at all as ME/MC sometimes simple
+ has nothing in the previous frames which matches the current, the current
+ algo has been found by trial and error and almost certainly can be
+ improved ...
+*/
+
#include <stdio.h>
#include <stdlib.h>
#include <string.h>