Posts: 12.057
	Threads: 66
	Joined: May 2017
	
	
 
	
	
		Okay, got the SvtHevEncApp problem on my system resolved.
a. ulimit needed to be increased (ulimit -n 1000)
 (see: 
https://github.com/OpenVisualCloud/SVT-HEVC/issues/495 + 
https://github.com/OpenVisualCloud/SVT-A...-481452141)
b. the cpus VMWare is running are too old (two Intel® Xeon® CPU           E5640  @ 2.67GHz) but SvtHevEncApp 
Quote:CPU Requirements
In order to achieve the performance targeted by the encoder, the specific CPU model listed above would need to be used when running the encoder. Otherwise, the encoder runs on any 5th Generation Intel Core™ Processors (formerly Broadwell) CPUs (Xeon E5-v4) or newer
source: 
https://github.com/OpenVisualCloud/SVT-HEVC
So my guess is that on more modern CPUs it should work. 
Cu Selur
	
 
	
	
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
	
	
 
 
	
	
	
		
	Posts: 788
	Threads: 16
	Joined: Mar 2020
	
	
 
	
	
		Maybe it is possible somehow attach to Hybrid that BBC QuickTime File Format and ProRes Video Parameter Editor binary to write proper tags in MOV files? 
https://github.com/bbc/qtff-parameter-editor
Davinci Resolve: (
all proper tags)
![[Image: tHSTZpg.jpg]](https://i.imgur.com/tHSTZpg.jpg)
Hybrid ffmbc: (
writes incorrect NCLC tags)
![[Image: EOAWKeq.jpg]](https://i.imgur.com/EOAWKeq.jpg)
Hybrid FFmpeg:(
can't write NCLC tags)
![[Image: XXWIRle.jpg]](https://i.imgur.com/XXWIRle.jpg)
Same time Tags in MP4 x264 and x265 
works correct when i use both MP4box and FFmpeg
	
 
	
	
	
	
 
 
	
	
	
		
	Posts: 788
	Threads: 16
	Joined: Mar 2020
	
	
 
	
	
		In addition to tags naming unification in distant future if it ever be possible, i suggest to 
unify tags lines order arrangement and names of those parameters. Currently we have four places with similar settings arranged in totally different ways and with slightly different naming variations. Unfortunately there is no any global specification how to order those lines and different media inspectors use different order. But i guess in most cases suggested order and naming looks like this:
Luma Range
Color Primaries
Transfer Characteristics
Matrix Coefficients
In addition in x264 and x265 there are common "Overscan" and "Video Format" settings lines. 
![[Image: TMJwX4m.jpg]](https://i.imgur.com/TMJwX4m.jpg)
![[Image: d8nVXMD.jpg]](https://i.imgur.com/d8nVXMD.jpg)
	 
	
	
	
	
 
 
	
	
	
		
	Posts: 788
	Threads: 16
	Joined: Mar 2020
	
	
 
	
	
		Also these checkboxes arrays probably may be unified to same look (I guess arrangement logic of those checkboxes in x265 looks more friendly):
![[Image: pZur3w1.jpg]](https://i.imgur.com/pZur3w1.jpg)
	 
	
	
	
	
 
 
	
	
	
		
	Posts: 788
	Threads: 16
	Joined: Mar 2020
	
	
 
	
	
		Another mistake in Filter(s) presets list name:
Change Resiual cleaner to Residual cleaner
	
	
	
	
	
 
 
	
	
	
		
	Posts: 788
	Threads: 16
	Joined: Mar 2020
	
	
 
	
	
		From conversation with 
TimeCube developer it seems 
mistake in script:
"TimeCube can work on any RGB format, not just RGB24, so it is an issue with the script generator."
"In the script you pasted, the input is converted to 8-bit before it reaches TimeCube:"
# adjusting color space from YUV422P10 to RGB24 for vscube
clip = core.resize.Bicubic(clip=clip, format=vs.RGB24, matrix_in_s="709", range_s="limited")
# color adjustment using TimeCube
clip = core.timecube.Cube(clip=clip, cube="/Applications/Hybrid.app/Contents/MacOS/TimeCubeFiles/identity.cube")
Guess it is better to fix it on Windows as well because that RGB24 probably force convert everything to crappy 8 bit
	
 
	
	
	
	
 
 
	
	
	
		
	Posts: 12.057
	Threads: 66
	Joined: May 2017
	
	
 
	
	
		Quote:"TimeCube can work on any RGB format, not just RGB24, so it is an issue with the script generator." 
Good to know.
8bit = vs.RGB24
9bit = vs.RGB27
10bit = vs.RGB30
16bit = vs.RGB48
-> will probably look at it after work
Quote:Change Resiual cleaner to Residual cleaner 
fixed locally
Cu Selur
	
 
	
	
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
	
	
 
 
	
	
	
		
	Posts: 788
	Threads: 16
	Joined: Mar 2020
	
	
 
	
	
		TemporalDegrain 
ERROR if input file is ProRes 10 bit 

No error with input 8 bit MP4 or VOB file
Failed to evaluate the script:
Python exception: Hqdn3d: input clip must be 8 bit, not RGB, and it must have constant format and dimensions.
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/tempPreviewVapoursynthFile06_16_47_222.vpy", line 26, in <module>
 clip = havsfunc.TemporalDegrain(inpClip=clip)
 File "/Library/Frameworks/VapourSynth.framework/lib/python3.8/site-packages/havsfunc.py", line 5181, in TemporalDegrain
 filterClip = denoiseClip.hqdn3d.Hqdn3d(4,3,6,3)
 File "src/cython/vapoursynth.pyx", line 2069, in vapoursynth.Function.__call__
vapoursynth.Error: Hqdn3d: input clip must be 8 bit, not RGB, and it must have constant format and dimensions.
 
	 
	
	
	
	
 
 
	
	
	
		
	Posts: 12.057
	Threads: 66
	Joined: May 2017
	
	
 
	
	
		Will restrict Temporaldegrain to 8bit formats.
Sadly libhqdn3d only supports 8bit.
	
	
	
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
	
	
 
 
	
	
	
		
	Posts: 12.057
	Threads: 66
	Joined: May 2017
	
	
 
	
	
		uploaded a new version,..
	
	
	
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.