avisynth on 64 bit processor

[whatyaar]

Hello guys, mine is a similar but more n00bish question..i tried googling for more than an hour and also here...most of the links are not working. i bought a new laptop with win 7 home premium and x64 processor.i tried somany times installing and uninstalling avisynth after long time found that there is an avisynth 64bit version and its a .dll then about the plugins and where we have to load the plugins and where i can find. More than that i curious about this thing ' read somewhere that avisynth 32 bit was also used in 64 by piping something i never understood that one. installed megui and it hardly taken less than 2 mins for d2v creation but its not loading avisynth. please help me guys.

[whatyaar]

sorry to give bump, i was really waiting for the solution.

[Guest]

Did you have a specific question?

[whatyaar]

Did you have a specific question?

yes sir, how to make use of avisynth on 64 bit processor. Mine is Intel I5 win 7. I believe there should be a thread for this. I followed some replies in net and able to download avisynth 64 from some place and also some 10 filters..avisynth 64 is only a .dll and .reg file so how can i use filters.
Ok, how to use avisynth 32 bit and all those filters in 64 bit win 7 system. Please help me.

Thanks,
WY.

[IanB]

The 64bit Avisynth is a very restricted subset of version 2.5.6. Large amount of the code for the internal filters are written as inline assembler for 32 bit MSVC++ and in many cases there is no C++ equivalent code. Squid80 did a mammoth job just to isolate a workable amount of the code and make it build, and he converted a token amount of assembler code to 64 bit format at great personal effort. Because of the lack of optimised MMX/SSE assembler code, the 64bit version is considerable slower than the 32 bit version and in many cases filters and codec simply do not exist. It is truly an experimental version for appropriately equipped fellow 64bit developers. If you are not prepared to accept it on those terms then you most likely should not be using it.

64bit Windows 7 runs 32bit software very well. A standard Avisynth install works quite well, most problems come from people attempting to use non mainline features like the "Standalone, Unpack files only" install type (sorry for the confusion in the incorrect foreign translations of the text for this option). By using the 32bit version all of your favourite filters and applications are available.

Some clever people have discovered by using piping they can efficiently transfer data between 32bit process and 64bit processes. This allows the results of complicated Avisynth scripts running in a 32bit process to be used in a subsequent 64bit encoder process.

If you want to volunteer to collate information about using Avisynth with 64Bit Windows 7, you will be warmly welcomed. I am sure many will appreciate such efforts.

[whatyaar]

The 64bit Avisynth is a very restricted subset of version 2.5.6. Large amount of the code for the internal filters are written as inline assembler for 32 bit MSVC++ and in many cases there is no C++ equivalent code. Squid80 did a mammoth job just to isolate a workable amount of the code and make it build, and he converted a token amount of assembler code to 64 bit format at great personal effort. Because of the lack of optimised MMX/SSE assembler code, the 64bit version is considerable slower than the 32 bit version and in many cases filters and codec simply do not exist. It is truly an experimental version for appropriately equipped fellow 64bit developers. If you are not prepared to accept it on those terms then you most likely should not be using it.

64bit Windows 7 runs 32bit software very well. A standard Avisynth install works quite well, most problems come from people attempting to use non mainline features like the "Standalone, Unpack files only" install type (sorry for the confusion in the incorrect foreign translations of the text for this option). By using the 32bit version all of your favourite filters and applications are available.

Some clever people have discovered by using piping they can efficiently transfer data between 32bit process and 64bit processes. This allows the results of complicated Avisynth scripts running in a 32bit process to be used in a subsequent 64bit encoder process.

If you want to volunteer to collate information about using Avisynth with 64Bit Windows 7, you will be warmly welcomed. I am sure many will appreciate such efforts.

Thanks for the reply. I will surely like to do if more people turn up.Right now i am getting close to my thesis, so give me time. I installed avisynth 2.5.7 32 bit and tried (yeah i installed the files i dint used standalone version)before, its not working may be i am missing some thing. No matter what the filter i use its giving errors, so manually coded with loadplugin for every filter then its saying unable to load and sometimes its not a avisynth 2.5 filter. I like to know what is this piping thing and how it to be done. One more time i have no problems if the 32 bit version runs on 64 bit...but it dint for me thats the problem.

[IanB]

Why 2.5.7, not 2.5.8?

