Ewi
17th April 2003, 08:06
Hi!
I'm sitting here playing around with the Dup threshold. But I can't get the right percentage. There are always some frames that I think should be replaced but are not and some frames, that should not be replaced.
So what about the following idea: A tool that accepts an avs script. Then ads internally a dup(...) with parameters you have specified somewhere plus "debug=true". Now the program captures the debug output (or the user captures it with debugview and saves it to a log file so the program can read it).
<Edit>
Alternative: perhaps a new parameter in Dup like this would do the same trick: "writeSelectionLog=..." and you simply run your avisynth script completly in a way (above realtime) and you would have the same info
</Edit>
Now the purpose of the program: let assume you have 3 successive 'dupped' frames. Now it would be great if the program displays in a left panel the 3 original frames and for comparing in the right panel the dupped frame (once or three times (don't know what's better)).
So you could choose what to do here: do not dup, or keep frame 1,2 or 3 as dupped frame. This choice could be saved to the log file; for example
[1940] Dup: frm 78: Using frm 80
[1940] Dup: frm 79: Using frm 80
[1940] Dup: frm 80: Using frm 80
becomes when discarding the dupped frames
[1940] Dup: frm 78: Using frm 78
[1940] Dup: frm 79: Using frm 79
[1940] Dup: frm 80: Using frm 80
or when keeping frame 2:
[1940] Dup: frm 78: Using frm 79
[1940] Dup: frm 79: Using frm 79
[1940] Dup: frm 80: Using frm 79
After this choice the programm could jump to the next location where a frame was dupped.....
If this is finished and the log file is saved, a new parameter in Dup like "useSelectionLog=c:\...." could completely control dup...
At first I thought I would be good to use the new conditional Stuff for this, but if you choose the frames this way I think it's would a very big AVS script.
So what do you think? For me it would be VERY useful (to do it manually with virtualdub is a pain and after that you can only choose another threshold value because there is no "useSelectionLog=c:\...." parameter), but there always has to be someone who is willing to code it... At the moment donald is in india, isn't he? (IIRC he said that somewhere...).
Don't know if this will ever be implemented but perhaps someone is looking for ideas, and god knows.... This total control would very great....
I'm sitting here playing around with the Dup threshold. But I can't get the right percentage. There are always some frames that I think should be replaced but are not and some frames, that should not be replaced.
So what about the following idea: A tool that accepts an avs script. Then ads internally a dup(...) with parameters you have specified somewhere plus "debug=true". Now the program captures the debug output (or the user captures it with debugview and saves it to a log file so the program can read it).
<Edit>
Alternative: perhaps a new parameter in Dup like this would do the same trick: "writeSelectionLog=..." and you simply run your avisynth script completly in a way (above realtime) and you would have the same info
</Edit>
Now the purpose of the program: let assume you have 3 successive 'dupped' frames. Now it would be great if the program displays in a left panel the 3 original frames and for comparing in the right panel the dupped frame (once or three times (don't know what's better)).
So you could choose what to do here: do not dup, or keep frame 1,2 or 3 as dupped frame. This choice could be saved to the log file; for example
[1940] Dup: frm 78: Using frm 80
[1940] Dup: frm 79: Using frm 80
[1940] Dup: frm 80: Using frm 80
becomes when discarding the dupped frames
[1940] Dup: frm 78: Using frm 78
[1940] Dup: frm 79: Using frm 79
[1940] Dup: frm 80: Using frm 80
or when keeping frame 2:
[1940] Dup: frm 78: Using frm 79
[1940] Dup: frm 79: Using frm 79
[1940] Dup: frm 80: Using frm 79
After this choice the programm could jump to the next location where a frame was dupped.....
If this is finished and the log file is saved, a new parameter in Dup like "useSelectionLog=c:\...." could completely control dup...
At first I thought I would be good to use the new conditional Stuff for this, but if you choose the frames this way I think it's would a very big AVS script.
So what do you think? For me it would be VERY useful (to do it manually with virtualdub is a pain and after that you can only choose another threshold value because there is no "useSelectionLog=c:\...." parameter), but there always has to be someone who is willing to code it... At the moment donald is in india, isn't he? (IIRC he said that somewhere...).
Don't know if this will ever be implemented but perhaps someone is looking for ideas, and god knows.... This total control would very great....