This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[INFO] Need - Avisynth FPS
#1
Need - Avisynth FPS http://avisynth.nl/index.php/FPS#Examples_2

1. AssumeFPS - Changes the frame rate without changing the frame count, causing the video to play faster or slower.

2. ChangeFPS - Changes the frame rate by deleting or duplicating frames.

3. ConvertFPS - Attempts to convert the frame rate without dropping or inserting frames, providing a smooth conversion with results similar to those of standalone converter boxes. The output will have (almost) the same duration as clip, but the number of frames will change proportional to the ratio of target and source frame rates.
Frame rate conversion is inherently difficult. This filter implements two common methods used by commercial Prosumer-level converter systems. The results are typically quite good. More sophisticated systems employ motion interpolation algorithms, which are difficult to get right, but, if done right, do yield superior results.
Footage converted with this filter should not be converted again. Blurriness builds up quickly in subsequent generations.
Reply
#2
Filtering->Speed Change will trigger the use of those.
For actual frame chagnes, instead of those, I would recommend using the the filters under Avisynth->Frame or better Vapoursynth->Frame.
(I don't really use Avisynth anymore)
Reply
#3
(31.03.2023, 12:25)Selur Wrote: I don't really use Avisynth anymore

Huh Huh Huh Huh Huh Huh Huh Huh Huh  avisynth better.............
Reply
#4
What makes you think that Avisynth is better?
Huh
Reply
#5
i like it - avisynth - all scripts

vapoursynth - just only Dain-app
Reply
#6
Vapoursynth like Avisynth is based on scripts, but since it's also based on Python it allows integrating other stuff more easily.
Didn't know the Dain-app nowdays uses Vapoursynth, I thought it was a small gui for using some of the python based ai filters,..
https://github.com/baowenbo/DAIN doesn't use Vapoursynth at all.
=> no problem, if you like Avisynth more, stick with it.

Cu Selur
Reply
#7
Big Grin Big Grin Big Grin 

vapoursynth - cool dad

avisynth - intelligent son
Reply
#8
No more the other way around.
Avisynth is the older one and folks came up with Vapoursynth since Avisynth was too restrictive and nobody then could port it to Linux and Mac.
(There's a Avisynth for Linux&Mac nowadays, but basically no plugins/filters for it)

Cu Selur
Reply
#9
green -  correctly?

red - what is it? how does it work?

pic. - https://drive.google.com/file/d/15pjjMom...share_link
Reply
#10
Not sure what you want to do, but in general those settings are trash.
a. "Interpolate frame rate" likely will create tons of interpolation artifacts (better use the Avisynth, Vapoursynth options).
"Interpolate frame rate" uses ffmpegs 'framerate' filter (https://www.ffmpeg.org/ffmpeg-all.html#framerate)
b. Scene change seems to be way too low for SD or higher resolutions.
c. 'Automatically adjust speed to stream frame rate' is an option you probably don't want to use.

Cu Selur
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)