> ... the filter i use its giving errors, ...

Clairvoyance is something I am not endowed with, you are going to have to quote the error messages, in full, with context, if you want help.

The piping is a function of the 64bit encoder application, so you will need to ask people supporting your 64bit encoder application of choice, hint H.624 subforum.


Mods, this thread might do better in the usage forum, can you please split from post 7 into a new thread.

[whatyaar]

surely i will get back with some error messages and screenshots...just now did a system restore. i regged the avisynth64 bit file before..give me sometime for now i have to meet some deadlines for my thesis on sunday.

[Wilbert]

Moved to usage forum.

[hydra3333]

Er, why 2.5.8, instead of TSP's 2.5.7 MT-0.7 version to gain reliable multi-threading ? I wonder if there's a link explaining what extras you get from 2.5.8 over 2.5.7 (and losing multi-threading) ?

[Blue_MiSfit]

There are MT builds of 2.5.8. In fact, they're a lot better than TSP's old MT builds.

Look in the AviSynth development thread. I believe SEt was the guy who made 2.5.8 MT happen.

~MiSfit

[IanB]

Er, why 2.5.8, instead of TSP's 2.5.7 MT-0.7 version to gain reliable multi-threading ? I wonder if there's a link explaining what extras you get from 2.5.8 over 2.5.7 (and losing multi-threading) ?
I cannot find any reference to using MT versions in whatyaar's posts. Maybe your clairvoyance is more highly attuned than mine ;)

For anyone starting with Avisynth I would strongly recommend avoiding all of the experimental builds. The point when a user is ready to experiment with experimental builds is when they have learnt to say at the beginning of post "I am having a problem using xyzzy versions of Avisynth built by plugh, I have also tested with the standard 2.5.8 version of Avisynth and the problem [does/does not] also occur" AND they post in the correct forum/thread AND they provide all of the salient information in the very first post.

[hydra3333]

I cannot find any reference to using MT versions in whatyaar's posts. Maybe your clairvoyance is more highly attuned than mine ;) My clairvoyance has not made me rich :) No, it occurred to me that whatyaar may not have been aware of the relative goodness of 2.5.8 single-threaded vs a reliable 2.5.7 multi-threaded (potentially vastly increased throughput)... which still applies to 64bit a I understand it.

There are MT builds of 2.5.8. In fact, they're a lot better than TSP's old MT builds.

Look in the AviSynth development thread. I believe SEt was the guy who made 2.5.8 MT happen.Thanks. I did read threads on that version some time ago and back then all I could ascertain was it was developmental and that people had problems with it. Must go look it again so see why it's a lot better (TSP's "just works" and keeps on doing so). Any hints on a link to diffs 2.5.8 vs 2.5.7 ?

[IanB]

... Any hints on a link to diffs 2.5.8 vs 2.5.7 ?AviSynth 2.5.8 [Dec 30th] - Release! (was RC-5 [Dec 27th])

[hydra3333]

Thanks. Followup question on MT continued over at http://forum.doom9.org/showthread.php?p=1330112#post1330112

[whatyaar]

Thanks for the replies guys. I am thankful to one and all for the friendly replies. 4 am...reached the deadline , will try your replies tomorrow. As said before this was a n00bish question. After following your replies i found that there is a special MultiThread edition of avisynth. Now i am confused can i use the mt for 64 bit processor and follow the instructions given my Mr.IanB in 2.5.8 MT thread.......so many questions. Well i try all what i can, with different versions of avisynth and give you a call. Once again guys (please bare with me, and i am thankful to it), I used avisynth 2.5.7 on my Dual Core notebook from a year or so and bought recently new notebook with core I5 processor and win 7. Trying to run avisynth on it and getting errors, i will post the screenshots and error messages what i will be doing tomorrow.

Once again thanks for your replies, and you are more friendlier than what i thought.

Thanks,
WY.

[whatyaar]

ok i followed this thread and taken care of all the steps mentioned in this thread..


http://forum.doom9.org/showthread.php?t=144852


now my avsp is not running saying some avsppro get errors and closing when i am trying to open megui and load the script i am getting this error



Megui Encountered a fatal error and may not be able to proceed. Reason: Attempted to read or write protected memory. this is often an indication that other memory is corrupt


These are the steps i followed..

i used revo uninstaller and removed all the reg files and installation folders of avisynth.

