Selur's Little Message Board

new version was renamed from libtimecube.dylib to libvscube.dylib maybe come conflict due names? I checked, i delete old version.

the name of the dll itself should not matter.
The way there are used 'core.timecube.Cube(' will.
If you got two filters with the same base 'core.timecube.Cube(' you will have a conflict.
So yeah best delete one of them.

Cu Selur

It looks normal only if i use
clip = core.resize.Bicubic(clip, format=vs.RGB48, range_in_s="limited", range_s="full")
Or if i remove range_in_s="limited", range_s="full" code at all:
just use clip = core.resize.Bicubic(clip, format=vs.RGB48)

Just ignore all that TimeCube story. Here is new fix from developer https://github.com/sekrit-twc/timecube/i...-685090200 Problem fixed.

to groggy today, will look at it tomorrow after work

And few more small mistakes and upper/lower case letters adjustments in Filter(s) presets list name:

Add grain -> Add Grain
Dehalo - FineDehalo -> DeHalo - FineDehalo (not sure why but currently FineDehalo is moved away of DeHalo group)
Denoise -> DeNoise
Dering -> DeRing
Deringing -> DeRing
Framerate interpolation -> Framerate Interpolation
Residual cleaner -> Residual Cleaner

Also remove AntiAliasing - SangNomMod preset, because plug-in disabled yet.

(30.08.2020, 19:36)Selur Wrote: [ -> ]-> If you can tell me a way tell ffmpeg to write those tags I can add an option for it, since I don't use lossy formats as intermediate I never really found any use for ProRes aside from exporting to it for others.

About ProRes NCLC tags and tests here https://forum.selur.net/showthread.php?t...41#pid8841

Not sure if it helps exactly, but i done quick search "ffmpeg nclc" and some info here and there.
For example here are a lot of nclc related code lines
https://ffmpeg.org/doxygen/3.1/mov_8c_source.html

https://video.stackexchange.com/question...-colr-atom
-movflags +write_colr -strict experimental

Some mov64Writer for Nuke app seems based on FFmpeg https://learn.foundry.com/nuke/developer...Writer.cpp it have like "writeNCLC_(true)"

Probably NCLC tags are inserted as numbers. Numbers description is here
https://github.com/bbc/qtff-parameter-editor
In some codes it look like this:
nclc: pri 1 trc 1 matrix 1

Maybe just look for something related to nclc in FFmpeg help and support?
Maybe somehow look at ffmbc NCLC code and in use it for FFmpeg?

Some early Kostya encoder requests from 2012 https://codecs.multimedia.cx/2012/03/a-f...s-encoder/
"For all your questions – encoders control only what’s written inside the frames and don’t (and probably cannot) affect MOV properties in the way you want. Sorry.
Maybe somebody will write a patch to address all this."

Quote:Also remove AntiAliasing - SangNomMod preset, because plug-in disabled yet.

too much hassle,..

About NCLC: so no real solution atm.

Uploaded a new version.

@Adamcarter: new version allows to change the deinterlacer in VIVTC to QTGMC or NNEDI3.

Cu Selur

some startup error popups

Hmm,.. probably happen if Vapoursynth isn't available.
-> looking into it.

No I accidentally added the parameter to the Avisynth init,..
-> will fix

It pops up same message 7 times.
Deleting preferences/presets folder didn't help