Quote:What's the problem with Avisynth+?
Why should there be a problem with Avisynth+?
Quote:And why is it not working with Avisynth 2.6 which is quite common?
Normal Avisynth doesn't support high bit depth as good as Avisynth, 64bit version is totally instable and as such not really suitable for UHD content.
Cu Selur
Quote:Why should there be a problem with Avisynth+?
Because you are using Vapoursynth instead.
a. Vapoursynth isn't limited to Windows only, like Avisynth+.
b. Vapoursynth has more potential in regards to expandability.
c. Vapoursynth uses multi-threading better.
Cu Selur
(10.09.2017, 16:26)Selur Wrote: [ -> ]a. Vapoursynth isn't limited to Windows only, like Avisynth+.
b. Vapoursynth has more potential in regards to expandability.
c. Vapoursynth uses multi-threading better.
Cu Selur
Hello,
Got from Donald Graft the infos as follows:
Quote:This Avisynth+ script works fine when opening in VirtualDub 64:
loadplugin("d:\don\Programming\C++\dgdecnv\DGDecodeNV\x64\Release\dgdecodenv.dll")
dgsource("H:\Streams\HEVC\10 Bit\ES\Philips_Ultra-HD_Beach_Life_supershop-demo-3.dgi",fulldepth=true)
convertbits(8)
If you have an application that accepts 16 bit you can omit the convertbits call. Or you can change it to convertbits(10) if your application accepts 10 bit.
It looks to me like Vapoursynth simply does not support HDR from Avisynth source filters. Or maybe it doesn't support 16 bit and you need to convert it to 10. Ask the author about that.
I think x265 can accept 16bit content. According to the profile chosen it will convert the input to the required bit depth (e.g. when using main10 profile x265 will convert the 16 bit input to a 10 bit output).
Quote:I think x265 can accept 16bit content. According to the profile chosen it will convert the input to the required bit depth (e.g. when using main10 profile x265 will convert the 16 bit input to a 10 bit output).
Yes, but unless Vapoursynth accepts the 16bit output of DGSource that doesn't help at all.
The problem isn't the conversion from 16bit to 10bit, but that Vapoursynth doesn't like the output of DGSource.
If you want Avisynth+ you could use StaxRip.
(12.09.2017, 20:36)Selur Wrote: [ -> ]Quote:I think x265 can accept 16bit content. According to the profile chosen it will convert the input to the required bit depth (e.g. when using main10 profile x265 will convert the 16 bit input to a 10 bit output).
Yes, but unless Vapoursynth accepts the 16bit output of DGSource that doesn't help at all.
The problem isn't the conversion from 16bit to 10bit, but that Vapoursynth doesn't like the output of DGSource.
If you want Avisynth+ your could use StaxRip.
Thanks! Staxrip seems to be working using Avisynth+!!!35-40% faster encoding than in Hybrid using software decoding.
Happy that helped.
Cu Selur
Ps.: To be sure, check that StaxRip is using the fulldepth flag, other than that it should be okay.
(14.09.2017, 05:19)Selur Wrote: [ -> ]Happy that helped.
Cu Selur
Ps.: To be sure, check that StaxRip is using the fulldepth flag, other than that it should be okay.
The script had to be supplemented manually to include this flag. x265 multilib could accept DGDecNV's 16-bit input and output the video as 10 bit (seemingly).
I didn't use ConvertBits(x) at the end of the script. After the encode is complete I have to check the output on my LG 4K TV and HTPC.
Just to inform you using Staxrip and DGDecNV with HDR10 input: I have completed my first HDR encode using DGDecNV, but unfortunately I saw some artifacts during decoding the output:
http://www.mammutmail.com/hu/download/bd...54b6fea0dd
I don't know yet if it is only a decoding problem now or if it is involved in the encode itself already due to some "problem" with decoding the original HDR content through DGDecNV.
Edit: It seems these artifacts are encoded into the output (the source material can be decoded without them).
Can't really help with StaxRip. There never is just a decoding problem,...
