WEBVTT

00:00:00.240 --> 00:00:07.040
cameras lights fancy calibrated monitors

00:00:03.840 --> 00:00:10.080
what is the point of any of this YouTube

00:00:07.040 --> 00:00:13.440
has supported 4K High dynamic range or

00:00:10.080 --> 00:00:15.160
HDR video for years and yet this

00:00:13.440 --> 00:00:20.439
so-called next Pig thing is conspicuously absent from the content of

00:00:17.400 --> 00:00:22.519
even the geekiest creators no offense

00:00:20.439 --> 00:00:28.760
sorry nothing personal I know you know it's true and I know this question has

00:00:24.760 --> 00:00:30.480
been eating away at you why I mean many

00:00:28.760 --> 00:00:36.480
of you are carrying an HD R display around in your pocket surely you'd like

00:00:32.480 --> 00:00:40.360
to use it so is it laziness

00:00:36.480 --> 00:00:42.360
incompetence both I don't know because

00:00:40.360 --> 00:00:48.160
the problem actually isn't on the Creator side it's with YouTube the truth

00:00:45.640 --> 00:00:52.399
is that getting that little HDR selector to show up that's the easy part

00:00:50.280 --> 00:00:56.480
delivering a consistent viewing experience well that's extremely hard

00:00:55.160 --> 00:01:02.079
right now because of platform limitations that have existed for years

00:00:58.879 --> 00:01:04.920
now and I say enough is

00:01:02.079 --> 00:01:08.640
enough it's time for YouTube to stop half baking features that actually

00:01:06.680 --> 00:01:13.159
Elevate the viewing experience and take these problems seriously you know what

00:01:10.640 --> 00:01:17.840
else we take seriously Segways to our sponsors I fix it need a diverse tool

00:01:15.960 --> 00:01:23.000
kit I fix it has just the right thing for you learn more about the Manta

00:01:19.920 --> 00:01:27.840
toolkit and it's 112 steel bits with two

00:01:23.000 --> 00:01:27.840
premium drivers at the end of the video

00:01:34.560 --> 00:01:41.119
HDR hasn't proven to be the kind of tech buzzword that really drives people to

00:01:38.600 --> 00:01:46.079
upgrade but when they finally experience it done well most do agree that it looks

00:01:43.640 --> 00:01:50.200
more lifelike and immersive this is thanks to both its wider color gamut and

00:01:48.079 --> 00:01:54.840
its ability to retain detail in both the brightest and the darkest portions of

00:01:52.040 --> 00:01:59.880
the scene now HDR recording is all around us with popular devices boasting

00:01:57.000 --> 00:02:04.719
the capability for years now but in inite of this most videos on YouTube are

00:02:01.960 --> 00:02:09.560
uploaded in standard dynamic range or SDR which has a much narrower range of

00:02:07.280 --> 00:02:14.760
colors to sample from and tends to look flat or more lifeless by comparison

00:02:12.680 --> 00:02:20.319
obvious fix then right let's all just upload our videos in HDR so they'll be

00:02:16.840 --> 00:02:23.120
more good well yeah we thought of that

00:02:20.319 --> 00:02:26.800
obviously but every time we revisit this conversation internally we run into

00:02:24.840 --> 00:02:31.480
YouTube platform problems that have made our efforts discouraging to say the

00:02:29.519 --> 00:02:35.360
least to fully understand them though we're going to need to dive into how HDR

00:02:33.760 --> 00:02:39.840
content gets from the sets of your favorite shows to your ey holes by the

00:02:38.480 --> 00:02:44.560
way if your eyeholes are starved for some more entertainment check out our Floatplane exclusive video on the

00:02:42.720 --> 00:02:49.680
biggest data hoarders at LMG you won't want to miss it first of all not all

00:02:47.000 --> 00:02:54.200
content benefits from HDR so lighting wardrobe and set design play a major

00:02:51.959 --> 00:02:59.080
part in the overall experience then there's your camera anything from your

00:02:56.640 --> 00:03:06.560
iPhone to a cinema camera costing tens of thousands of dollars can capture HDR

00:03:02.239 --> 00:03:09.319
video but not all is created equal to

