View Single Post
Old 15th June 2018, 16:25   #12  |  Link
l33tmeatwad
Registered User
 
l33tmeatwad's Avatar
 
Join Date: Jun 2007
Posts: 414
Quote:
Originally Posted by kolak View Post
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1847, in vapoursynth.vpy_evaluateScript
File "", line 9, in
File "/Library/Frameworks/VapourSynth.framework/lib/python3.6/site-packages/havsfunc.py", line 1222, in QTGMC
dnWindow = core.fft3dfilter.FFT3DFilter(noiseWindow, sigma=Sigma, planes=CNplanes, bt=noiseTD, ncpu=FftThreads)
File "src/cython/vapoursynth.pyx", line 1561, in vapoursynth._CoreProxy.__getattr__
File "src/cython/vapoursynth.pyx", line 1416, in vapoursynth.Core.__getattr__
AttributeError: No attribute with the name fft3dfilter exists. Did you mistype a plugin namespace?


even if libfft3dfilter.dylib is in plugins folder and gcc 8.1.0 is already installed and up-to-date.

Had issues with mvtools (mv.Super) also but installing with brew and overwriting library fixed it.
Did you install GCC 8.1.0 through brew? If so, FFT3DFilter is looking for the LibstdC++ library file the directory above where it is located (in /Library/Frameworks/VapourSynth.framework/libs) and not in /usr/local/lib. You can either create a link or download library file itself. As for the issues with mv.Super, can you provide the error messages so I can investigate?

Side note, if you are already using brew to install some things, I would recommend using it to install vapoursynth as well, this will help to avoid any issues of finding dependencies as they will all be in a single location. The installer is intended to be used if you do not wish to install xcode & brew and creates it's own self contained environment to not conflict with anything already installed. This is to maintain it working and not break things if other updates are done (like if you are using brew and update FFmpeg beyond the version FFMS2 or LSMASHSource was compiled to be compatible with). This means that the location /Library/Frameworks/VapourSynth.framework will need it's own copy of each dependency, or you can create links to them.

Last edited by l33tmeatwad; 15th June 2018 at 16:43.
l33tmeatwad is offline   Reply With Quote