This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

HDR encoding
#31
(08.09.2017, 18:00)Selur Wrote: Had a quick look at did some adjustments, color matrix should now be detected correctly.
DebugLog shows that DGSource was used, so that seems to work,.. Smile

I am testing. Until then could you please help because still do not understand:

Quote:# adjusting output color from: YUV420P16 to YUV420P8

clip = core.resize.Bicubic(clip=clip, format=vs.YUV420P8)

Why adjusting output color to 8 bit and feed that to the encoder which will use 10 bit? (I am a bit confused)

Preview window still not working. "Interesting": after pushing crop window icon Hybrid start indexing for a few minutes, after indexing crop window doesn't show up but a Windows 10 bug report on the tray is displayed for just a few seconds directly after indexing.
Reply
#32
Quote:Why adjusting output color to 8 bit and feed that to the encoder which will use 10 bit? (I am a bit confused)
should be 10bit probably a bug
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#33
(08.09.2017, 18:00)Selur Wrote: Had a quick look at did some adjustments, color matrix should now be detected correctly.
DebugLog shows that DGSource was used, so that seems to work,.. Smile

After having loaded an other HDR10 source to Hybrid, it immediately started reencoding without extracting, indexing after pressing start queue button. Is it the correct behaviour?
Vapoursynth refers to a dgi file but when was that being created? Sorry for a lot of question but it seems the program is still using software decoding.
Reply
#34
a. DGSource doesn't do software decoding.
b. If you don't use any Vapoursynth filters Hybrid will not use Vapoursynth.
-> I can look into it and make Hybrid use Vapoursynth whenever DGDecNV is used,..
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#35
(08.09.2017, 22:37)Selur Wrote: a. DGSource doesn't do software decoding.
b. If you don't use any Vapoursynth filters Hybrid will not use Vapoursynth.
-> I can look into it and make Hybrid use Vapoursynth whenever DGDecNV is used,..

Project has been crashed directly after indexing.
Reply
#36
Indexing finished without a problem.

Script looks fine:
# Imports
import vapoursynth as vs
core = vs.get_core()
# Loading Plugins
core.avs.LoadPlugin(path="C:/Program Files/Hybrid/vsfilters/SourceFilter/DGDecNV/DGDecodeNV.dll")
# Loading D:\UHD\x\x.mkv using D2VSource
clip = core.avs.DGSource("C:/Users/Bogárdi Mátyás/AppData/Local/Temp/11_21_27_4610.dgi", fulldepth=true)
# making sure input color matrix is set as 2020ncl
clip = core.resize.Point(clip, matrix_in_s="2020ncl")
# Making sure input color range is set to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# adjusting output color from: YUV420P16 to YUV420P10
clip = core.resize.Bicubic(clip=clip, format=vs.YUV420P10)
# Output
clip.set_output()

Decoder and encoder call look fine too:
"C:\PROGRA~1\Hybrid\VAPOUR~1\vspipe.exe" "C:\Users\Bogárdi Mátyás\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy" - --y4m | c:\PROGRA~1\Hybrid\x265.exe" --preset slow --tune grain --input - --output-depth 10 --y4m --profile main10 --crf 24.00 --qpfile "C:\Users\BOGRDI~1\AppData\Local\Temp\teszt_11_21_27_4610_04.qp" --range limited --colormatrix bt2020nc --output "C:\Users\BOGRDI~1\AppData\Local\Temp\11_21_27_4610_05.265"
What happens when you call:
"C:\PROGRA~1\Hybrid\VAPOUR~1\vspipe.exe" --info "C:\Users\Bogárdi Mátyás\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy" -
and assuming there is no problem what happens if you call:
"C:\PROGRA~1\Hybrid\VAPOUR~1\vspipe.exe" "C:\Users\Bogárdi Mátyás\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy" - --y4m | c:\PROGRA~1\Hybrid\x265.exe" --preset slow --tune grain --input - --output-depth 10 --y4m --profile main10 --crf 24.00 --qpfile "C:\Users\BOGRDI~1\AppData\Local\Temp\teszt_11_21_27_4610_04.qp" --range limited --colormatrix bt2020nc --output "C:\Users\BOGRDI~1\AppData\Local\Temp\11_21_27_4610_05.265"

