Originally Posted by shortyg83
A couple issue with this.
First while in some interviews and such google did say that it would support dolby vision, they never said at release. In fact they never posted anything on the official site regarding it supporting dolby vision. And nothing on the packaging states it supports it as well.
Second the article you linked states something you seem to be ignoring. It says yes it supports Dolby Vision, but in the same paragraph it states that at first it will only support 4k video and later will add more 4k and HDR support. It doesn't state at release it will support Dolby Vision in fact it states the opposite.
The whole sound thing on the other hand, while it sucks, isn't exactly googles fault.
1. Chromecast states on their website and in product description. The chromecast is designed to be hooked up to the tv using the tvs speakers. That statement while saddening, basically means anything outside of your tv getting stereo sound isn't actually guarenteed or really supported by them.
2. Buying devices and trying to get cutting edge tech like HDR, Dolby Vision and 4k and then also buying a tv that doesn't support Dolby Digital + is just simply a mistake. You can argue only a few tvs support it, but that doesn't change the fact that this information is available before you made that purchase and you can't exactly expect every device you buy to completely be backwards compliant.
3. The last thing is as far sound goes, it falls on the APP maker to be able to functionally use the hardware they are given. Apps like Netflix and vudu tend to use Dolby Digital +. If they use dolby digital + they don't use dolby digital. So here is the deal the chromecast doesn't claim to convert music and via its "we only support connection to tv" it doesn't fall on them to. So if netflix and vudu don't choose to include a DD track along with the DD+ track then its gonna default to PCM. Im not really sure who should fix this because it obviously sucks. But don't think the issue is actually with google. You are playing a video that does not have Dolby Digital Audio you are playing a video that only has dolby digital plus audio and your tv cannot accept that. And chromecast is far from the only device that handles it this way.
As for the article I linked to where it is your position that it states something I seem to be ignoring, I would beg to differ.
Here is the quote you are referring to again...
Right there in the very first sentence of the Engineers blog entry it says "Chromecast Ultra supports 4K, HDR and Dolby Vision...
" -- it doesn't say it will support it later. Nor did it say that in the rest of that entire paragraph... or the entire blog entry for that matter.
If you want to parse his words and put your own spin on something where the second sentence begins by saying "At first, you'll be able to stream 4K content from Netflix, YouTube and Vudu
" we know he means 4K HDR content because that's what I am getting. Saying HDR and Dolby Vision would have been redundant at this point since he said that in the opening sentence.
You might have seen my reference to the public speaking circuit where I have been written up a number of times and each and every one of those times the article has been presented to me or I would be asked for clarification before it was published to ensure they didn't misrepresent what I was trying saying. I would assume that the same could be said for the dozens of articles published all over the web and in print which all say something along the lines of "...the new device supports both HDR10 and Dolby Vision flavors of HDR...
" just like the article published on AVS Forum announcing the Chromecast Ultra. Are you saying they ALL got it wrong?
I do take exception to your position that...
buying a tv that doesn't support Dolby Digital + is just simply a mistake
Like I said, the Samsung TVs do
support the Dolby Digital Plus codec (see attached thumbnail) it just doesn't pass DD+ over ARC that is why we only get DD 5.1 from apps when a device is hooked up directly to the TV whereas you would get DD+ passed to your Receiver. But hey, up until recently no TVs supported DD+ over ARC so a little unfair to call it a 'mistake' but not the first time I have had to point out to someone I am not a wizard with a crystal ball.
That all changed when we got our hands on the Chromecast Ultra and that is why the questions started appearing on this thread from guys like
, myself, and countless others I have seen while researching the issue on the Chromecast Help Forum threads so I would hardly go so far as saying...
that this information [was] available before [we] made that purchase
If that was the case then it sure wasn't clear and certainly not normal for an audio device. As a matter of fact when
first raised the question in this thread I think only one guy offered some help.
And as far as this comment of yours goes...
You can argue only a few tvs support it, but that doesn't change the fact that this information is available before you made that purchase and you can't exactly expect every device you buy to completely be backwards compliant.
I presume by "that purchase" you are now referring to the Chromecast Ultra -- not our TVs. If the information was available I would submit that it would have been readily apparent to the guys without asking the questions on this thread and the many, many, posts on the Chromecast Help Forum threads.
As for me, I primarily bought mine since my TV doesn't have the VP9 Profile 2
chipset so I can watch YouTube HDR. Hope you don't chalk that up to a 'mistake' too since that chipset didn't come along until later in 2016.
As for Netflix I am happy to say my TV app supports both 4K HDR and Dolby Digital 5.1 so no issues there. And if I want to watch a Netflix video that is SDR, I can always use my Ultra HD Blu-ray player (who's app hasn't been updated to support HDR) and get DD+.
It's getting to the point that for some of us we need a quick reference chart to determine what device we should use to get the optimum pleasure from our equipment for a particular program.
Isn't it ironic that 2 out of the 3 apps that their Engineering Director said we'd be able to stream in his blog entry, they only stream in Stereo unless you have one of the new TV's that support Dolby Digital + over ARC. Maybe he could have made that clear as well.
And while you can argue that we "can't exactly expect every device you buy to completely be backwards compliant
", while that may be true for some things I never thought Dolby Digital would be one of them. As a matter of fact here is an except taken right off Dolby's website...
Compatibility with Current Equipment
Equipment with Dolby Digital Plus will unlock its full feature set, including 5.1- and 7.1-channel capability (depending on the program).
If your system includes only Dolby Digital, you'll still get 5.1-channel surround sound, with the highest-quality Dolby Digital signal possible—Dolby Digital Plus content is easily converted to a traditional Dolby Digital signal.
They go onto say...
Because Dolby Digital Plus is built on core Dolby Digital technologies, content that is encoded with Dolby Digital Plus is fully compatible with the millions of existing home theaters and playback systems worldwide equipped for Dolby Digital playback.
I am not trying to argue with anyone on this thread, I was just trying to clarify what the issues are for a large cross-section of TV owners while helping a couple of guys out. At the end of the day if Google can't get the Chromecast Ultra to work like the array of Ultra HD Blu-ray Players and other devices out there who's apps such as Netflix and VUDU can
send Dolby Digital through the vast number of TVs that don't support DD+ over ARC then I guess it is what it is and for that reason I will not be recommending the Chromecast Ultra to those who seek my opinion without encouraging them to read from post 335 to the bottom of this page.