|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
In Reply to: Re: You, too... posted by williak on April 25, 2003 at 11:23:53:
Autin,Thanks for the additional information to my post which I will take forward in other communications. Please note I was attempting to provide was a more balanced statement then the post I was responding too. I do not believe that all of my information was out of date, incorrect and speculative. I attempt to identify within my post where I was being speculative hence words such as 'contender' and some recently shipped products *do* happen to use propritory connections (Meridian, Denon).
Now if I may ask a couple of questions to clarify the IEEE issue further:
1) Is the Pioneer implementation based on the offical standard or developed prior to the ratification of the standard? I have seen a referrence to the effect that they worked with TI on the standard.
2) Is the dCS implementation compatible with the Pioneer implementation?
3) Are there any 'teeth' to the standard - Do manufactures have to comply? (e.g. DVD-A and SACD are standards, VHS and Beta are standards....) I did error in saying there was no standard when it may be more correct to say a standard exists but it is uncertain how well it will be adopted (Pioneer, dCS, MSB, Sony). This is an issue due to the cost of licencing and implementing the interface.
4) What are your thoughts on some companies (Meridian, Tag McLaren) that at one point (recent history) announced that they are planning to use HDMI instead of IEEE?
Follow Ups:
Rod,1. The Pioneer implementation is fully compliant with the standards. It adheres to the A&M protocol as well as the rate control protocol. Further, it has been approved by both 4C and 5C groups for transmission of copy-protected DVD-Audio and SACD. TI provides the 1394 interface mechanics embedded in silicon - they have two versions of the chipset one with and one without integrated encryption. The Pioneer gear necessarily uses the one with encryption.
2. Unfortunately, the dCS gear was developed in advance of the full adoption of the 1394 standard. It therefore is incompatible from a protocol standpoint with compliant devices from others. To be clear, the dCS gear DOES utilize a 1394 interface but it DOES NOT speak A&M protocol over that interface.
3. There are no "teeth" as such that would FORCE adoption of the 1394 digital audio standard. That said, NOBODY is allowed to transmit a digital representation of DVD-Audio or SACD material without complying with the encryption and other copy-protection mechanisms the different groups require. A manufacturer would get his ass sued off should he attempt to do so.
This is precisely what happened to Denon with their DenonLink (proprietary). They ran afoul of the DVD group and had to cripple the link just before the 5803 receiver and 9000 player hit the market. After some quick and very intense negotiations, Denon and the DVD-Audio group came to an agreement. Denon had to reconfigure the link as Denon Link SE (Second Edition), upgrade hardware in both the receiver and player, and all was well - at least for DVD-Audio. Sony has Denon in a pickle as they will not certify Denon Link for SACD transmission.
You are quite correct in assuming there are substantial cost issues associated with the 1394 standard. I believe the licensing costs are reasonable for the major manufacturers but the development costs in implementing the communication protocols are substantial. With less than stellar demand for the capability, most manufacturers are taking a "wait and see" attitude. This serves to delay their R&D outlays and possibly give them the advantage of using someone else's implementation via licensing or reverse engineering.
4. Meridian and Tag have taken positions on the hirez digital interface that could be due to several considerations on their part. First, Meridian is the developer of MLP which as you must know is integral to DVD-Audio. As Sony is the primary force behind the competing format, SACD, it is entirely understandable that either party would be less than enthused about supporting the other's technology and its wider acceptance in the marketplace. It's the same answer to the question: how come there aren't any Sony universal players? I'm not familiar with Tag's position but will keep my ears open.
As to HDMI, this is a further development of the existing DVI/HDCP video standard that has been demanded by content producers to transmit high-definition material in digital form. DVI/HDCP is now ubiquitous in display products. The last holdout, Mitsubishi, just caved in a few days ago and will provide DVI/HDCP interfaces on all their new displays. There are solid technical reasons for DVI to be the digital display interface of choice as it keeps HD digital signals in the digital realm without extraneous D/A and A/D conversions. Remind you of anything?
And of course, the copy-protection mechanism is very important to the further rollout of HD - both from cable and satellite sources as well future HD-DVD. HDMI improves on the DVI/HDCP interface but goes a bit too far in my opinion when it attempts to serve as the interface of choice for hirez audio. HDMI topology, cabling and internetworking capabilities seem singularly unsuited to the relatively simple bus structure and control protocols of 1394. It's clearly overkill and an attempt to be "all things to all people".
Just as you probably don't care for "one size fits all", I don't either. I feel strongly that audio and video should be kept separate and each allowed to develop its technology without negatively impacting the other. By putting both audio and video on one wire, HDMI violates this principle and I can easily imagine the difficulty a new audio scheme would have trying to get "space on the wire" from the HDMI committee.
I apologize for my curt and rude remarks to your previous post. I hope this post, in some small way, makes up for my previous one.
.
Meridian is sending encrypted digital to their dsp loudspeaker range for several years already. Since firewire wasn't available for audio applications at that stage they opted for their own protocol.Denon had a legal issue with the DVD Video license on the link, it wasn't the DVD Audio side of the interface that crippled the link.
Thanks for the info, Frank.I wasn't aware Meridian had already tangled with digital transmission of audio. No doubt they'd like to amortize their R&D investment over upcoming hirez audio products and perhaps they will.
Thanks for the reminder on the DVD-Video aspect of Denon's recent fumble. As I recall, the initial Denon products COULD run uncopy-protected DVD-Audio over the link but of course there were about two disks in existence that met that requirement.
My understanding of HDMI as it is proposed, is that the interface is fully backward-compatible with DVI in all its carnations. There may be provision for different HDMI cables to pick up these "stragglers" for compatibility purposes. The full-blown spec calls for a multi-conductor HDMI cable will fit HDMI connectors but will only use whichever signal wires are appropriate for the specific point to point use. That is, if the source is DVI/HDCP video STB driving a non-audio display device (such as a plasma), the would be no live connections for audio transmission between the two components.
This post is made possible by the generous support of people like you and our sponsors: