Selur's Little Message Board - Esxi running macos For selur

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108

And seems we found a source of problem with sangnom errors:

Code:
/Library/Frameworks/VapourSynth.framework/bin/vspipe --info /Users/shph/Desktop/test.vpy -

Script evaluation failed:

Python exception: Plugin load of /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib failed, namespace sangnom already populated by /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnommod.dylib

Traceback (most recent call last):

 File "src/cython/vapoursynth.pyx", line 2244, in vapoursynth.vpy_evaluateScript

 File "src/cython/vapoursynth.pyx", line 2245, in vapoursynth.vpy_evaluateScript

 File "/Users/shph/Desktop/test.vpy", line 20, in <module>

 core.std.LoadPlugin('/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib')

 File "src/cython/vapoursynth.pyx", line 2069, in vapoursynth.Function.__call__

vapoursynth.Error: Plugin load of /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib failed, namespace sangnom already populated by /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnommod.dylib

Quote:Python exception: Plugin load of /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnom.dylib failed, namespace sangnom already populated by /Library/Frameworks/VapourSynth.framework/lib/vapoursynth/libsangnommod.dylib

Ah okay, that doesn't happen on Windows since I always load each library explicitly and don't use the autoload.
Best solution would probably be to only use sangnommod since it's the newer library and adjust all the script accordingly (if need be).
-> Does it work if you simply delete libsangnom.dylib (or libsangnommod.dylib) ?

will try to look at the rest of the post tomorrow

Test 1. I removed SangNomMod and use SangNom.
MAA and AAF filters WORKS.
SangNomMod Anti Aliasing don't works.
Santiag Anti Aliasing filter don't works:
if i choose "Type: sangnom" - No error, but empty preview window.
If i use "Type: selectHV" - Error "TypeError: santiag() got an unexpected keyword argument 'typevh'"

ChaosKing response at doom9 that: selectHV is not a valid type. Read the doc https://github.com/HomeOfVapourSynthEvol...nc.py#L134

Code:
type = "nnedi3", "eedi2", "eedi3" or "sangnom"

Test 2. I removed SangNom and use SangNomMod.
MAA and AAF give me ERROR

Code:
Failed to evaluate the script:

Python exception: There is no function named SangNom

Traceback (most recent call last):

  File "src/cython/vapoursynth.pyx", line 2244, in vapoursynth.vpy_evaluateScript

  File "src/cython/vapoursynth.pyx", line 2245, in vapoursynth.vpy_evaluateScript

  File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile09_22_44_706.vpy", line 33, in <module>

    clip = havsfunc.aaf(inputClip=clip)

  File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 5333, in aaf

    aa = aa.sangnom.SangNom(aa=aay)

  File "src/cython/vapoursynth.pyx", line 1934, in vapoursynth.Plugin.__getattr__

AttributeError: There is no function named SangNom

Santiag if i choose "Type: sangnom" give me ERROR

Code:
Failed to evaluate the script:

Python exception: There is no function named SangNom

Traceback (most recent call last):

  File "src/cython/vapoursynth.pyx", line 2244, in vapoursynth.vpy_evaluateScript

  File "src/cython/vapoursynth.pyx", line 2245, in vapoursynth.vpy_evaluateScript

  File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile09_24_35_473.vpy", line 33, in <module>

    clip = havsfunc.santiag(c=clip, type="sangnom", opencl=True, device=1)

  File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 218, in santiag

    c = santiag_dir(c, strh, typeh, fwh, fhh)

  File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 150, in santiag_dir

    c = santiag_stronger(c, strength, type)

  File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 172, in santiag_stronger

    c = santiag_stronger(c, strength - 1, type)

  File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 195, in santiag_stronger

    return c.sangnom.SangNom(order=field, aa=aa)

  File "src/cython/vapoursynth.pyx", line 1934, in vapoursynth.Plugin.__getattr__

AttributeError: There is no function named SangNom

SangNomMod Anti Aliasing WORKS

@shijan you mentioned prores 422 hq was essentially Lossless do i need to pick others settings other than that, there seems to be other options within prores422hq that i can pick.

Selur
I noticed on legacy hybrid 2018 if i pick x264 i can’t pick crf=0 which is essentially lossless, it goes as low as 1.0. I was on some forums that mentioned That x264 has a range from 0-63, with a Crf=0 Being lossless. Is this a hybrid limitation?

Secondly, for the encoding suggestions you mentioned for that video i shared return to treasure Island.
Could you show me via pictures the settings i need to pick on hybrid? Or do i just copy the code scripts?

No rush on this, would rather have the focus on the mac app than my video, but see where the settings are located and what i should click on would be helpful.

Thanks in advance.
And thank you for your hard work.

@Adamcarter PM'ed to you...

@ Selur
Also in addition to color edges degradation. I notice that there is a some brightness levels shift when use Color -> ColorMatrix transform.
Seems brightness levels shift visible only in VS viewer preview. When rendered to x264 and in player levels are back to normal.
But chroma edges artifacts are still there.
UPDATE. seems chroma edges artifacts where caused by MPEG1 source. Seems Hybrid reads MPEG1 in some strange way. When i convert source file to 10bit ProRes422HQ and import again in hybrid, chroma edges have no artifacts when i apply 601 to 709 color matrix. But anyway other problems with color matrix still exists. I am not soo deeply technical in theory to explain the nature of this transformation. Seems part of this problem was discussed here:
https://forum.doom9.org/showthread.php?s...post514595
https://forum.doom9.org/showthread.php?s...adid=37082
https://forum.doom9.org/showthread.php?s...adid=82217

