Vapoursynth

[poisondeathray]

Originally Posted by StainlessS

Its really the binary digits that count, and 10 is not a power of 2, so it works (rounds) a bit weird.

Thanks

[StainlessS]

PDR, a bit more.

There are a fractional number of binary digits per decimal digit, and although float only precise to 6 [EDIT: significant] digits, there will likely be one or more decimal digits which are not quite correct.

EDIT: Note, below 6 significant digits

0.921468
  ^^^^^^

1.921468    # Adding 1.0, last digit is not within first 6 significant digits : Note that the extra digit is printed because of the default print format, rather than it being within first 6 significant digits.
^ ^^^^^

a = 0.921468  # This was probably not exact to begin with

b = a + 1.0

DIGS=32      # Digits to the right of decimal point

BlankClip

RT_DebugF("a=%.*f\nb=%.*f",DIGS,a,DIGS,b)
RT_subtitle("a=%.*f\nb=%.*f",DIGS,a,DIGS,b)

return last

00000057    0.29118466  [1068] RT_DebugF: a=0.92146801948547363000000000000000
00000058    0.29125640  [1068] RT_DebugF: b=1.92146801948547360000000000000000

EDIT:

RT_subtitle("a=%.*f\nb=%.*f",DIGS,a,DIGS,b)

Equiv

RT_subtitle("a=%.32f\nb=%.32f",a,b)

EDIT: No reply necessary.

EDIT:

There are a fractional number of binary digits per decimal digit

Function Log2(float n) {
    return Log(n) / Log(2.0)
}

blankclip
DIGS=32      # Digits to the right of decimal point

BitsPerDecDigit = Log2(10.0)
Test10=Pow(2.0,BitsPerDecDigit)
RT_debugF  ("BitsPerDecDigit=%.*f\nTest10         =%.*f",DIGS,BitsPerDecDigit,DIGS,Test10)
RT_Subtitle("BitsPerDecDigit=%.*f\nTest10         =%.*f",DIGS,BitsPerDecDigit,DIGS,Test10)
return last

00000231    0.29308608  [4064] RT_DebugF: BitsPerDecDigit=3.32192802429199220000000000000000
00000232    0.29313752  [4064] RT_DebugF: Test10         =9.99999904632568360000000000000000

[ifb]

Originally Posted by Myrsloik

Speed comparisons with R46 also welcome.

Threadripper 1920X w/64GB ECC and Windows 10 x64
Local build of VS with the latest AVX2 fix (ac74e9b)
Three runs on a script that's all float and 16-bit (CinemaDNG sequence):

time vspipe -e 1000 script.vpy .

                 1      2      3        avg      stddev  relative
R48-RC3+1  avx2  432.83 434.95 435.22   434.33   1.309   1.0080x
           sse2  431.05 433.80 436.28   433.71   2.616   1.0095x
           none  467.84 465.92 463.87   465.88   1.985   0.9398x
R46        sse2  434.29 440.49 438.68   437.82   3.188   1.0000x

~1% faster vs R46 even though AVX2 doesn't help poor Zen1.

[Myrsloik]

Originally Posted by ifb

Threadripper 1920X w/64GB ECC and Windows 10 x64
Local build of VS with the latest AVX2 fix (ac74e9b)
Three runs on a script that's all float and 16-bit (CinemaDNG sequence):

time vspipe -e 1000 script.vpy .

                 1      2      3        avg      stddev  relative
R48-RC3+1  avx2  432.83 434.95 435.22   434.33   1.309   1.0080x
           sse2  431.05 433.80 436.28   433.71   2.616   1.0095x
           none  467.84 465.92 463.87   465.88   1.985   0.9398x
R46        sse2  434.29 440.49 438.68   437.82   3.188   1.0000x

~1% faster vs R46 even though AVX2 doesn't help poor Zen1.

You've most likely hit the ram bandwidth limit. Run it with a single/few threads and the difference should be obvious.

[Myrsloik]

R48-RC4

Fixes the floating point edge handling of RC3.

Test harder!

[HolyWu]

Originally Posted by Myrsloik

r48:
added an option to add vspipe, avfs and vsrepo to path in the installer

It seems that the PATH is always added even though I have unchecked the option.

[Myrsloik]

Originally Posted by HolyWu

It seems that the PATH is always added even though I have unchecked the option.

Congratulations! You've won a free RC5 build which you can redeem tomorrow! That was a really stupid typo. At least there are no known image corruption problems. (test the unprivileged installs too just to be sure)

[Myrsloik]

R48-RC5

The only change from RC4 is that the installer now correctly respects the add to PATH options.

[l00t]

I've found another bug. When I try to use nyuszika7h's FFInfo the result is a pile of garbage with R48-RC4, while it was perfectly fine with R47.2. The picture is also okay without the script.

nyuszika7h's FFInfo script:
https://gist.github.com/nyuszika7h/3...0b35a464ef9a91

with FFInfo:


without FFInfo:

import vapoursynth as vs
from vapoursynth import core
clip = core.ffms2.Source(source=r'some_hd_footage.mkv')
clip = vs_ffinfo.FFInfo(clip, text='some text', frame_num=True, frame_type=True, frame_time=True)
clip.set_output()

FFMS2 is the latest version from 10/07/2019 from StvG

Video parameters:
Resolution: 1920x1038
Format: YUV420P8
FPS: 24000/1001

Thanks in advance

[ChaosKing]

The problem is in: clip.sub.Subtitle("this is art")

[Myrsloik]

R48-RC6

Fixes premultiplied maskedmerge and a few expr problems that most likely were never encountered by anyone.

[l00t]

Thanks, now it's perfect.

BTW: If someone's interested in FFInfo, I've pumped up a bit nyuszika's version: https://gist.github.com/l00tzOMG/404...d96b57b08f32ce

[_Al_]

I've pumped up a bit nyuszika's version: https://gist.github.com/l00tzOMG/404...d96b57b08f32ce

To get string equivalents for those numerical frame property values, you can use dictionaries/ tables and then just get value you need.
With if , elif approach you can end up having hundreds of them is database is large. Look in that example:
https://forum.doom9.org/showthread.p...59#post1885759

[ifb]

Originally Posted by Myrsloik

You've most likely hit the ram bandwidth limit. Run it with a single/few threads and the difference should be obvious.

core.num_threads = 1
R48 RC4   avx2  5975.40  1.0062
          sse2  5938.56  1.0125
R46       sse2  6012.63  1.0000

I only did 1 run each, but still ~1% faster.

[_Al_]

@l00t

MATRIX =  {
                     0:'rgb',
                    1:'709',
                     .
                     .
                     .
                }   
PRIMARIES = { .....}
TRANSFER = {....}

try:
    lines.append(f'Matrix: {MATRIX[f.props["_Matrix"]]}')
except Exception as e:
    lines.append(f'Matrix: {str(e)}')

try:
    lines.append(f'Primaries: {PRIMARIES[f.props["_Primaries"]]}')
except Exception as e:
    lines.append(f'Primaries: {str(e)}')

[l00t]

Thanks for the idea, modified the script accordingly

Originally Posted by _Al_

...

[MonoS]

Since version R46 i get the error "Failed to initialize VapourSynth environment" even execuiting a simple vspipe -v
I've tried R46, R47 and R48-RC6, all giving me the same error, this on two different machine, one Win 10 the other Win Server 2019 even after reboot

Installing R45 it works without problem.

What could be the issue? what can i do to help you diagnose the problem?

[Myrsloik]

Originally Posted by MonoS

Since version R46 i get the error "Failed to initialize VapourSynth environment" even execuiting a simple vspipe -v
I've tried R46, R47 and R48-RC6, all giving me the same error, this on two different machine, one Win 10 the other Win Server 2019 even after reboot

Installing R45 it works without problem.

What could be the issue? what can i do to help you diagnose the problem?

Which install type? Did you really install the vs2019 runtimes? You can simply run vspipe in a debugger if you still can't figure it out since I've even included pdbs for the main dlls.

[MonoS]

Originally Posted by Myrsloik

Which install type? Did you really install the vs2019 runtimes? You can simply run vspipe in a debugger if you still can't figure it out since I've even included pdbs for the main dlls.

64bit non portable version, installed vs2019 runtimes the first time, then in subsequent install skipped that.

For setting up the debugger what should i do? Download the source and put a breakpoint inside real_init and see what fail?

[Myrsloik]

Originally Posted by MonoS

64bit non portable version, installed vs2019 runtimes the first time, then in subsequent install skipped that.

For setting up the debugger what should i do? Download the source and put a breakpoint inside real_init and see what fail?

Yes, that should work and give you the best information.