Avisynth+

[ultim]

Originally Posted by real.finder

hi

I have two aWarpSharp in autoload folder, aWarpSharp and aWarpSharp2 by SEt

In normal avs if I use

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\aWarpSharp.dll")
someSource("E:\New.mkv")
aWarpSharp

green border will appear which mean that old aWarpSharp is using

but in avs+ only aWarpSharp2 will be used

I use this method in other cases also

Are you using the latest release (r1576)? This is something that should have been fixed there.

[real.finder]

Originally Posted by ultim

Are you using the latest release (r1576)? This is something that should have been fixed there.

yes, and even r1595 the same thing

[ultim]

Originally Posted by real.finder

yes, and even r1595 the same thing

the only difference between 1576 and 1595 is the cache, so if the former one didnt work, the latter one is no surprise.

anyway, thx for reporting, i'll investigate.

[list]

In Avisynth 2.58, i used to make it portable, and just place avisynth.dll and devil.dll beside my mplayerc player and play any avs's, just needed to run this .reg with these values for "installing" on my system manually, without any installer.
The reg file contains these register key values:

REGEDIT4

[HKEY_CLASSES_ROOT\avifile\Extensions\AVS]
@="{E6D6B700-124D-11D4-86F3-DB80AFD98778}"

[HKEY_CLASSES_ROOT\Media Type\Extensions\.avs]
"Source Filter"="{D3588AB0-0781-11CE-B03A-0020AF0BA770}"

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}]
@="Avisynth"

[HKEY_CLASSES_ROOT\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}\InProcServer32]
@="avisynth.dll"
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\Wow6432Node\Media Type\Extensions\.avs]
@=""
"Source Filter"="{D3588AB0-0781-11CE-B03A-0020AF0BA770}"

[HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\WOW6432NODE\CLSID\{E6D6B700-124D-11D4-86F3-DB80AFD98778}\INPROCSERVER32]
@="AviSynth.dll"
"ThreadingModel"="Apartment"

But now, this dosn't work with avsPlus. So i needed to run the full install to make it work.
What would be the new .reg equivalent now to meke it portable if possible?
BTW the project looks promising

[qyot27]

I'm guessing that due to the use of C++11 (the future header and whatnot), the MT additions will bump the compiler requirements up to VS 2012 or higher?

[innocenat]

Originally Posted by qyot27

I'm guessing that due to the use of C++11 (the future header and whatnot), the MT additions will bump the compiler requirements up to VS 2012 or higher?

Yes, the MT additions will bump the compiler requirement to VS2012. (It's actually already available in MT branch on GitHub)

[qyot27]

Originally Posted by innocenat

Yes, the MT additions will bump the compiler requirement to VS2012. (It's actually already available in MT branch on GitHub)

Okay. That's why I asked; it failed to build under 2010.

[jpsdr]

Will avs+ still working under Windows XP after MT...?

[TurboPascal7]

Originally Posted by jpsdr

Will avs+ still working under Windows XP after MT...?

Yes. Public builds have been compiled with VS2012 since the beginning I think.

But I'm afraid it won't work in wine anymore, at least my threaded plugins don't.

[ultim]

OK, seeing that words about the MT version is beginning to spread on the forums, I'd like to point out that it is very experimental and still has some problems. I am very gratefull if anybody wants to test and give feedback / problem reports, but if your motivation is not to test but to start using it earlier, don't. The quality is not there yet. I'll announce in this thread when it reaches a quality niveau worthy of public testing. That being said, you can find the experimental builds on http://goo.gl/e0VFYn . Just remember, don't use it until you're prepared that it will break.

[easyfab]

Do we need some setmtmode() or mt() or is it automaticaly multithreaded ?

[ultim]

Originally Posted by easyfab

Do we need some setmtmode() or mt() or is it automaticaly multithreaded ?

You need to enable MT operation in the script. But let's just first test the single-threaded mode...

[naoan]

Originally Posted by ultim

You need to enable MT operation in the script. But let's just first test the single-threaded mode...

Is SetFilterMTMode disabled on that build?

[innocenat]

Originally Posted by naoan

Is SetFilterMTMode disabled on that build?

There is no public MT build yet.

[naoan]

Oh sorry, I thought it is with experimental.

[TurboPascal7]

Okay, it appears I was right and new experimental threaded builds do not work in wine. If anyone figures how to run it - please feel free to post the instructions. Otherwise poor linux users won't be able to enjoy any newer build of avs+ until native support is implemented and plugins are ported or this gets fixed in wine.

[ultim]

Originally Posted by TurboPascal7

Okay, it appears I was right and new experimental threaded builds do not work in wine. If anyone figures how to run it - please feel free to post the instructions. Otherwise poor linux users won't be able to enjoy any newer build of avs+ until native support is implemented and plugins are ported or this gets fixed in wine.

It is most probably because of the threading bits of the VC++2012 runtime.

Possible solutions:
- Get the VC++2012 runtime somehow correctly working on Wine.
- Submit bug report to Wine and have it fixed.
- Wait for native Linux support in avs+ so that Wine won't be needed.

[dvdan23]

The bug which prevents vc++2012 from installing under WINE was reported in 2009

http://bugs.winehq.org/show_bug.cgi?id=17273

Waiting for that to get fixed seems like a long shot, though it has been targeted for 1.8 for whatever that's worth.

As awesome as it sounds, waiting for "native Linux support" seems fraught with peril also, since many have attempted this in the past and not quite made it (Avisynth3, avxsynth, vapoursynth).

Ultim, have you taken some time to assess the downsides of limiting yourself to VC++2010 SP1? if you would consider it at least one linux user will rejoice.

http://appdb.winehq.org/objectManager.php?sClass=application&iId=5766

[TurboPascal7]

Actually, getting native linux support on the core side is not hard. You can expect the core to work in its full power, unlike avxsynth that removed optimizations and some filters which didn't have C versions, avisynth 3 that didn't happen or vsynth, which is vsynth. You'll also get some essential plugins from avs+ modernization efforts thread and maybe some more. But of course it'll be quite a while before any serious scripts like qtgmc can run on linux. As usual - patches welcome.

To replace vs2012 features with vs2010, one will need to introduce some huge dependency like boost. This was discussed already and we decided that using C++11 is a better option. Also Myrsloik promised to kill me if we don't go C++11 and you don't want that, do you? >__>

[ultim]

It is pretty much as Turbo explained. I have originally implemented avs+MT with only boost, and thus I could compile the code with VC++2010. Because of the threading part I was relying on the non-header-only libraries of boost (but even with headers only, boost is a beast considering its size). So later the requirement was bumped to VC++2012 in order to remove the boost dependency, because C++11 implements everything I used from boost, but VC++2010 doesn't yet implement the necessary parts of the standard.

Anyway, I didn't foresee that it would break Wine-support, that hit me unexpected. IMHO we should try to put some pressure on the Wine folks, and depending on what their reaction is, we either win, or I can step back and pull in boost again. I'd rather not though unless it is really necessary, so let's try convincing the Wine folks first. It's on their to-do list anyway