New HDMI 1.4 Spec Set To Confuse

thefickler writes "HDMI Licensing LLC, the company that determines the specifications of the HDMI standard, is set to release the HDMI 1.4 spec on 30 June. Unfortunately it could very well be the most confusing thing to ever happen to setting up a home theater. When the new cables are released, you're going to need to read the packaging very carefully because effectively there are now going to be five different versions of HDMI to choose from — HDMI Ethernet Channel, Audio Return Channel, 3D Over HDMI, 4K x2K Resolution Support and a new Automotive HDMI. At least we can't complain about consumer choice."

Comments

Re:Set fail...

[Jeremiah Cornelius]

There will be 12 different MONSTER cables.

I look forward to the Audiophile gold ends.

article summary is very poor

[YesIAmAScript]

There are 5 cables in the spec, but the descriptions are incorrect.

There 4 cables which are the 4 possible combinations of low-bandwidth (often referred to as HDMI 1.1) and high-bandwidth (capable of 1080p/60, deep color, etc., often referred to as HDMI 1.3) with the possibilities of supporting ethernet in the cable (100mbit) or not.

So there are:
low-bandwidth no ethernet (effectively an HDMI 1.1 cable)
high-bandwidth no ethernet (effectively an HDMI 1.3 cable)
low-bandwidth with 100mbit ethernet
high-bandwidth with 100mbit ethernet

Now, in reality, it's already difficult to buy an HDMI 1.1 cable, and likely few going to make a low-bandwidth cable with ethernet added, since low-bandwidth cables aren't popular already.

So that leaves two of these cables to decide between:
HDMI 1.3 cable
high-bandwidth with 100mbit ethernet (perhaps to gain the popular name HDMI 1.4 cable?)

and then there is one final cable, the wildcard, the automotive HDMI cable.

So 3 cables to choose from, one of which is a weirdo cable (automotive).

I don't think this will cause much of a problem.

The options listed in the article, return channel, etc, are all things added to the spec that can be there for an HDMI 1.4 device but without needing a specialized cable.

Re:Set fail...

[bmo]

Oxygen free "magnetically aligned" copper, hand twisted, and manually rubbed between the breasts of virgins for extra "lustre."

They just won't tell you that the virgins look like Rush Limbaugh.

--
BMO

HDMI Ethernet

[NFN_NLN]

â HDMI Ethernet Channel
"The HDMI 1.4 specification will add a data channel to the HDMI cable and will enable high-speed bi-directional communication. Connected devices that include this feature will be able to send and receive data via 100 Mb/sec Ethernet, making them instantly"... OBSOLETE

Thanks for coming out.

Re:HDMI Ethernet

[pla]

100Mb/s bandwidth for a 40Mb/s signal. What is the problem?

Well, for starters, 1080p (keep in mind this involves "raw" devices, not sending an MPEG4 down the line) uses just shy of 1.5 Gbps.

We can follow that up with "anyone not using wireless already upgraded to gig-E switches about five years ago".

We can then finish it off with one of my favorites (actually not, but in this case it really does serve the described need) - Any attached devices needing bidirectional communication can use plain ol' ubiquitous USB. And really, do my speakers actually need to talk back to my receiver under any even remotely plausible scenario that doesn't scream "DRM, mother fucker, do you speak it?"

Yah but

[Colin Smith]

Are they gold plated?

The TV manufacturers are simply screwing themselves over. They're dreaming. The new standard is going to be a computer screen attached to a PC streaming from youtube or similar.

 

Re:Set fail...

[Qubit]

They just won't tell you that the virgins look like Rush Limbaugh.

Well they are Monster cables....

I'm a geek, but...

[raddan]

Ugh. Maybe you can explain why I'd want to buy an HDTV with all of the accoutrements rather than buy a vastly cheaper flat panel display, and use it with my far more flexible computer. In my opinion, TVs and computers are converging, and new revisions of HDMI are a way to keep them differentiated. Is there really an advantage to an HDTV? This is the thing that has stopped me from buying an HDTV.

Now, as far as cabling goes, I suspect most of this is driven by a marketing department. If you look at computer display technology, which has been in rapid flux for at least 20 years, they've managed to standardize on TWO different connectors: one for analog and one for digital. Sure, there are some weirdo ones out there, like ADC and 13W3, but they never really had any real relevance. But with TVs, which is ostensibly simpler than computer displays, we have this panoply of cables. Why?

Now, Cat5e-- that's an impressive technology. The data rates people have been able to squeeze out of plain ol' twisted pair! But seriously; we do everything in software now. Why does television insist on having cable after cable to do functions that we could do with a single one?

Re:I'm a geek, but...

[LoRdTAW]

That's the way to go. When I bought my HDTV I mainly used it solely as a HTPC monitor and console monitor (have cable now so its a TV too).

