1 Reply by Falconbox

(1 replies, posted in Using SVP)

Ok, I largely fixed most of the issues.  Uninstalled AviSynth, direct installed AviSynth+, and then had a new error which was solved by having to paste the AviSynth MT into the syswow64 folder (thanks to this post from Ganfall here: https://www.svp-team.com/forum/viewtopic.php?id=2761).

Now the only issue is that MeGUI, when I go to use the script to encode a video and click to open with DirectShowSource, I get:

http://i.imgur.com/LKFS2zW.png

which is weird, since I still have the DirectShowSource.dll file in the MeGUI Program Files x86 folder, so idk where it's attempting to look for it.

I CAN encode the video with MeGUI's One-Click method though, so I guess that will have to do for now, unless someone can maybe figure out what the issue is.

Go to forum: Using SVP

2 Topic by Falconbox

(1 replies, posted in Using SVP)

Hi everyone,

Sorry if this is a dumb question, as I'm new to most of this.  I've been using Spirton's method for converting 30fps clips to 60fps, which I've used for simple clips and gifs (http://www.spirton.com/convert-videos-to-60fps/).  I recently learned of SVP and installed SVP4 to watch longer videos in real-time.

However, after installing SVP4, it seems to mess with MeGUI.  When attempting to save an avs script, I receive the following error message:

http://i.imgur.com/2F2KJAR.png

If I reinstall Avisynth 2.6, it fixes the error, however it then breaks SVP4.  When playing a video then, I receive the following errors in the log for SVP, and also at the top of the video while it is playing:

http://i.imgur.com/bqu2UK0.png

Uninstalling and re-installing SVP fixes SVP, but brings the MeGUI error back.  Can someone who help me as to what I can do here?   Thanks.



EDIT:  I see in the changelogs that SVP now uses Avisynth+ as of April.  Could it be the Interframe 2.8.2 script, which is part of Spirton's method...is it not compatible with Avisynth+?   If so, is there anything I can do to make it compatible?

Go to forum: Using SVP