oriento
5090 and ... 8700K. I'm not laughing, I'm just perplexed. You have a video card, the owners of which are now considered the most successful (and rich))) at the moment. But at the same time, you have a 2017 platform. Dissonance. Maybe the chipset and pci-e can't, or something else besides the processor. I have 13900K + 4090, everything is great, if 4K>1440p x 3, or 4K x 2 (x3 on v2)

Chainik wrote:

generate.js

Now everything is fine, being in this tab, the smoothing is simply disabled, but nothing freezes and no inscriptions

After the update, when switching to the Frame Size tab, the video starts to stutter, smoothing is disabled, it slows down, and incomprehensible text appears in the corner. This did not happen before the update

narkohol wrote:

Dropped/Skipped/Delayed

In nvcp, set the player to fast sync. Most likely, you have dropped frames due to desynchronization. This is the only case when the ancient fast sync can be useful.

I checked it many more times 4.26. It's surprising that many people don't see her mistake. No, I stay at 4.18, that's the best for me.

Blackfyre wrote:

Matching the FPS and display Refresh Rate gives a smoother experience.

To avoid missing frames, in nvcp set the player "fast sync"

flowreen91 wrote:

@pensioner600 The mpcVR devs are looking for you:

Yes, I saw it, thanks!

I didn't like 4.26 at all.
I usually compare them on this video.
https://drive.google.com/file/d/1OQAHl3 … sp=sharing

At 57 seconds on Steve Carell's nose.
4.18 is the best nose.
4.15lite is a little worse.
4.26 is the worst nose, it doubles.
The nose is an example where everything is clearly visible. In my other testing moments, 4.26 also showed itself poorly.
Before this, 4.15lite was the best model for me. I'm switching to 4.18 for now. I'll test other models when I have time. But 4.26 is very bad.

pensioner600 wrote:

The movie Twisters (2024) is unpleasant to watch. 4K---1440p. When the characters broadcast, there are constant glitches on the screen. TRT9.2/4.15 lite. Can this be fixed? If I understand correctly, any other movie can have the same thing when the frame rate changes.

Answering myself and everyone. It's all because of black bars detection. Why is it enabled by default??? When the size of the displayed area changes in a movie (for example, a character is filming with a video camera), new black bars are detected, the resolution changes and recalculation is performed for this resolution. I disabled black bars detection and now everything is fine.

The movie Twisters (2024) is unpleasant to watch. 4K---1440p. When the characters broadcast, there are constant glitches on the screen. TRT9.2/4.15 lite. Can this be fixed? If I understand correctly, any other movie can have the same thing when the frame rate changes.

Xenocyde wrote:

Will test MPC-BE for microstuttering.

If you plan to melt above 160 fps, then I recommend version 0.7.1.2172 of mpcVR. Here (and in the following messages) it’s clear why.  The developer does not fix this error and wants a high-frequency monitor))
https://mpc-be.org/forum/index.php?topi … 18#msg8818

Xenocyde wrote:

The microstuttering happens

Mpc-be+mpcVR. If there is a global FPS lock in nvcp, then this lock must be turned off separately on the player. I also install the ancient and forgotten fast sync on the player; it is in this scenario that it works best. Never any stuttering or skipped frames.

Chainik wrote:

try updated svpflow2_vs.dll from that post: https://www.svp-team.com/forum/viewtopi … 672#p84672, any changes?

Of course, everything was updated initially, all three files. I saved the old files just in case))

Chainik wrote:

2. scene change based on SVP's motion vectors - when "scene change threshold" is "6%"
3. scene change based on NVOF's motion vectors - when "scene change threshold" is "8%"

None of this eliminates the problem of instantaneous judder in many fast-moving scenes. That is, the first frame (or the first few frames), but most likely only the first frame of the next scene seems to be lost and shifted a little to the side and with the next frame it returns to its correct position. For me, 8% is almost the same as SC100%, only in VERY dynamic scenes there are stutters, otherwise the problems are the same. What other scene change settings can you tweak? I feel that the solution is somewhere nearby, but I lack knowledge. For now I'm staying at SC100%.

Chainik wrote:

> How can I change the TRT version? And how can I find out the current version? I really don’t like the scene change on any model at any 6%-100% values.

this isn't related to the TRT version at all
TRT version can only affect build time, memory usage and overall performance

Are there any other settings besides rife_sc that affect scene changes? I really don’t like how it works, I’ve already tried many options. It's as if the algorithm in the next scene is confused and momentarily doesn't know what to do. Everything is perfect, smooth as butter, except for this trouble with the scene change.

cws wrote:

