Avisynth+

[ajp_anton]

Originally Posted by StainlessS

Default() must be a function, moving into the Parser as you suggest would likely result in a lot of work for printerf, and for no real reason, you can easily get around that (EDIT: rare) 'problem' yourself.

Well, (2) isn't that important, I'm just using a simple "if" (? and to get around it. Took a while to be desperate enough to try it though, because I though that's basically how Default did it and it wasn't working there.

Originally Posted by LigH

1. is probably asking for a chance to overlay the Info() details over a blank clip, for better readability. Well ... BlankClip(reference_clip) could be a base with mostly identical attributes, to display Info text onto. Except for the case that the clip has too small dimensions for the Info text to render completely; in that case it may indeed need a larger area than the original clip.

Yes, I was thinking of the dimensions. Sure, can get around it by resizing, assuming that the clip dimension is not what you're interested in.

Originally Posted by StainlessS

No problem with (3) [EDIT: I quite like the idea].

Not sure what idea you quite like, because I just noticed that the forum messed up my (3) =). Apparently you can't put a \ between "". I now edited my previous post.
Basically, what I meant is that you could write

a = somefunction(argument1  #comment for arg1
\,               argument2) #another comment

or

a = somefunction(argument1,\ #comment for arg1
                 argument2)  #another comment

[StainlessS]

Originally Posted by ajp_anton

Not sure what idea you quite like, because I just noticed that the forum messed up my (3) =). Apparently you can't put a \ between "". I now edited my previous post.
Basically, what I meant is that you could write

a = somefunction(argument1,\ #comment for arg1
                 argument2)  #another comment

That is what I took you to mean

[raffriff42]

>1. Function "Info": Add a second clip as an optional argument.

## show information on clip 'C' over base clip 'B'
function Info(clip B, clip C)
{
    return B.Overlay(
    \   C.Levels(0, 1, 0, 0, 0) [* make black BG *]
    \    .Info                  [* show info     *]
    \    .Crop(0, 0, 384, 240), [* crop to size  *]
    \   opacity=1.0             [* overlay       *]
    \ ) 
}

Can't support an optional second clip as this collides with built-in Info(clip C).

>3. The ability to add comments at the end of a line that continues on the next line
See above

[ajp_anton]

Originally Posted by raffriff42

>1. Function "Info": Add a second clip as an optional argument.

## show information on clip 'C' over base clip 'B'
function Info(clip B, clip C)
{
    return B.Overlay(
    \   C.Levels(0, 1, 0, 0, 0) [* make black BG *]
    \    .Info                  [* show info     *]
    \    .Crop(0, 0, 384, 240), [* crop to size  *]
    \   opacity=1.0             [* overlay       *]
    \ ) 
}

Can't support an optional second clip as this collides with built-in Info(clip C).

>3. The ability to add comments at the end of a line that continues on the next line
See above

Nope, "you cannot use crop to enlarge or 'shift' a clip".
And the "CPU detected" line goes on even further than that 384, so an even bigger area is needed. I know, totally not important, but it looks ugly. Not to mention that the whole black rectangle is really ugly. So not really a "nice" solution.

Didn't know you could comment like that. Though I still prefer # because it's easier to keep track of.

[StainlessS]

from Docs

Avisynth ignores anything from a # character to the end of that line. This can be used to add comments to a script.

# comment

In v2.58 it is possible to add block and nested block comments in the following way:

# block comment:
/* 
comment 1
comment 2
*/

# nested block comments:
[* [* a meaningful example will follow later :) *] *]

Avisynth ignores anything from an __END__ keyword (with double underscores) to the end of the script file. This can be used to disable some last commands of script.

Version()
__END__
ReduceBy2()
Result is not reduced and we can write any text here

Seems that we are still awaiting a meaningful example, since v2.58.

But below produces "Parse Error: orphan block comment closing */". [The 1st */ ends the comment]

/* /* something */ */

whereas

[* [* something *] *]

