pkeegan
10-04-07, 08:44 PM
it appears HDMI auto negotiates audio and video settings between components.
Why don't manufacturers have manual override/force of HDMI auto settings?
My new DVDO VP50Pro is having trouble with the HDMI auto audio negotiation with an Oppo DV-970HD. The Oppo has an auto audio setting on its HDMI audio output. Via HDMI I can only receive 2 channel LPCM instead of the RAW digital audio from the Oppo.
It would be nice to be able to force HDMI settings on both ends via an interface.
This auto negotiations of video & audio is giving equipment manufacturers headaches. At least it would give the consumer the ability to use the HDMI
interface when auto doesn't work.
HDMI implementation has been terrible.
PooperScooper
10-05-07, 11:53 AM
This isn't an HDMI issue. It's an implementation issue or product issue. The Oppo sends PCM or DD/DTS bitstreams via HDMI. Multi-channel or 2ch PCM will only be sent for DVD-A/SACD/Redbook discs unless you tell it to do otherwise (I think it will decode DD/DTS to PCM, not sure. I have a 970 but I use defaults for HDMI audio output). It's not clear what you are trying to do.
larry
pkeegan
10-05-07, 07:00 PM
The Oppo talks with the HDMI attached device to determine what formats, audio and video, its capable of receiving. The Oppo has HDMI audio settings of AUTO, LPCM & OFF.
In auto the Oppo will use HDMI negotiation to determine what is to be sent (RAW or LPCM). In my case the Oppo decides to output only LPCM, but I want RAW. I want the option to set HMDI audio output to RAW manually. RAW will allow my separate Surround Sound Processor to decode Dolby & DTS bitstreams. I know of other devices having similar HDMI negotiation issues. I think the manufacturers should have a way to bypass/force what the HDMI settings are at both component sides.
Again I think this is an example of why I consider HDMI implementation to be extremely poor.
Richard Paul
10-05-07, 08:09 PM
it appears HDMI auto negotiates audio and video settings between components.
Why don't manufacturers have manual override/force of HDMI auto settings?Well HDMI is meant to be plug and play simple so for most CE companies they don't bother providing much in the way of forced settings for HDMI. Also if things go well you shouldn't need to force settings since auto-negotiation should work fine if both devices are doing it properly.
My new DVDO VP50Pro is having trouble with the HDMI auto audio negotiation with an Oppo DV-970HD.Well from what I have read it sounds like the DVDO VP50PRO (http://www.avsforum.com/avs-vb/showpost.php?p=11344581&postcount=305) is the problem. You should contact DVDO about this issue.
pkeegan
10-05-07, 11:02 PM
DVDO is aware. it's unfortunate that the HDMI spec hasn't made implementation easy. Its unfortunate that CE manufacturers would rely only on an auto function.
I guess the Oppo didn't have an HDMI audio AUTO selection at one point and you could select SPDIF or Multichannel (on board decoders) but a firmware update changed these options. Too bad they just didn't leave the original selections and add AUTO.
PooperScooper
10-06-07, 01:16 PM
The Oppo talks with the HDMI attached device to determine what formats, audio and video, its capable of receiving. The Oppo has HDMI audio settings of AUTO, LPCM & OFF.
In auto the Oppo will use HDMI negotiation to determine what is to be sent (RAW or LPCM). In my case the Oppo decides to output only LPCM, but I want RAW. I want the option to set HMDI audio output to RAW manually. RAW will allow my separate Surround Sound Processor to decode Dolby & DTS bitstreams. I know of other devices having similar HDMI negotiation issues. I think the manufacturers should have a way to bypass/force what the HDMI settings are at both component sides.
Again I think this is an example of why I consider HDMI implementation to be extremely poor.
Ok, understood. Like already mentioned it sounds like a VP50 issue. I'm guessing you want the VP50 to just pass through the bitstream from the DVD. The big problem with HDMI is no validation mechanism. There is no "box" that acts as a source to validate a target and no "box" that acts as a target to validate a source. I think one of the problems with this is that it would take to long to build and validate the validation "boxes". :)
larry