Also it seems there is some confusion:
Button "Save" in Hybrid acts as button "Save As..." in all other apps
Button "Save Same" in Hybrid acts as button "Save" in all other apps

Hopefulle I didn't miss something, if I did post again about it.

Loading cube files in TimeCube should work now.
Regarding ColorMatrix and 'Rec.2020', no clue how to properly use it. Seems like the call needs additional parameters, but I couldn't find any usable documentaion.
-> removed 'Rec.2020'
Quote:Meatwad mentioned that getting ffmbc compiled for mac may not be worth the trouble. He said it was meant to support DNxHD and Prores better which is already in FFMpeg.
-> https://forum.selur.net/showthread.php?t...51#pid8551
Quote:I always wonder why tabs in "Config" tab made like this?
They are this way due to some problems with MacOS (back from 10.9 iirc).
Problem was the 'Output'-tab, when using additional tabs in it MacOS broke the layout.
No clue whether this is still the case,...
-> not spending time on this at this moment, since I think the other issues are more important.
Quote:Filtering -> Other -> VFM ERROR
...
"Got an empty value for 'vsOVFMMChroma', please report to Selur!"
You probably used some old preset or profile which didn't include the value.
-> reset your defaults and don't try to use old presets&code, I told you before this would cause unforseen problems,...
Quote:"AntiAliasing - Nedi3aa" located before global "AntiAliasing"
-> "AnitAliasing" typo fixed
Quote: seems chroma edges artifacts where caused by MPEG1 source. Seems Hybrid reads MPEG1 in some strange way.
Seems like a bug in the source filter, nothing I can do about it.
Especially since I don't know what source filter is used for your input.
Quote:DeHalo YAHR ERROR
Works fine here. -> reset your defaults don't use old presets&co.
Quote:Also in ColorMatrix SMPTE 240M may be broken as well.
In all sources it is described that SMPTE 240M should look similar to BT.709 https://forum.doom9.org/showthread.php?t=133982 https://avisynth.org.ru/docs/english/ext...matrix.htm
But in Hybrid ColorMatrix SMPTE 240M looks same as Rec.601
If the Vapoursynth calls are correct, there is nothing I can do about it. You would have to complain to the Vapoursynth authors.
Quote:Error "TypeError: santiag() got an unexpected keyword argument 'typevh'"
Yup, that's a typo should be named 'typev' instead of 'typevh'.
SangNomMod vs SangNomMod:
-> I opened an issue about it with the dev: https://github.com/HomeOfVapourSynthEvol...d/issues/5
Waiting for a reply from the authors to decide what to do.
Quote:I noticed on legacy hybrid 2018 if i pick x264 i can’t pick crf=0 which is essentially lossless, it goes as low as 1.0. I was on some forums that mentioned That x264 has a range from 0-63, with a Crf=0 Being lossless. Is this a hybrid limitation?
To use lossless encoding use:
1. Encoding Mode: 'constant quantizer (1-pass)'; because using crf=0 is just a syntactic sugar for cq=0.
2. AVC Profile: 'High 4:4:4' or 'None'
3. enabled 'Lossless'
Quote:Could you show me via pictures the settings i need to pick on hybrid? Or do i just copy the code scripts?
Which of the settings is unclear?
Quote:Is it possible to arrange buttons in "Audio Presets" and in "Config -> Profiles" in same order as buttons in other places?
-> rearranged the buttons
Quote:Also it seems there is some confusion:
Button "Save" in Hybrid acts as button "Save As..." in all other apps
Button "Save Same" in Hybrid acts as button "Save" in all other apps
Not really.
'Save'-> Saves current settings under a new name
'Save Same' -> Save the current setting under the selected name

Uploaded a new version to the google drive.

Cu Selur

Ps.: @Adamcarter: best open a separate thread about your video, since it's not really related to the new version.

Aha, so i need to reset presets every time i update hybrid. I thought it was critical only when move from 2018 to 2020 version.

See my update about Color Matrix chroma edges: "seems chroma edges artifacts where caused by MPEG1 source. Seems Hybrid reads MPEG1 in some strange way. When i convert source file to 10bit ProRes422HQ and import again in hybrid, chroma edges have no artifacts when i apply 601 to 709 color matrix. But anyway other problems with color matrix still exists."
So formally currently only 601 to 709 and 709 to 601 works for sure.

Quote:Aha, so i need to reset presets every time i update hybrid. I thought it was critical only when move from 2018 to 2020 version.

No, you don't need to reset the presets, but from the looks of it you did not start with properly reset settings when switching to 2020 and somewhere along the lines mixed old and new presets/settings.

Quote:So formally currently only 601 to 709 and 709 to 601 works for sure.

Look at the Vapoursynth calls, are those correct?
If they are it's a bug in Vapoursynth, if they are wrong it's a bug in Hybrid I can fix.

Cu Selur

Also instead color matrix we can now use TimeCube. I see you add a lot or transformation LUTs for this