The biggest offense of HDMI is the simple fact that multiple HDMI inputs on a TV/monitor are useless. If you want to use a home theater receiver for surround sound then you have to upgrade to one that has HDMI inputs. Why? Well Hollywood decided that HDMI cannot have its digital sound passed through the optical or coaxial output of your TV. So if you are thinking of using that shiny new HDTV with four HDMI inputs as your AV switch box then your out of luck. Even though that TV has an optical/coaxial output it will be disabled for HDMI, only analog outputs will work. You need to buy an expensive HDMI receiver for that setup to work.

My friend learned the hard way after purchasing a 47 inch HDTV with four HDMI inputs. He connected his XBox 360, PC and cable box. After digging through menus and testing his receiver he emailed the manufacturer of the TV and found out that his perfectly working Dolby digital receiver was now useless. He wound up getting an optical switch box to switch between inputs but OH wait the XBox 360's optical port is blocked when using the HDMI port. Fuck them for screwing us like that. HDCP and all the other copyright protection is a fucking sham.

Re:I'm a geek, but...

[YesIAmAScript]

No there isn't.

There is no adapter that will let you hook a DVI output to a DisplayPort-only monitor.

There are physical adapters that let you get DVI output from some DisplayPort ports. But it just ties a line on the connector that tells the sending device to not actually send DisplayPort signaling, but send DVI instead. This has a couple problems. First is that you are still paying the DVI licensing fees, including HDCP fees. Second is that if the source device doesn't have this alternate mode, the adapter doesn't work, because it can't convert it itself, it can only tell the sending device to send DVI instead.

Apple's adoption of DisplayPort seems like a disaster so far. If you have a more then 3 month old MacPro or iMac, Apple doesn't have a 24" display they can offer you. If you want to put an Apple 30" display on your MacPro, Mac Mini, MacBook or iMac, you need a $99 adapter that is large, takes up a USB port and doesn't even work right on some displays. And if you want to be able to give a presentation from your MacBook/Macbook Pro, you had better have brought a gaggle of adapters with you, since there isn't a projector on the planet that accepts DisplayPort. Not that you would have a DisplayPort cable to connect to the projector anyway, Apple doesn't even sell one! And even if the projector had a DisplayPort cable already attached, you couldn't use that either because Apple used mini DisplayPort, so it's adapter time again, except Apple doesn't sell that adapter either.

Re:I'm a geek, but...

[ion.simon.c]

Simple example: what about networked players?
* Do you add a switch into the unit and have both the TV and the player on the same subnet/VLAN? Or does the player and TV have its own subnet and the unit acts as a router?

If we assume that these devices are going to be on Joe Average's network, then we do nothing fancy... behave just like any PC attached to the network would behave.

[Should the player be a router o]r should the TV?

Neither, unless one really *wanted* to make them a router, I would make them a switch. I suppose that you could advertise your network-enabled media device as a handy-dandy router, for those folks who can't be arsed to buy a $30 router + WAP. But then, you'd need to add an IP stack to the devices in question.

Which address space should it pick? What if it clashes with the existing network?

Use DHCP to figure this out. If there are no DHCP servers, turn to the procedures outlined in RFC 3927.

What if there are duplex negotiation bugs/issues?

I imagine that duplex/rate negotiation is a solved problem by now. Have you seen issues caused by non-broken hardware that would not negotiate rate or duplex settings?

Re:I'm a geek, but...

[gittela]

Now, as I work most of my time as an AV-tech, I'd have to say that this is truth with modifications.
Projectors at conferences are usually vga only. I've never encountered a DVI cable in static systems at conferences. Sure, when we set it up ourselves and go for high quality HD projectors @ 10k ansilumens we will use our nice fiberoptic dvi cables or hd-sdi, but most of the time it is vga/rgb-hv.

That means one(1) adapter, if you bring your own laptop. Even peecees come with DVI these days.
For us techs, it means 3 adapters, one dvi-vga, one minidvi-vga and one DisplayPort-vga. This will not make much of a difference in our flight cases...

Apart from that, I agree. Apple pulled a bit of a stunt with the DisplayPort. While I like the new port, I think it's way too arrogant to assume that people will ditch a 6 months old machine just like that. :-)
H

Re:I'm a geek, but...

[Bert64]

People buying a 40" monitor would expect a much better resolution than that offered by 1080p... Look at the resolutions supported by the high end displays from Apple for instance.

Great

[macemoneta]

This is the 11th revision of the HDMI specification in the less-than 7 year life of HDMI. Meanwhile, the 22-year old VGA connection still works fine, at full HDTV resolution, and with none of the incompatibility or usage restrictions (DRM) that HDMI brings to the table. Um, progress?