installed avisynth 2.5.8.
later replaced the dlls avisynth.dll and MT.dll in both system 32 and SysWOW64 folder. also copied and placed the mvcp71.dll and msvcr71.dll in syswow64 folder and avisynth plugins folder.

also installed the Visual C++ redistributable from the above thread.

Not getting what to do and try may be i am doing completely wrong please guide me.

Thanks,
WY.

[IanB]

Clear everything again!

Do a standard install of Avisynth 2.5.8!

Test with the simple "Version()" only script first.

Report the explicit problem you have with a basic configuration.


Include your script in full.

Include the exact error messages.

Include versions of all other involved software and where you actually obtained them from.

Only when everything is working 100% with a standard installation should you commence trying any experimental software.

At the point where any experimental software fails revert back to the standard software and confirm it still works.

[whatyaar]

ok i took care of those things and uninstalled avisynth and manually deleted all the dlls from system files.

now the megui shows....avisynth was not installed and saying to install it.

installed avisynth 2.5.8 downloaded from sourceforge.net

Now i am loading already created d2v in this system.

Megui dint asked for avisynth..i opened avs script creator and loaded d2v and analyizing the filter selected heavy noise , spiline 36 resize and auto crop.
every thing went good and it opened in megui..trying avsp

before that the basic script generated from megui


LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Users\wy\Desktop\VIDEO_TS\VTS_01_1.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
crop( 16, 124, -30, -128)

Spline36Resize(688,304) # Spline36 (Neutral)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\Convolution3DYV12.dll")
Convolution3D("movielq") # Heavy Noise

avsp opened and every thing going good..

source is progressive so i am not thinking about interlacer :)

adding remove grain- worked good

Temporalsoften(2,3,3,mode=2,scenechange=6)- this also working.



also tried thse and its working

removegrain(mode=4)
Temporalsoften(2,3,3,mode=2,scenechange=6)
MergeChroma(blur(-.36))
toon(.64)


vaguedenoiser was also working but when i added tweak color avsp is giving this errors


Traceback (most recent call last):
File "AvsP.pyo", line 5804, in OnMenuVideoRefresh
File "AvsP.pyo", line 8925, in ShowVideoFrame
File "AvsP.pyo", line 9467, in PaintAVIFrame
File "pyavs.pyo", line 322, in DrawFrame
File "pyavs.pyo", line 306, in _GetFrame
File "avisynth.pyo", line 309, in GetPitch
ValueError: NULL pointer access


Did some script like this and it started working....i dont know how.


LoadPlugin("C:\Program Files (x86)\megui\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("C:\Users\wy\Desktop\VIDEO_TS\VTS_01_1.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)

#deinterlace
removegrain(mode=17)
crop( 16, 124, -30, -128)


Temporalsoften(2,3,3,mode=2,scenechange=6)
MergeChroma(blur(-.36))
toon(.64)

Levels(0, 1, 255, 0, 255)

VagueDenoiser(threshold=0.8, method=1, nsteps=6,wavelet=1,percent=93,wiener=true)
dull = last
sharp = dull.limitedsharpenfaster(ss_x=1.6,ss_y=1.6,strength=100,overshoot=1,undershoot=1,edgemode=0,Smode=3,soft=30)
Soothe( sharp, dull, 18)

Tweak(bright=1,sat=1.45,cont=.98,hue=2)

Spline36Resize(688,304) # Spline36 (Neutral)
#LoadPlugin("C:\Program Files (x86)\megui\tools\avisynth_plugin\Convolution3DYV12.dll")
#Convolution3D("movielq") # Heavy Noise
undot()





also tried fft3d...at first it worked , and later its keep on showing access violation even after loading plugin



i really apologize for what happened.i dont know how come it working now. lets see the ripping started and the results. now going at 17FPS. if possible please comment on the script...i welcome brickbats. so this worked i like to test the next step on your advice.

Thanks,
WY.

[IanB]

I am glad it is now working properly for you.

I think. like a lot of new users, you tried to run before you have learned to walk. Using the experimental builds can have significant gain but involves some risk and can cause problems, problems that can require a very high level of experience to diagnose and solve.



Hint :- Make some system checkpoints before you start to experiment, rollbacks are much easier than uninstalling and reinstalling.

[whatyaar]

I am glad it is now working properly for you.

