Search options (Page 64 of 360)

What I can say it's an incompatibility between the video cut with VLC and mkvmerge.
I'd say VLC produces somehow broken output (mpv shows 1000.000fps, MPC-HC shows 48 fps while the video is actually 24 fps - this isn't normal in any case).
Transcoded video itself is OK, but the playback hangs AFTER processing via mkvmerge (used to attach audio / subs streams).

Possible solutions:
1. do not cut video with VLC
2. do the final muxing with ffmpeg rather than mkvmerge: set code.tools.use_mkvmerge = false in SVP's All settings --> in this case this video works after transcoding

but keep in mind that mkvmerge usually works better than ffmpeg

> На последней версии AVSF (0.9.1)

это в смысле что раньше работало, а на последней перестало?

> имеем черный экран при воспроизведении 10-битного видео

не знаю, не могу подтвердить, у меня работает
какой плеер? какой рендерер?

indeed... just updated the wiki page

the same way as you're using ffdshow filter?

when you choose Linux - be prepared for reading the manuals and following "the Unix way"

some dependency is not installed

> отпадает даже на условных минималках?

хз, только тесты покажут... если оно там вообще запустится - по-любому OpenCL нужен, наличие и доступность зависят от производителя девайса. чо там на ноунейм китайцах я пока вообще не знаю.
а еще андроид 9 и гугломаркет.

---
вот можешь попробовать запустить это - https://play.google.com/store/apps/details?id=kr.clpeak

updated to 0.9.1

> which natively supports frame rate interpolation using shared SVP libraries

this is not true
mpv doesn't use shared SVP libraries
moreover, mpv doesn't provide motion interpolation at all, it's just a frames blending

yeah, ok, I can reproduce this
lets wait for the fix - https://github.com/CrendKing/avisynth_filter/issues/35

> SVP ends up interpolating everything to 95 FPS instead of 60 for some reason

do the math
30 fps source -> 60 fps --> x2 - 30*2  = 60
with "Remove every other frame" it have to do x4 --> 30*4 = 120, 120/2 = 60
now you still have x4 but removes only 1/5 of frames --> 120*4/5 = 96

bottom line: if you want 60 then you have to set fi_target = 1.25 in the corresponding profile

> You're not making any sense and not answering my question

the question was "I see two rendering options. Which one should I watch out for?"
the answer was "both" - i.e. both "average stats - rendering" and "max stats - rendering", as there're no more "rendering" words in madvr's stats

> keep telling yourself that.

keep telling myself what? that "41.71 is obviously 1000/23.976", where 23.976 is the source frame rate thus 41.71 is a constant value making your "making everything at lowest settings, the frames value doesn't go below 41.71ms though" a nonsense? ok, I'll keep telling myself that.

next time please try to read carefully and think first before commenting