00:03:06.560 --> 00:03:15.799
explain we need to actually Define the dynamic range part of high dynamic range

00:03:12.799 --> 00:03:18.480
for a camera sensor the dynamic range is

00:03:15.799 --> 00:03:24.000
the number of increments or stops that it's rated for each stop up is double

00:03:21.400 --> 00:03:29.360
the amount of light and vice versa in a nutshell then the more stops the sensor

00:03:26.720 --> 00:03:34.120
can see at a time the higher the dynamic range and top tier Cinema cameras can do

00:03:31.680 --> 00:03:38.560
14 or more before they start to lose details in the darkest or the brightest

00:03:36.000 --> 00:03:44.200
parts of a scene when it comes to the content that we consume however HDR also

00:03:42.200 --> 00:03:48.480
comes with the expectation of a wider color gamut and well mastered HDR

00:03:46.680 --> 00:03:52.720
content should take advantage of both of these elements not to end up with an

00:03:50.840 --> 00:03:57.879
even worse version of the Vivid mode in a Best Buy showroom but to get a more

00:03:55.239 --> 00:04:03.079
natural appearance to achieve this a colorist will use specialized soft Ware

00:04:00.360 --> 00:04:08.000
and an ungodly expensive HDR mastering display to fine-tune details in a video

00:04:05.680 --> 00:04:12.040
like the texture of plants the lines on a person's face or the different shades

00:04:10.239 --> 00:04:15.959
of blue in the sky making them appear more true to life but we've got a

00:04:13.959 --> 00:04:20.120
problem the professional grade display that that colorist is working on is

00:04:17.959 --> 00:04:25.639
undoubtedly much nicer than anything you'll own in the next probably 5 to 10

00:04:22.320 --> 00:04:27.880
years so how do we translate what

00:04:25.639 --> 00:04:32.199
they're working on to your experience at home well that's where all of these

00:04:29.880 --> 00:04:37.840
competing HDR formats come in whether you're talking about hdr1 hdr10 plus DOL

00:04:34.880 --> 00:04:42.280
be Vision hlg or any of the others all of them exist to solve the same

00:04:39.800 --> 00:04:46.440
fundamental challenge of somehow delivering a consistent viewing

00:04:43.960 --> 00:04:52.680
experience across displays that have vastly different capabilities thankfully

00:04:49.160 --> 00:04:55.520
we do have a solution tone mapping

00:04:52.680 --> 00:04:59.840
metadata metadata is best defined as data that accompanies other data

00:04:58.000 --> 00:05:05.320
providing helpful information about it and oh you also want to know about tone

00:05:02.320 --> 00:05:07.840
mapping ah now that is a way of

00:05:05.320 --> 00:05:13.080
mathematically scaling the brightness and the color values of the content to

00:05:10.120 --> 00:05:17.720
match your current display it's super cool and without it this shot from the

00:05:15.479 --> 00:05:23.160
HDR Channel looking toward the sun would turn into a massive stain of white light

00:05:20.319 --> 00:05:29.080
on anything but a $30,000 reference monitor so then back to YouTube the SDR

00:05:27.160 --> 00:05:32.960
content on the platform is also accompanied by all sorts of metadata

00:05:31.319 --> 00:05:38.639
this includes information about the video and audio codec the creation date

00:05:35.639 --> 00:05:41.720
Etc what it doesn't include is any

00:05:38.639 --> 00:05:43.880
brightness or color information SDR

00:05:41.720 --> 00:05:47.880
devices expect this metadata to be encoded directly into the video file

00:05:46.199 --> 00:05:52.520
well that would be a big problem if they clicked on an HDR upload where the

00:05:49.759 --> 00:05:57.960
metadata is stored separately from the video file while HDR video can be played

00:05:55.759 --> 00:06:02.560
back by an SDR device it's going to end up looking a little something like this

00:06:00.680 --> 00:06:07.199
and given that the majority of viewers on YouTube are still likely watching on

00:06:04.840 --> 00:06:11.199
an SDR device that would be an unacceptable

00:06:08.599 --> 00:06:16.759
compromise but don't worry they do have a better one it's called a l or a lookup

00:06:13.759 --> 00:06:18.880
table Luts are essentially data files

