Page 17 of 19

Re: Feature Requests

Posted: Mon May 04, 2020 4:43 pm
by Rocky
I don't know of any low-cost tools to generate the RPU data from the stream. ColorFront Transkoder is an option but is very expensive.

Re: Feature Requests

Posted: Fri May 08, 2020 7:03 pm
by MeteorRain
Extra zoom ratio for 8K contents?

Tried to index a 8K file on a 1080p screen, and the main window broke the border of the screen.
Would be sweet to have an extra zoom ratio of 1/6 or 1/8 and be able to automatically switch to that for 8K content.

Thanks.

Re: Feature Requests

Posted: Fri May 08, 2020 7:20 pm
by Rocky
Yup, I agree. Thank you for the suggestion.

Re: Feature Requests

Posted: Sat May 09, 2020 11:44 am
by gonca
Along the same line
Would it be possible to add more zoom options or a sliding scale
My particular case use
I use 4K tv as monitor
My settings in Win 10 are to use 175% size
I can only use up to zoom 1/2 ( 0.5*1.75=0.875) of screen
If I select zoom=1 ( 1* 1.75 ) then the window is to big
Also consider zooming a 1080p video on a 4k monitor, zoom>1 would be nice to have

Re: Feature Requests

Posted: Sat May 09, 2020 12:45 pm
by Rocky
Bullwinkle has talked about the "handcuffs of zoom". Need to break the chains.

viewtopic.php?f=8&t=28&p=9983&hilit=handcuffs#p9983

Maybe we can get Sherman on this...when he finishes his homework. :lol:

Re: Feature Requests

Posted: Sun May 10, 2020 4:54 am
by tormento
Thanks for pcm to w64. You read my mind.

Re: Feature Requests

Posted: Tue May 12, 2020 12:43 pm
by Rocky
I've got Zoom = 1/8 implemented but need to get the PCM wrapping in there. Sherman, how is that coming along?

Re: Feature Requests

Posted: Tue May 12, 2020 12:47 pm
by Sherman
Sorry, Rock, I was busy reading Peres' book:

https://www.springer.com/gp/book/9780792325499

I'll get right on the W64 porting. Thank you for your forebearance.

Re: Feature Requests

Posted: Tue May 12, 2020 12:48 pm
by Curly
And your afterbeareance, nyuk nyuk.

Re: Feature Requests

Posted: Tue May 12, 2020 7:40 pm
by Sherman
Code's done for DGIndexNV W64 wrapping. I updated the DGIndexNV user manual too.

Over to you, Rocky.

Re: Feature Requests

Posted: Tue May 12, 2020 7:46 pm
by Rocky
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.

Re: Feature Requests

Posted: Tue May 12, 2020 7:47 pm
by Sherman
And get some chocolate ice cream too?

Re: Feature Requests

Posted: Wed May 13, 2020 5:14 pm
by alexantr
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

Posted: Wed May 13, 2020 6:29 pm
by Rocky
I don't know what X265_CL is, and it doesn't seem related to DG stuff.

Re: Feature Requests

Posted: Thu May 14, 2020 2:36 am
by alexantr
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. :salute: Boulder

Re: Feature Requests

Posted: Thu May 14, 2020 3:16 am
by Rocky
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

Posted: Thu May 14, 2020 4:14 am
by alexantr
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

Re: Feature Requests

Posted: Thu May 14, 2020 5:10 am
by Rocky
Please re-download build 2053 and update DGIndexNV. I snuck this feature in for you. Thank you for the suggestion.

Re: Feature Requests

Posted: Thu May 14, 2020 7:05 am
by alexantr
Thanks. It may help other people to create more correct 4k HDR videos

Re: Feature Requests

Posted: Thu May 14, 2020 8:45 am
by hydra3333
Yes, thank you.

Re: Feature Requests

Posted: Thu May 14, 2020 6:22 pm
by Rocky
You are most welcome, guys. We aim to please.

Re: Feature Requests

Posted: Sat May 16, 2020 9:03 am
by Boulder
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

Posted: Sat May 16, 2020 12:49 pm
by Boulder
No, I mean the output you get from DGSource. As far as I know, both Avisynth+ and Vapoursynth accept YUV420P10 happily.

Re: Feature Requests

Posted: Sat May 16, 2020 12:52 pm
by Rocky
You can use ConvertBits(). Is it so terrible?

NVDec gives me 16-bit output. You know that, right?

Re: Feature Requests

Posted: Sat May 16, 2020 1:47 pm
by Boulder
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.