Closed Disaer closed 3 years ago
Oh, I get it now. It is by design. When you don't have avs script, avsf won't do anything other than introducing extra transformation overhead. So by design it disconnects itself from the graph (also see reasoning under AvsFilterDisconnect()). Activating remote control forces it to stay in, as it expects 3rd party application to "injects" an avs script on the fly. You can see these actions in log (the "Disconnect due to AvsFilterDisconnect()" line).
Is there a particular reason you want to see avsf in there even you don't effectively use it?
On my main PC, AVSF was installed by SVP. On my second PC, I've installed AVSF manually to test script problems. So, how should I load a script to it for the first time?
I'm using MPC-BE as an example. In Options, you register avsf in External Filters. Once registered, remember to set merit to Preferred. Now you can double click on "AviSynth Filter" to bring up a settings page. You can specify your .avs file there.
Also, you can use (portable mode)[https://github.com/CrendKing/avisynth_filter/wiki/Portable-mode] to allow multiple instances of avsf in one computer, if that's not too complicated for you.
Closing. If you have more question, feel free to follow up here.
OK, thanks for the trick with opening settings via double click on "AviSynth Filter".
Environment
Describe the bug
After repeating all install steps from README.md AviSynth Filter doesn't appear in the video player filters list. AviSynth Filter appears in the video player filters list only after applying activate_remote_control.reg manually.
To Reproduce
Delete AvsFile and RemoteControl keys under registry path HKEY_CURRENT_USER\SOFTWARE\AviSynthFilter
Checklist
Try a different video player and check if the issue persist. For example, if your main video player is MPC-HC, try MPC-BE. Findings: tried MPC-HC+madVR and MPC-BE+EVR-CP, issue persist
Try a different video renderer and check if the issue persist. For example, if issue exists with madVR, try EVR. Findings: doesn't matter
Try a different video file and check if the issue persist. Try another file with different format, dimension and frame rate. Findings: doesn't matter
avsf.log