Search options (Page 6 of 9)

scb wrote:

RickyAstle98 wrote:

Line 137
Line 1179
Line 1297

Please do elaborate.. what is the impact of this? What are my options and how does it help?

There's very little benefit in changing it. I've played with many of the options including this one and the default settings are mostly the best settings.

RickyAstle98 wrote:

Insindro wrote:

In your opinions, which rife model is currently the smoothest?

4.4 smoothest (for me)

For me they are all about as smooth as each other but 4.15 and 4.15 lite have by far the least artefacts. 4.15 lite is the best all round.

Could someone let me know how I’d be able to change my builder optimization level?

RickyAstle98 wrote:

I found a temporary FIX for my issue, I detect RIFE prerendered video has no issues while playback, only realtime playback (even just only 24>48 hd source, easy for 4070 isnt it?) improper encoded movies MKV containers broke models frame handling, because I reencoded same video to MKV back again, and voila no issues! Also this is HEVC issue, LOL!

LOL! Well done for finding the origin of the issue.
@Chainik can u add something from SVP side to correct/prevent/fix this blocker issue?
We don't want other SVP users to go through all the stress of trying to figure it out like Ricky just did.

RickyAstle98 wrote:

2) Начиная с моделей 4.9 по 4.16 кадры будто сдвигаются в обоих направлениях, видео перестало быть плавным

Hmm, did you try these too in order to fix the frames stutters?
1. stop using Lossless Scaling on top of SVP
2. change MPV config to prevent additional frame blending like:
video-sync=audio
interpolation=no
gpu-api=d3d11
hwdec=no
3. RIFE GPU threads = 1 (in case multi threading would break the interpolated frames order)
4. frc.frame.resize to smaller resolution until your GPU has enough extra bandwidth for the worse case scenario interpolation scenarios
5. check if issue persists on v1 without performance boost (in case there are major internal differences between that and v2 with performance boost that we don't know about)
Compare it on a basic predictable panning scene like:
https://drive.google.com/drive/folders/ … nG0qJnlw4I

> к сожалению вы мне дали онлайн пакет

в смысле? это - оффлайн пакет(ы)

если в модели 4.6 что-то одно, а в 4.9 что-то другое, то SVP тут не при чём

> просто я обращался с проблемой несколько раз которую сам же и решил

ну, вот, так и надо :up:
не надо обращаться с проблемами которые можно самому же и решить
обращаться надо с проблемами которые самому решить нельзя

RickyAstle98 wrote:

Можно и на английском, но в обоих случаях они перевели и мой пост тоже, но думаю на английском нам обоим придется слегка переводить, реши как будем, then go?!

Мне удобнее на русском, если никто не против))
Так в MPV оверлея мониторинга нет? Что-то он ну совсем не юзер френдли. Наверное всё-таки останусь на mpc-be/hc, смирюсь с выбрыками при запуске файла))
Кстати, мне почему-то больше понравился 4.16lite, нежели 4.15lite
Тестирую на этом
https://workupload.com/file/DMzZaEaXKmn
Ореолы вокруг головы на фоне зелёного забора вроде бы меньше на 4.16lite. Попробую ещё другие не lite.
А кто-то может поделиться хорошим видео для теста качества уплавнения?

RickyAstle98 wrote:

5c. There is no point in 240 frames because RIFE will encounter the problem of the SVP algorithm, where excessive interpolation starts duplicating its own created frames (depends on the resolution)!

As long as the two source frame images are not identical, RIFE will try to make a smooth transition between them so it will generate all the intermediary frames. If you set Scene change threshold 100 it will not duplicate frames.
If you set a low Scene change threshold like 1-15 then it will compare the two images and it might come to the conclusion that the difference between the two source images is big enough that it will consider it a scene transition.
When it concludes that it is a scene transition it will stop generating intermediary frames and start duplicating/reusing the same source frame so instead of a smooth transition it will "teleport" to the new source frame instead.
So use a high Scene change threshold value (or 100) for 240 fps+ to address this problem.

dawkinscm wrote:

BTW Is the number being used in your attachment 2560x1440 resolution?

No, i just searched the resolution pensioner600 was asking for.
For 240 fps RIFE we must go much much lower than that.

dawkinscm wrote:

I found I had to turn SCT back for best overall smoothness.The default value of 10 works best although 12 works better for one particular instance. YMMV.

Interesting. Are you talking about this particular instance? https://www.svp-team.com/forum/viewtopi … 121#p84121
Share the video if not.