Avisynth 2.6 MT - Page 28

Keiyakusha · 5th September 2012, 10:29

so by latest api change what exactly we gained other than some broken plugins and scripts?

Atak_Snajpera · 5th September 2012, 11:13

Quote:

Originally Posted by manolito

This is a childish statement.

Latest statistics about marketshare of different Windows versions:
http://marketshare.hitslink.com/oper...11&qpcustomb=0

42.52% of all users still use XP. It would be a very bad idea to drop XP support at this time already...

Cheers
manolito

http://www.w3schools.com/browsers/browsers_os.asp

the_weirdo · 5th September 2012, 11:23

Quote:

Originally Posted by SEt

2) Correct passing of float parameters discussed here.

Those "buggy" scripts are broken by that change. IIUC, that "fix" isn't commited to CVS Repo yet. And here is IanB's opinion:

Quote:

Originally Posted by IanB

[...]
I am not say this should not be fixed, just that it will need banner headlines when we do.

I have had a quick look at doing this fix in ScriptFunction:: and although it is slightly more work it is still trivial and it will have less impact overall.

Like I've said before, I didn't complain at all. I discover that now a float value cannot pass to an int parameter like before, so just find those buggy functions and correct them. FYI, if f is a float, Float(f) is still valid even IsInt(f)=false.

manolito · 5th September 2012, 17:15

From the w3schools website:

Quote:

"There are three kinds of lies: lies, damn lies, and statistics."
Benjamin Disraeli

Groucho2004 · 5th September 2012, 17:30

Quote:

Originally Posted by Atak_Snajpera

http://www.w3schools.com/browsers/browsers_os.asp

I don't see how a statistic about the OS behind a browser is representative for the entire market share of an OS.

active1 · 8th September 2012, 13:48

Quote:

Originally Posted by SEt

People, these builds are not user-friendly: they are pretty stable and as bug free as possible, but API changes and breaking something old already broken are to be expected. Do not expect that everything will behave as in previous build, especially if you use 2.6 features.

any builds you mean?

SEt · 9th September 2012, 18:52

Any 2.6 builds.
But if you are using only 2.5 features (not 2.5 bugs) you should be pretty safe.

pbristow · 10th September 2012, 15:58

Please can we move the silly OS war somewhere else? It's hard enough to track the main discussion without that.

Stealth5325 · 19th September 2012, 00:23

SEt, thank you for all your hard work. I, as well as many others are in your debt.
I was wondering if you'd be so kind as to help me with the basic install of this AviSynth. I'm running Windows 7, with nothing but FFDShow, InterFrame, and AviSynth, and I can't for the life of me use AVISynth with FFDShow without an instant crash.
I'm installing as so:
Downloading the 2.6 ST (x86) from here: http://avisynth.org/mediawiki/Main_Page#Official_builds
Taking your version and putting in c:\windows\syswow64

Then, I run my media player (Win7 media center, properly configured with Win7DSFilterTweaker to enable FFDShow), and run a movie. If AVISynth is checked, instant crash. If not, runs fine. This is with and without a script in the box at all, and with all the options checked/not checked.

I would, of course like to run the 64 bit version, if you have one. I have both 32bit and 64 bit ffdshow installed, from the ffdshow-tryouts website. Most recent official version.
Any suggestions?
Thank you in advance kind sir.

wOxxOm · 19th September 2012, 00:36

Stealth5325, this might be caused by an incompatible plugin in avisynth\plugins folder, it could be either .dll or .avsi, and if I remember correctly I've used sysinternals' filemon to track which dll/avsi was causing the crash (options->filter = name of avisynth plugins folder). Just run a movie with ffdshow->avisynth enabled, and look in the end of filemon's log.

Stealth5325 · 19th September 2012, 01:32

wOxxOm, thank you for that idea.
I tried to have a look with process monitor, but the folder's not even being accessed.
Even deleting the folder and creating a dummy plugins folder didn't yield results. Any other ideas?

Stealth5325 · 19th September 2012, 02:43

