Хорошо, когда проблема решается без участия разработчиков wink

Ну да, списочек обновлений не маленький. Видно, что давно не обновляли.
LAVFilters как компонент пакета вообще уже давно не присутствует в пакете. Зачем он удаляется установщиком - большой вопрос.

Один из вариантов: да, чистая установка.
Удалить пакет SVP и поставить заново.

You can use NVIDIA CUVID if you need hardware deinterlace. In other cases NVIDIA CUVID, Intel Quicksync and DXVA (cope back) give the same quality.

If you use 32bit player then you can use ReClock to get maximum fluidity playback with no dropped frames.

954

(13 replies, posted in Using SVP)

No. Both 378.49 and 378.66 are with issue.
Use driver ver.378.72 or versions older than 378.49.

rix23
Это 2:3 pulldown.
Исправлять надо при помощи IVTC.
Преобразовать телевизионные 30 fps в киношные 24 fps восстановлением прогрессивных кадров и выкидыванием дублей.
Вон там описано подробнее и с картинками: Просмотр телекино-видео с плавностью

> Refresh rate 29 Hz
надо бы выбрать 59 Hz или 60 Hz.

> Screens: screen 0 - 3840x2160 @29.000 Hz [using OS refresh rate], x3.0 [109 DPI]
Ого! Это и есть 4K.
если исходник видео обычный FullHD, то переключить вывод на ТВ в режим 1920x1080 @ 60 Hz
Телевизор уже сам разрешение до 4K своими встроенными улучшателями добавит wink

быстро он их печет! wink

nemoW
> при последнем обновлении SVP заменил avisynth+ 32-bit на какую-то древнюю версию
Точно, это сделал SVP? hmm
Если так, то надо чинить.

Какая версия была, а какая стала?

Blackfyre
10bit decoding in some cases can't use hardware acceleration, So it uses CPU.
You need to reduce SVP settings to use it with 10bit videos.

960

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

iiiii11111
Ответил там

Можно использовать либо настройку --ontop, либо горячую кнопку "T".
Подробнее там: mpv.io

Hm. It is not expected. I see the same thing with my computer.
So, I don't know why PotPlayer uses (shows) YV12 color space for Video Codec Output.

> Why is that, shouldn't the input be the same?
No. NV12 is just hardware oriented YV12 for NVIDIA.

> How can I force YUY2 output on LAV Decoder?
Just disable YV12 and NV12 options in LAV decoder properties window.

No one knows what conversation of color is better:
AVC 12bit -- LAV --> NV12 12bit -- GPU --> RGB 24bit
or
AVC 12bit -- FFmpeg --> YUY2 16bit -- GPU --> RGB 24bit

You can try and decide it for yourself.

DXVA Native work: GPU decode frame -> GPU show frame
DXVA Copy Back work: GPU decode frame -> pass to RAM -> (CPU filtering) -> pass back to GPU -> GPU show frame
If you not using ffdShow (CPU filtering) then you don't need two passes to RAM and from RAM.
Quality must be identical. CPU usage higher with DXVA Copy Back due to double copying to/from RAM.

> Source is YUY2
Why do you think so?
Your LAV settings has enabled option YUY2 but it automatically selected YV12.

See YV12 and YUY2 options at your picture.

http://image.prntscr.com/image/b4c45ee6b3bb43b5b915c1ce7c3a55ae.png

YUY2 has better color resolution compared to YV12.
See Chroma subsampling "4:2:0" compared to "4:2:2"

> with the built in decoder I get a YUY2 16 bit output
And what is the source? Common source have 12bit YV12 color space.

> with LAV I get 12bit NV12
NV12 is similar to YV12 but with swapped color channels.

ffdShow is software (post)filter. If you want to use only hardware processing (DXVA) then ffdShow is not needed.

It wont work with Native DXVA Decoder as I can see. Perhaps there is some cause of it wink

Native DXVA needs DXVA renderer to be successfully connected to it. Each decoded frame must be passed to renderer in graphics memory. Directly.
Check Video - Video renderer. I use Auto: Enhanced Video Renderer (Custom Present)

GPU load is not the same as HW Decoder (Video engine) load. They are different blocks of graphics adapter.

Just the picture of GPU-Z from Internet.

I don't know. With the same settings I see DXVA is working to me.
http://www.svp-team.com/forum/misc.php?action=pun_attachment&item=4473

971

(5 replies, posted in Флуд)

Онлайн заработал только алгоритм "Арт", "Фотография" не работает.

Исходник:
http://www.svp-team.com/forum/misc.php?action=pun_attachment&item=2379

Арт (глаза и нос пилота отфильтровались шумодавом wink ):

dlr5668
madVR is for advanced users with high performance video adapters wink

There is no information about DXVA at your screenshot.

Video Codec: Built-in FFmpeg Decoder
CPI: 24/26%

Is is software decoder. DXVA (Native) decoder is not used. NVIDIA (CUVID) decoder is not used.

> If you can only use either DXVA or CUDA, then why would the guide tell you to enable DXVA and set CUDA as the decoder?
I tell about DXVA and CUDA DECODERS. One is used at once. About the guide - ask it guide's author wink

I think he wrote guide for common cases and used one decoder by priority: CUDA for NVIDIA users, DXVA - for Intel and AMD users.

Zachn wrote:

Is using DXVA the same as using CUDA Decoder?

No. DXVA is not CUDA. But both of them uses the same hardware engine to decode video (from NVIDIA adapter in your case).
And in one time you can use only one decoder: DXVA or CUDA.
So, press Tab hotkey to get more info about currently used decoder in PotPlayer.

Да уж, табличка "наи-ожидаемая" получилась!
Остается найти, где она, о которой я в октябре указывал, что наполовину готовая лежит wink