Page 17 of 29
Re: Feature Requests
Posted: Thu Apr 16, 2020 5:18 pm
by Sherman
That lady looks like
Natasha! And the narcissism is off the charts. I call that "stupid confident".
Boris taught me about that. He said always reduce "I" and "me" to the absolute minimum. When you look back on your writing you always see those spurious little "me, me, me" references. Thinking he makes a lot of sense. See, don't say "I'm thinking". Nobody cares about you.
One day you will thank me for this.
EDIT: Oops, meant one day you will be thankful for this. OK?
Re: Feature Requests
Posted: Thu Apr 16, 2020 5:25 pm
by Guest
Natasha wrote: ↑Thu Apr 16, 2020 5:12 pm
You ever heard of
#MeToo? I can take you down in a
hot minute.
Have I ever heard of #YouToo
No, but I heard of YouTube
By the way, how is tiny Boris treating you
Re: Feature Requests
Posted: Thu Apr 16, 2020 6:06 pm
by Natasha
Boris? Not so much. Mr. Big? Watch out!
Re: Feature Requests
Posted: Mon Apr 20, 2020 4:05 am
by Guest 2
Rocky wrote: ↑Wed Apr 15, 2020 2:54 pm
If I may add, yes
Guest 2, just make a project and script for your HDR stream. Then run x265.exe with the script and the options
Boulder described. It's not that involved.
Is it the "same" as hdr10plus_parser found here
https://github.com/quietvoid/hdr10plus_parser?
Can I throw it away?
Re: Feature Requests
Posted: Mon Apr 20, 2020 5:41 am
by Rocky
HDR10 has static metadata while HDR10+ has dynamic metadata. I understand that x265.exe can encode with HDR10+ if built appropriately. DGIndexNV only understands HDR10 so you would need a different tool to extract HDR10+ metadata. There are no plans to do anything about HDR10+. DolbyVision is winning. DGTools already extracts that.
Re: Feature Requests
Posted: Sun May 03, 2020 9:28 am
by Beta
Rocky wrote: ↑Mon Apr 20, 2020 5:41 am
There are no plans to do anything about HDR10+. DolbyVision is winning. DGTools already extracts that.
Hello Sir!
Sorry for the dumb question, but what you mean under the DGTools?
Re: Feature Requests
Posted: Sun May 03, 2020 9:40 am
by Rocky
I mean the DG tools that can demux: DGDemux and DGIndexNV. DolbyVision metadata is carried as a secondary video stream.
Re: Feature Requests
Posted: Mon May 04, 2020 12:02 am
by Beta
Rocky wrote: ↑Sun May 03, 2020 9:40 am
I mean the DG tools that can demux: DGDemux and DGIndexNV. DolbyVision metadata is carried as a secondary video stream.
Thank You!
There is any way to save these meta datas in separated file?
Re: Feature Requests
Posted: Mon May 04, 2020 6:20 am
by Rocky
It's a video stream so it is saved as a video elementary stream.
Re: Feature Requests
Posted: Mon May 04, 2020 2:15 pm
by Beta
Rocky wrote: ↑Mon May 04, 2020 6:20 am
It's a video stream so it is saved as a video elementary stream.
I thought about a file what the x265 encoder accepts
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 Guest
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.
Re: Feature Requests
Posted: Sun May 10, 2020 4:54 am
by Guest 2
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.
Boulder