Jump to content

Recommended Posts

Posted

For sometime now I cannot cast any files from within Emby libraries on a Windows 10 server to Chromecast.   I have three TV's, two with differing Chromecast devices and one with built in Chromecast. When attempting to cast to Chromecast each shows the selected TV ready to cast screen when the cast is connected but on attempting to play any file all that happens is the "spinning circle" that so many complain of.

The TV with built in Chromecast also offers DLNA and if DLNA is selected Emby casts all files without problem.  Additionally casting any file to Chromecast from others apps VLC, Media Player, Calibre, etc.etc, is always successful.

I have tried unsuccessfully all the possible fixes mentioned in the community pages here. From port fowarding, firewalling, restarting Emby, reinstalling Chromecasts and on and on. I have even installed Emby server on another brand new PC using a libraries of totally different files but alas I still have the same spinning circle when casting to Chromecast using Emby.

This all seems to show that Emby does connect to each Chromecast when asked to, as do all other apps I have tried, but having connected does not stream the selected file.  Also Emby does connect and stream properly where I could ask it to connect using DLNA.  This would suggest that the problem so many of us seem to be experiencing lies within that area of code where Emby fails for some reason to actually stream the selected file having successfully connected to a selected Chromecast.

Hopefully this problem can finally be addressed in the near future as I really want to avoid the effort of having to remove two Emby servers and installing and learning another product and moving our libraries to it so that that is able to meet my families sole desire "to stream stuff to their TV's" so they have something to watch in those hours where we don't have access the satellite that gives us an internet connection. 

 

 

 

 

visproduction
Posted

I've read about security Chromcast features to keep stray Wifi commands locked out.  I believe this built in security may have caused your problem.   I am guessing that Wifi security settings are updated automatically and Chromcast doesn't really care if everything still works the same.  They are not in the business to support 3rd party media streaming.  They prefer that their services work best and others are blocked. 

See if these pages might help.
https://support.google.com/chromecast/answer/7206638?hl=en
https://www.digitaltrends.com/home-theater/common-google-chromecast-problems-and-how-to-fix-them/

Posted

I have a Linux server running Emby server and TVHeadend, I can cast my liveTV through Emby but not my film and tv-shows. I found out thoug that I could cast my film and  tv show when I choose to cast it with no subtitle and when The cast play I can put subtitle back on.

I hope it help u

/Henrik

Posted

Thanks visproduction. A couple of points.

Firstly, Emby is connecting to Chromecast on every attempt as shown by Emby's spinning circle being displayed. The problem is that Emby is failing to actually cast any selected files having connected to Chromecast.

Secondly, I'd be a little cautious, particularly in the USA, making claims that Google is blocking any other streaming service than their own.  I'm sure Google has a lot more money than you and could decide to contest your published claim.

Thanks truntemus. I've not experienced your finding and might guess it to perhaps be within Emby's on the fly or other transcoding.

Posted

Hi, there isn't any connectivity problem with the Emby Chromecast app. What you're seeing usually means that although your casting app can connect to your chromecast receiver, your chromecast receiver can't reach your emby server.

Sometimes this can be caused by https, for example, if you have configured SSL on your Emby Server and the chromecast receiver is rejecting your certificate. Other times it can be caused by vpn or reverse proxy configuration.

If you can start by providing an emby server log file, that will help tell us if any traffic at all was able to reach your server from the receiver:

Thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...