Avisynth+

[TheFluff]

The reason Avs+ is slower on a 32-bit non-SSE machine might also be because IIRC a bunch of ancient MMX optimizations that were at best completely useless on any sort of reasonable hardware were removed from Avs+ pretty early on. Don't expect software that is actually maintained to keep optimization for ancient hardware forever.

If Avs+ is slower on an i5 though you're probably doing something wrong.

[Groucho2004]

Originally Posted by TheFluff

If Avs+ is slower on an i5 though you're probably doing something wrong.

It's not. In the example above, heavy use of mvtools mainly contributes to the speed. Simple internal operations such as resizing are much faster with AVS+.

[tormento]

Plus, if you have a x64 capable CPU, I strongly suggest to jump on x64 train, where FPS can see up to 10-25% increase. Nowadays a Windows 10 x64 Pro license can be found on Amazon for a few bucks. Nonsense to stay on ancient XP.

[manolito]

Sorry I really cannot live without a couple of older 32-bit plugins. AVS64 is definitely not for me...

[Groucho2004]

Originally Posted by manolito

Sorry I really cannot live without a couple of older 32-bit plugins.

Just curious - which ones?

[ChaosKing]

Can you give an example? I never found a non working plugin for avs+.

[manolito]

Originally Posted by Groucho2004

Just curious - which ones?

The most important one is LogoAway which is a 32-bit VDub plugin. Easy to use, very nice results and relatively fast. I tried most of the available logo removers, and this one did beat them all.

I just glanced over the list of available 64-bit AVS plugins, and this list has grown considerably. With a little effort I could probably find 64-bit replacements for most of my plugins. But there is another reason why I am not going to do this:

I do video conversions on at least 3 different computers. There's the notorious ancient WinXP machine, there is one Win7-32 laptop (only 2GB Ram, the 64-bit Win7 version is too slow on this laptop, constant swapping), and another Win7-64bit laptop with 8GB RAM. I have no intention to maintain 3 different AVS plugins folders, it is hard enough for me to maintain just one plugins folder. Getting working plugin versions for several scripts like QTGMC, LSFMod, Srestore or Finesharp took me a long time, and I want to keep this configuration. I know that if everything works on the WinXP machine then it will also work on the other computers. Maybe a little bit slower than it could, but no headaches for me.


Cheers
manolito

[manolito]

Originally Posted by ChaosKing

Can you give an example? I never found a non working plugin for avs+.

What tormento suggested is go the 64-bit route exclusively. For AVS+ the installer suggests to install both the 32-bit and the 64-bit versions in parallel (of course only if a 64-bit OS is detected).

While having both versions installed at the same time is possible, you can not mix 32-bit and 64-bit plugins in the same script. It's either one or the other, you need to keep the plugins separate.


Cheers
manolito

[lansing]

Originally Posted by manolito

The most important one is LogoAway which is a 32-bit VDub plugin. Easy to use, very nice results and relatively fast. I tried most of the available logo removers, and this one did beat them all.

I just glanced over the list of available 64-bit AVS plugins, and this list has grown considerably. With a little effort I could probably find 64-bit replacements for most of my plugins. But there is another reason why I am not going to do this:

I do video conversions on at least 3 different computers. There's the notorious ancient WinXP machine, there is one Win7-32 laptop (only 2GB Ram, the 64-bit Win7 version is too slow on this laptop, constant swapping), and another Win7-64bit laptop with 8GB RAM. I have no intention to maintain 3 different AVS plugins folders, it is hard enough for me to maintain just one plugins folder. Getting working plugin versions for several scripts like QTGMC, LSFMod, Srestore or Finesharp took me a long time, and I want to keep this configuration. I know that if everything works on the WinXP machine then it will also work on the other computers. Maybe a little bit slower than it could, but no headaches for me.


Cheers
manolito

It might be a good time to buy new computers

https://www.newegg.com/Product/Produ...82E16819113480

Ryzen 5 4-core/8 threads for $150, that will fix all your problem. Heck you can probably build three under $1000.

[real.finder]

Originally Posted by manolito

While having both versions installed at the same time is possible, you can not mix 32-bit and 64-bit plugins in the same script. It's either one or the other, you need to keep the plugins separate.


Cheers
manolito

you can mix 32-bit and 64-bit plugins in the same script with mpp (mp_pipeline), you can even run avs+ inside it even if you have old avs installed by using "### dll:"

[Stereodude]

Originally Posted by Groucho2004

Just curious - which ones?

AFAIK, MCTD is 32-bit only so far. However, MP Pipeline lets you use it in an otherwise x64 process.

[poisondeathray]

MTCD works ok in avs+ x64 , just not higher bit depths (except in vapoursynth)

hdragc is one that is still x86 only (but you can get similar results with smoothcurve x64)

[wonkey_monkey]

Using multiline syntax (".\"), is there any way to comment out a line in the middle of a set of lines? For example:

version.\
fliphorizontal.\
flipvertical.\
killaudio

Is there any way to comment out the fliphorizontal line without affecting parsing of the rest of the script?

I don't know how much use multiline syntax gets, but I'm guessing it may have originally been something of an after-thought. Semi-colon termination would be so nice...

[qyot27]

C-style /* */ works:

Version()/*.\
FlipHorizontal()*/.\
FlipVertical().\
KillAudio()

[* *] are also allowed as comment delimiters as well.

Although on something that simple (for exposition's sake) I wouldn't bother with the .\ style multiline syntax at all, and use the standard multiline form:

Version()
#FlipHorizontal()
FlipVertical()
KillAudio()

In the above, /* and */ could also be used, and would format more sanely, since they'd be contained to just the FlipHorizontal() line.

[Stereodude]

Was there an issue before with the dithering when reducing the color depth in AVIsynth+ (4:2:0 chroma formats) that was fixed? I noticed some vertical banding in the output video when dithering was enabled with SD/REC.601 previously with build 2700. I didn't see it in HD/REC.709 content. However, with the latest build 2772 AVIsynth+ I don't see it anymore.

[StainlessS]

Stereodude, see Changelog for current & prev versions via Pinterf (via his sig) on github / releases :- https://github.com/pinterf/AviSynthPlus/releases

[pinterf]

I don't remember any issues or coding activities connected to dithering.

[Stereodude]

Originally Posted by StainlessS

Stereodude, see Changelog for current & prev versions via Pinterf (via his sig) on github / releases :- https://github.com/pinterf/AviSynthPlus/releases

I didn't see anything listed that would directly explain my observations. Hence the question.

Originally Posted by pinterf

I don't remember any issues or coding activities connected to dithering.

Weird... Oh well, I'm not seeing it now.

[FranceBB]

Originally Posted by qyot27

In the above, /* and */ could also be used

I use /* */ everyday to comment out multiple lines.
For the sake of coding, // would also be appreciated to have available as comment instead of using just "#" for single line commands, just to feel a bit more like C++ and C#.

I don't remember any issues or coding activities connected to dithering.

Speaking of Dithering, will other dithering algorithms be added in the near future? You know, like the Stucki error diffusion and the Atkinson error diffusion?
Don't get me wrong, I'm totally happy with the current Floyd-Steinberg error diffusion as it's one of the best dithering algorithms, but what if people need/would like to use other dithering algorithms?
After all, back when the world was 8bit stacked, 8 dithering methods were available.

[StainlessS]

// would also be appreciated

Bad idea at this late date. Too much potential to f*** up stuff, eg script scanning apps like AvsPMod, Avisynthesizer etc.
Also, adds nothing to the language.