Welcome to our forums! Please take a few moments to read through our Community Guidelines (also conveniently linked in the header at the top of each page). There, you'll find guidelines on conduct, tips on getting the help you may be searching for, and more!

New issue - Casting to Chromecast hangs at 34 minutes into any media

thegreennatthegreennat Posts: 9Members ✭✭

Has anyone else hit this issue? I noticed it for the first time this weekend (6th May).
Basically when casting from Plex Media Server to Chromecast, the film stops playing at around the 34 minute mark.

Can anyone help fix please?

This is what I have tried so far.
Installed updates to Plex, and mac OS X sierra on 7th May, did a full restart and reboot of Chromecast but problem persists.
Plex media server served the entire Trolls film to Plex client on iPad no problem. Started 7th May 6.20ish, duration 1.5hours, finish roughly 8pm.
I then started the film again from iPad and cast it to Chromecast at 20:18. The film then hung on Chromecast at about the 34 minute point., so 20:52. Plex Media Server thinks it’s still streaming. No obvious errors in the PMS logs or on chrome cast screen.
No error messages on the TV screen.

Media Server log file attached.

System details:
Plex Media Server v1.5.5.3634 running on MacMini i7 2.3Ghz with 8Gb ram running macOs Sierra 10.12.4 with media on an external SSD. Network connection is LAN.
Chromecast firmware version 1.23.84839 country code GB
Cast initiated from ipad air 2

«13

