Upscaling to 60FPS with MeGUI/Avisynth trouble....

[FormulaFox]

Okay, so... I know there's a lot to be said about the headaches of this process around the internet, but there's actually so much that I can't parse through it and what I've been able to try from it has utterly failed me... So as a last ditch attempt to solve this, here I sit asking for personalized help in the hopes that someone either has, or can help me find, the smoking gun that will fix this weirdness.

So, a while back I used this guide: http://www.spirton.com/convert-videos-to-60fps/ to start using to MeGUI to upscale various content to 60FPS. As someone who's on the go a lot but doesn't have a data plan, having pre-converted 60FPS videos is rather nice.

For a long time, it worked well, and all was good. But recently after installing an SSD(no other changes) and doing a Windows reset, I can't get it to work. So here's my specific problem...

I've never been able to get MeGUI to update as recommended in the guide, and with my recent troubles that's been no different. This problem I always fixed with a certain batch of files(found at https://sourceforge.net/projects/megui/), but this time it hasn't worked. I've looked up a few suggested fixes for the errors I get, but each one just lead to another error.

I can't recall all the errors I've gotten or the changes made to trigger them, so for now I've cleaned out MeGUI and restarted the process down to when the first error occurs. Seems the best point to start at.

I have the script entered into the system, adjusted for my computer(Cores set to 6 and GPU set to True), as it was before, but when I load the file I wish to upscale, and click Save, I get"

"The File D:\Video\Upscales\filename.AVS Cannot be opened.
Please make sure that it is a valid Avisynth script and that Avisynth is properly installed
Error message for your reference: Can't read the video stream."

This would seem to point to an issue with the codecs installed on my system, but I can find no issue to explain it. If I tell it to try and queue the job anyway, I get another error:

"Your Avisynth clip has the following problem
Error in Avisynth script:
ScriptError: There is no function named 'SetMTMode.'
(D:\Video\Upscales\filename.avs, line 3)
Continue anyway?"

Saying yes queues the file, but unsurprisingly it errors out(and does not give a popup for WHAT error) when you try to start it.

So what should I do first?

Thank you in advance for any and all help provided.

[Cauptain]

Just install the correct version for correct system (32 or 64 bits).

Look here: http://forum.doom9.org/showthread.php?t=174614




Claudio

[LigH.de]

For people who install MeGUI, but no additional system-wide AviSynth version, MeGUI contains a portable fallback version of AviSynth+ (notice the "plus"). This does not use "SetMTMode" like in SEt's AviSynth MT, though.

If you have installed AviSynth, MeGUI should use that version which is installed in your Windows system (except you always prefer its internal copy). If that is not SEt's AviSynth MT either, then "SetMTMode" isn't available either.

In any case, always post a complete log file of an MeGUI session, from a time after you closed MeGUI (so the log is properly closed and complete). So we can check your MeGUI version, the used AviSynth version, the whole AviSynth script, etc.

Being unable to update MeGUI to the most recent development version requires an investigation as well.

[FormulaFox]

For people who install MeGUI, but no additional system-wide AviSynth version, MeGUI contains a portable fallback version of AviSynth+ (notice the "plus"). This does not use "SetMTMode" like in SEt's AviSynth MT, though.

If you have installed AviSynth, MeGUI should use that version which is installed in your Windows system (except you always prefer its internal copy). If that is not SEt's AviSynth MT either, then "SetMTMode" isn't available either.

In any case, always post a complete log file of an MeGUI session, from a time after you closed MeGUI (so the log is properly closed and complete). So we can check your MeGUI version, the used AviSynth version, the whole AviSynth script, etc.

Being unable to update MeGUI to the most recent development version requires an investigation as well.

I have installed Avisynth separately, as recommended in the process on the page I linked.

I knew there was something I wasn't thinking of when posting this sofar as providing information, though; The log file. That would be kind of important and I feel like an idiot for forgetting. But I've attached one for you to look at now - I just ran through the process that's been stumping me to generate a fresh log to make sure I didn't post the wrong one.

[FormulaFox]

Just install the correct version for correct system (32 or 64 bits).

Look here: http://forum.doom9.org/showthread.php?t=174614




Claudio

This thread is one of the ones I stumbled across while trying to research the problem previously. The information contained within did not fix my problem - it merely changed what the error referred to.

[jagabo]

You need a multithreaded build of AviSynth to use SetMtMode(). The regular AviSynth is not multithreaded. I'm not sure if this is the latest build:

http://forum.doom9.org/showthread.php?t=148782

Or you can just remove the SetMtMode() line(s) from your script. It will run slower though.

[FormulaFox]

You need a multithreaded build of AviSynth to use SetMtMode(). The regular AviSynth is not multithreaded. I'm not sure if this is the latest build:

http://forum.doom9.org/showthread.php?t=148782

Or you can just remove the SetMtMode() line(s) from your script. It will run slower though.

Both of those were steps I tried before which failed - the multithread Avisynth gives the same error as before, removing SetMTMode generates a new error;

"Your Avisynth clip has the following problem:
Error in Avisynth script:
Cannot load a 32-bit DLL in 64-bit Avisynth: 'C:/Program Files (x86)/MeGUI/tools/avisynth_plugin/svpflow1.dll'"

This error is particularly confusing to me as while trying to troubleshoot previously, I've gotten it even if I made sure there was a 2-bit Avisynth isntalled.

Attached the resulting log files from both updating the Avisynth, and removing the SetMTMode lines. (log files are named appropriately)

I also need to point out that while we're focusing on the SetMTMode issue, the FIRST error I've been getting seems to have been completely ignored.

[LigH.de]

If you get an error about things not working in a 64-bit AviSynth, then the script was called by a 64-bit application.

---[Warning] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] Date: 20-02-2015
----[Information] Name: Avisynth 2.6
----[Warning] Status: Installed AviSynth build cannot be used. Switching to the portable build.
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 29-06-2017
----[Information] Name: AviSynth+ 0.1 (r2508, MT, x86_64)
----[Information] Version: AviSynth+ 0.1 (r2508, MT, x86_64)
----[Information] AviSynth+: true
----[Information] MT: true
----[Information] Status: active