00:06:16.759 --> 00:06:23.599
that are applied onto videos that transform the existing color values with

00:06:21.360 --> 00:06:27.479
their own color grade for you Zoomers out there you could think of them kind

00:06:25.039 --> 00:06:32.199
of like Instagram filters they're not quite the same as tone mapping which

00:06:29.120 --> 00:06:34.400
translates the entire color space but

00:06:32.199 --> 00:06:39.400
YouTube's one siiz fits-all L application looks all right enough that

00:06:37.319 --> 00:06:44.319
Joe average with his TN monitor isn't going to complain when they're watching

00:06:41.039 --> 00:06:47.639
your HDR video in its autogenerated

00:06:44.319 --> 00:06:50.000
SDR however because it's not tailored to

00:06:47.639 --> 00:06:53.680
your exact video I can pretty much guarantee that the colors are not going

00:06:52.000 --> 00:06:59.879
to come out the way that you intended yielding dull lifeless results and it's

00:06:57.400 --> 00:07:03.080
bad enough that the HDR Channel actually includes a disclaimer in their video

00:07:01.400 --> 00:07:07.280
descriptions warning that if their video looks pretty crap it's probably because

00:07:05.280 --> 00:07:11.039
YouTube ruined it you know what doesn't look crappy are LTT beanie in seven

00:07:09.520 --> 00:07:16.520
gorgeous colors available at LTT Store.com now you can upload your own L

00:07:14.000 --> 00:07:21.199
file alongside the video with customized values but the process by which you go

00:07:18.879 --> 00:07:25.879
about applying the L is convoluted at best involving stumbling across Google's

00:07:23.720 --> 00:07:29.560
help page on uploading HDR videos which then directs you to a GitHub page where

00:07:27.919 --> 00:07:33.199
you download a tool and Fiddle around around with the command prompt in order

00:07:31.039 --> 00:07:37.840
to apply the custom Lu to your video even then the tool itself is Antiquated

00:07:35.639 --> 00:07:42.400
as it was originally intended just to flag a video as HDR so that YouTube

00:07:40.199 --> 00:07:48.000
would know what you were uploading since flagging content for HDR metadata wasn't

00:07:44.720 --> 00:07:50.159
easy 6 years ago nowadays though

00:07:48.000 --> 00:07:54.520
software like Premier Pro can export a video with the requisite HDR metadata

00:07:52.319 --> 00:08:00.080
that YouTube needs to identify the video as HDR it's just that YouTube isn't

00:07:57.199 --> 00:08:06.240
using all of the provided metad data like supposedly YouTube supports hdr10

00:08:03.319 --> 00:08:11.240
plus which is great because it's an open standard for dynamic metadata which

00:08:08.759 --> 00:08:15.960
provides enough info for tone mapping on a scene by scene basis rather than just

00:08:14.039 --> 00:08:20.680
applying One Tone map for the entire video but neither we nor the gentleman

00:08:18.879 --> 00:08:26.560
who runs the HDR Channel have been able to get the HDR 10 plus to work so we've

00:08:23.879 --> 00:08:32.000
all given up on that the tool does however still give you an attempt at an

00:08:28.560 --> 00:08:33.599
SDR conversion by embedding your own L

00:08:32.000 --> 00:08:39.399
like separate from YouTube's standard one but this is with Dynamic metadata

00:08:36.680 --> 00:08:42.640
limitations and the loss of detail for bright areas in a bright scene for

00:08:40.880 --> 00:08:47.680
example another solution could be letting you upload both an SDR and an

00:08:45.279 --> 00:08:52.760
HDR grade of your video something that Prime video by contrast does give you

00:08:49.880 --> 00:08:57.800
the option of doing but I can't exactly easily migrate my business to Prime

00:08:54.640 --> 00:08:58.959
since in addition to obvious reasons

00:08:57.800 --> 00:09:04.000
it's geared toward professional filmmaker ERS and Distributors and before you even begin to upload anything

00:09:02.480 --> 00:09:07.760
you've got to jump through hoops like adding your bank account tax info and if

00:09:06.320 --> 00:09:12.079
you read deep enough in the fine print probably a pledge to donate a kidney in

