Support forum for DG Tools

Do you have QTGMC working in all 64-bit?

I haven't tried QTGMC yet.
I have been using some new filters instead. They do a darn good job overall.
You might have heard of them, names start with DG and end with NV.

Glad you like the new stuff. Don't be shy to suggest things.

I have a motion compensation solution running at 25 fps. It's RGB32 for now but conversion to YV12 should be a doddle. Famous last words, eh?

I abandoned the edge-based approach again.

should be a doddle. Famous last words, eh?

Done that a few times myself.
I've downloaded QTGMC and its core plugins.
Tomorrow, if I have time - its tax time up here, I'll try them out.

One thing i read, a user having problems running it solved it by renaming mvtools2.dll to mvtools.dll

No joy getting 32 bit plugin running in a 64 bit environment, so QTGMC is a no go.
I do have some 32 bit apps (1or 2) that I might still use on occasion and they don't like avisynth+ 32bit.
So, I replaced the avisynth+ dll is syswow64 with the one from 2.60. All is good, I hope.

<RANT> why does MS insist on putting 32 bit stuff in a folder with 64 on it, and 64 bit stuff in a folder with 32 in the name, why not use system32 for 32 bit and system64 for 64 bit<RANT>
I need a drink

There shouldn't be any problem with Avs+ 32 that would make you need to go to 2.60. Maybe you are missing a 32-bit runtime. Can you give details of the error? Also, run AVSMeter32 with -avsinfo and it should report any missing runtimes.

I can run QTGMC just fine on Win10 64.

Its not a problem with avisynth+ 32 bit
These apps check for avisynth version on launch, and so they refuse to actually launch.
I didn't mean run a 32 bit plugin on win 64 bit. Because of the CUDA Tools I learned some basic scripting and I use my settings for x264 to run my encodes with 64 bit apps.
That's how good your CUDA Tools are, not only do they do the job well but they got me to learn how to do avisynth scripting.
No biggie, if I encouter a situation where I need QTGMC I can run it with 32 bit avisynth

OK, I see.

I have both VirtualDub 32 and VirtualDub 64 installed. When I want to preview QTGMC stuff, then I just drop the script on Virtualdub 32. Of course, everything in the script must be 32-bit. I just use QTGMC as my gold standard for bobbing. For me, it's too slow to use in practice.

Actually, I can make my situation work well enough.
If I need an app that wants AviSynth 2.60, I drop in the old dll.
If I want to use Avisynth+ I just put in the new dll
I didn't have to change the DeviL.dll file.
But for now I am just trying to get the hang of the 64 bit chain, and adding 64 bit plugins as I encounter a need

What apps "want" 2.60 and can't use avs+?

BD_RB and possibly AVStoDVD (haven't tested this one yet)
Haven't used AVStoDVD so I might just remove it
BD_RB has some features that I can use for my series discs

They can all use Avs+. You just have to know how to set it up.

Dropping DLL's in system directories is a pain in the ass that should be avoided.

IMHO.

They can all use Avs+. You just have to know how to set it up.

Could you please give me a hint

Tomorrow. I'm watching telly now. Then off to bed.

Sounds like a plan

admin wrote:I have a motion compensation solution running at 25 fps. It's RGB32 for now but conversion to YV12 should be a doddle. Famous last words, eh?
I abandoned the edge-based approach again.

Cough, expectation set and lofty anticipation mode functioning.

To be more precise I have the motion estimation running. It's full per-pixel flow, not block-based. I still haven't done the compensation part but that is not computationally intensive.

@gonca

Reading up on BD Rebuilder it appears that there should be no obstacle to running with Avisynth+. Exactly what error condition are you running into?

Just got home from work so I couldn't answer earlier
Without Avisynth 2.60 dll in SysWOW64 BD_RB pops an error message upon launch and shuts down
Error message is "BD_RB needs Avisynth to function"

Before you drop it in there do you have the Avs+ avisynth 32-bit DLL in there? Another way to ask it: did you install both 32-bit and 64-bit Avs+?

Yes.
I believe BD_RB looks in SysWOW64 and queries avisynth.dll for a version number??
Avs+ doesn't have the right version number for acceptance by BD_RB, it wants original avisynth 2.58 and above
Its a very limited (niche) use thing so I can put up with it
Side note
Posted in BD_RB forum and asked jdobbs if he could make it so BD_RB works with avs+
Let us see what he says

Yes, I'll be interested in his reply. I have always thought of Avs+ as being in the category "2.6 and later".

2.6 is from mid 2015, so the + version would be later
Lets wait and see what the response is

I didn't see your post in the BDRB forum. Can you link it?

Anyway, I have BDRB running fine with Avs+ 32-bit in SysWOW64. BDRB reports it as not recommended version but it goes ahead and runs fine.

http://forum.doom9.org/showthread.php?t=174528
Are you using this version

AvisynthPlus-r2455-MT

I just get a refusal to load