MeGUI doesn't want to use the AviSynth version you installed; it prefers its portable AviSynth+ version. And then it prefers its 64-bit version.

You may be able to run your script manually, calling the encoder with e.g. avs4x26x to use a 64-bit encoder via a 32-bit "bridge". But loading it in MeGUI may not work until you find a version of SVPFlow compatible with AviSynth+ 64-bit...

The more custom your scripts are, the less likely they can be supported by converter GUIs which must rely on a specific set of components.

[FormulaFox]

Unfortunately I know absolutely nothing about running Avisynth scripts manually. This is one area where I'm a complete and utter moron.

The strange thing is that the SVPFlow dlls are supposed to be both 32 and 64 bit compatible from what I understand.

[FormulaFox]

Okay, so, I got it to work. Something must've gone wrong with the SVPFlow installation that caused the DLLs to be recognized incorrectly - I reinstalled SVP and copied the DLLs to the appropriate location, and it worked.

However, I still have to remove the SetMT lines to make it work. From what little I understand of multithreading, this means I'll have slower conversions. So while everything WORKS, it'd be nice if we could figure out how to fix the SetMT problem. There's got to be SOMETHING, it's just a question of whether or not we can find it.

I doubt it will help, but I've attached the log from the attempt with the MT mode lines still in the script just to cover all bases.

[FormulaFox]

Whoops, I forgot to actually ADD the log before submitting. My bad. Here you go.

[jagabo]

I think the log says you're running AviSynth+.
http://avisynth.nl/index.php/AviSynth%2B#Setting_MT_modes

[FormulaFox]

I think the log says you're running AviSynth+.
http://avisynth.nl/index.php/AviSynth%2B#Setting_MT_modes

Following that information results in the same error as before, just with SetFilterMTMode instead of SetMTMode.

[FormulaFox]

I think the log says you're running AviSynth+.
http://avisynth.nl/index.php/AviSynth%2B#Setting_MT_modes

Following that information results in the same error as before, just with SetFilterMTMode instead of SetMTMode.

Sorry, forgot to post log file again.

[poisondeathray]

It should be

SetFilterMTMode("DEFAULT_MT_MODE", 2)

When I use

SetFilterMTMode(2)

I get the same error message as you

You need to add Prefetch(some number) at the end as well . Try 4 first . Use avsmeter to test which settings are the fastest with lowest cpu usage

[FormulaFox]

It should be

SetFilterMTMode("DEFAULT_MT_MODE", 2)

When I use

SetFilterMTMode(2)

I get the same error message as you

You need to add Prefetch(some number) at the end as well . Try 4 first

The previous log included a test where I add Prefetch(2) to the end of the script - first try I'd forgotten it. Result was the same both times.

Making the adjustment recommended results in the same error. Log attached.

[FormulaFox]

Hold up, I think I got it. Running a full test now.

[FormulaFox]

All right, thanks to that last post I got everything running now.

The final issue was that instead of altering the FIRST SetMTMode line to Avisynth+'s preferred form, you DELETE that from the script. Completely. This does not work in the original form of the script, of course; The second SetMTMode input must be altered to the Avisynth+ version.

I'll be making a little note of this stuff to put into my backup files for future reference. Thank you all for your assistance - my test files are coming out nicely. Any optimization recommendations for number of threads would be nice(avsmeter just confused me until my brain oozed out my ears...), but 4 seems to be balanced fairly well(CPU not getting terribly hot, and files are processing fairly quickly) so I'm not TOO worried about it.