I think. like a lot of new users, you tried to run before you have learned to walk. Using the experimental builds can have significant gain but involves some risk and can cause problems, problems that can require a very high level of experience to diagnose and solve.



Hint :- Make some system checkpoints before you start to experiment, rollbacks are much easier than uninstalling and reinstalling.

yes thats what i did this time, thanks for ur suggestion. i will try the rest of the filter and let you know which ones are not working. while installing i also installed the extras this time....may be those...no idea.

[whatyaar]

i really want to know how to use avisynth 64 software. so if download the plugins do i have to load plugin everytime. And can you help where to look for piping thing i am not sure about it. but want to try .

[rack04]

i really want to know how to use avisynth 64 software. so if download the plugins do i have to load plugin everytime. And can you help where to look for piping thing i am not sure about it. but want to try .

For piping to x264 I use avs2yuv and pipebuf.

For example:

Pass 1
"C:\Program Files (x86)\avs2yuv\pipebuf.exe" "C:\Program Files (x86)\avs2yuv\avs2yuv.exe" "E:\Work\Couples Retreat.avs" - : "C:\Program Files\x264\x264.exe" --profile high --preset slower --tune film --pass 1 --bitrate 4354 --stats "E:\Work\Couples Retreat.stats" --level 4.1 --ref 6 --bframes 3 --keyint 48 --min-keyint 2 --vbv-bufsize 15000 --vbv-maxrate 15000 --aud --sar 1:1 --slices 4 --b-pyramid strict --nal-hrd vbr --aq-mode 4 --output NUL --qpfile "E:\Work\Couples Retreat_Qpfile.txt" --frames 163527 --stdin y4m - : 4

Pass 2
"C:\Program Files (x86)\avs2yuv\pipebuf.exe" "C:\Program Files (x86)\avs2yuv\avs2yuv.exe" "E:\Work\Couples Retreat.avs" - : "C:\Program Files\x264\x264.exe" --profile high --preset slower --tune film --pass 2 --bitrate 4354 --stats "E:\Work\Couples Retreat.stats" --level 4.1 --ref 6 --bframes 3 --keyint 48 --min-keyint 2 --vbv-bufsize 15000 --vbv-maxrate 15000 --aud --sar 1:1 --slices 4 --b-pyramid strict --nal-hrd vbr --aq-mode 4 --output "E:\Work\Couples Retreat-output.mkv" --qpfile "E:\Work\Couples Retreat_Qpfile.txt" --frames 163527 --stdin y4m - : 4

[whatyaar]

For piping to x264 I use avs2yuv and pipebuf.

For example:

Pass 1
"C:\Program Files (x86)\avs2yuv\pipebuf.exe" "C:\Program Files (x86)\avs2yuv\avs2yuv.exe" "E:\Work\Couples Retreat.avs" - : "C:\Program Files\x264\x264.exe" --profile high --preset slower --tune film --pass 1 --bitrate 4354 --stats "E:\Work\Couples Retreat.stats" --level 4.1 --ref 6 --bframes 3 --keyint 48 --min-keyint 2 --vbv-bufsize 15000 --vbv-maxrate 15000 --aud --sar 1:1 --slices 4 --b-pyramid strict --nal-hrd vbr --aq-mode 4 --output NUL --qpfile "E:\Work\Couples Retreat_Qpfile.txt" --frames 163527 --stdin y4m - : 4

Pass 2
"C:\Program Files (x86)\avs2yuv\pipebuf.exe" "C:\Program Files (x86)\avs2yuv\avs2yuv.exe" "E:\Work\Couples Retreat.avs" - : "C:\Program Files\x264\x264.exe" --profile high --preset slower --tune film --pass 2 --bitrate 4354 --stats "E:\Work\Couples Retreat.stats" --level 4.1 --ref 6 --bframes 3 --keyint 48 --min-keyint 2 --vbv-bufsize 15000 --vbv-maxrate 15000 --aud --sar 1:1 --slices 4 --b-pyramid strict --nal-hrd vbr --aq-mode 4 --output "E:\Work\Couples Retreat-output.mkv" --qpfile "E:\Work\Couples Retreat_Qpfile.txt" --frames 163527 --stdin y4m - : 4

thanks for replying...can you put more light on piping. i dont know anything. or guide me to proper threads. But thanks for replying and appreciate for that.