Only thing that might cause a problem might be that the temp path contains special characters. Iirc Vapoursynth can handle them fine, but I'm not sure about DGSource and DGDDecNV. -> Does is work if you use a simple path like 'X:\Temp' as temp folder?

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#37
Quote:What happens when you call:

"C:\PROGRA~1\Hybrid\VAPOUR~1\vspipe.exe" --info "C:\Users\Bogárdi Mátyás\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy" -

This has happened:

Quote:C:\Users\Bogárdi Mátyás>"C:\PROGRA~1\Hybrid\VAPOUR~1\vspipe.exe" --info "C:\Users\Bogárdi Mátyás\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy" -
Script evaluation failed:
Python exception: name 'true' is not defined
Traceback (most recent call last):
  File "src\cython\vapoursynth.pyx", line 1821, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:36464)
  File "C:\Users\Bog├írdi M├íty├ís\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy", line 7, in <module>
    clip = core.avs.DGSource("C:/Users/Bog├írdi M├íty├ís/AppData/Local/Temp/11_21_27_4610.dgi", fulldepth=true)
NameError: name 'true' is not defined

C:\Users\Bogárdi Mátyás>

Quote:and assuming there is no problem what happens if you call:

"C:\PROGRA~1\Hybrid\VAPOUR~1\vspipe.exe" "C:\Users\Bogárdi Mátyás\AppData\Local\Temp\encodingTempSynthSkript_11_21_27_4610.vpy" - --y4m | c:\PROGRA~1\Hybrid\x265.exe" --preset slow --tune grain --input - --output-depth 10 --y4m --profile main10 --crf 24.00 --qpfile "C:\Users\BOGRDI~1\AppData\Local\Temp\teszt_11_21_27_4610_04.qp" --range limited --colormatrix bt2020nc --output "C:\Users\BOGRDI~1\AppData\Local\Temp\11_21_27_4610_05.265"

This has happened:

Quote:A rendszer nem találja a megadott elérési utat, which means the system doesn't find the path given.
Quote:Only thing that might cause a problem might be that the temp path contains special characters. Iirc Vapoursynth can handle them fine, but I'm not sure about DGSource and DGDDecNV. -> Does is work if you use a simple path like 'X:\Temp' as temp folder?

No, the result is the same.
Reply
#38
Quote: fulldepth=true)
NameError: name 'true' is not defined
Are you using the latest DGDecNV version? (it's from 2017-08-28)

Since according to DG:
Quote:Yes, it is possible. Use the fulldepth parameter to DGSource. From the user manual:

fulldepth: true/false (default: false)
When fulldepth=true and the encoded video is HEVC 10-bit or 12-bit, then DGSource() delivers 16-bit data to Avisynth+ with the unused lower bits zeroed. The reported pixel format is CS_YUV420P16. If either of the two conditions are not met, then DGSource() delivers 8-bit YV12 or I420 data, as determined by the i420 parameter. When fulldepth=false and the video is HEVC 10-bit or 12-bit, then the video is dithered down to 8-bit for delivery. If you need a reduced color space (less than 16 bits) for your high-bit-depth processing, you can use ConvertBits() as needed after your DGSource() call.
source: http://rationalqm.us/board/viewtopic.php...595&p=7154

Strange thing that the path seems to be broken,... (looked fine in the debug output)
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#39
Quote:Are you using the latest DGDecNV version? (it's from 2017-08-28)

Sure.

Attached the debug output when "C:\Temp" is used as the temp path.
Reply
#40
Created another dev version which should adjust the paths, may be it will help.
(will send link in a few minutes)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)