Zibb

Brian DipertEDN Senior Technical Editor Brian Dipert exposes, analyzes and
opines on diverse topics in technology. Follow the Brian's Brain Twitter feed at www.twitter.com/BrianzBrain.



   Advertisement

Profile

RSS Feed

  • Add this blog to your RSS newsreader!

Recent Posts

Recent Comments

Most Commented On

Archives

By Category

Consumer Electronics Design Articles

Blog

Wednesday, January 3, 2007

Connecting Systems To Displays: HDMI 1.3 Counter-Points

Jan 3 2007 5:06AM | Permalink |Comments (3) |


This blog post references my cover story 'Connecting Systems To Displays: What We Got Here Is A Failure To Communicate' in EDN's January 4, 2007 edition.

In my article, I point out that it's not absolutely necessary to upgrade to HDMI 1.3-cogniscent multimedia sources, destinations and in-between cabling in order to enjoy high-resolution audio in Dolby TrueHD and DTS-HD Master Audio formats. As I put it:

HDMI Version 1.3 also broadens audio-transport support to encompass the latest high-fidelity lossless-compression formats from Dolby Labs and DTS. This addition is significant only if the transmitting device is incapable of decoding these formats; if it can decode these formats, it could alternatively employ the support for uncompressed audio transport in earlier HDMI versions, along with multichannel-analog-audio connections.

In a letter to the editor in the January 2007 issue (#116) of Widescreen Review, Microsoft's Kevin Collins echoes this point and expands on it, revealing several good reasons why you might not want to rely on a downstream A/V receiver to do the decoding even if the HDMI transport and audio destination both support this feature:

Another point to keep in mind is that if the audio is not decoded in the player, then none of the interactivity that utilizes sound can be achieved. This means that the PIP that people are coming to love with IME and U-Control would not be possible. The audio must be decoded in the player and mixed with the audio from the secondary video. Another advantage of decoding in the player with next-generation audio codecs is that they have meta-data that the studio, while authoring, can control the down-mixing and fold-down with.

I'll close with another HDMI 1.3 qualifier. Over and over again I see Sony's PS3 marketing fingerprints when I read that someone has claimed that HDMI 1.3 is required in order to support 1080p60 (1080-line resolution, progressive-scan, 60 fps) images. This is simply not true; the original HDMI 165 Mpixel/sec bandwidth was more than adequate to handle this display setting. Do the math yourself if you don't believe me (1920x1080x60=124,416,000 pixels/sec). When you see, for example, a first-generation Toshiba HD-A1 HD DVD player whose HDMI video output tops out at 1080i, that's simply because the HDMI transmitter inside the player is incapable of running at peak HDMI speeds. Again quoting from my article, specifically about HDMI's predecessor, DVI (the point also applies to the HDMI successor):

However, some silicon suppliers, particularly those that attempted to integrate a DVI transceiver within a larger piece of silicon such as a graphics chip, were unable to meet the 165-MHz design target. (DVI’s I2Cbased DDC (display-data-channel) bus is the means by which graphics chips and displays communicate their respective capabilities and limitations to each other.)

Digg This | Slashdot This


Reader Comments



at 1/3/2007 8:50:03 AM, Taylor Gautier said:
I may have missed it - have you discussed DisplayPort? I only just found out about it on this Engadget post -

www.engadget.com/2007/01/03/displayport-to-support-hdcp-too/

Yet Another Display Standard - unbelievable.



at 1/3/2007 10:25:49 AM, Brian Dipert said:
Taylor, I'll cover DisplayPort at length in tomorrow's cover story. Look for it; I welcome your feedback.



at 1/3/2007 11:31:21 AM, Paul Wolf, HDMI LLC said:
Brian,
There are several reasons that users would like to see the decode happen in the player but there are also reasons to decode it in the AVR (amplifier).

In addition to the audio mixing issues that Kevin Collins points out, decoding in the player provides backward compatibility with the existing HDMI multi-channel AVRs, allowing them to be used with Dolby TrueHD or DTS-HD MA audio content.

That said, there are also reasons for shipping the compressed stream over to the AVR, which may be more suitable for doing bass management and other functions that are not implemented or only minimally implemented in the player.

So where should the decode happen? Talk to some player guys and they'll say "the player" but if you talk to the amplifier folks, they'll say "the amp".

HDMI 1.3 enables both configurations. We would prefer to see most BD and HD-DVD players support decode, since that will cause the least confusion, but we absolutely wanted to support the alternative as well and that's why we included it in HDMI 1.3.

Paul Wolf
Chief Technologist
HDMI LLC

Post a comment



Display Name

Change Image
Before submitting this form, please type the characters displayed above.
Note the letters are NOT case sensitive.


ADVERTISEMENT

©1997-2009 Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy

Please visit these other Reed Business sites