The latter is actually, indeed, not present on my system, as I replaced it with libdfttest.dll recently (from another author). Whenever I start the preview (F5), I get a fatal error something about fftw_make_planner_thread_safe entry point not found in the fft3dfilter library. I'm loving this piece of software! :) Found it very useful, recently, to get a quick preview of a movie I wanted to burn subs into. It's shit and should be avoided at any cost. I'm sorry to say that, but I'm NOT going to test on Windows 10. For now, try to reinstall Python "for all users". One of the things on my TODO list is to make custom paths take priority over registry. I'm out of ideas!The only thing that comes to mind is registry. That resets all settings, but it did not change behavior. I also deleted the config file that shows up in my AppData\Local directory. So it is just failing on custom paths that I add into vsedit Settings.Īlso, I gave my user account full rights to Python37 and everything in it, plus the VapourSynth install directory (and everything in it), and the VapourSynth Editor directory (and everything in it). Running vsedit as my normal user account works fine for library files that I add to. I also added the path to PYTHONPATH and it works fine at the Python CLI, as one would expect. It does not work when I run as my normal user account. It works fine (meaning I can import library files in that path) when I run vsedit as Admin. I add a custom library search path into vsedit Settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |