Vapoursynth

[dipje]

It's RGB.. the way I see it there is no 'colormatrix' then, that's only for YUV files. Maybe an RGB colorprofile / ICC-profile but that is something you should override in whatever application you use to read the file, I'm pretty sure AVI can't store ICC profiles for RGB data somewhere .

[Jamaika]

Originally Posted by dipje

It's RGB.. the way I see it there is no 'colormatrix' then, that's only for YUV files.

I don't believe it is RGB. Image with FFmpeg:

Video AVI RGB24:

Video AVI R210:

[dipje]

R210 is RGB 10bit. https://wiki.multimedia.cx/index.php/R210. 10 bits R, 10 bits G, 10 bits B, 2 bits padding.

There can still be a thing such as 'broadcast safe levels' and full range (like I said, RGB can have things as color profiles, but that has nothing to do with the codec, more with the what your program interprets the RGB values as), even in RGB. Doesn't change the fact that R210 is a RGB packing method.. that's the whole thing I asked.. 'Can you pack vs.RGB30 as R210 in the VfW interface'.

Anyway, I don't install any Blackmagic codecs anyway. Don't see why anyone would. Maybe you can configure the codec (or the encoder that created the clip) to use full range or not. In Davinci Resolve you can click the clip properties in your Media Bin to change the interpretation of the levels.

[Jamaika]

Originally Posted by dipje

In Davinci Resolve you can click the clip properties in your Media Bin to change the interpretation of the levels.

Thanks for the answer. I can't change the interpretation of the levels in Sony Vegas 14 or VirtualDub. So theme about the R210 codec I throw in the trash. For me it is the sRGB is equal to only bt709.

[Joachim Buambeki]

Originally Posted by dipje

No, it means you can frameserver the output of a RGB 10bit Vapoursynth script directly into Resolve.
If you actually want to work on it 'live' is another question, but quick grading and fixes and using Resolve's export module to save it into a format of your choosing is possible.

Ok, got it, thanks.
When you say 10bit, this means a ProRes444 file (which is 12bit) is piped in reduced quality into Resolve - is there a way to feed it to Resolve in a way no quality is lost (meaning in 16bit, 32bit or whatever Resolve internally uses)?

I asked for an OFX plugin a (short) while ago but it seems Myrsloik missed my second post. I still believe such a plugin (if technically possible) that runs VS code would be great to lift VS more into the professional realm and I assume many professionals would be very happy to this in their toolkit. If communicated right, I am sure some of them will be willing to donate to make this happen.

TIA!

[dipje]

Replying in pm as I think we're moving away from vapoursynth stuff

[Myrsloik]

Originally Posted by Joachim Buambeki

Ok, got it, thanks.
When you say 10bit, this means a ProRes444 file (which is 12bit) is piped in reduced quality into Resolve - is there a way to feed it to Resolve in a way no quality is lost (meaning in 16bit, 32bit or whatever Resolve internally uses)?

I asked for an OFX plugin a (short) while ago but it seems Myrsloik missed my second post. I still believe such a plugin (if technically possible) that runs VS code would be great to lift VS more into the professional realm and I assume many professionals would be very happy to this in their toolkit. If communicated right, I am sure some of them will be willing to donate to make this happen.

TIA!

Sigh, enterprise apis... That mess looks like it'd take at least a month to understand. How you even imagine the integration to work well is also a mystery.

[Selur]

using portable R37 64bit with:

# Imports
import vapoursynth as vs
core = vs.get_core()
# Loading Plugins
core.std.LoadPlugin(path="G:/Hybrid/vsfilters/Support/fmtconv.dll")
core.std.LoadPlugin(path="G:/Hybrid/vsfilters/SourceFilter/LSmashSource/vslsmashsource.dll")
# Loading F:\TestClips&Co\test.avi using LWLibavSource
clip = core.lsmas.LWLibavSource(source="F:/TESTCL~1/test.avi", format="YUV420P8", cache=0)
# making sure input color matrix is set as 470bg
clip = core.resize.Point(clip, matrix_in_s="470bg")
# making sure input color range is set to TV (16-235) scale.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
original = clip
# dualView True
# vsPreview True
# cropping the video to 600x312
clip = core.std.CropRel(clip=clip, left=40, right=0, top=40, bottom=0)
# cropping the video to 600x312
original = core.std.CropRel(clip=original, left=40, right=0, top=40, bottom=0)
# clip resizing to 960x500
#clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
#original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
original = core.sub.Subtitle(clip=original, text="Original")
clip= core.sub.Subtitle(clip=clip, text="Filtered")
stacked = core.std.StackHorizontal([original,clip])
# Output
stacked.set_output()

and

VSPipe.exe  --y4m h:\Temp\tempPreviewVapoursynthFile11_03_52_922.vpy -  | g:\Hybrid\mplayer.exe -

vspipe crashes for me and I don't see why.

Removing:

# clip resizing to 960x500
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)

from the script and I get no crash.

=> Does anyone see what I do wrong? (using 'clip.set_output()' or 'original.set_output()' the script doesn't crash either)

Leaving out the cropping doesn't change anything, so this seems to be related to fmtc.

Using:

# clip resizing to 960x500
clip = core.resize.Spline16(clip, width=960, height=500)
# original resizing to 960x500
original = core.resize.Spline16(original, width=960, height=500)

instead of:

# clip resizing to 960x500
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)

also fixes the problem.

=> seems like there is a problem with fmtc when used multiple times inside a script. (I'm using fmtconv r20 from https://github.com/EleonoreMizo/fmtconv/releases)

[dipje]

I use fmtc a lot of times in most scripts, no problem there . Proves that no two scripts are ever the same :P

[sneaker_ger]

Originally Posted by Selur

=> seems like there is a problem with fmtc when used multiple times inside a script.

How did you arrive at that conclusion?

[Selur]

When I use:

# clip resizing to 960x500
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
stacked = core.std.StackHorizontal([original,clip])
# Output
stacked.set_output()

the problem occurs.
When I use:

# clip resizing to 960x500
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
stacked = core.std.StackHorizontal([original,clip])
# Output
original.set_output()

or

# clip resizing to 960x500
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
stacked = core.std.StackHorizontal([original,clip])
# Output
clip.set_output()

or just

stacked = core.std.StackHorizontal([original,clip])

the problem doesn't occur.

So it seemed to me that the problem only occurred when I used two fmtc calls, like I did with:

# clip resizing to 960x500
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
# original resizing to 960x500
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)

If you got another explanation for it please share.

[Selur]

Can someone aside from me reproduce the issue?
(just to be sure this isn't somehow related to my setup)
Minimal example would be:

clip = core.lsmas.LWLibavSource(source="F:/TESTCL~1/TEST-A~1.AVI", format="YUV420P8", cache=0) # source and source filter don't matter, tried different sources and source filters
original = clip # copying current clip state to original
clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=720, interlaced=False, interlacedd=False) # resizing clip
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=720, interlaced=False, interlacedd=False) # resizing clip
stacked = core.std.StackHorizontal([original,clip]) # stacking 
stacked.set_output() # return

Cu Selur

[sneaker_ger]

No crash here. (R37 x64 on Windows 7, i5-2500K, fmtconv r20)

[sneaker_ger]

I just got crashes immediately after upgrading to R38 test2. Then it worked after a few tries.

/edit:
Then crashes again. Kinda random. No idea what's going on. Just doing vspipe - script.vpy > NUL

[Selur]

Still using R37 so that isn't it. But since it works for you it might be something with my setup. (R37 64bit, on Win 10 pro, Ryzen 7 1800x, fmtconv r20)

[Selur]

What's the resolution of your avi file?

640x352 (this is one of my test samples which I have converted hundreds of times; https://drive.google.com/drive/folde...UZibG5XZkRfeTg -> test.avi)

Does it still crash if you simply use core.std.BlankClip(width=1920, height=1080, format=vs.YUV420P8) as the source clip?

Yes

Does it still crash if you specify cpuopt=0 in both fmtc.resample()?

Yes

----
downloaded:
https://www.python.org/ftp/python/3....mbed-amd64.zip
and
https://github.com/vapoursynth/vapou...ortable-R37.7z
extracted both into one folder

called:

VSPipe.exe c:\Users\Selur\Desktop\Test.vpy - | ffplay.exe -

vspipe still crashing.

copied the files to my laptop, got the same crash. (Both run Win10 latest updates; laptop is an i7, main system is a Ryzen 7 1800x)

---
replacing:

original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)

with

original = clip

and thus not using fmtc two files also 'fixes' the issue.
RAM usage of vspip is ~870MB upon the crash.

Cu Selur

[Selur]

Copied the whole thing into a Win 8.1 64bit VM and there the script worked as it should. No problem.
-> HolyWu what OS are you on? Could this be a problem thanks to Windows 10 Creators Update?

replacing:

clip = core.lsmas.LWLibavSource(source="F:/TESTCL~1/test.avi", format="YUV420P8", cache=0)

original = clip

clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)

with:

clip = core.lsmas.LWLibavSource(source="F:/TESTCL~1/test.avi", format="YUV420P8", cache=0)
original = core.lsmas.LWLibavSource(source="F:/TESTCL~1/test.avi", format="YUV420P8", cache=0)

clip = core.fmtc.resample(clip=clip, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)
original = core.fmtc.resample(clip=original, kernel="spline16", w=960, h=500, interlaced=False, interlacedd=False)

doesn't help either,...

[Selur]

Since the core resizer only covers Bicubic/Point/Lanczos/Spline16/Spline36, but I sometimes like gauss more I normally stick with fmtconv. (I also like to have the option to use the other resizers offered by fmtconv.)
Strange thing that I get the crash each time (on both my i7 and my Ryzen system) and you only very seldom and random.

[Selur]

Tested it. Still crashing here.

[Selur]

Correction: New version does fix the crash for me too.
(somehow overlooked that Win10 asked whether the file should be overwritten and tested the old version again before. )

Cu Selur