Ok. I delete Hybrid folder from user application support to make sure that it will be 100% clean install.
I got 5x this pop-up message at start:
![[Image: lU7bZPL.jpg]](https://i.imgur.com/lU7bZPL.jpg)
Same pop-up message appears when i navigate between Config tabs.
Small problem in TimeCube. LUTs in list arranged in some strange random order compare to LUTs finder folder. (Funny thing - i reported exact same problem to PhotoLine.app developers when they first time add LUTs support to their app. They somehow fix it)
![[Image: y5x94X2.jpg]](https://i.imgur.com/y5x94X2.jpg)
![[Image: XRSCoNM.jpg]](http://i.imgur.com/XRSCoNM.jpg)
Ahh,... accidentally deleted the entry,..
-> re-upload the version with 'menus' still there.
Cu Selur
Ps.: will adjust lut order next time, difference is simple: atm. Hybrid simply takes the luts in the way they are reported from MacOS, finder by default sorts by name.
Quote: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
"Save As..." in all other apps means save to some new file file with new name.
"Save" in all other apps means save (overwrite current file) under same name
(but same as tabs in Config tab it is not too critical problem at all)
VFM
works with updated presets
DeHalo YAHR
works with updated presets
OpenCL device autodetection (Device: -1)
WORKS
Small request - is it possible somehow be enable to close VS preview window with usual macOS shortcut
Command+W?
Quote:Small request - is it possible somehow be enable to close VS preview window with usual macOS shortcut Command+W?
This would require adjusting vsViewer not Hybrid itself -> So this will have to wait till at least the initial bug fixing and compiling tools etc. is over.
ColorMatrix Tests:
Rec.601 to Rec.709 WORKS (Rec.709 to Rec.601 also generates same proper "# ColorMatrix:" line)
Code:
# making sure input color matrix is set as 709
clip = core.resize.Point(clip, matrix_in_s="709",range_s="limited")
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# ColorMatrix: adjusting color matrix from 470bg to 709
clip = core.resize.Bicubic(clip=clip, matrix_in_s="470bg", matrix_s="709", range_in=0, range=0)
# adjusting output color from: YUV420P8 to YUV422P10 for ProResModel (i422)
clip = core.resize.Bicubic(clip=clip, format=vs.YUV422P10, range_s="limited")
# Output
clip.set_output()
(
but it just generates same "# ColorMatrix:" line as Rec.601) FCC usually described as "similar to BT.601" so seems Vapoursynth just decide to simplify things and just use same tag as Rec.601 when you select FCC.
Guess formally it is useless confused option if it designed like this.
Code:
# making sure input color matrix is set as 709
clip = core.resize.Point(clip, matrix_in_s="709",range_s="limited")
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# ColorMatrix: adjusting color matrix from 470bg to 709
clip = core.resize.Bicubic(clip=clip, matrix_in_s="470bg", matrix_s="709", range_in=0, range=0)
# adjusting output color from: YUV420P8 to YUV422P10 for ProResModel (i422)
clip = core.resize.Bicubic(clip=clip, format=vs.YUV422P10, range_s="limited")
# Output
clip.set_output()
("# ColorMatrix:" line always missing with it) SMPTE 240M usually described as "similar to BT.709"
Code:
# making sure input color matrix is set as 709
clip = core.resize.Point(clip, matrix_in_s="709",range_s="limited")
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# adjusting output color from: YUV420P8 to YUV422P10 for ProResModel (i422)
clip = core.resize.Bicubic(clip=clip, format=vs.YUV422P10, range_s="limited")
# Output
clip.set_output()
I'll look at the code tomorrow.
Cu Selur
Strange artifacts when i apply any LUT. Probably something related to color range, because artifacts partially disappear when i activate range conversion.
![[Image: r2GSmza.gif]](https://i.imgur.com/r2GSmza.gif)
(27.08.2020, 20:53)Selur Wrote: [ -> ]Quote:Small request - is it possible somehow be enable to close VS preview window with usual macOS shortcut Command+W?
This would require adjusting vsViewer not Hybrid itself -> So this will have to wait till at least the initial bug fixing and compiling tools etc. is over.
Seems no need to change things because seems VS preview window is easy to close by Command+Q. And this is logical because VS preview is just a separate single window app, but not a part of Hybrid windows system.
Probably you may add close window Command+W shortcut to "Vapoursynth Script View" Seems it is a part of Hybrid UI windows system.
Here is also Config tabs arrangement and simplified naming idea for discussion.
- "Output" submenu transformed to normal tabs in same row.
- Names shortened to make tabs block length more compact.
- MKV container and MKV tags settings combined into one single tab.
| Automation | Communication | Input | Internals | Containers | Filenames | Thumbnails | MKV | Paths | Profiles | Tools | View |
EdgeFixer and CAS updated by l33tmeatwad formally require 10.15+, but WORKS well on my 10.14.6. No errors, no crashes. Render goes well.