More information:
I've also tried using the SVP project at www.svp-team.org. It works fine with MPC-HC, because it's using the 32 bit FFDShow and 32 bit filters. The minute I install FFDShow x64 and run the SVP manager, it crashes. I'm assuming that manager is running something through AVISynth.
I'm basically feeling like I can't use this 2.6 AVISynth on 64 bit FFDShow. Can anyone help?

Keiyakusha · 19th September 2012, 02:51

you right you can't have 64bit ffdshow. make sure all your playback chain is 32 bit, you lose nothing anyway.

Stealth5325 · 19th September 2012, 05:59

I've found basically the same thing. 64 bit AVISynth isn't working for me.
I am, however, wanting to use Windows Media Center to run everything, and of course, I use 64 bit Windows, because 4GB RAM doesn't cut it nowadays.
Any way to make 32 bit FFDShow work with 64 bit Windows Media Center?

Keiyakusha · 19th September 2012, 07:06

Oh I didn't though of WMC. No, you can't make x32 software work with x64...

forclip · 19th September 2012, 14:22

SEt, can you confirm that your recent build includes this commit? Because I get this problem again.

SubJunk · 19th September 2012, 20:56

Wish they would start using SVN or Git...

SEt · 20th September 2012, 12:52

Stealth5325
This build is 32 bit only, so you need 32 bit player. 64 bit builds of Avisynth 2.6 are unlikely.

forclip
Yes it does. Btw, in MT mode it worked this way all the time. If you want to investigate further be sure what mode (MT or not) is activated as they use different caches.

forclip · 20th September 2012, 13:48

Quote:

Originally Posted by SEt

If you want to investigate further be sure what mode (MT or not) is activated as they use different caches.

Thanks, very interesting. When I start my script with SetMTMode >=1 this problem seems to go away. Non-MT cache is broken?!

lansing · 26th September 2012, 21:36

i have a rare problem here, I can't get the mt running on my machine.

I'm using Windows 7 64bit, and installed everything correctly. A fresh official avisynth with no additional plugins, and then replace the avisynth.dll in the Syswow64 folder with the mt one. And when I called SetMTMode() whatever in the script, it works with no error. However when I tried on different filters, the speed boost I was supposed to get was not there, it just seems like the mt part was not even in the picture. I also tested with filters that were reported to work like trim(), limitedsharpenfaster().

When I ran a script like this on AVSmeter, the line that reports "active MT mode" was 0.

Code:

SetMtMode(2)
LimitedSharpenFaster()

19th September 2012, 00:36	#550 \| Link
wOxxOm Oz of the zOo Join Date: May 2005 Posts: 208	Stealth5325, this might be caused by an incompatible plugin in avisynth\plugins folder, it could be either .dll or .avsi, and if I remember correctly I've used sysinternals' filemon to track which dll/avsi was causing the crash (options->filter = name of avisynth plugins folder). Just run a movie with ffdshow->avisynth enabled, and look in the end of filemon's log. Last edited by wOxxOm; 19th September 2012 at 00:47.

19th September 2012, 02:43	#552 \| Link
Stealth5325 Registered User Join Date: Dec 2009 Posts: 4	More information: I've also tried using the SVP project at www.svp-team.org. It works fine with MPC-HC, because it's using the 32 bit FFDShow and 32 bit filters. The minute I install FFDShow x64 and run the SVP manager, it crashes. I'm assuming that manager is running something through AVISynth. I'm basically feeling like I can't use this 2.6 AVISynth on 64 bit FFDShow. Can anyone help? Last edited by Stealth5325; 19th September 2012 at 02:45.

19th September 2012, 20:56	#557 \| Link
SubJunk Registered User Join Date: Jun 2010 Posts: 443	Wish they would start using SVN or Git... __________________ InterFrame (HFR Conversion Script) :: MPlayer Builds

