search

pinterf / AviSynthPlus

AviSynth with improvements
http://avs-plus.net
208 stars 24 forks source link

Avisynth+ x86 and Windows Server 2008 R2 x64 #32

Closed TbtBI closed 5 years ago

TbtBI commented 5 years ago

When trying SupTitle plugin with Avisynth+ x86 on Windows Server 2008 R2 x64 Standard, there is no output and the Avisynth process is hanging - example. Tested different older versions, the behavior is the same. Removing SupTitle, there is no problem - example. Using SupTitle plugin with AviSynth 2.6.0/2.6.1, there is no problem - example. Using SupTitle x64 and Avisynth+ x64, there is no problem. Here SupTitle plugin x86. On Windows 10 there is no such problem.

fuchanghao commented 5 years ago

Check if you don't install .net framework 4.5 or newer.

TbtBI commented 5 years ago

I had 4.72 installed. Uninstalled and installed 4.0, but no change - Avisynth+ x86 is still hanging.

pinterf commented 5 years ago

By this page .Net 4.0 is needed, maybe client profile is not enough? http://avisynth.nl/index.php?title=SupTitle

Unfortunately there are no source code is available (author had hdd crash), nor can I reproduce the problem.

As I see in the forum, Stax76 had also random problems. https://forum.doom9.org/showthread.php?t=148167&page=7

If the problem is of software (and not .net environment/c++ redistributable) related, we cannot do much. Sometimes things just work accidentally on one system and not on another. Maybe the plugin uses assumptions that are not true for all systems. Or since it's a hybrid C/C# (?) filter, the interface wrappers are more sensitive to the internal structures and exact sizes of basic Avisynth data types. E.g. introducing alpha plane in AVS+ one of the basic structures became 4-8 bytes larger than it was in the old times. As this plugin is using a v2.5 interface which had a lot of ugly "baked" code which was partly removed in Avisynth 2.6 and on, it's more prone to such scenarios.

TbtBI commented 5 years ago

I tried .Net 4.0 Full, but no change.

Thanks for the replies. I guess this ticket could be closed.