Avisynth 64 Troubles...

[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.

[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.

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.

How can you call IVTC simple if you're using a DVD and avisynth? There are, to my knowledge, only three people on this forum who can IVTC properly. So why bother taking the time to use AVS at all if you're not one of them?

I still do not agree that using a frameserver in an NLE is the right idea. Lossless is faster unless you suck at encoding/decoding it, especially when you consider frame access times compared to avisynth which is very reliant on the source plugins not being aids, as well as the processing time. Every time you access a frame outside the framecache, you are re-running the filterchain on it, which isn't exactly fast, especially when you're using temporal filters like field matching.

[Castor Troy]

How can you call IVTC simple if you're using a DVD and avisynth? There are, to my knowledge, only three people on this forum who can IVTC properly. So why bother taking the time to use AVS at all if you're not one of them?

I agree ErMaC, AbsoluteDestiny, and Zarxrax were quite the pioneers.

[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.

How can you call IVTC simple if you're using a DVD and avisynth? There are, to my knowledge, only three people on this forum who can IVTC properly. So why bother taking the time to use AVS at all if you're not one of them?

I still do not agree that using a frameserver in an NLE is the right idea. Lossless is faster unless you suck at encoding/decoding it, especially when you consider frame access times compared to avisynth which is very reliant on the source plugins not being aids, as well as the processing time. Every time you access a frame outside the framecache, you are re-running the filterchain on it, which isn't exactly fast, especially when you're using temporal filters like field matching.

I never said it would be a "proper" ivtc. For short and fast filter chains, using aviysnth in an NLE isn't all that bad if you don't have the disk space to convert to lossless (was the case back in the day). I personally try to convert all my stuff to lossless now, i also have the resource to make it more worth my while (CPU and disk space). I don't expect everyone to have that luxury. So while it is better to convert to lossless, if someone wants to edit with the scipts in an NLE, i don't see any reason for them not to. They're the ones who are going to have to deal with the slow editing.

There are, to my knowledge, only three people on this forum who can IVTC properly. So why bother taking the time to use AVS at all if you're not one of them?

Because only 3 people on this forum would notice a bad IVTC.

[mirkosp]

There are, to my knowledge, only three people on this forum who can IVTC properly. So why bother taking the time to use AVS at all if you're not one of them?

Because only 3 people on this forum would notice a bad IVTC.

Actually, a bad IVTC is prolly more obvious that you'd think it would be, really...
That said, there is a difference between "bad" and "acceptable," but Hatt doesn't quite agree on that...

[Pwolf]

There are, to my knowledge, only three people on this forum who can IVTC properly. So why bother taking the time to use AVS at all if you're not one of them?

Because only 3 people on this forum would notice a bad IVTC.

Actually, a bad IVTC is prolly more obvious that you'd think it would be, really...
That said, there is a difference between "bad" and "acceptable," but Hatt doesn't quite agree on that...

"bad" by what ever standard he's thinking of.