Closed GoogleCodeExporter closed 8 years ago
same here, i tried it via BubbleUPNP and the webpage solution. AAC 5.1 works
fine, but no pass through/sound with AC3 or E-AC3. Chromecast is connected
directly to A/V Receiver with Dolby Digital support.
Original comment by berner.a...@gmail.com
on 17 Oct 2014 at 10:15
Please add DTS
Original comment by brettwhi...@gmail.com
on 28 Oct 2014 at 10:50
DTS would make Chromecast the most relevant Home-Media-Device ever?!
Original comment by mike.wil...@gmail.com
on 2 Nov 2014 at 10:53
Add DTS please.
Original comment by m4ck...@gmail.com
on 18 Nov 2014 at 7:59
AC3 passthrough not working for me. MKV and MP4 files with AC3 streams casted
by localcast/bubblepnp give no passthrough steam to a/v receiver.
Original comment by mhagera...@gmail.com
on 19 Nov 2014 at 11:21
AC3 passthrough not working, not when connected directly into TV and amp
connected with optical and not with a HDMI -> HDMI,optical splitter, where as
the XBOX 360 passes the DD5.1 signal in both situations.
Original comment by rsvvuu...@gmail.com
on 21 Nov 2014 at 8:32
Please add DTS passthrough. Otherwise the CC is useless in most home cinemas...
Original comment by akjeld...@gmail.com
on 4 Dec 2014 at 6:05
With the latest BubbleUPNP server - 0.9-update1 - the passthrough works! I run
Bubble UPNP on my phone, the server runs on my PC as a service, and I initiate
playback from my Synology to Chromecast, no problem.
Original comment by bogo...@gmail.com
on 5 Dec 2014 at 8:06
AC pass-through is not working for me (including html test suggested above).
Same hdmi input on my receiver works fine for 5.1 AC3 with a DVD player or a
laptop's hdmi output. I also tested CC passthough option for 5.1 AC3 in the
recent update of bubleUPNP server and it did not work for me (no audio). This
is probably the same problem.
Original comment by yboy...@gmail.com
on 11 Dec 2014 at 4:25
No news from Google team about it? For me just DTS is pending, if works
chromecast is great device!
Original comment by car.cran...@gmail.com
on 17 Dec 2014 at 4:45
Issue 452 has been merged into this issue.
Original comment by na...@google.com
on 18 Dec 2014 at 6:03
Definitely not fixed in all cases. My TV happily decodes AC3 from my PVR, XBox
and Popcorn Hour but not Chromecast
Original comment by GaryWal...@gmail.com
on 18 Dec 2014 at 8:47
A lot of discussion about this over at the plex forum and inconsistencies over
when it works and when it doesn't. Definitely appears to be the Chromecast at
fault in it's implementation or it's been too literal in how it was implemented
https://forums.plex.tv/index.php/topic/121442-ac3-pass-through-has-arrived/page-
6
Original comment by GaryWal...@gmail.com
on 26 Dec 2014 at 12:51
I think google doesn't want to license dolby digital or DTS... have you people
notice that some movies in play store are in 5.1 but they're not dolby digital
but pcm, I know this because I made the test with a receiver with hdmi input
and all I got was PCM 5.1...
Original comment by ricardo...@gmail.com
on 30 Dec 2014 at 5:38
Just got it work using the Videostream app (at Play Store) In sound options,
i choose AC3 and it works! Clear and good Dolby Digital 5.1 directly from my
Chromecast, can't believe in it. Others apps such as Popcorn time and Plex:
still no luck. I will try more later.
Original comment by luizota...@gmail.com
on 4 Jan 2015 at 11:06
Thanks luizato! working for me too now!
But still.. want an app from where i can do this directaly from my NAS through
my smatphone..
Original comment by Tiago...@gmail.com
on 4 Jan 2015 at 11:31
It's not working for me.
If have tested lots of Apps and Files....
Do I have to update the Chromecast as well?
Original comment by Johannes...@gmail.com
on 7 Jan 2015 at 3:03
Tried Video stream. Still silence with ac3
Original comment by GaryWal...@gmail.com
on 7 Jan 2015 at 11:27
Give us proper 5.1, we have expensive equipment we cannot use because of dd+,
give us something we can all use.
Original comment by barefoot...@gmail.com
on 14 Jan 2015 at 8:24
this is not working for me with popcorn time (from opcorntime.io) and 720p
filethat use 1C3. There is no sound on TV (but I guess TV does not support AC3
Passthrough)
Why chromecast cant decode AC3 instead ???
Original comment by solstice.dhiver@gmail.com
on 17 Jan 2015 at 5:16
Not working here either. TV doesn't detect a DD input. Works fine with a PS3.
Original comment by sct.nico...@gmail.com
on 20 Jan 2015 at 10:25
I can't belive it's so hard to implementiert pass-through. And i absolutely
can't believe a company throws a streaming device on the market that is not
capeable of dealing with the two most important audio Codecs for home cinema.
The CC is good for presenting pictures, but it is useless for Video streaming.
Original comment by heus...@gmail.com
on 21 Jan 2015 at 10:27
LAN AC3 and DTS support, please.
Original comment by diego.ar...@gmail.com
on 4 Feb 2015 at 12:01
Audio pass-through is now enabled by the Media Player Library for E-AC-3 (EC-3,
Dolby® Digital Plus™ audio technology).
https://plus.google.com/117916055521642810655/posts/HwjvkqAf9VP
Original comment by lnicho...@google.com
on 4 Feb 2015 at 4:41
Thank you! Helluva birthday present to me :)
Original comment by skipmeis...@gmail.com
on 4 Feb 2015 at 4:45
Latets firmware was installed 26653 and now AC3 Passthrough is broken.
Only the first frame of the movie is shown after a couple of seconds the
chromecast reboots.
Plz fix :)
Original comment by rsvvuu...@gmail.com
on 4 Feb 2015 at 7:18
Yeah, my Chromecast reboots for both Plex and Localcast for AC3 files. You are
putting in a ton of effort to support passthough, but limiting it to certain
codecs. Perhaps you should just make passthrough passthrough and let the
receiver app either allow and/or restrict which container it is.
Original comment by ch...@cotehome.com
on 5 Feb 2015 at 1:35
I am having the same issue with version 26653, AC3 Passthrough does not work
anymore. Chromecast freezes and reboots. Please fix this.
Original comment by thean...@gmail.com
on 5 Feb 2015 at 7:54
Yep - add one more broken Chromecast
Original comment by achrisma...@gmail.com
on 7 Feb 2015 at 3:44
[deleted comment]
Shame on YOU GOOGLE!
it is sufficient only audio formats to support in the videos in it that you are
selling. Money money money and more money you vultures !
Give US AC3 & DTS GODDAMN!!!!!!! Or go to Hell...
Original comment by Ripcord1...@googlemail.com
on 7 Feb 2015 at 5:52
se BSPlayer FREE in Chrome OS and you got to see your videos (with locks )
1 - Download the Archon for the link
https://github.com/vladikoff/chromeos-apk/blob/master/archon.md
2 - Go to Google Play :
https://play.google.com/store/apps/details?id=com.bsplayer.bspandroid.free
3 - Opens this link:
http://apps.evozi.com/apk-downloader/?id=com.bsplayer.bspandroid.free and paste
the above address
4 - Download the apk .
5 - Convert utiizando the Twerk in its own chromebook
6 - Add the extensions list.
7 - Smile .
Original comment by hadriel....@gmail.com
on 7 Feb 2015 at 9:21
Same here - Chromecast updated to 26653.
Chromecast reboots immediately after casting movie with AC3 soundtrack
Original comment by Grochol...@gmail.com
on 8 Feb 2015 at 3:49
Same issue here. Chromecast freezes and reboots when trying to pass through an
AC3 audio track.
Most of my movies contain two audio tracks: An MP3 stereo track and an AC3
multichannel version.
When the Chromecast is connected to a TV without AC3 capability, the MP3 audio
track of my movies is automatically selected and the movie plays fine.
When I want to play a movie containing an AC3 audio track on a TV which allows
AC3 passthrough, I can circumvent the problem with the following procedure:
1. Disconnect CC from TV
2. Reboot CC
3. Start up the movie
4. Plug CC into the TV again (while the movie is playing)
5. Now the movie plays on the TV with the alternative (MP3) audio track.
Original comment by ken.tho...@gmail.com
on 20 Feb 2015 at 11:11
Same here with 26653.
I've been using Videostream and Bubbleupnp fine up until recently. I now get 2
seconds of video and then the Chromecast reboots after about 10 seconds. If I
disable AC3 Pass-through in Bubble the video plays. Was working OK before 26653.
Original comment by dlo...@gmail.com
on 20 Feb 2015 at 9:28
Exactly the same here since the latest fw update. With AC3 track video freeze
and CC reboot. With 2chan AAC track on the same MKV, it works fine. Can't check
version right now but with the same behaviour I have a feeling I'm on 26653 too.
Original comment by thomas.e...@gmail.com
on 20 Feb 2015 at 9:48
Same crashes with Dolby Digital (AC3) passthrough.
Original comment by rolando....@mymdc.net
on 25 Feb 2015 at 4:08
Same crashes with Dolby Digital (AC3) passthrough...
Original comment by jchecava...@gmail.com
on 26 Feb 2015 at 4:34
Same crashes with Dolby Digital (AC3) passthrough......
Original comment by lahrjoc...@googlemail.com
on 28 Feb 2015 at 9:19
Still no new update, crashes with Dolby Digital (AC3) passthrough......
Original comment by maurice....@gmail.com
on 6 Mar 2015 at 11:16
Pre 26653 update, Plex via Chromecast on either Nexus 7/Chrome browser on PC/My
Android phone all worked with AC3 and my AVR receiver displayed the correct
audio format which is Dolby Digital.
Post 26653 update, any AC3 materials using Chromecast failed. Screen diplayed
the content for 1 second and Chromecast shits itself. : (
Please provide update to remedy the problem.
Original comment by shing...@gmail.com
on 8 Mar 2015 at 4:40
Status = fixed - Surely some mistake - it has been broken since 26653 - it
worked briefly - can someone log a new bug?
Original comment by achrisma...@gmail.com
on 15 Mar 2015 at 9:07
Still NOT getting sound through.... Any feedback from Google pls?!?
Original comment by Skaarup....@gmail.com
on 15 Mar 2015 at 10:26
What the hell is going on with this? I'm having the exact same issue since
26653 too. Casting with mkv and ac3 now crashes. No comment, no fix no
explanation to reduced functionality? Does Google actually give a sh*t about
it's customers and the people who PAY to use their products?
Original comment by tthfl...@gmail.com
on 20 Apr 2015 at 9:46
LoL, Chalk up another reason I am glad I do my research before buying things.
If you need AC3 / DTS passthru just grab yourself a Tronsmart or other Android
Stick that has it. Yeah it may run you bout $50 - 70 USD, but much better than
a $35 useless player. To think they could just add AC3/DTS passthru on a whim
and not need to pay any extra and allow the receiver/TV do the decoding, but no
that would mean they would have to give raw access to an audio stream on their
devices. Google is too big a fan of sandboxing to do that.
Remember everyone you can vote with your wallet and especially in the Android
arena Google will still make some money off whatever you buy, but don't give
them anymore than is neccesary until they maybe remember customer support.
They could prolly find some way to allow raw streams within their sandboxing
architecture, but until they have a finiancial reason to do so you are going to
be waiting a L O N G T I M E
Original comment by MillerMi...@gmail.com
on 11 May 2015 at 2:32
[deleted comment]
The latest firmware version 31432 on gen 1 of Chromecast appears to have
re-mediated the Dolby Digtial passthru crashing issue. See Chromecast issue
number 510.
https://code.google.com/p/google-cast-sdk/issues/detail?can=2&start=0&num=100&q=
&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&so
rt=&id=510
Original comment by shing...@gmail.com
on 18 May 2015 at 8:42
I played up the 5.1 audio tests available on youtube. results only PCM 2.0 on
my LG home theater. Some people say that Chromecast sends DD+ to their receiver
Original comment by anders.l...@gmail.com
on 1 Jun 2015 at 4:26
Developers can now query the Chromecast for support of AC-3 and E-AC-3 as
described in https://developers.google.com/cast/docs/media.
Original comment by jonathan...@google.com
on 19 Jun 2015 at 12:24
Many of us have expensive 5.1 DTS sound systems that just can't be thrown away.
Please add DTS support for environment sake (assuming if we do throw away these
perfectly working sound systems).
Original comment by jho...@gmail.com
on 30 Sep 2015 at 8:12
Original issue reported on code.google.com by
cole.mickens
on 7 Mar 2014 at 11:54