does not.

EDIT: (1) Perhaps new function InfoText() or Info_Text() would be easy to implement (as for Subtitle, with '\n').

[jpsdr]

Is there a way with the CPU flags to detect FMA4 ? I've seen there's allready FMA3, but didn't seen FMA4.

[Foja]

Hello,

since long time I am a silent reader in this discussion. I am using the plug-in RemoveDirt in the 8-bit version of avisynth for many years. I am very satisfied with this plug-in.
Now I am starting to use avisynth+ for my cleaning script, all plugins which i normaly use in the 8-bit version are already available exept "RemoveDirt".
RemoveDirt is for me a important plugin which I don't want to miss in my cleaning script for avisynth+.

Is there the plan to convert the plugin "RemoveDirt" to the new version avisynth+?

Thanks for the great work and for providing such a powerful software.

Best wishes from Germany and a Happy New Year!

[LigH]

Hi, thanks, and same to you, from Germany as well.

In the AviSynth Wiki for RemoveDirt I read that it "has now become a script function which involves RestoreMotionBlocks and various filters from the RemoveGrain package." And if you substitute them with RgTools, I guess it should be possible to run it with equivalent results and better speed in AviSynth+ ... so much guesswork from me; but other members may know it better.

[pinterf]

I didn't include fma4 in CPU flags. But it seems I will have to.

[Foja]

Originally Posted by LigH

Hi, thanks, and same to you, from Germany as well.

In the AviSynth Wiki for RemoveDirt I read that it "has now become a script function which involves RestoreMotionBlocks and various filters from the RemoveGrain package." And if you substitute them with RgTools, I guess it should be possible to run it with equivalent results and better speed in AviSynth+ ... so much guesswork from me; but other members may know it better.

Thanks for your reply. Unfortunately, the "RestoreMotionBlocks" function is part of RemoveDirt and not the RemovGrain or RgTools package. Although there is an x64 version (RemoveDirt v1.0 pre-release x64), but this is not running under Avisynth +. The error message "System exeption - Access Violation" are shown.
I guess for the support of a bit depth of 10 - 16 bit, RemoveDirt is likely to be completely revised??!

Best wishes!

[feisty2]

Originally Posted by Foja

Thanks for your reply. Unfortunately, the "RestoreMotionBlocks" function is part of RemoveDirt and not the RemovGrain or RgTools package. Although there is an x64 version (RemoveDirt v1.0 pre-release x64), but this is not running under Avisynth +. The error message "System exeption - Access Violation" are shown.
I guess for the support of a bit depth of 10 - 16 bit, RemoveDirt is likely to be completely revised??!

Best wishes!

takes ~10min to make it work on higher bit depth integer samples, just reinterpret_cast all uint8_t * to uint16_t * and append "/ sizeof(uint16_t)" after all stride variables and you're done, do it yourself

[LigH]

Originally Posted by feisty2

takes ~10min to make it work on higher bit depth integer samples, just reinterpret_cast all uint8_t * to uint16_t * and append "/ sizeof(uint16_t)" after all stride variables and you're done, do it yourself

What kind of programmer do I have to be to understand these instructions? And which kind of compiler do I have to know to use?

[videoh]

C or C++. It's very basic. As they say, google is your friend.

[Reel.Deel]

Originally Posted by feisty2

takes ~10min to make it work on higher bit depth integer samples, just reinterpret_cast all uint8_t * to uint16_t * and append "/ sizeof(uint16_t)" after all stride variables and you're done, do it yourself

~10 min? I call BS on that. Have you even looked at the source code? I'm no programmer but I've heard other knowledgeable people describe Kasandro's code as pure spaghetti. If it was so easy why was it not done here: https://github.com/handaimaoh/removedirtvs

Edit:

Originally Posted by Foja

Thanks for your reply. Unfortunately, the "RestoreMotionBlocks" function is part of RemoveDirt and not the RemovGrain or RgTools package. Although there is an x64 version (RemoveDirt v1.0 pre-release x64), but this is not running under Avisynth +. The error message "System exeption - Access Violation" are shown.

