Quote:it broke again, many times already, got tired of it - interframe in avisynth mode, CPU and GPU
Okay, you got some motion interpolation artifacts when using Interframe Avisynth instead of using Vapoursynth.
Since there are afaik. no newer free, not bundled to some manager, versions, there is nothing I can do about differences between the versions. Or a way to report the problem to the developers, since they do not support those old versions anymore.
Only suggestions I can give:
- try lower core counts in the Interframe settings to see whether the problem is threading related
- try whether using a different source filter makes a difference
- also if you compare the Vapoursynth and Avisynth version, at least share the settings you used in both
Depending on the content, adjusting the settings (see:
https://www.svp-team.com/wiki/Manual:SVPflow) can also sometimes help with interpolation artifacts.
Cu Selur
Ps.: sharing the output not the input file also doesn't really help to reproduce or advise your problem.
(11.01.2025, 06:59)Selur Wrote: [ -> ]- try lower core counts in the Interframe settings to see whether the problem is threading related +etc
I've already done different options.
this defect appears only with Avisynth
log files, avisynth
Yes, I understood that you have this problem with Avisynth, but - like I wrote - there is nothing I can do or recommend - aside from what I wrote - since I can not reproduce the problem.
Quote:maybe using 32-bit version of Avisynth will help?
Couldn't say, since I can't reproduce the problem.
Quote:how to set it up?
Close Hybrid, extract the extension, start Hybrid, tell Hybrid to use 32bit version,...
Quote:should I download the old version for stability?
Since neither 32bit or 64bit Avisynth in Hybrid has changed for years, I doubt that the 32bit version will help, but do what you want. I already wrote what I would suggest to try.
Cu Selur
it didn’t help, I will continue to use Vapoursynth for such defects
Code:
# Not using InterFrame since input (29.97) is less or equal target (25) fps!
source: Vapoursynth script from the debug output
=> you might want to look into what you are doing,... seems like you are comparing non-interpolated reencodes with interpolated ones,...
Cu Selur
Ps.: Again: I do not care about reencodes. So I again downloaded another 500MB+ useless file.
(11.01.2025, 10:22)Selur Wrote: [ -> ]Ps.: Again: I do not care about reencodes. So I again downloaded another 500MB+ useless file.
PS
once upon a time, after processing I saw this defect
then under the same interframe conditions I used Vapoursynth and then released it
and then for test-experiment I tried different options, and today I finally realized that Avisynth itself is buggy
