Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)
Register FAQ Calendar Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
Old 28th June 2021, 15:34   #21  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,771
Quote:
Originally Posted by FranceBB View Post
Well, since we're talking about annoying things from the past, what about overscan/safe area?
To this very day, in 2021, some TVs still crop the image... and for what? Only 'cause back in the days timecodes and teletex subtitles were not muxed but rather displayed in the inactive lines of the screen which were not meant to be displayed to the user... Nowadays, in 2021, everything is muxed, it would be madness to put the timecode or subtitles there when you can easily just mux them in the container, but TVs still crop all around the screen, getting rid of what is actually a part of the image that should be displayed and they do that "just to play safe"...
Overscan can definitely die now. In the Filmmaker Mode spec from the UHDA, we mandated that there be no overscan.

The only content that even nominally benefits from overscan is legacy standard def stuff. And the solution there is simply cropping to 704x480 or 704x576 as appropriate. The eight left/right pixels aren't supposed to be displayed per SMPTE spec, and there's definitely no reason to encode them if they contain non-image content.
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 2nd July 2021, 21:15   #22  |  Link
kolak
Registered User
 
Join Date: Nov 2004
Location: Poland
Posts: 2,843
Quote:
Originally Posted by FranceBB View Post

- Overshooting
Some light overshoots are still allowed, though. The reason is that, even though you might get the waveform perfectly fine in Avisynth, once you encode with a lossy codec, the approximations that are gonna occur might lead to overshooting, so slightly out of range values. This was very much true for MPEG-2, but way less pronounced for H.264 and H.265, but it still occurs, which is why nobody is gonna tell you anything if you get some light compression overshooting every now and then.
Not only heavy compression overshoots, but intermediate codecs as well (ProRes, DNxHR etc). Quite often it's good few levels (of course on high contrast areas).
Not a big deal in current digital world. Broadcast freaks out about it for no real reason (it was a real problem in analog era, but not now).

Good that EBU R103 got updated. Key point is in line 2:

"The EBU, considering that,
• video levels have traditionally been measured with devices that display a trace, such as a traditional waveform monitor,
• that readings in mV no longer give relevant information in digital signal infrastructures,
• television systems now include high dynamic range and wide colour space images as well as
standard dynamic range and colour space images in the same digital container,
• that a certain tolerance can be allowed in digital signal levels,"

mV should be gone. They serve no role anymore. It should be either % of signal or simply levels per given bit depths.

Last edited by kolak; 2nd July 2021 at 21:25.
kolak is offline   Reply With Quote
Old 24th August 2021, 12:41   #23  |  Link
Balling
Registered User
 
Join Date: Feb 2020
Posts: 541
Facepalm! Ffmpeg default to limited BT.601 matrix. Okay. If you are using swscale that is, if you are using zscale it defaults to source range.

Oh, and also, ffmpeg still does not support limited RGB. So... It should now only ever tag full.

Last edited by Balling; 24th August 2021 at 12:46.
Balling is offline   Reply With Quote
Old 24th August 2021, 12:43   #24  |  Link
Balling
Registered User
 
Join Date: Feb 2020
Posts: 541
"To this very day, in 2021, some TVs still crop the image... and for what? "

It is very hard to not crop the image for HW SD image. Google VITC, for example. LG CX started doing that though.

Last edited by Balling; 24th August 2021 at 12:52.
Balling is offline   Reply With Quote
Old 24th August 2021, 14:52   #25  |  Link
FranceBB
Broadcast Encoder
 
FranceBB's Avatar
 
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,905
Quote:
Originally Posted by Balling View Post
It is very hard to not crop the image for HW SD image.
For SD sure, but the problem is that this still happens for FULL HD. You have no idea how many people use their TVs by default and watch FULL HD 25i channels and they expect the safe area / overscan to be respected 'cause otherwise it crops.
Sure, they can disable overscan in their TV settings if they want to, but by default TVs still crop and that's insanity but it's one of the reasons why we have to respect safe area / overscan for HD/FULL HD contents as well.

See the bottom blue line with no thicker on it (right below the white option on the right with the green button to get into the interactive menu)?



Well, that thing is there to respect the safe area / overscan.
Users at home who don't disable safe area / overscan in their newly purchased Samsung TV only see this:



As you can see this is just right 'cause we can't take a risk and therefore we make sure everyone (even those who don't disable overscan) see it correctly.
I would very much like to see TV manufacturers shipping TVs with the default option of NOT Cropping anything above SD resolutions...

Last edited by FranceBB; 24th August 2021 at 14:55.
FranceBB is offline   Reply With Quote
Old 24th August 2021, 15:21   #26  |  Link
Balling
Registered User
 
Join Date: Feb 2020
Posts: 541
Well, what happens on ads? I guess it will not account for it, just checked with my channels. Usually those UIs are very old.
Balling is offline   Reply With Quote
Old 24th August 2021, 15:23   #27  |  Link
Balling
Registered User
 
Join Date: Feb 2020
Posts: 541
BTW, D-1 has nothing to do with 16-235, 16-240 designation. See: https://tech.ebu.ch/docs/techreview/...ec601_wood.pdf

It was actually different originally, changed last moment. If we believe the doc, original was 72-252 for chroma, dunno for luma.

Last edited by Balling; 24th August 2021 at 15:30.
Balling is offline   Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 06:27.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.