PPs.: you need to rename AVSMeter64.exe to AVSMeter.exe
#Discworld scummvm code#
Ps.: you might have to copy some of the scripts from the 32bit avisynthPlugins-folder to the 64bit avisynthPlugins-folder since I don't know for sure whether I updated the 64bit when I updated the general code and the 32bit scripts. I started working on Avisynth 64bit support a while ago, but due to lack of time it's on ice for the time being. Note that this should work, but I haven't tested everything that much since I usually don't use 64bit Avisynth, but 64bit Vapoursynth (which for me usually is faster than 64bit Avisynth). To revert to 32bit, simply rename the '64bit\Avisynth'-folder and restart Hybrid. Tell me more, I mean, you know that you can change the order of the filters, right?Ībout using Avisynth 64bit simply extract a 64bit Avisynth Package into your "Hybrid/64bit folder" restart Hybrid, and check the Log-tab, it should report:Īvisynth plugin path: "PATH TO Hybrid"\64bit\Avisynth\avisynthPlugins Quote:Hybrid has a problem with the order in which masking and resizing is done. Interlaced VHS > H264, bob QTGMC and masked (nothing else). My current project is taking 3x longer than it should. Perhaps that can be addressed more quickly. I make make a new thread on the order of operations issue. Great app you have here, and I want to help make it better. Hybrid already uses 32 (isn't it self-contained?), and 64 shouldn't be much different. But I then have +64 installed, and use it frequently.
I don't like +32, and do not have it installed. In terms of replace, do you refer to filters trying to overwrite one another? Just do the Avisynth+ route. You'd need some sort of checkbox with a warning ("SOME STUFF MAY NOT WORK, ONLY FOR ADVANCED USERS!"), to switch out of 32-bit processing to 64. Even if only QTGMC works well, for now (or foreseeable fitire), it'd be a win. Yes, more stuff to maintain, but I think it's worth it. Some filters not being supported? Are you referring to general 32/64 issue? That's not a concern, and I support your project. If your worried about something secondary (in regards to size), like costs to host the larger files, then PM for email, let's talk. So I was forced to write an AVS script, then open it in Hybrid. Nothing special, just the Crop() and AddBorders(), not even the resizing, as test to 720x480 output. I tried to used Avisynth custom code within Hybrid, but it always crashed.
Trying to mask results in stretched AR with wrong matting. But it does have some limitations in the order of operations. Also a good lazy app, even if you know the scripting, I use it frequently. I keep touting Hybrid as a GUI for Avisynth newbie users (start Hybrid, then learn AvsPmod+Avisynth). Had to process to another intermediary lossless, then encode that in Hybrid.
-1.png "discworld scummvm")
Yes, I could learn Vapoursynth for the exact minimalist script (QTGMC, crop, addborder, resize), but there have been times where I wanted to run something more complex like KNLmeansCL (64-bit DLL), and could not. I'm not fond of the +32 version in general (+64 works perfectly). And it seems to make Hybrid less stable, and sometimes cascades to Hybrid crashing as well (usually just encode crashes, but not always). Yes, you can add the MT/+ syntax to make it faster, but it's just not stable. And that's where the problem comes in.Īvisynth QTGMC 32-bit is slow. Since it's better to deinterlace before a mask (not required, but more ideal), I also run QTGMC first.
0 kommentar(er)
