476

(2 replies, posted in Using SVP)

No messages attached

Try these settings:
https://www.svp-team.com/forum/viewtopi … 465#p73465

First try to use H.264 instead of H.265
Perhaps it will be good enough for your tasks.

Bluray players are very sensitive to profile level and advanced settings used in H.265.
I see you are using x265 coder and profile Main@L8.5@Main. Perhaps it is not good for your Bluray player. Try another more standard settings when encode.

Variable framerate can be a result of combining two videos with different framerate into one video.

How your questions are connected to SVP? Are you using SVPcode?

If it will not help you then give a link to one of "0fps" video please.
We will take a closer look to it.

Looks like this is the cause:

Frame rate mode                          : Variable

Да, можно. Для ДЕкодирования, кодирования, а также для расчета промежуточных кадров.
https://www.svp-team.com/wiki/GPU_Compatibility

483

(8 replies, posted in Using SVP)

Congratulations!
Thank you for information about PCIE lanes

484

(8 replies, posted in Using SVP)

Oh! Sorry. Looks like I was wrong about EVR renderer for high framerate smile
Try Chainik advices: madVR and NVIDIA CUVID Decoder.

485

(8 replies, posted in Using SVP)

chriswakelin22
Check if you are using madVR. You have monitor with high resolution:

2560x1440 @164.769 

It can lead to high GPU load while render 1080p video in fullscreen mode because of upscaling.
Try to reduce madVR settings or select another renderer. For example EVR Custom with D3D Fulscreen option enabled.

It must be so. At every changing of position (seeking) frames buffers must be filled with frame interpolation faster than real time. It uses CPU and GPU at this moment.
You can try any directShow player (MPC-HC for example). You can use setting "Reset on seek". SVP menu: Application settings - Additional options.
To faster seek use value "Don't reset". You can see some "old" frames within short time just after seeking.

Disable option: Application settings - Show OSD messages.

488

(4 replies, posted in Using SVP)

GPU can be used in several tasks: decoding, frames calculating, rendering.
In SVP menu GPU-acceleration you are selecting device for frames calculating.
See more: https://www.svp-team.com/wiki/GPU_Compatibility

Your discrete graphics Radeon RX 560X is powerful enough to SVP task. So you will get GPU load far from 100%. Is it what you expect?
You can disable GPU-acceleration in SVP and enable it again to get difference.

I think your Vega 8 is used more than RX because of it used for rendering.
You need to move rendering work to your discrete GPU. To do this disconnect your display from MoBo and connect it to Radeon RX 560X output.

How many displays yo have?
It will be audio-video synchronization issue in Windows in multi-display configuration.
It is recomended to make your 120Hz dispay the primary display or better is to disable all other displays while you watching movie.
You can use Win-P hotkey for speed switching between displays.

To minimize dropped frames use exclusive mode with madVR or D3D Fullscreen mode with EVR Custom.

490

(4 replies, posted in Using SVP)

How did you change rendering device to your discrete GPU?
I know only one way - is to phisically connect your display to it's out.
---

I see no files attached.

James D
Your link is working to me from Google chrome address bar.

> почему 72Гц должны уменьшать ореолы?
Потому что это ровно в 3 раза больше, чем 24 к/сек. smile
Представим машину, которая проезжает 72 метра/сек.
При 24 к/сек ее положение в метрах от старта будут 0, 3, 6, 9 и т.д.
При 72 к/сек ее положения в метрах будут 0* 1 2 3* 4 5 6* 7 8 9* и т.д., где * - исходный кадр.
Теперь рассчитаем максимальную вероятность ореолов. Они появляются на рассчитанных кадрах всегда, но зависят линейно от расстояния до ближайшего исходного кадра. Максимальное искажение будет на расстоянии 1,5 метра. Примем его за 100%. Тогда кадры 1 и 2 дадут равные расстояния до ближайших исходных кадров, а видимость ореолов составит 66%. Теперь почитаем среднюю видимость ореолов для видео. Оно будет меняться периодически для последовательности кадров: 0 66 66 0 66 66 0 66 66 0 и т.д. Это в среднем даст (0+66+66)/3 = 133/3 = 44%

Для утроения кадров (x3) максимальная вероятность видимости ореолов = 44%. Теперь посчитайте эту величину для x2.5 и остальных случаев wink

> появился ТВ со 120гц
> одни и те же ореолы хоть при 60гц (х2.5), хоть при 120гц (х5)
Как Вы смогли вывести 120 к/сек на ТВ? Его вход HDMI поддерживает 120 Гц? hmm

493

(4 replies, posted in Using SVP)

Video by your link is working to me:
https://www.crunchyroll.com/the-island- … vie-792591

SVPtube2 opens mpv window just after press Play button with delay about 5 seconds.
---

What format are you open (720p or 1080p)?

if you have true 29.97 fps then it must be smoothed.
Looks like you have "fake" 29.97 fps (not every frame contain motion). You can check it with frame-by-frame rewind (for example use hotkey ctrl-right arrow in pause mone in HPC player).

Converting 30 to 24 is bad solution. The best way is to get better video source with true frame rate.

I've just tested. SVPtube 2 is working to me in both cases.
Copying link from youtube is working from address bar and from context menu on the video thumbnails.

Выйти из SVP - зеленая полоска в VLC остается?

497

(53 replies, posted in Using SVP)

> black frame insertion
What model of monitor do you have? Is it flashing backlight technology or something else?

498

(2 replies, posted in Using SVP)

You can use SVPcast to convert videos on PC and stream them to your phone.
https://www.svp-team.com/wiki/Manual:SVPcast

Try to find the cause of these random 1s lags.
1. Is it CPU or GPU temperature (throttling because of overheating)?
2. Is it some windows application (or process) running in background?
3. Is it the video ralated issue (the same lag at the same place)?

You CAN convert 60fps videos into 165fps.
You need to change frc.target.max value from 47 to 65 (something greater than 60).

You can override it by using the All settings window, see frc.target.max value.