00:09:09.320 --> 00:09:16.760
the event daddy Bezos needs it all of which means that I need YouTube to care

00:09:14.720 --> 00:09:22.959
enough to make this process manageable for independent creators and and to know

00:09:19.839 --> 00:09:24.839
that they should care we know from our

00:09:22.959 --> 00:09:29.160
audience data that about half of our viewers are on mobile with roughly half

00:09:26.880 --> 00:09:34.640
of those running Android 10 or newer which by Our rough napkin calculations

00:09:31.920 --> 00:09:40.399
means that at least a third of you right now are on an HDR capable screen at

00:09:37.920 --> 00:09:44.839
least on your phone even then there are some hiccups though on Android there's

00:09:42.839 --> 00:09:50.440
still no user brightness control alongside HDR so HDR videos will just

00:09:48.200 --> 00:09:55.040
Blast Your Eyes with maximum brightness not that great at night and according to

00:09:52.839 --> 00:10:00.200
the most recent steam Hardware survey over 80% of you are running at 1080P or

00:09:57.519 --> 00:10:05.000
less on your computers which are almost certainly not HDR and of the remaining

00:10:02.399 --> 00:10:10.320
20% very few will have shelled out for an HDR capable model with few were still

00:10:07.760 --> 00:10:15.519
spending the thousand plus on a quality HDR display that will truly give you a

00:10:12.600 --> 00:10:19.160
better viewing experience but the question there is why would you shell

00:10:17.519 --> 00:10:24.120
out the extra it's not like your favorite content creators are uploading

00:10:20.680 --> 00:10:26.200
an HDR or anything so I guess that's the

00:10:24.120 --> 00:10:30.279
point of this video I just wanted you to know that it's not because I don't want

00:10:27.720 --> 00:10:34.720
to and I wanted to finally get this out of my system because it might sound

00:10:32.680 --> 00:10:40.320
harsh but YouTube has been kind of like a disappointing child for me lately I

00:10:37.040 --> 00:10:43.800
can't control it all I can do is sit it

00:10:40.320 --> 00:10:45.519
down and talk about how deep down it

00:10:43.800 --> 00:10:51.279
knows it's capable of living up to its untapped potential but only if it

00:10:47.959 --> 00:10:53.320
applies itself you know so hopefully

00:10:51.279 --> 00:10:58.240
this rant reaches someone over there who cares enough to make a change oh and I

00:10:55.600 --> 00:11:02.480
hope it also reaches our sponsor I fix it Father's Day is quickly approaching

00:11:00.440 --> 00:11:05.760
which I love and iFixit has gifts for dads at all price points if you're

00:11:04.200 --> 00:11:10.399
looking for The Ultimate Gift check out iFixit Manta kit it comes complete with

00:11:08.519 --> 00:11:14.560
112 steel bits with everything from standard bits like Phillips and Flathead

00:11:12.360 --> 00:11:19.360
to more Niche bits like Torx TriPoint and game bits as well I fixi man kit

00:11:17.120 --> 00:11:23.279
includes not one but two aluminum screwdriver handles with a hefty quarin

00:11:21.560 --> 00:11:27.760
drive for full sizeize applications and a smaller 4mm one for precision work

00:11:26.120 --> 00:11:31.519
both drivers feature magnetic bit sockets knurled grips and silky smooth

00:11:30.120 --> 00:11:36.200
spinning tops you can just Nestle them in your palm and plus the toolkit's lid

00:11:34.440 --> 00:11:40.200
doubles as a sorting tray for added convenience and that's magnetic too work

00:11:38.240 --> 00:11:44.639
confidently knowing all iFixit tools are backed by a lifetime warranty and check

00:11:42.320 --> 00:11:48.279
out iFixit gifts for dads using the link below if you guys enjoyed this video and

00:11:47.079 --> 00:11:53.639
you want to learn more about the inner workings of HDR check out our video HDR

00:11:50.760 --> 00:11:57.240
standards explained hdr10 dby Vision hlg over on techwiki and be sure to let us

00:11:55.760 --> 00:12:00.920
know what you think about YouTube's implementation of HDR and if you're

00:11:59.240 --> 00:12:06.160
content creator yourself we'd love to hear about any problems you've experienced down in the comments