RestoreFPS - Revision history

Reel.Deal: add archived downloads

2015-02-22T23:07:58Z

add archived downloads

Reel.Deal: reformat

2015-02-22T14:29:34Z

reformat

Admin: 1 revision

2013-05-09T15:02:01Z

1 revision

Aand: New page: {{FilterCat|External_filters|Restoration_filters|Deblenders}} {{Filter|{{Author/mg262}}|2005.07.31|[http://avisynth.org/warpenterprises/files/restorefps_25_dll_20050731.zip restorefps_25_d...

2008-10-15T19:44:12Z

New page: {{FilterCat|External_filters|Restoration_filters|Deblenders}} {{Filter|{{Author/mg262}}|2005.07.31|[http://avisynth.org/warpenterprises/files/restorefps_25_dll_20050731.zip restorefps_25_d...

New page

{{FilterCat|External_filters|Restoration_filters|Deblenders}}
{{Filter|{{Author/mg262}}|2005.07.31|[http://avisynth.org/warpenterprises/files/restorefps_25_dll_20050731.zip restorefps_25_dll_20050731.zip]|Deblenders|
* YV12
|}}
{{Template:FuncDef|RestoreFPS(''clip'', float ''fps'', float ''phase'') }}

== Abstract ==
[[RestoreFPS]] reverses the kind of blending generated by [[ConvertFPS]], restoring original framerate.
It will work perfectly well on any regular blend pattern, including the [http://home.arcor.de/scharfis_brain/ExotischesInterlacing/#2.3 types] mentioned by scharfis_brain [http://forum.doom9.org/showthread.php?s=&threadid=89266 in this thread]

The framerate to restore should be less than the current framerate, and more than half of it. (So restoring from 24 back to 25 and from 24 back to 11 are both illegal.)
==Parameters==
*It takes a [[YV12]] clip which has an 'underlying' frame rate of '''''fps''''', but a higher actual frame rate due to blending, and reverses the blending to restore the original frame rate.
*'''''Phase''''' is a number between 0 and 1 which specifies the relative displacement of old and new clips (see example below).
== Examples==
In order to test the filter we need to generate a clip using ConvertFPS. A script like this:
<pre>
bicubicresize(4*60,3*60)
selectevery(200,0)
converttoyuy2
assumeFPS (24/1.001)
convertFPS (25)
converttoyv12
overlay(crop(0,0,-0, 26). showframenumber)
</pre>
will do the trick.
Now running RestoreFPS(24/1.001, 0.00) produces a stream of frames.
In this case, the start (in time) of the input clip corresponds exactly to the start (in time) of a frame of the original clip. That won't always be true - if we take the '''convertFPS''' clip above and trim it (say add '''Trim(10,0)'''), then we have a different situation.
Dealing with this requires us to guess the amount by which the converted clip is 'slid' with respect to the original, i.e. to guess the ''phase'' parameter. I used this script to help with this:
<pre>
function phase(clip c, float phi){
c
RestoreFPS(24/1.001, phi) #here set appropriate frame rate

#trim here if desired

a=selectevery(6,0)
b=selectevery(6,1)
c=selectevery(6,2)
d=selectevery(6,3)
e=selectevery(6,4)
f=selectevery(6,5)

stackhorizontal(a,b,c,d,e,f)
Reduceby2()
stackvertical(last, trim(1,0), trim(2,0), trim(3,0), trim(4,0), trim(5,0))
Trim(0,-1).Loop(0,1000)
subtitle(String(phi, "%f"))
}

#insert source clip here

animate(0,100,"phase",0.0,1.0)
trim(0,100)
</pre>
Save the output of this, open it up in VirtualDub, and drag the slider around to find a phase that looks correct (you may get an unusual effect in the first few frames of the clip, because of an edge effect).

'''Note''': If you're dealing with a clip in which fields (not full frames) are blended, separate them and process them separately; the phase parameters for the top and bottom fields will possibly differ by 0.5.

==External Links==
*[http://forum.doom9.org/showthread.php?t=94091 Discussion thread] at [http://forum.doom9.org/ Doom9's Forum]

@@ Line 2: / Line 2: @@
 {{Filter3
 |{{Author/mg262}}
-|2005.07.31
+|v1.0
-|[http://www.avisynth.nl/users/warpenterprises/files/restorefps_5F25_dll_20050731.zip restorefps_25_dll_20050731.zip]
+|[http://wilbertdijkhof.com/mg262/Restorefps_v10.zip Restorefps_v10.zip]
 |Deblenders
-|Closed source
+|[http://www.gnu.org/licenses/gpl-2.0.txt GPLv2]
 |6=[http://forum.doom9.org/showthread.php?t=94091 Doom9 Thread]}}
@@ Line 77: / Line 77: @@
 <br>
 <br>
 ==External Links==
 *[http://forum.doom9.org/showthread.php?t=94091 Doom9 Forum] - RestoreFPS discussion.
 <br>
 <br>
 -----------------------------------------------
 '''Back to [[External_filters#Fieldblending_and_Frameblending_removal|External Filters]] &larr;'''

@@ Line 1: / Line 1: @@
-{{FilterCat|External_filters|Restoration_filters|Deblenders}}
+{{FilterCat4|External_filters|Plugins|Restoration_filters|Deblenders}}
-{{Filter|{{Author/mg262}}|2005.07.31|[http://avisynth.org/warpenterprises/files/restorefps_25_dll_20050731.zip restorefps_25_dll_20050731.zip]|Deblenders|
+{{Filter3
-* YV12
+|{{Author/mg262}}
-|}}
+|2005.07.31
-{{Template:FuncDef|RestoreFPS(''clip'', float ''fps'', float ''phase'') }}
+|[http://www.avisynth.nl/users/warpenterprises/files/restorefps_5F25_dll_20050731.zip restorefps_25_dll_20050731.zip]
+== Description ==
-== Abstract ==
 [[RestoreFPS]] reverses the kind of blending generated by [[ConvertFPS]], restoring original framerate.
 It will work perfectly well on any regular blend pattern, including the [http://home.arcor.de/scharfis_brain/ExotischesInterlacing/#2.3 types] mentioned by scharfis_brain [http://forum.doom9.org/showthread.php?s=&threadid=89266 in this thread]
 The framerate to restore should be less than the current framerate, and more than half of it. (So restoring from 24 back to 25 and from 24 back to 11 are both illegal.)
-==Parameters==
+<br>
-*It takes a [[YV12]] clip which has an 'underlying' frame rate of '''''fps''''', but a higher actual frame rate due to blending, and reverses the blending to restore the original frame rate.
+<br>
-*'''''Phase''''' is a number between 0 and 1 which specifies the relative displacement of old and new clips (see example below).
+== Requirements ==
 == Examples==
-In order to test the filter we need to generate a clip using ConvertFPS. A script like this:
+In order to test the filter we need to generate a clip using [[ConvertFPS]]. A script like this:
-<pre>
+<ul><pre>
-bicubicresize(4*60,3*60)
+ BicubicResize(4*60,3*60)
-selectevery(200,0)
+ SelectEvery(200,0)
-converttoyuy2
+ AssumeFPS(24000,1001)
-assumeFPS (24/1.001)
+ ConvertFPS(25)
-convertFPS (25)
+ Overlay([[Crop(0,0,-0, 26, true).ShowFrameNumber)
-converttoyv12
+</pre></ul>
-overlay(crop(0,0,-0, 26). showframenumber)
 </pre>
 will do the trick.
-Now running RestoreFPS(24/1.001, 0.00) produces a stream of frames.
+Now running <tt>RestoreFPS(24/1.001, 0.00)</tt> produces a stream of frames.
 In this case, the start (in time) of the input clip corresponds exactly to the start (in time) of a frame of the original clip. That won't always be true - if we take the '''convertFPS''' clip above and trim it (say add '''Trim(10,0)'''), then we have a different situation.
 Dealing with this requires us to guess the amount by which the converted clip is 'slid' with respect to the original, i.e. to guess the ''phase'' parameter. I used this script to help with this:
-<pre>
+<ul><pre>
 function phase(clip c, float phi){
+c
@@ Line 36: / Line 53: @@
 #trim here if desired
-a=selectevery(6,0)
+a=SelectEvery(6,0)
-b=selectevery(6,1)
+b=SelectEvery(6,1)
-c=selectevery(6,2)
+c=SelectEvery(6,2)
-d=selectevery(6,3)
+d=SelectEvery(6,3)
-e=selectevery(6,4)
+e=SelectEvery(6,4)
-f=selectevery(6,5)
+f=SelectEvery(6,5)
-stackhorizontal(a,b,c,d,e,f)
+StackHorizontal(a,b,c,d,e,f)
-Reduceby2()
+ReduceBy2()
-stackvertical(last, trim(1,0), trim(2,0), trim(3,0), trim(4,0), trim(5,0))
+StackVertical(last, Trim(1,0), Trim(2,0), Trim(3,0), Trim(4,0), Trim(5,0))
 Trim(0,-1).Loop(0,1000)
-subtitle(String(phi, "%f"))
+Subtitle(String(phi, "%f"))
+}
 #insert source clip here
-animate(0,100,"phase",0.0,1.0)
+Animate(0,100,"phase",0.0,1.0)
-trim(0,100)
+Trim(0,100)
-</pre>
+</pre></ul>
 Save the output of this, open it up in VirtualDub, and drag the slider around to find a phase that looks correct (you may get an unusual effect in the first few frames of the clip, because of an edge effect).
 '''Note''': If you're dealing with a clip in which fields (not full frames) are blended, separate them and process them separately; the phase parameters for the top and bottom fields will possibly differ by 0.5.
+<br>
 ==External Links==
-*[http://forum.doom9.org/showthread.php?t=94091 Discussion thread] at [http://forum.doom9.org/ Doom9's Forum]
+*[http://forum.doom9.org/showthread.php?t=94091 Doom9 Forum] - RestoreFPS discussion.