Avisynth 64 Troubles...

[EvaFan]

Just wanted to clear up my last post cause it is kind of confusing.

What I did was take the 64 bit dgdecode.dll file and replace the 32 bit dgdecode.dll in my dgindex folder. I reindexed deleting the old .d2v for a new copy. This was the problem, both dgindex's dgdecode and the one avisynth is using has to be the same 64bit or 32 bit. I noticed alot of ppl having problems on the internet that could be related to why they can't get 32 to work but can get 64 to work or vice versa.

On a somewhat related note:

Code: Select all

Mpeg2source("F:\hack.d2v")
interp = separatefields().selecteven().eedi2()
tdeint(edeint=interp)
removegrain(mode=5)
fft3dfilter(bw=6, bh=6, ow=3, oh=3, plane=0, bt=1, sigma=6)
fft3dfilter(bw=216, bh=216, ow=108, oh=108, plane=4, bt=3, sigma=6/8, sigma2=6/4, sigma3=6/2, sigma4=6,sharpen=0.6)
gradfun2db()
Tweak(hue=1.0,sat=1.3,bright=-0.2,cont=1.0)
crop(4,0,-4,0)
spline36resize(848,480)

Render rate as avi from vdub: 5.6fps

and:

Code: Select all

setmtmode(2,6)
Mpeg2source("F:\hack.d2v")
interp = separatefields().selecteven().eedi2()
tdeint(edeint=interp)
removegrain(mode=5)
fft3dfilter(bw=6, bh=6, ow=3, oh=3, plane=0, bt=1, sigma=6)
fft3dfilter(bw=216, bh=216, ow=108, oh=108, plane=4, bt=3, sigma=6/8, sigma2=6/4, sigma3=6/2, sigma4=6,sharpen=0.6)
gradfun2db()
Tweak(hue=1.0,sat=1.3,bright=-0.2,cont=1.0)
crop(4,0,-4,0)
spline36resize(848,480)

15fps rate... I shat bricks... I could practically edit with the filters attached. That was just adding a simple mt line... with more testing could do even better. Supposedly resizing doesn't work unless you resize height and width seperately but it works for me just fine. No clue why.


All in all if you can run avisynth 64 and get it working, IT IS WORTH IT.

[Pwolf]

hmm, i didn't have that issue. i just copied the dll from the 64bit version into my 64bti plugins folder. my dgindex is 1.5.8 for both 32 and 64bit though, maybe that was the issue, your 32bit version wasn't that same.

let me know how editing goes with the premiere plugin, there's a few issues with it.

[BasharOfTheAges]

Sounds like it might be beneficial for simple filter chains even when you're dumping files to disc. Even with a decent system, BRD resolution processing is slow.

[EvaFan]

let me know how editing goes with the premiere plugin, there's a few issues with it.

Will test either tomorrow or day after and post here.

Sounds like it might be beneficial for simple filter chains even when you're dumping files to disc. Even with a decent system, BRD resolution processing is slow.

I should add that the speed gains from switching to avisynth 64 bit (I think I read somewhere online 15% speed boost) isn't nearly as beneficial as using the MT (multithreading, works in same way for multicore processors too). Since there is a MT avisynth version for 32 bit, you don't necesarily have to switch to avisynth 64 if the trials and tribulations of getting it all to work worries you. That single MT line gave me a 3x speed boost. I checked my taskbar performance pane and all 6 cores were running 97-100%. I might Overclock this thing sometime next week since I have leeway with liquid cooling.

Using the MT version requires some reading though for compatability flaws and other problems with filters. Nothing near a reason to turn a blind eye to it considering the performance gains.

[BasharOfTheAges]

Even 15% is something when you're doing 30+ hours of transcoding.

[Mister Hatt]

Stop using old avisynth, seriously, 2.6 is out, use it.
Stop reading avs scripts in your media player or NLE, it is NOT made for that and will be terribly slow. I don't know why you want to do this instead of lossless, but if you really feel like waiting a few seconds for each frame, then go ahead.
Avisynth in 64bit is dumb anyway, don't use it. There is NO advantage in doing so.
MT is also dumb, and causes all sorts of problems that you probably aren't even aware of. Explaining half of this is too difficult so :trustme: orz.

