Feature Requests
Re: Feature Requests
Thank you, Sherman. I'll make a release first thing in the morning.
As a reward, I'll ask Mr. Peabody to let you stay up an extra hour tonight.
As a reward, I'll ask Mr. Peabody to let you stay up an extra hour tonight.
Re: Feature Requests
And get some chocolate ice cream too?
Sherman Peabody
Director of Linux Development
Director of Linux Development
Re: Feature Requests
I checked many HDR10 movies and everyone has "Chroma subsampling : 4:2:0 (Type 2)" in MediaInfo. Do you think X265_CL must contain one more option --chromaloc 2 ?
Re: Feature Requests
I don't know what X265_CL is, and it doesn't seem related to DG stuff.
Re: Feature Requests
DGDecNV slipstream 207:
* Added a line X265_CL to the bottom of the HEVC index file (for HDR PQ streams) containing command line
parameters for x265.exe derived from the colorimetry, HDR metadata, and frame count. This line
can be cut and pasted to your x265 invocation. Boulder
Re: Feature Requests
Ah yes, dementia setting in. I'll look into whether there is enough information in the input stream to definitively set this option.
Re: Feature Requests
Default undefined (not signaled)
https://x265.readthedocs.io/en/default/ ... -chromaloc
MediaInfo displays "Chroma subsampling : 4:2:0" in encoded movie, without Type 2 if chromaloc not set in x265.
ITU-T Recommendation - table 1 on page 8
https://x265.readthedocs.io/en/default/ ... -chromaloc
MediaInfo displays "Chroma subsampling : 4:2:0" in encoded movie, without Type 2 if chromaloc not set in x265.
ITU-T Recommendation - table 1 on page 8
Re: Feature Requests
Please re-download build 2053 and update DGIndexNV. I snuck this feature in for you. Thank you for the suggestion.
Re: Feature Requests
Thanks. It may help other people to create more correct 4k HDR videos
Re: Feature Requests
You are most welcome, guys. We aim to please.
Re: Feature Requests
Would it be possible to have DGDecode output the native bitdepth of the source? My point is that for HDR sources, I could do the motion analysis in MVTools in 10-bit domain and then denoise in 16-bit domain for a nice little speedup. It doesn't make sense to dither down to 10 bits in this case as the final output will be 16 bits anyway.
Re: Feature Requests
No, I mean the output you get from DGSource. As far as I know, both Avisynth+ and Vapoursynth accept YUV420P10 happily.
Re: Feature Requests
You can use ConvertBits(). Is it so terrible?
NVDec gives me 16-bit output. You know that, right?
NVDec gives me 16-bit output. You know that, right?
Re: Feature Requests
Actually I didn't know that 16-bit output is what the NVidia decoder gives you
I'll test if there is any actual visible difference if I dither down to 10 bits and use that as an analysis clip. It won't be used for the actual final output so chances are that it's faster and not distinguishable at all.
I'll test if there is any actual visible difference if I dither down to 10 bits and use that as an analysis clip. It won't be used for the actual final output so chances are that it's faster and not distinguishable at all.
Re: Feature Requests
You don't have to dither. Most likely the lower 6 bits are all zeros. They just need to be truncated by ConvertBits() if that is important for you.
DGDemux parser integration
It would be nice to have the same parser as DGDemux to select the correct mpls looking at lenght and streams, instead of needing to find it with other programs such as DGDemux itself or eac3to.
You already have the code, just make DGIndexNV capable of selecting a single file (usual behaviour) or give a "0" in the file field to select the whole directory.
P.S: I gently remind you language preferences too.
You already have the code, just make DGIndexNV capable of selecting a single file (usual behaviour) or give a "0" in the file field to select the whole directory.
P.S: I gently remind you language preferences too.
Re: Feature Requests
I'll consider it but honestly I'm not highly motivated for it.
Re: Feature Requests
Minor feature request: Isn't it time for a version bump of dgdecnv? it's been stuck on 2053 for years now and probably has had over hundreds of changes slipstreamed.
- Bullwinkle
- Posts: 338
- Joined: Thu Sep 05, 2019 6:37 pm
Re: Feature Requests
What's in a number? A program by any other number would smell as sweet.
Re: Feature Requests
This will probably be a pain to implement, but is there any possibility of getting nvidia NGX working for upscaling video in DG Tools?
Link for nvidia NGX: https://developer.nvidia.com/rtx/ngx
Link for nvidia NGX: https://developer.nvidia.com/rtx/ngx
Re: Feature Requests
If their claims about the simplicity of the API is true, then implementation may not be so difficult. I've applied for early access. We'll see if they grant it. Thank you for the request, astrayred.
Re: Feature Requests
My application was approved (in record time!) and I have downloaded the NGX SDK. As I get my feet wet I will report about it in another thread.