Answers

  • richarddc79richarddc79 Posts: 186Members, Plex Pass Plex Pass

    I have just been watching a film on a Chromecast, and had to restart my Chromecast twice, and thinking back, I would say it was between 34 and 40 minute intervals, I will try some more streams tomorrow and see what happens.

    HP Laptop core i5 (Plex Server hardware transcoding)
    Lenovo M58p Core 2 Duo Windows 10 (secondary Plex Server + NAS - 4TB Movies + TV shows)
    Xbox One S
    Fire TV stick gen 2
    Fire TV stick gen 1
    Chromecast gen 2 wired ethernet x 1
    Chromecast gen 1 x 2
    iPhone 6
    iPhone 7
    iPad Mini
    iPod touch
    Fire kids tablet

  • FireHelmetFireHelmet Posts: 4Members ✭✭

    I encountered the same problem last friday

  • javerrejaverre Posts: 42Members, Plex Pass Plex Pass

    Exact same issue here, and exact same timing: 34 minutes

    Looking your logs I see the message:

    May 07, 2017 20:19:10.645 [0x70000a92d000] WARN - [Chromecast] Player: Excessive buffering detected; unknown

    which I also see in my log (and logs from other's reporting this issue) at the time when the issue occurs. I think this issue may have started when Google pushed out new Chromecast firmware 1.23.84839, as prior to that my setup worked flawlessly. Would be interested to hear from anyone running that firmware without the issue.

    The issue has been so far been confirmed on PMS 1.5.5.3634 and PMS 1.6.0.3720.

  • thegreennatthegreennat Posts: 9Members ✭✭

    Thanks for confirming. As a work around I tried casting from iPad running Plex web app client in Chrome browser, that hung too at 33 minutes. Server shows it's Direct Play. No high CPU spikes as some people have reported.
    There are a number of other threads with similar sounding symptoms.
    https://forums.plex.tv/discussion/264699/plex-1-5-and-1-5-1-with-chromecast#latest

    I'll try again tomorrow night switching audio to AC3 5.1 which seems to have resolved it for some.

    Plex devs - are you aware of the issue and is there a fix in the backlog?

  • andrew.cloud@oldutch.comandrew.cloud@oldutch.com Posts: 5Members ✭✭

    I've got the same issues and error message in my logs running Plex 1.5.5.3634 on Windows 10 and Chromecast 1.23.84839. I'm new to Plex and have actually never experienced a successful experience yet. It seriously makes me consider purchasing a Plex Pass when many people seem to have the same issue and no official word from Plex is out there that they're even aware of the issue. Plex support/developers, are you out there?

  • jtr165jtr165 Posts: 14Members ✭✭

    Just in here to confirm the exact same situation. 30 - 35 minutes into any video on my server pushed to a 2nd gen chromecast and it stutters, then hangs, and needs to be relaunched. Happens when launching from my PC browser, and both an android phone (a nexus 6) and a tablet (a pixel C)...both of which are running Android 7.1.1. PC is windows 10, and Plex server version is 1.5.5.3634. Will have to check my chromecast version, but it's definitely up to date and works flawlessly with everything else.

    The other part of this 'bug' is that time tags no longer work to the chromecas. Meaning, launching a movie/show to the chromecast starts at the beginning no matter what. I can clearly see in the app/browser that the tag is recorded, and launching prompts the 'start from xxx' and 'start from beginning'...but both result in the content starting from 0 seconds.

    I have not needed to reboot the chromecast, I can relaunch the content from any device just by tapping the cast icon, disconnecting, and connecting again. I tried rebooting several times, made no difference (my chromecast also only boots up when the TV is turned on). When the content stalls, the time tag is not recorded. If I quit out of a movie properly, it does keep the tag, but relaunching does not 'use' it.

    Everything thing i have in my library direct plays to my chromecast locally. Also worth mentioning, absolutely no issues with streaming to said devices, using the browser, or accessing content remotely (which often does transcode). They all play fine (my wife and I have been just using the tablet at night because it continues to work).

    This all started about 10 days ago. Haven't added any new content to the server since before that, and watched what was added with no issues on the chromecast before things got sour. I too will try switching audio when I can, I have both AAC stereo and passthrough AC3 5.1 on almost everything I add. I'll see what happens.

  • thegreennatthegreennat Posts: 9Members ✭✭

    I'm glad I'm not alone in facing these issues. Looks to be caused by the 1.23.84839 Chromecast firmware, but I guess we're reliant on Plex devs to fix. Any Plex developers watching this?

  • andrew.cloud@oldutch.comandrew.cloud@oldutch.com Posts: 5Members ✭✭

    I've just upgraded to Plex 1.5.6.3790 and still experience the issue.

  • BlurryBirdBlurryBird Posts: 7Members, Plex Pass Plex Pass

    Interesting, I've actually noticed this in Chrome Web App and thought it was coincidental. Annoyingly the resume doesn't work on anything for me either when using Chrome Web App which means I need to restart playing and click "resume from"

  • jtr165jtr165 Posts: 14Members ✭✭

    Can confirm for my setup that switching to anything but the default ACC stereo audio profile (that is what I have for most media in my library) works for resume. PMS transcodes back to AAC for the chromecast, but the resume functionality is working like it should.

    This also fixed the 34 minute thing, but i've only had a chance to test a single movie in person. I left a few others running while I was in and out of the room, and they finished, but can't confirm that they never paused/buffered/etc. entirely.

    What worked was Benjamin Button ripped from a BD, encoded in HB at H264 w/ a passthrough track of DTS-HD. PMS said it was transcoding audio (to AAC for the CC apparently) only. let it run for an hour + with no issues, paused, restarted, resume worked...restart PC in the middle of it, resume worked after, also. When I switched back to the AAC stereo track, which made PMS direct play it, right back to 0 seconds. Didn't sit through 30 minutes again, so can't comment on that.

    I lose interest in the technical aspects pretty quickly...but for my purposes, I can derive that either AAC direct played to the CC, or direct play in general to the CC, is part of the current problem. PMS has no issues transcoding audio into the same audio codec it's supposed to just push, on my system anyway...That's all I can tell so far.

  • thegreennatthegreennat Posts: 9Members ✭✭
    via Email
    I still haven't had chance to try out the audio fix, will try tonight.
    The other thing I want to test is cast directly from Plex Media Server to CC, although that option was greyed out the last time I looked.
  • spectre51spectre51 Posts: 9Members ✭✭
    edited May 13

    I too am experiencing this issue with the hangs and inability to resume at time tag. Have restarted chromecast, updated plex server, updated synology. I am also running the 1.23.84839 Chromecast firmware. Hoping we can figure this out.

    Can anyone shed light on the other entries in this log and what they mean?

    May 12, 2017 20:13:48.514 [0xe3e23b40] WARN - [Chromecast] Player: Excessive buffering detected; unknown
    May 12, 2017 20:13:55.632 [0xe9f35b40] WARN - [Chromecast] [MDE] Unable to validate videoResolution; re-analyze the media if possible
    May 12, 2017 20:13:55.798 [0xe9959b40] WARN - [Chromecast] [MDE] Unable to validate videoResolution; re-analyze the media if possible
    May 12, 2017 20:14:45.240 [0xf1223b40] WARN - [Chromecast] Sender disconnected. Reason: unknown. Total number of senders: 0
    May 12, 2017 20:30:23.256 [0xeca23b40] WARN - HTTP error requesting GET http://192.168.1.171:8008/ssdp/device-desc.xml (0, No error) (Empty reply from server)
    May 12, 2017 20:44:42.981 [0xe4111b40] WARN - HTTP error requesting GET http://192.168.1.170:8008/ssdp/device-desc.xml (0, No error) (Empty reply from server)
    

    Tried the audio trick listed above and indeed it fixed the resume issue. If I tried to resume and changed to AC3 it resumed fine. Tried to resume using AAC and it reset to the beginning. Resumed the same movie again using AC3 and no issue. I'll try this and see if a movie will go through and finish without hanging.

  • thegreennatthegreennat Posts: 9Members ✭✭
    via Email
    Looks like switching to audio other than AAC works for me too.

    Nathan
  • mackensenmackensen Posts: 1Members, Plex Pass Plex Pass

    I'm seeing these two issues as well. This is my setup:

    • PMS 1.5.5.3634, running on a Raspberry Pi 3
    • Media is stored on a NAS
    • Chromecast 2, firmware 1.23.84839

    I found that certain videos failed after 22 minutes, and I noted the "WARN - [Chromecast] Player: Excessive buffering detected; unknown" error in my logs when it failed. This probably started a few weeks ago. I can confirm that switching audio from AAC to AC 5.1 resolved both issues.

  • vididigi13vididigi13 Posts: 4Members, Plex Pass ✭✭

    @mackensen said:
    I'm seeing these two issues as well. This is my setup:

    • PMS 1.5.5.3634, running on a Raspberry Pi 3
    • Media is stored on a NAS
    • Chromecast 2, firmware 1.23.84839

    I have the same exact versions of PMS and Chromecast running. I also recieve the "Excessive buffering detected" in my logs that occurs around 23ish minutes of playback on a chromecast. All my media is encoded with AAC so I'm not sure I'll be able to try switching audio formats.

    Playback works great on all my mobile devices, just not the chromecast.

    This sucks.

  • crono141crono141 Posts: 6Members, Plex Pass Plex Pass

    I too am seeing this issue, and I think the problem is with direct stream in general, as jtr165 observed.

    I have customized my chromecast profile to direct stream AC3 (as chromecast supports AC3 natively as of several years ago). All my movies then are direct streamed from the server, and I experience this issue about ever 10 minutes for HD films, or every 15 for SD films. I believe something has broken with the direct stream function. Everything else I'm seeing in the thread I am also experiencing. I noticed in the OP thread that he has a repeated set of Auth and reAuth, that I am also experiencing. I'm not sure if its related or not.

    May 13, 2017 23:39:38.754 [0x7f801a7f9700] DEBUG - [Now] Updated play state for /library/metadata/67113. May 13, 2017 23:39:38.755 [0x7f801a7f9700] DEBUG - Statistics: (07s1rkcz3muu8jbm1gyn0l766r) Reporting active playback in state 2 of type 1 (scrobble: 0) for account 1 May 13, 2017 23:39:38.756 [0x7f801a7f9700] DEBUG - It took 0.0 sec to serialize a list with 0 elements. May 13, 2017 23:39:38.757 [0x7f8036fff700] DEBUG - Completed: [::ffff:192.168.1.202:37927] 200 GET /:/timeline?hasMDE=1&ratingKey=67113&key=%2Flibrary%2Fmetadata%2F67113&state=buffering&playQueueItemID=10149&time=516328&duration=6898560 (5 live) GZIP 8ms 496 bytes (pipelined: 1) May 13, 2017 23:39:40.763 [0x7f80367fe700] DEBUG - handleStreamRead code 2: End of file May 13, 2017 23:39:40.775 [0x7f8036fff700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication. May 13, 2017 23:39:40.775 [0x7f8036fff700] DEBUG - Auth: authenticated user 1 as crono141 May 13, 2017 23:39:40.775 [0x7f8036fff700] DEBUG - Auth: Came in with a super-token, authorization succeeded. May 13, 2017 23:39:40.775 [0x7f8035ffd700] DEBUG - Request: [::ffff:192.168.1.179:62953 (Allowed Network)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (5 live) GZIP Signed-in Token (crono141) May 13, 2017 23:39:40.776 [0x7f8035ffd700] DEBUG - Beginning read from two-way stream.

    master@HomeServer:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs$ tail "Plex Media Server.log"

    May 13, 2017 23:42:26.065 [0x7f8017bfe700] DEBUG - [Now] Updated play state for /library/metadata/67113. May 13, 2017 23:42:26.065 [0x7f8017bfe700] DEBUG - Statistics: (07s1rkcz3muu8jbm1gyn0l766r) Reporting active playback in state 2 of type 1 (scrobble: 0) for account 1 May 13, 2017 23:42:26.067 [0x7f8017bfe700] DEBUG - It took 0.0 sec to serialize a list with 0 elements. May 13, 2017 23:42:26.067 [0x7f8036fff700] DEBUG - Completed: [::ffff:192.168.1.202:37940] 200 GET /:/timeline?hasMDE=1&ratingKey=67113&key=%2Flibrary%2Fmetadata%2F67113&state=buffering&playQueueItemID=10149&time=516328&duration=6898560 (5 live) GZIP 8ms 496 bytes (pipelined: 1) May 13, 2017 23:42:40.862 [0x7f80367fe700] DEBUG - handleStreamRead code 2: End of file May 13, 2017 23:42:40.871 [0x7f8036fff700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication. May 13, 2017 23:42:40.871 [0x7f8036fff700] DEBUG - Auth: authenticated user 1 as crono141 May 13, 2017 23:42:40.872 [0x7f8036fff700] DEBUG - Auth: Came in with a super-token, authorization succeeded. May 13, 2017 23:42:40.872 [0x7f8017bfe700] DEBUG - Request: [::ffff:192.168.1.179:62983 (Allowed Network)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (5 live) GZIP Signed-in Token (crono141) May 13, 2017 23:42:40.872 [0x7f8017bfe700] DEBUG - Beginning read from two-way stream.

    master@HomeServer:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs$ cat "Plex Media Server.log" | grep "Excessive buffering"

    May 13, 2017 23:25:04.839 [0x7f80123ff700] WARN - [Chromecast] Player: Excessive buffering detected; unknown

    I'm also seeing a lot of

    handleStreamRead code 2: End of file

    When clearly the playback state is not at the end of file.

  • javerrejaverre Posts: 42Members, Plex Pass Plex Pass

    I'm experiencing this issue and see lots of Auth & reAuth in my logs as well, though this happens even when no content is streaming to the Chromecast so may be another issue.

    I'm not seeing the "handleStreamRead" tracing at all.

  • crono141crono141 Posts: 6Members, Plex Pass Plex Pass

    I can't be entirely sure (because I've only tested one SD film) but it seems the issue is fixed in 1.6.1. Can anyone else confirm?

  • gerozsoltgerozsolt Posts: 49Members, Plex Pass Plex Pass

    @crono141 said:
    I can't be entirely sure (because I've only tested one SD film) but it seems the issue is fixed in 1.6.1. Can anyone else confirm?

    No, it still exits.

  • gpaolo79@gmail.comgpaolo79@gmail.com Posts: 4Members

    I am running 1.5.6.3790 on my Netgear NAS and Chromecast and I have also encountered this problem after the last update. I thought it was a problem of the video I was watching, since I have observed it only with that specific file, but it was the exact behavior that you are describing here.
    Stopping and restarting lead Chromecast to crash and disconnect, then reconnecting and resuming went fine for other 30-40 minutes.

«13
Sign In or Register to comment.