I think this has been fixed in newer TensorRT 9.x testing releases (note the current release that is part of SVP is 8.x.) If you can still see it with 9.x, it should be reported so developers are aware and hopefully it can be addressed.

How can I change the TRT version? And how can I find out the current version? I really don’t like the scene change on any model at any 6%-100% values. If the dynamic scene changes to dynamic, then some kind of jerk occurs, it is instantaneous, but it is visible. Maybe they fixed this in other versions of TRT?

I also noticed that ALL versions of V2 give the entire picture a shake, which is very clearly visible on a static scene on small light objects on a dark background. I noticed a long time ago that something was wrong, but I didn’t have time to watch movies. Versions NOT V2 and lite no jitter. I’m definitely switching to 15lite or 16lite, even if it’s x3, not x4. V2 is complete nonsense. Today I devoted half a day to tests, a lot became clear))

I noticed that setting the scene change threshold (rife_sc) to 100% is a very bad idea. And for some reason I noticed this specifically in The Last of Us)) At the change of scenes from dynamic to dynamic, it happens, I don’t even know what to call it, back and forth for a moment. This happens at any high values. I set it to 20%, everything was fine, but in a VERY dynamic scene I caught a freeze. I consider 25% optimal so far, smooth and the scene changes are almost adequate. What percentage do you bet on yourself? Do all models behave the same during scene changes? Has anyone tested models not based on artifacts, but specifically on scene changes?
I use MPC-BE+mpcVR+trt 4.15liteV2
The quality is almost always 4K with downscale to 1440P. x4

Chainik wrote:

downscale resize changed from bicubic to Lanczos

Thank you!!! Where can I see which one is currently working? Is there any overlay with current readings?

What is the downscale algorithm in SVP? Can it be changed or improved somehow? I just compared frame-by-frame screenshots. It loses greatly in the downscale of mpcVR, small details are lost. If it could be changed, then that would be ideal))

RickyAstle98 wrote:

What do you see, its feels smooth? big_smile

In terms of smoothness, of course, it does not reach dmitrirender 240fps, but there are significantly fewer artifacts and this makes the picture clearer, especially on small objects, and in general dynamic scenes look better, you can see more.

I tested it. 4.15 lite (V2) with SVP downscaling to 1440p, even 4K 10bit x4 works well. It is excellent! Great progress in technology while I was on dmitrirender)) I also confirm that 4.15 lite has fewer artifacts than just 4.15. I still stick with MPC-BE, since MPV is very confusing, even the ASIO driver is not clear how to attach it to it. Here are my settings, see who is experienced, maybe I missed something or made a mistake?

22

(46 replies, posted in Эксплуатация SVP)

RickyAstle98 wrote:

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

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

23

(46 replies, posted in Эксплуатация SVP)

RickyAstle98 wrote:

Ты его установил из пакета SVP а не отдельно? Просто если отдельно придется привязать mpvpipe чтобы он считывал скрипт VapourSynth и какая-либо уплавнялка сработала!

Установил из пакета, но я к такому вообще не привык)) Даже не вижу что там творится, какой рендер и фильтры и т.д. А ещё мне надо в него запихнуть сторонний асио драйвер для прямого вывода на внешнюю звуковуху. У него есть какой нибудь оверлей показаний? Ещё по умолчанию вижу какое-то мигание изображения, то тусклее то светлее. А так да, запускается с rife быстрее намного, без всяких трёхсекундных дёрганий. Похоже не подружусь я с ним))
А тут на русском можно общаться??

24

(46 replies, posted in Эксплуатация SVP)

Installed MPV. Did I understand correctly that this is a player without a settings interface and everything needs to be written manually in files? And this will take a very long time to figure out.

25

(46 replies, posted in Эксплуатация SVP)

5в. в 240 кадрах нету смысла ибо РИФЕ столкнется с проблемой SVP алгоритма, когда чрезмерная интерполяция начинает дублировать свои же собственные созданные кадры (зависит от разрешения)!

Thank you!  240fps with good downscaling mpcVR jinc2m 4K>1440p worked perfectly with dmitrirender, not a single dropped frame, perfect.  And in RIFE with such a resolution you can only dream of 240fps, it’s unlikely that even the 5090 can handle it)) RIFE 4K>1440p works for me now without any problems (by reducing the SVP frame) maximum x3.  And 4x in 10bit is already skipping frames.  I never turn off HAGS, I need it for FG, but it’s inconvenient to turn it on and off.  I’ll try to set everything up perfectly again)) Or maybe there is an all-in-one instruction with a description for setting up RIFE correctly?