Re:Set fail...

[3vi1]

Yes, much less confusing.

Hey, if I want to use a ZuneHD in my car which cable do I need?

Re:Set fail...

[im_thatoneguy]

My mistake. They are in fact releasing 5 + mini plug:

o Standard HDMI Cable - supports data rates up to 1080i/60;
o High Speed HDMI Cable - supports data rates beyond 1080p, including Deep Color and all 3D formats of the new 1.4 specification;
o Standard HDMI Cable with Ethernet - includes Ethernet connectivity;
o High Speed HDMI Cable with Ethernet - includes Ethernet connectivity;
o Automotive HDMI Cable - allows the connection of external HDMI-enabled devices to an in-vehicle HDMI device.

But. Standard HDMI cable == HDMI 1.1 cable and I don't even see those for sale anywhere. I assume it's pin compatible. So really the only new cables that people will encounter are:

1.4 Highspeed (1080p -> 4k, 3D, Deep color etc)
1.4 Highspeed + Ethernet.

Automotive will be built into your car hidden away from view. So unless you work at crutchfield you can ignore it.

Mini will be the same cables just with a differently sized plug.

Re:Set fail...

[3vi1]

Ha! TRICK QUESTION! I would never buy a Zune.

Re:Why not just use Ethernet?

[Zero__Kelvin]

" ... so why did these folks feel the need to reinvent the wheel?"

To sell more wheels.

Re:Why not just use Ethernet?

[evilviper]

Forgive me for not having kept up with the progress of HDMI,

...nor having the most basic knowledge of the topic at hand, correct?

wouldn't it have made infinitely more sense to have simply used gigabit Ethernet for all this?

Oh, my, yes. When transferring 16 Gigabits/sec of uncompressed HD video at high frame rates from your DVD player to your TV, what you really want is a 1 Gigabit/sec standard, designed for unreliable communications over 500 meter distances, using a shared-channel, with LOTS of overhead, and very high computational requirements...

Your insight is... stunning.

Re:Why not just use Ethernet?

[TopSpin]

Or did someone in the entertainment industry worry that using Ethernet for connecting entertainment devices would make it too easy for those evil hacker types to connect a computer to the setup and break their DRM?

Forgive me; I'm going to offer something other than 0MG iT'5 Ev1L DEE-ARE-EM zors.

Ethernet is slow. 10Gbit Ethernet is still exotic and costly. Gigabit Ethernet is much too slow for digital video, and gigabit phys cost more than what high volume TV manufactures will tolerate. An HDMI phy manufactured in 2003 sources or sinks 4.9Gbit/s. Two subsequent revisions have doubled this twice to 10Gbit and then 20Gbit. Basically HDMI provides an order of magnitude more bandwidth than the sort of common Ethernet you have in mind. Uncompressed digital video and audio (what HDMI does) requires emense bandwidth.

Ethernet is designed for the LAN use case. Consider the magic 300m minimum distance copper Ethernet is built around. This distance is desirable because it covers a large percentage of facilities where LANs exist without additional infrastructure. Among other things, signal frequency and copper (read cheap) cable construction are both bound by this. HDMI has no such requirement and thus does not incur the cost to achieve it.

HDMI clearly distinguishes between sources and sinks and has different expectations of each. Your digital TV will never suddenly begin transmitting Gbits of data someone will wish to render. It is exclusively a sink. Ethernet doesn't make provision for this sort of asymmetry which means both ends are peers and both suffer a certain minimum amount of complexity (read cost) because of it.

Ethernet is overly robust for digital TV. There are no packet collisions between your cable box and your TV. While HDMI does provide for error detection and correction, the remedy is radically different than what occurs on a LAN (retransmission usually.) The bad data is just spaced. The moment has passed and whatever pixel(s) or audio samples were corrupted are replaced by new bits before you perceive it (hopefully.) Here is some language from HDMI 1.3, 7.7:

The behavior of the Sink after detecting an error is implementation-dependent. However, Sinks
should be designed to prevent loud spurious noises from being generated due to errors. Sample
repetition and interpolation are well known concealment techniques and are recommended.

You wouldn't need to read many IEEE 802.whatever documents see just how far computer networking is from the design of HDMI. It is an entirely distinct use case.

Finally, HDMI provides timing guarantees that are totally absent in Ethernet. Devices are made cheaper through accurate timing (your TV doesn't need a larger high speed buffer for instance.) Recently so-called "Data Center Ethernet" has emerged to address this so that Ethernet can be used in latency sensitive applications. HDMI had this baked-in on day #1.

Some people are convinced that DRM is the only concievable reason for creating HDMI and all other claims offered are a smokescreen. That's the fashion around Slashdot, anyhow. Don't believe it. Those folks don't know what digital TV is.