WEBVTT

00:00:00.240 --> 00:00:07.040
it used to be that trying to hook up something to a tv or monitor was like

00:00:04.400 --> 00:00:11.040
dumping garbage onto a truck you'd plug in some analog cables and the tv would

00:00:08.960 --> 00:00:15.120
just show whatever it was sent if the picture looked off in some way such as

00:00:13.120 --> 00:00:19.439
having weird colors or being the wrong size it was up to the user to

00:00:17.199 --> 00:00:23.680
troubleshoot the problem but these days most digital screens and video sources

00:00:21.279 --> 00:00:29.039
will support a standard called extended display identification data or edited

00:00:26.800 --> 00:00:33.600
the purpose of edit is to allow devices to talk to each other and share

00:00:31.439 --> 00:00:37.840
information about their own capabilities so both devices are on the same page the

00:00:36.160 --> 00:00:42.480
basic way it works is that when two devices are connected by a protocol that

00:00:40.079 --> 00:00:47.520
supports edit such as HDMI or displayport the display will tell the

00:00:44.559 --> 00:00:51.520
source device its manufacturer model and supported resolutions and color spaces

00:00:49.600 --> 00:00:56.160
the source device will then take this information and output a video signal

00:00:53.440 --> 00:01:00.960
which fits those parameters which is part of how auto settings on something

00:00:58.800 --> 00:01:05.119
like a game console works once the source receives the edit information

00:01:02.879 --> 00:01:09.360
from your screen it can auto magically output the game at the correct

00:01:07.040 --> 00:01:15.280
resolution and color space and even enable HDR if appropriate

00:01:12.479 --> 00:01:19.920
or at least that's how it's supposed to work like many other things in tech the

00:01:17.759 --> 00:01:23.119
addition of processing to make setup more convenient introduces a number of

00:01:22.000 --> 00:01:28.400
things that can go wrong one minor annoyance is

00:01:26.320 --> 00:01:32.720
because edited data has to be processed at every point in the device chain

00:01:30.479 --> 00:01:37.520
you might experience longer delays if you're routing a source device through a

00:01:34.720 --> 00:01:42.560
receiver so be prepared for some black screen time when you first turn

00:01:39.360 --> 00:01:45.360
everything on but larger issues can also

00:01:42.560 --> 00:01:49.759
arise you see because modern interfaces like HDMI feature hot plug support

00:01:47.759 --> 00:01:54.240
meaning you can plug or unplug it while the system's running the connector has a

00:01:52.000 --> 00:01:58.880
special pin to detect when it's being hot plugged when a device detects a

00:01:56.479 --> 00:02:04.159
voltage on the hot plug pin it starts the edited process but sometimes devices

00:02:01.360 --> 00:02:09.119
don't read the hot plug signal in the same way as it can be implemented

00:02:06.320 --> 00:02:14.000
inconsistently so the edit exchange never happens and as a result you get a

00:02:11.840 --> 00:02:17.520
blank screen as one device in the chain may think it's not connected to anything

00:02:16.160 --> 00:02:21.920
but even if you're not struggling with your setup completely refusing to work

00:02:20.000 --> 00:02:27.440
equipment coming with incorrect edit information coded in is a more common

00:02:24.480 --> 00:02:33.040
problem than we'd all like a device like an av receiver might actually be capable

00:02:30.080 --> 00:02:38.080
of accepting a surround sound signal yes edit works with audio too but thanks to

00:02:35.599 --> 00:02:43.120
bad edit information an attached device like a set-top box or a blu-ray player

00:02:40.800 --> 00:02:48.000
might not send it along since that particular receiver doesn't say hey i

00:02:45.440 --> 00:02:52.239
can support dolby digital plus frustratingly this is often a firmware

00:02:50.160 --> 00:02:56.640
issue caused by programming oversights meaning that a hapless home user can't

00:02:54.879 --> 00:03:00.640
just easily fix this on their own and actually a similar

00:02:58.480 --> 00:03:07.200
culprit was behind the recent issue in which certain sony tvs couldn't display

00:03:02.879 --> 00:03:08.720
a dolby vision signal at 4k at 120 hertz

00:03:07.200 --> 00:03:13.200
which of course was disappointing for owners of a gaming pc or an xbox series

00:03:11.120 --> 00:03:16.640
x you see edit actually has character limits which appears to keep these

00:03:14.640 --> 00:03:20.159
displays from telling the video source what it supports because they just

00:03:18.080 --> 00:03:24.959
support so much stuff now other times devices might receive the correct edit

00:03:21.920 --> 00:03:27.360
information but not do the correct thing

00:03:24.959 --> 00:03:31.680
with it for example a computer plugged into a display knows through the edit

00:03:29.920 --> 00:03:35.280
that the display can support a large range of resolutions and a range of

00:03:33.360 --> 00:03:39.519
refresh rates but instead of picking the native resolution at the highest refresh

00:03:37.440 --> 00:03:42.720
rate possible it might default to something completely different meaning

00:03:41.599 --> 00:03:47.440
you have to go into the settings yourself and adjust everything which

00:03:44.640 --> 00:03:50.879
kind of defeats the whole point if you're having problems with edith there

00:03:48.959 --> 00:03:54.640
are special edit emulators that you can program yourself to ensure the correct

00:03:52.640 --> 00:03:59.599
information is being passed along but of course it's often easier simply to take

00:03:57.599 --> 00:04:03.760
a minute and check that the settings you can adjust are the way you want them

00:04:02.000 --> 00:04:07.360
it's a little annoying that we haven't figured out how to make edit work

00:04:05.599 --> 00:04:11.840
correctly without intervention every time but hey we also haven't figured out

00:04:09.200 --> 00:04:15.280
how to make self checkouts not totally suck so

00:04:14.159 --> 00:04:21.280
here we are so thanks for private internet access for sponsoring this video pie is a tool

00:04:19.040 --> 00:04:25.280
that masks your ip address and encrypts traffic on your devices you can combine

00:04:23.440 --> 00:04:28.400
it with private browsing tools to even make savvy websites think you're

00:04:26.880 --> 00:04:33.040
somewhere else they offer reliable service with over 12 000 servers in 74

00:04:30.800 --> 00:04:36.479
countries and no bandwidth caps they have configurable encryption and an

00:04:34.560 --> 00:04:40.479
internet kill switch prevents data from leaking should you be involuntarily

00:04:38.400 --> 00:04:44.639
disconnected their mace feature blocks requests to known malware and tracking

00:04:42.320 --> 00:04:48.160
domains all together so you are safe try it risk free with their seven day money

00:04:46.479 --> 00:04:52.160
back guarantee right now they got clients for Windows macOS Android iOS

00:04:50.080 --> 00:04:56.160
and Linux to get you connected up to five devices at once you can check them

00:04:53.600 --> 00:04:59.520
out at privateinternetaccess.com techweek so thanks for watching guys if

00:04:57.759 --> 00:05:02.240
you liked this video hit subscribe give us a thumbs up and be sure to hit us up

00:05:01.040 --> 00:05:07.280
in the comments section with your suggestions for topics that we should cover in the future