26th September 2012, 21:36	#560 \| Link
lansing Registered User Join Date: Sep 2006 Posts: 1,657	i have a rare problem here, I can't get the mt running on my machine. I'm using Windows 7 64bit, and installed everything correctly. A fresh official avisynth with no additional plugins, and then replace the avisynth.dll in the Syswow64 folder with the mt one. And when I called SetMTMode() whatever in the script, it works with no error. However when I tried on different filters, the speed boost I was supposed to get was not there, it just seems like the mt part was not even in the picture. I also tested with filters that were reported to work like trim(), limitedsharpenfaster(). When I ran a script like this on AVSmeter, the line that reports "active MT mode" was 0. Code: SetMtMode(2) LimitedSharpenFaster()

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

5th September 2012, 10:29	#541 \| Link
Keiyakusha 契約者 Join Date: Jun 2008 Posts: 1,576	so by latest api change what exactly we gained other than some broken plugins and scripts?

9th September 2012, 18:52	#547 \| Link
SEt Registered User Join Date: Aug 2007 Posts: 374	Any 2.6 builds. But if you are using only 2.5 features (not 2.5 bugs) you should be pretty safe.

10th September 2012, 15:58	#548 \| Link
pbristow Registered User Join Date: Jun 2009 Location: UK Posts: 263	Please can we move the silly OS war somewhere else? It's hard enough to track the main discussion without that.

19th September 2012, 00:23	#549 \| Link
Stealth5325 Registered User Join Date: Dec 2009 Posts: 4	SEt, thank you for all your hard work. I, as well as many others are in your debt. I was wondering if you'd be so kind as to help me with the basic install of this AviSynth. I'm running Windows 7, with nothing but FFDShow, InterFrame, and AviSynth, and I can't for the life of me use AVISynth with FFDShow without an instant crash. I'm installing as so: Downloading the 2.6 ST (x86) from here: http://avisynth.org/mediawiki/Main_Page#Official_builds Taking your version and putting in c:\windows\syswow64 Then, I run my media player (Win7 media center, properly configured with Win7DSFilterTweaker to enable FFDShow), and run a movie. If AVISynth is checked, instant crash. If not, runs fine. This is with and without a script in the box at all, and with all the options checked/not checked. I would, of course like to run the 64 bit version, if you have one. I have both 32bit and 64 bit ffdshow installed, from the ffdshow-tryouts website. Most recent official version. Any suggestions? Thank you in advance kind sir.

19th September 2012, 01:32	#551 \| Link
Stealth5325 Registered User Join Date: Dec 2009 Posts: 4	wOxxOm, thank you for that idea. I tried to have a look with process monitor, but the folder's not even being accessed. Even deleting the folder and creating a dummy plugins folder didn't yield results. Any other ideas?

19th September 2012, 02:51	#553 \| Link
Keiyakusha 契約者 Join Date: Jun 2008 Posts: 1,576	you right you can't have 64bit ffdshow. make sure all your playback chain is 32 bit, you lose nothing anyway.

19th September 2012, 05:59	#554 \| Link
Stealth5325 Registered User Join Date: Dec 2009 Posts: 4	I've found basically the same thing. 64 bit AVISynth isn't working for me. I am, however, wanting to use Windows Media Center to run everything, and of course, I use 64 bit Windows, because 4GB RAM doesn't cut it nowadays. Any way to make 32 bit FFDShow work with 64 bit Windows Media Center?

19th September 2012, 07:06	#555 \| Link
Keiyakusha 契約者 Join Date: Jun 2008 Posts: 1,576	Oh I didn't though of WMC. No, you can't make x32 software work with x64...

19th September 2012, 14:22	#556 \| Link
forclip Registered User Join Date: Dec 2009 Posts: 63	SEt, can you confirm that your recent build includes this commit? Because I get this problem again.

20th September 2012, 12:52	#558 \| Link
SEt Registered User Join Date: Aug 2007 Posts: 374	Stealth5325 This build is 32 bit only, so you need 32 bit player. 64 bit builds of Avisynth 2.6 are unlikely. forclip Yes it does. Btw, in MT mode it worked this way all the time. If you want to investigate further be sure what mode (MT or not) is activated as they use different caches.