serpi 72 Posted April 6, 2018 Share Posted April 6, 2018 Hi, my wife is often using the Android App and streaming to Chromecast (first generation). This used to work without problems, but in the last time, she says, the playback now stops from time to time and she has to restart the video. I couldn't find much about problems in the log file, this is (I think) what was written, when playback stopped: 2018-04-06 20:44:58.262 Info HttpServer: HTTP Response 500 to 192.168.178.128. Time: 681611ms. http://192.168.178.25:8096/emby/Videos/3f04343dd30b344f472daeb995b4a9f5/stream.mkv?Static=true&mediaSourceId=3f04343dd30b344f472daeb995b4a9f5&deviceId=U2xlZXBDaHJvbWU1&Tag=d905851f64adafe0f90e619f2a446634 2018-04-06 20:44:58.307 Info HttpServer: HTTP POST http://192.168.178.25:8096/emby/Sessions/Playing/Stopped. UserAgent: Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.58 Safari/537.36 CrKey/1.29.104827 2018-04-06 20:44:58.309 Info SessionManager: Playback stopped reported by app Emby for Chromecast 2.1.0 playing Down By Law. Stopped at 678948 ms 2018-04-06 20:44:58.310 Info HttpServer: HTTP Response 204 to 192.168.178.128. Time: 4ms. http://192.168.178.25:8096/emby/Sessions/Playing/Stopped The video wasn't transcoded but directly played. For me, it seems, http 500 is an error? She didn't touch her phone when playback stopped, so it's sure, she didn't accidentially stop the playback. In this case, playback stopped again only a few seconds after restarting: 2018-04-06 20:46:42.176 Info HttpServer: HTTP Response 500 to 192.168.178.128. Time: 15620ms (slow). http://192.168.178.25:8096/emby/Videos/3f04343dd30b344f472daeb995b4a9f5/stream.mkv?Static=true&mediaSourceId=3f04343dd30b344f472daeb995b4a9f5&deviceId=U2xlZXBDaHJvbWU1&Tag=d905851f64adafe0f90e619f2a446634 2018-04-06 20:46:42.204 Info HttpServer: HTTP POST http://192.168.178.25:8096/emby/Sessions/Playing/Stopped. UserAgent: Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.58 Safari/537.36 CrKey/1.29.104827 2018-04-06 20:46:42.206 Info SessionManager: Playback stopped reported by app Emby for Chromecast 2.1.0 playing Down By Law. Stopped at 690946 ms 2018-04-06 20:46:42.207 Info HttpServer: HTTP Response 204 to 192.168.178.128. Time: 3ms. http://192.168.178.25:8096/emby/Sessions/Playing/Stopped And again, there's a http response 500 to Chromecast. Is this a known problem or anything I can do about it? Thanks & Ciao, Alfred Link to comment Share on other sites More sharing options...
Luke 37112 Posted April 6, 2018 Share Posted April 6, 2018 If it is direct playing then Emby is not heavily involved. This sounds network related to me. You may want to try setting the Chromecast quality setting in the casting app to a low value. This will result in more transcoding but will reduce the size of the data that has to flow through the network. I would see if this helps. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now