The RemoveDirt script also uses SCSelect fucntion from the RemoveDirt plugin. Regarding the x64 version on the wiki, there's a note on there that says it's incompatible with AviSynth.

For the mean time you can use a similar workaround as described here: http://forum.doom9.org/showthread.ph...83#post1599783

o16 = last #Stack16 video

o = DitherPost(mode=-1)
o.RemoveDirt(...)

dif = mt_makediff(last, o, y=3, u=3, v=3)
dif16 = dif.Dither_convert_8_to_16()
o16.Dither_add16(dif16, dif=true)

[feisty2]

Originally Posted by Reel.Deel

~10 min? I call BS on that. Have you even looked at the source code? I'm no programmer but I've heard other knowledgeable people describe Kasandro's code as pure spaghetti.

Lol ur full of crap, it doesn't matter how messed up the code is cuz ur not rewriting the whole plugin, simply modifying it a tiny little bit.

If it was so easy why was it not done here: https://github.com/handaimaoh/removedirtvs

Because unlike c and c++ which are easy to modify, assembly is an evil bitch

[tuanden0]

I'm using filter MCTemporalDenoise.avsi
Can everyone tell me what is the MT mode of this?

[tormento]

Originally Posted by tuanden0

I'm using filter MCTemporalDenoise.avsi
Can everyone tell me what is the MT mode of this?

I warmly suggest you to use SMDegrain.

[pinterf]

Happy New Year!

After having spent many days with understanding how multithreading works with runtime scripts I felt myself so miserable and tired that I had to abandon that investigation a bit. I have searched for an area with more success factor instead.

New dev build:
Download Avisynth Plus r2359

Changes since r2347:

Avisynth plus r2359dev (20170104)

• Overlay:
  new parameter: bool use444 (default true for compatibility/until under construction, etc...)
  
  Parameter is valid only for "blend" at the moment
  When set to false, and base clip/overlay clip is 420/422/Planar RGB, no conversion occurs to and back from YV24 (4:4:4 in general)
  
  Mask can be either greyscale or can be any planar YUV when greymask=true (default)
  
  Works for Planar RGB, so blending is basically lossless for this format (no YUV conversion)
  todo: support for other modes, convert packed RGB to planar RGB internally instead of YUV
• Overlay:
  Add fast 4:2:0<->4:4:4 conversion, e.g. YV16<->YV24 (only fast YUY2 and YV12 existed so far)
  instead of invoking generic core conversion
• Overlay:
  10-16bit SSE2/SSE4 for 420/422<->444 conversions
• Info() made a bit more compact.
  Bit depth info moved after color space info
  Does not display pre-SSE2 CPU flags when at least AVX is available.
  AVX512 flags in separate line (would be too long)
• new CPU feature constants (see cpuid.h and avisynth_c.h)
  Detect FMA4 and AVX512F,DQ,PF,ER,CD,BW,VL,IFMA,VBMI
• new script function:
  string ReplaceStr(string s, string pattern, string replacement)
  Function is case sensitive, parameters are unnamed
• new script function
  int NumComponents(clip)
  returns 1 for grayscale, 3 for YUVxxx, YUY2, planar RGB or RGB24/RGB48, 4 for YUVAxxx, Planar RGBA or RGB32/64
• new script function:
  bool HasAlpha(clip)
  returns true when clip is YUVA, Planar RGBA, or packed RGB32 or RGB64

[real.finder]

Originally Posted by pinterf

Happy New Year!

After having spent many days with understanding how multithreading works with runtime scripts I felt myself so miserable and tired that I had to abandon that investigation a bit. I have searched for an area with more success factor instead.

New dev build:
Download Avisynth Plus r2359

Happy New Year and

what about make AddAlphaPlane accept clip too?

[pinterf]

It was planned then forgotten