@pwolf: if you still don't kow, DeViL.dll is a library for handling PNG files, it is mostly used by the imagesource/read/write functions.

[Pwolf]

Stop using old avisynth, seriously, 2.6 is out, use it.
Stop reading avs scripts in your media player or NLE, it is NOT made for that and will be terribly slow. I don't know why you want to do this instead of lossless, but if you really feel like waiting a few seconds for each frame, then go ahead.
Avisynth in 64bit is dumb anyway, don't use it. There is NO advantage in doing so.
MT is also dumb, and causes all sorts of problems that you probably aren't even aware of. Explaining half of this is too difficult so :trustme: orz.

@pwolf: if you still don't kow, DeViL.dll is a library for handling PNG files, it is mostly used by the imagesource/read/write functions.

I'm going to disagree that there "no" advantage in using avisynth 64bit. I've been using avisynth in premiere for years and it's been very useful. upgrading to CS5 forces me to use 64bit. For simple import and IVTC, thats fine. If i was going to do any more filtering, i would convert to lossless. The loss in speed is too much of a bottleneck to my workflow. Actually, in most cases, i usually just convert to lossess. It doesn't take me long to do the encoding and i have plenty of space. I also wouldn't use 64bit avisynth to do it either.

[Castor Troy]

Stop using old avisynth, seriously, 2.6 is out, use it.
Stop reading avs scripts in your media player or NLE, it is NOT made for that and will be terribly slow. I don't know why you want to do this instead of lossless, but if you really feel like waiting a few seconds for each frame, then go ahead.
Avisynth in 64bit is dumb anyway, don't use it. There is NO advantage in doing so.
MT is also dumb, and causes all sorts of problems that you probably aren't even aware of. Explaining half of this is too difficult so :trustme: orz.

@pwolf: if you still don't kow, DeViL.dll is a library for handling PNG files, it is mostly used by the imagesource/read/write functions.

I'm going to disagree that there "no" advantage in using avisynth 64bit. I've been using avisynth in premiere for years and it's been very useful. upgrading to CS5 forces me to use 64bit. For simple import and IVTC, thats fine. If i was going to do any more filtering, i would convert to lossless. The loss in speed is too much of a bottleneck to my workflow. Actually, in most cases, i usually just convert to lossess. It doesn't take me long to do the encoding and i have plenty of space. I also wouldn't use 64bit avisynth to do it either.

I can't even edit anymore without complete access to every bit of footage thanks to using AVS scripts. I used to make huffy/lagariths of everything and it was the worst feeling ever when you realized you forgot to huffy/lag one part and you deleted the vobs off your hard drive.

Then again, hard drive space was small back then, but now it's become affordable for large amounts of it.

[mirkosp]

I just convert whole BDs to lossless. It's not like it's an issue when 2TB drives are 80 bucks...

[EvaFan]

Stop reading avs scripts in your media player or NLE, it is NOT made for that and will be terribly slow. I don't know why you want to do this instead of lossless, but if you really feel like waiting a few seconds for each frame, then go ahead.

You're right, you don't know and I don't really care to tell you why but let me just say I don't have any problems with FPS when I edit with an AVS.

Avisynth in 64bit is dumb anyway, don't use it. There is NO advantage in doing so.

Every plugin I've used with it so far has had a speed boost (some minor, some major) even without MT. All the plugins I use regularly have been ported to 64 now so I don't have any problems. That by itself is an advantage... The doom9 thread is all so litered with ppl showing speed advantage benchmarks.

MT is also dumb, and causes all sorts of problems that you probably aren't even aware of. Explaining half of this is too difficult so :trustme: orz.

Ok, I'll go ahead and believe you that it has all sorts of problems that I'm not aware of and that its dumb even though a simple avs line from mt triples my speed, however, since I'm not aware of the problems and am able to achieve a result that I like... There is no reason for me not to use it. I'm not a video analyst and neither are most of the people that watch AMVs. They aren't going to watch it and notice, this guy clearly used MT in avisynth causing this error in the video quality...

I might have to wait till next week to test the avs import plugin due to crazy holidays.