Search options

That uploaded DLL by Chainik? For me also allowed any threads (4 too) but couldn't fast forward or jump to another time. Is it working for you? same driver version too.

Woowww, believe it or not it's working. (almost)
The video when i switch to RIFE, i can play even 4K videos. The only problem is if i fast forward to another time position the player immediatelly die with the error (see the picture at the bottom)

A little additional info:
Before the topic started i used avisynth i just changed to vapoursynth for testing purpose (but same error message as avisynth about the thread numbers). Now i changed to Vapoursynth because of the dll.

On the other hand i understand why Chainik said it doesn't matter if we replace the vs_rife.dll to the latest one, because with the current dll and with the old driver would allow the 2 threads.
So the limitation should be on driver level, if i understands well.
But in this case i don't understand what they fix in the Vapoursynth at r9_mod_v14 -> adjusting gpu_thread related code and changing workflows to latest vapoursynth

Overall, it looks like it's not the driver problem anymore, the vs_rife.dll was the problem, but still have this seek error. i will try another player (now i use  Potplayer)

EDIT:  with MPC-HC i got this dump when i try to seek forward in the video:

rife_vs!VapourSynthPluginInit2+0x1baa7
rife_vs!VapourSynthPluginInit2+0x34f1d
rife_vs!VapourSynthPluginInit2+0x34903
rife_vs!VapourSynthPluginInit2+0x2cccf
rife_vs!VapourSynthPluginInit2+0x2c6f8
rife_vs+0x2235
rife_vs+0x505b
vapoursynth!getVapourSynthAPI+0xcadf
vapoursynth+0xfe1c0
vapoursynth_cp38_win_amd64+0x83eac
python38!Py_CheckFunctionResult+0x516
python38!Py_BuildValue_SizeT+0x884
python38!PyObject_GenericSetAttrWithDict+0xcf7
python38!PyDict_SetDefault+0x3be
vapoursynth_cp38_win_amd64!PyInit_vapoursynth+0x1732e
vapoursynth_cp38_win_amd64+0x4c31c
vapoursynth_cp38_win_amd64+0x4b906
python38!Py_gitversion+0x9af4
python38!PyEval_EvalFrameDefault+0x195a
python38!PyEval_EvalCodeWithName+0x228
python38!PyEval_EvalCodeEx+0x9b
python38!PyEval_EvalCode+0x2d
vapoursynth_cp38_win_amd64!PyInit_vapoursynth+0x1be5f
vapoursynth_cp38_win_amd64+0x709f8
vapoursynth_cp38_win_amd64+0x742dc
vapoursynth_cp38_win_amd64+0x74f19
vsscript!vsscript_evaluateFile+0x17b
vapoursynth_filter_64!DllMain+0x10e6a
vapoursynth_filter_64!DllMain+0xdf18
vapoursynth_filter_64+0x1938a
vapoursynth_filter_64!DllMain+0x16d3c
lavvideo!CLAVVideo::DeliverToRenderer+0x12b0
lavvideo!CLAVVideo::Deliver+0x273
lavvideo!CDecD3D11::DeliverD3D11Frame+0x1f9
lavvideo!CDecD3D11::HandleDXVA2Frame+0x107
lavvideo!CDecAvcodec::DecodePacket+0xcbe
lavvideo!CDecAvcodec::Decode+0x1a5
lavvideo!CDecBase::Decode+0x13a
lavvideo!CLAVVideo::Receive+0x219
lavvideo!CDeCSSTransformInputPin::Receive+0x5e
lavsplitter!CLAVOutputPin::DeliverPacket+0x4ae
lavsplitter!CLAVOutputPin::ThreadProc+0x272
lavsplitter!CAMThread::InitialThreadProc+0x4c
lavsplitter!thread_start<unsigned int (__cdecl*)(void *),1>+0x50
kernel32!BaseThreadInitThunk+0x1d
ntdll!RtlUserThreadStart+0x28

Is there anything i can do about it? Any setting, another "unlocked" driver or tool?
It was worked before, so maybe have a chance to get back this somewhow.

Nothing special, latest SVP, and the included generic 4.4  --  If double the frames (~48-50fps), CPU usage around 80%, but if i choose fix 60FPS, its too much for my videocard)
(on the picture you see GPU Threads 2, because i went back to driver v23.11.1. otherwise it's choppy)

Here are some testing result (because you said it's driver limitation, i just remember i updated my videocard driver):

Revert back to older AMD driver (v23.11.1) i could go up to gpu thread 2 (not more), how i remembered. 4K video are able to play by double frames (GPU usage ~80%)
Update to the latest driver (v24.1.1) is the same problem. only accepted gpu thread 1.  4K videos are unable to handle, its around 12 fps (GPU usage 100%) with the same settings.

Could you or anyone can tell me how/where to "unblock" this driver limitation to properly use SVP RIFE?
Thank you!