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!

Are you having Stuttering/Buffering Issues? Look Here

DancherBoiDancherBoi Posts: 178Members, Plex Pass Plex Pass
edited January 2015 in Google Chromecast
It's probably your server.
 
Now before I get flamed to death, hear me out. In troubleshooting my own issues and helping others here on this forum, take a deep breath, follow these steps, and don't assume that the Plex software or the Chromecast device are to blame.
 
Let's also set something straight before we begin. Just because your Chromecast plays Netflix and YouTube fine from your Android device means only that your Chromecast is functioning properly. Think about this for a second. Google has whitelisted certain services to work with it's device, which means a certain amount of cooperation is involved, not to mention that Google owns YouTube. Those services do 1 of 2 things. They either already have the video stored in a format in which the Chromecast understands and sends it directly...or it transcodes the videos it has into the format Chromecast needs. If it does the latter, it is safe to assume that it is happening in a pooled server farm with a huge network pipe and loads of teraflops of processing power. Try to compare this to the resources you have on your NAS box...no comparison...please don't expect the same results.
 
Another misconception is this...Most of my videos play fine on my                       , why is it a problem sending to the Chromecast? There must be something wrong with the Chromecast, right? Unfortunately, as much as this may make sense, it's more likely to be something other than the Chromecast (again...probably your server). As you will see in my troubleshooting steps below, the Chromecast only plays one type of file with one type of video encoding and one type of audio encoding. It's very likely that the device you have good luck with supports many types of containers and video/audio formats. Since that is the case, Plex doesn't have to do anything to the video except send it in it's current form to the device. But since Chromecast only supports one format, it's more likely that Plex needs to transcode that file into something acceptable for Chromecast to play. Transcoding is a system intensive process, and if the server struggles to transcode, you will get buffering. Check the specs of your other devices and compare them to the Chromecast which you can find officially here...Google Chromecast Supported Media Types.
 
Below are some initial steps you can take to troubleshoot your own problems before you throw your hands up!
 
First thing's first...It's worth it! Take some time to understand your Plex Server and the Chromecast device. Understand how each works independently and what they need to do to work together. You are creating a media factory here which is nothing short of miraculous...treat it like that. Also, when this combination works correctly...it's absolutely amazing and worth the trouble you may feel you are experiencing right now.
 
Onto the troubleshooting...
 
Are you a PlexPass member? No longer required...Chromecast support is open to non-PlexPass members!
If not, you can stop here. Chromecast support is only available for PlexPass members at this time. You have to use the Plex for PlexPass version of the Android and iOS apps which require you to sign in with your PlexPass account. The paid app does not constitute you as a PlexPass member. [Please do not ask when it will be released to the general public, the Plex team never gives release dates.]
 
Old Fix:
Reboot your Chromecast. - You can do this by unplugging the USB power and replugging, or by using the Chromecast Android app and under the menu is a setting to send a soft reboot.
 
5.0GHz WiFi:
Don't...switch your Chromecast to a 2.4GHz band. There are known issues with Chromecast operability on the 5.0GHz band.
 
Can you see the Chromecast within the Chromecast Android or iOS app?
If the official app can't see it, how can Plex?
 
Can you watch the same video on your Android/iOS device?
If not, there is a bigger problem outside the scope of this troubleshooting guide. Get that working first before you try to cast.
 
Easy Fix:
Upgrade your Plex Server software and reboot.
 
Try reducing your quality settings:
Remember that the Chromecast is a WiFi only device. Let's not send it volumes of data and expect it to be able to consistently keep up. Go into the Plex app, choose settings and play with the 'Quality over local network' options. I have found 8Mbps 1080p is a nice place, but your mileage may vary depending on your router. I am using an ASUS RT-N66U running Shibby's Tomato firmware. While you are in there, make sure Direct Stream, Direct Play and Use new transcoder are all set to 'YES'. You may also want to play with the Plex Media Server Transcoder settings. I have Transcoder quality set to Automatic. You may want to try 'Prefer higher speed encoding'.
 
What kind of video are you playing?
You can't expect too much from a $35 media player. And as such, the Chromecast is built to only work with .mp4 contained videos that are encoded with H.264 video and AAC audio. Take a look at the video you are trying to play. You can find this info in Plex on the video detail page. Choose a video and press the Media Info icon (it's the round circle with an 'i' in it). First look at the Container property. Then the VIDEO > Codec. Finally the AUDIO > Codec. If they are MP4, H.264 and AAC respectively, then you should get good results out of the gate. That's because Plex is simply just sending the video file as-is to the Chromecast. If any one of those are different, then transcoding needs to take place. What is transcoding you ask? Well, Have you ever created a video on your PC or MAC before? When you have all your clips and audio in place, the very last step is what? The encoding or publishing process. Do you remember how long that process takes? It depends on the length of your movie, but it's not a short period of time. What it's doing is compressing the file, putting it into a container and making it ready for distribution to players. Well, transcoding is exactly the same, except it's simply taking one file format and converting it to another. Plex is great in that it does this for you as you watch your video. If you can imagine, this takes a bit of memory and a lot of CPU cycles. If your server can't do this fast enough, you will get stuttering/buffering...guaranteed. So what does this mean to you? If you have a decent enough server, really nothing. If you are trying to watch videos streamed from your prefabricated NAS box, then your expectations are too high. NAS devices aren't built for encoding/decoding, only simple file sharing and web serving. I host my Plex Media Server on a 13.10 Ubuntu server with an Intel Core 2 Quad Q6600 @ 2.4GHz with 4GB RAM. Refer to the Plex system requirements for more info.
 
Transcoder using too many system resources?
If you have a mixed media library (like me) you depend on Plex's built-in transcoding feature to prevent the horror which is to re-encode your entire collection. As stated in the previous step, if your file is not MP4, H.264, AAC, it will require transcoding. To check this out, start your video and look at the running processes on your server. You should see something to the tune of 'Plex Transcoder' or 'Plex New Transcoder'. How much memory and CPU is this taking up? How much memory and CPU do you have left while it's running? If it's too high, then consider upgrading your memory and/or CPU...or perhaps get a new system to run it on.
 
Check the health of your system:
If your server is not functioning properly, all kinds of weirdness can be experienced. In my personal quest for Plex/Chromecast nirvana, I went through a long period of stuttering/buffering. Turns out that the culprit was a failing root hard drive on my Ubuntu server that didn't start to report errors until a month after I started experiencing Plex to Chromecast issues. Once I replaced the drive, I was golden again. This can be extremely frustrating, but one way to rule this out is to install the Plex Server on another machine like your PC or MAC and see how it goes. Good luck with this one.
 
Check your logs:
This may be a bit daunting for some of you, but the logging provided by Plex is very robust and is indicative to what is going on. Particularly look for [Transcoder] and see what's going on. Another good indication is to do a search for 'speed =>'. This will give some value that tells you how the transcoder is keeping up. If this value is less than 1.0, you are pretty screwed and it's time to upgrade your server or maybe just limit the activity this server is responsible for (turn off that Left4Dead2 Steam Server!). A value here of 2.0 means that the transcoder is encoding at twice the speed of realtime playback. Anything over 1.5 is good, under 1.0 is bad.
 
Hit the forums:
If you have tried all of the above, it's time to beg for help. Luckily the forums are frequented by folks like me and the Plex support team to lend you a hand.
 
***Update*** 3/27/2014
 
Turn off AES encryption on your WiFi router:
Thanks to mdr76 for this one (if that's your 'real' name). This is another thing to try. I personal use AES encryption over WPA2 security and all 4 of my Chromecasts work fine all over my house (router is in the downstairs family room, CC next to it, another in the adjacent garage, another in a bedroom directly above, and the last in a bedroom on the second floor on the other side of the house), but at least one user has indicated that stuttering has been remedied by turning off AES encryption. Turn security completely off first and see how it goes, then try to enable TKIP encryption.
«13456710

Comments

  • AsphyxNYCAsphyxNYC Posts: 1,347Members, Plex Pass Plex Pass

    This should get Pinned for the newcomers!

  • jsdecker10jsdecker10 Posts: 27Members, Plex Pass Plex Pass
    AsphyxNYC wrote on January 25 2014, 4:21 AM: »

    This should get Pinned for the newcomers!

    Good call, Asphyx!  This is an excellent write-up and it reminds me a lot of bhiga's "FAQ" thread on XDA.  Oh, btw, I was gonna ask you earlier on the XDA Chromecast forum if you were AsphyxNYC on the PlexPass forums, but I got busy around the house and never got around to it.  Good to see a name on here that I recognize from XDA and I know that when I read a post of yours that it's gonna be very accurate and informative!  XDA needs a few more like you on there!

  • AsphyxNYCAsphyxNYC Posts: 1,347Members, Plex Pass Plex Pass
    jsdecker10 wrote on January 25 2014, 8:37 AM: »

    Good call, Asphyx!  This is an excellent write-up and it reminds me a lot of bhiga's "FAQ" thread on XDA.  Oh, btw, I was gonna ask you earlier on the XDA Chromecast forum if you were AsphyxNYC on the PlexPass forums, but I got busy around the house and never got around to it.  Good to see a name on here that I recognize from XDA and I know that when I read a post of yours that it's gonna be very accurate and informative!  XDA needs a few more like you on there!

    LOL and Thanks...Yes I'm the same Schlub from XDA! LOL

    There are a ton of smart folks over at XDA (and here as well) I just happen to work in Broadcasting on the engineering side so the CCast and Plex stuff is right up my alley which is why I have been active on both sites regarding the CCast.

  • zerolim1tzerolim1t Posts: 390Members, Plex Pass Plex Pass
    edited January 2014

    ChromeCast doesn't support 5.0ghz

    https://support.google.com/chromecast/answer/3046409?hl=en

    Chromecast Specs:

    • Output: HDMI, CEC (Consumer Electronics Control) compatible
    • Max. Output Video Resolution: 1080p
    • Dimensions: 72(L) x 35(W) x 12(H) mm
    • Weight: 34g
    • Wireless Standards: 802.11b/g/n Wi-Fi (802.11n 2.4GHz only)
    • Wireless Security: WEP, WPA/WPA2
    • Power: USB (USB cable and power adapter included)
    • Plugs into TV directly and powered from TVs USB port or wall outlet
    • Media Center
    • ZeroFlixs.com
    • i5 System 16gigs ram 50 TB 
    • Movies | Tv Shows | Boxing | UFC | Stand-up | Documentaries | Broadway |
  • cjpasulacjpasula Posts: 53Members, Plex Pass Plex Pass

    This is exactly the issue that I'm experiencing myself.  Videos play fine on my PC through the web client or my phone but are stuttering on the Chromecast.  Thanks for the post, it's pretty much the same process I'm going through right now (finding out what the issue is, is it the Chromecast, network, server, media file, etc.).

    You mention to check your logs and to look for a speed entry.  Where are these logs stored?  I've checked the upstart logs (/var/log/upstart) as well as the plex logs (/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/) and grep'd for speed but have had no results.

  • stiblstibl Posts: 19Members, Plex Pass Plex Pass
    edited January 2014

    I've been having issues with the playback in plex/web and streaming to the CC. I've been over pretty much everything you mention but hadn't looked at the logs, so gave it a shot. 

    The transcoding is at 2.0 in speed, but then goes down to 0.0 a couple of times, then back up to 2.0 and so on. Any ideas as to why? Shouldn't my i7 be able to handle a single stream that's being transcoded?

    (If this is the wrong place to ask, please direct me towards the right forum!)

  • DancherBoiDancherBoi Posts: 178Members, Plex Pass Plex Pass
    cjpasula wrote on January 27 2014, 5:12 PM: »

    You mention to check your logs and to look for a speed entry.  Where are these logs stored?  I've checked the upstart logs (/var/log/upstart) as well as the plex logs (/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/) and grep'd for speed but have had no results.

    The plex logs as you mention in the latter. Make sure you have debug logging turned on. It's found under the General settings, but you have to be showing the Advanced Settings. 'Plex Media Server debug logging' is the precise setting you are looking for. Restart Plex and try again.

  • DancherBoiDancherBoi Posts: 178Members, Plex Pass Plex Pass
    stibl wrote on January 27 2014, 9:33 PM: »

    The transcoding is at 2.0 in speed, but then goes down to 0.0 a couple of times, then back up to 2.0 and so on. Any ideas as to why? Shouldn't my i7 be able to handle a single stream that's being transcoded?

    Ya...I would think any i7 would be able to handle a single transcoding session. Try again and see what your CPU and memory usage is while that is going on. The fact that it dips to 0 is concerning and may or may not indicate a buffering problem. If the transcoding is happening twice as fast as playback, you would think that a couple of dips down wouldn't cause stuttering playback since the transcoder is getting ahead of the playback. But one thing I do know is that the transcoder doesn't just keep going waaaay ahead of playback. You can see in the log '[Transcoder] Throttle - Going into sloth mode.' which means the transcoder pauses and waits for the playback to catch up some.

  • rsavarsava Posts: 2,739Members, Plex Pass Plex Pass

    One suggestion for an edit:

    Are you a PlexPass member?
    If not, you can stop here. Chromecast support is only available for PlexPass members at this time. You have to use the Plex for PlexPass version of the Android and iOS apps which require you to sign in with your PlexPass account. The paid app does not constitute you as a PlexPass member. [Please do not ask when it will be released to the general public, the Plex team never gives release dates.]

    Can probably be removed.

    If they are not a PlexPass member they can't see this post.

    R Sava

  • stiblstibl Posts: 19Members, Plex Pass Plex Pass
    DancherBoi wrote on January 27 2014, 9:46 PM: »

    Ya...I would think any i7 would be able to handle a single transcoding session. Try again and see what your CPU and memory usage is while that is going on. The fact that it dips to 0 is concerning and may or may not indicate a buffering problem. If the transcoding is happening twice as fast as playback, you would think that a couple of dips down wouldn't cause stuttering playback since the transcoder is getting ahead of the playback. But one thing I do know is that the transcoder doesn't just keep going waaaay ahead of playback. You can see in the log '[Transcoder] Throttle - Going into sloth mode.' which means the transcoder pauses and waits for the playback to catch up some.

    Well my cpu falls down to about 2-5% when this happens and I have plenty of free ram. Looked at the log, but nowhere does it say anything about throttle or sloth mode. Here's a copy of some of the log if it helps.

    Jan 27, 2014 21:57:11:862 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.4&remaining=446308 [::ffff:127.0.0.1:55159] (3 live)
    Jan 27, 2014 21:57:11:862 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:11:862 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:11:862 [6240] DEBUG -  * speed => 2.4
    Jan 27, 2014 21:57:11:862 [6240] DEBUG -  * remaining => 446308
    Jan 27, 2014 21:57:11:866 [6240] DEBUG - HLS segment range: 160 - 169 average bitrate: 4.51 Mbps
    Jan 27, 2014 21:57:11:866 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 169.
    Jan 27, 2014 21:57:11:866 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:11:866 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.4&remaining=446308: 2200
    Jan 27, 2014 21:57:11:866 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.4&remaining=446308, 0 bytes in 4025ms
    Jan 27, 2014 21:57:13:863 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453827 [::ffff:127.0.0.1:55166] (3 live)
    Jan 27, 2014 21:57:13:863 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:13:863 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:13:863 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:13:864 [8048] DEBUG -  * remaining => 453827
    Jan 27, 2014 21:57:13:866 [8048] DEBUG - HLS segment range: 160 - 169 average bitrate: 4.51 Mbps
    Jan 27, 2014 21:57:13:866 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 169.
    Jan 27, 2014 21:57:13:866 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:13:866 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453827: 2200
    Jan 27, 2014 21:57:13:866 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453827, 0 bytes in 4009ms
    Jan 27, 2014 21:57:14:874 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55172] (3 live)
    Jan 27, 2014 21:57:14:874 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:14:874 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:14:874 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:14:874 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:14:876 [6240] DEBUG - HLS segment range: 160 - 169 average bitrate: 4.51 Mbps
    Jan 27, 2014 21:57:14:876 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 169.
    Jan 27, 2014 21:57:14:877 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:14:877 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:14:877 [8572] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 3011ms
    Jan 27, 2014 21:57:17:875 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.4&remaining=-1 [::ffff:127.0.0.1:55176] (3 live)
    Jan 27, 2014 21:57:17:875 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:17:875 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:17:875 [8048] DEBUG -  * speed => 2.4
    Jan 27, 2014 21:57:17:875 [8048] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:17:879 [8048] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:17:879 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:17:879 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:17:880 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.4&remaining=-1, 0 bytes in 4009ms
    Jan 27, 2014 21:57:17:880 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.4&remaining=-1: 2200
    Jan 27, 2014 21:57:19:878 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55182] (3 live)
    Jan 27, 2014 21:57:19:878 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:19:878 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:19:878 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:19:878 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:19:881 [6240] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:19:881 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:19:881 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:19:881 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:19:881 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 3994ms
    Jan 27, 2014 21:57:21:879 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55188] (3 live)
    Jan 27, 2014 21:57:21:879 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:21:879 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:21:879 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:21:879 [8048] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:21:882 [8048] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:21:882 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:21:882 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:21:882 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:21:882 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 4009ms
    Jan 27, 2014 21:57:23:880 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55191] (3 live)
    Jan 27, 2014 21:57:23:880 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:23:880 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:23:880 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:23:880 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:23:883 [6240] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:23:883 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:23:883 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:23:883 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:23:883 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 4009ms
    Jan 27, 2014 21:57:25:881 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55199] (3 live)
    Jan 27, 2014 21:57:25:881 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:25:881 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:25:881 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:25:881 [8048] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:25:884 [8048] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:25:884 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:25:884 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:25:884 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:25:884 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 3994ms
    Jan 27, 2014 21:57:27:882 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55208] (3 live)
    Jan 27, 2014 21:57:27:882 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:27:882 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:27:882 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:27:883 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:27:885 [6240] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:27:885 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:27:885 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:27:885 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:27:885 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 4009ms
    Jan 27, 2014 21:57:28:883 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55212] (3 live)
    Jan 27, 2014 21:57:28:883 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:28:883 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:28:883 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:28:883 [8048] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:28:885 [8048] DEBUG - HLS segment range: 160 - 170 average bitrate: 4.57 Mbps
    Jan 27, 2014 21:57:28:886 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 170.
    Jan 27, 2014 21:57:28:886 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:28:886 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:28:886 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 3011ms
    Jan 27, 2014 21:57:31:883 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.5&remaining=-1 [::ffff:127.0.0.1:55227] (3 live)
    Jan 27, 2014 21:57:31:883 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:31:883 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:31:883 [6240] DEBUG -  * speed => 2.5
    Jan 27, 2014 21:57:31:883 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:31:887 [6240] DEBUG - HLS segment range: 160 - 171 average bitrate: 4.65 Mbps
    Jan 27, 2014 21:57:31:887 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 171.
    Jan 27, 2014 21:57:31:887 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:31:887 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.5&remaining=-1: 2200
    Jan 27, 2014 21:57:31:887 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.5&remaining=-1, 0 bytes in 4009ms
    Jan 27, 2014 21:57:33:885 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453324 [::ffff:127.0.0.1:55232] (3 live)
    Jan 27, 2014 21:57:33:885 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:33:885 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:33:885 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:33:885 [8048] DEBUG -  * remaining => 453324
    Jan 27, 2014 21:57:33:888 [8048] DEBUG - HLS segment range: 160 - 171 average bitrate: 4.65 Mbps
    Jan 27, 2014 21:57:33:888 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 171.
    Jan 27, 2014 21:57:33:888 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:33:888 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453324: 2200
    Jan 27, 2014 21:57:33:888 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453324, 0 bytes in 3994ms
    Jan 27, 2014 21:57:35:886 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55239] (3 live)
    Jan 27, 2014 21:57:35:886 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:35:886 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:35:886 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:35:886 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:35:889 [6240] DEBUG - HLS segment range: 160 - 171 average bitrate: 4.65 Mbps
    Jan 27, 2014 21:57:35:889 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 171.
    Jan 27, 2014 21:57:35:889 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:35:889 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:35:889 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 4009ms
    Jan 27, 2014 21:57:36:887 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55256] (3 live)
    Jan 27, 2014 21:57:36:887 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:36:887 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:36:887 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:36:887 [8048] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:36:890 [8048] DEBUG - HLS segment range: 160 - 171 average bitrate: 4.65 Mbps
    Jan 27, 2014 21:57:36:890 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 171.
    Jan 27, 2014 21:57:36:890 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:36:890 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:36:890 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 3011ms
    Jan 27, 2014 21:57:39:891 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.3&remaining=446389 [::ffff:127.0.0.1:55278] (3 live)
    Jan 27, 2014 21:57:39:891 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:39:891 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:39:891 [6240] DEBUG -  * speed => 2.3
    Jan 27, 2014 21:57:39:892 [6240] DEBUG -  * remaining => 446389
    Jan 27, 2014 21:57:39:895 [6240] DEBUG - HLS segment range: 160 - 172 average bitrate: 4.71 Mbps
    Jan 27, 2014 21:57:39:895 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 172.
    Jan 27, 2014 21:57:39:895 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:39:895 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.3&remaining=446389: 2200
    Jan 27, 2014 21:57:39:896 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.3&remaining=446389, 0 bytes in 4009ms
    Jan 27, 2014 21:57:41:892 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453435 [::ffff:127.0.0.1:55282] (3 live)
    Jan 27, 2014 21:57:41:892 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:41:892 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:41:892 [8048] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:41:892 [8048] DEBUG -  * remaining => 453435
    Jan 27, 2014 21:57:41:895 [8048] DEBUG - HLS segment range: 160 - 172 average bitrate: 4.71 Mbps
    Jan 27, 2014 21:57:41:895 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 172.
    Jan 27, 2014 21:57:41:895 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:41:895 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453435: 2200
    Jan 27, 2014 21:57:41:895 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453435, 0 bytes in 4009ms
    Jan 27, 2014 21:57:42:892 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1 [::ffff:127.0.0.1:55288] (3 live)
    Jan 27, 2014 21:57:42:892 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:42:892 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:42:892 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:42:892 [6240] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:42:895 [6240] DEBUG - HLS segment range: 160 - 172 average bitrate: 4.71 Mbps
    Jan 27, 2014 21:57:42:895 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 172.
    Jan 27, 2014 21:57:42:895 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:42:895 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1: 2200
    Jan 27, 2014 21:57:42:895 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=-1, 0 bytes in 3011ms
    Jan 27, 2014 21:57:44:904 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.5&remaining=-1 [::ffff:127.0.0.1:55299] (3 live)
    Jan 27, 2014 21:57:44:904 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:44:904 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:44:904 [8048] DEBUG -  * speed => 2.5
    Jan 27, 2014 21:57:44:905 [8048] DEBUG -  * remaining => -1
    Jan 27, 2014 21:57:44:908 [8048] DEBUG - HLS segment range: 160 - 173 average bitrate: 4.75 Mbps
    Jan 27, 2014 21:57:44:908 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 173.
    Jan 27, 2014 21:57:44:908 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:44:908 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.5&remaining=-1: 2200
    Jan 27, 2014 21:57:44:909 [8572] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.5&remaining=-1, 0 bytes in 3026ms
    Jan 27, 2014 21:57:46:901 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.2&remaining=4051 [::ffff:127.0.0.1:55311] (4 live)
    Jan 27, 2014 21:57:46:901 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:46:901 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:46:901 [6240] DEBUG -  * speed => 2.2
    Jan 27, 2014 21:57:46:901 [6240] DEBUG -  * remaining => 4051
    Jan 27, 2014 21:57:46:905 [6240] DEBUG - HLS segment range: 160 - 174 average bitrate: 4.76 Mbps
    Jan 27, 2014 21:57:46:906 [6240] DEBUG - We want 240 segments ahead, last returned was 164 and max is 174.
    Jan 27, 2014 21:57:46:906 [6240] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:46:906 [6240] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.2&remaining=4051: 2200
    Jan 27, 2014 21:57:46:906 [8572] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.2&remaining=4051, 0 bytes in 3011ms
    Jan 27, 2014 21:57:49:906 [8048] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.1&remaining=4412 [::ffff:127.0.0.1:55321] (4 live)
    Jan 27, 2014 21:57:49:906 [8048] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:49:906 [8048] DEBUG -  * size => -22
    Jan 27, 2014 21:57:49:906 [8048] DEBUG -  * speed => 2.1
    Jan 27, 2014 21:57:49:906 [8048] DEBUG -  * remaining => 4412
    Jan 27, 2014 21:57:49:910 [8048] DEBUG - HLS segment range: 160 - 175 average bitrate: 4.83 Mbps
    Jan 27, 2014 21:57:49:910 [8048] DEBUG - We want 240 segments ahead, last returned was 164 and max is 175.
    Jan 27, 2014 21:57:49:910 [8048] DEBUG - It took 0.000000 sec to serialize a list with 0 elements.
    Jan 27, 2014 21:57:49:911 [8048] VERBOSE - Completed request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.1&remaining=4412: 2200
    Jan 27, 2014 21:57:49:911 [9168] VERBOSE - Finished writing response for PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=2.1&remaining=4412, 0 bytes in 4009ms
    Jan 27, 2014 21:57:51:908 [6240] DEBUG - Request: PUT /video/:/transcode/session/51ua4top6jqq6w29/progress?progress=0.0&size=-22&speed=0.0&remaining=453681 [::ffff:127.0.0.1:55330] (3 live)
    Jan 27, 2014 21:57:51:908 [6240] DEBUG -  * progress => 0.0
    Jan 27, 2014 21:57:51:908 [6240] DEBUG -  * size => -22
    Jan 27, 2014 21:57:51:908 [6240] DEBUG -  * speed => 0.0
    Jan 27, 2014 21:57:51:908 [6240] DEBUG -  * remaining => 453681
    
  • derekrossderekross Posts: 29Members, Plex Pass Plex Pass
    edited February 2014

    Out of nowhere yesterday and today I started having stuttering issues on some videos and I am not sure why. I haven't changed anything. The videos seem to both be MKV files. They play fine on my computer, Plex web, and Android phone/tablet. I doubt it's my server seeing as my computer is sitting at single digit CPU while streaming and with under 40% memory utilization. I factory reset my Chromecast too. I would test on another Chromecast but my wife is sleeping now :P

    Edit: So I tested on another Chromecast today, same thing. Stuttering on videos that previously didn't stutter.

    Any thoughts? My log file says my speed is either 6, 8, or 11.

  • DaveELDaveEL Posts: 6Members, Plex Pass Plex Pass
    edited February 2014

    I just fixed some issues i was having with streaming. I was trying to playback some mkv/h.264@720p/ac3 files the cpu in my NAS could not keep up as it was trying to transcode the video rather than just the audio. Checking the logs showed an exceeded bandwidth limitation as the reason for the transcode and indicated the limit was 4mbps (my video was ~4.4). I checked my player settings and had no such limitation. However it looks like the Chromecast.xml profile has bandwidth limits for transcoded video set to 4000 i bumped this up to 8000 and it streams fine now. I couldn't find any documentation to specify what the actual device limit is.

    I did also notice that the VideoCodec limitations indicate 1080p but the VideoTranscodeTarget limits are only 720p. I think this may cause unnecessary transcoding of 1080p video tracks if the transcoder is invoked for the audio track?

  • DancherBoiDancherBoi Posts: 178Members, Plex Pass Plex Pass
    edited February 2014
    DaveEL wrote on February 19 2014, 9:19 AM: »

    I did also notice that the VideoCodec limitations indicate 1080p but the VideoTranscodeTarget limits are only 720p. I think this may cause unnecessary transcoding of 1080p video tracks if the transcoder is invoked for the audio track?

    Plex has introduced a forced downward transcode from 1080p to 720p based on their testing of Chromecast's lack of ability to handle the 1080p stream from Plex. I think they are working on efficiencies to try and remove this limitation.

  • Chris CChris C Posts: 11,810Members, Plex Employee, Plex Pass, Plex Ninja Plex Employee

    The limitations in the XML profile are there for a reason based on extensive testing. Folks can, of course, always edit theirs, but we do not recommend doing so.

    There's definitely a lot of work being done for Chromecast stuff right now. Recent Plex Pass preview release PMS builds have included improvements. You can expect more improvements to come in the future.

    Need help? Having trouble?
    » Visit our Support Site for documentation, guides, and more - including the Getting Started section!
    » Attach Log Files when reporting issues // See how to attach files in the forums
    » Name and Organize your content correctly for best results

    (no private messages for support unless requested, please)

  • DaveELDaveEL Posts: 6Members, Plex Pass Plex Pass

    Yeah i've since had a few issues with others files at much higher bitrates. It looks like the file i originally had an issue with is ok as it's only just above 4mbps but when i tried on something more like a 7mbps file the chromecast chokes every few minutes, I only set it to 8 as that was the bitrate recommended in the first post. Looks like my shiny new chromecast is going to sit in a draw with all my other redundant gadgets at least for a while and i'll have to go back to LG medialink for now.

  • rcombsrcombs Transcoder Engineer Posts: 360Members, Plex Employee, Plex Pass, Plex Ninja Plex Employee
    edited February 2014

    Please try out the latest version of Plex Media Server (0.9.9.5). Quality and reliability on Chromecast should be significantly improved.

  • derekrossderekross Posts: 29Members, Plex Pass Plex Pass
    edited February 2014
    Rodger Combs wrote on February 25 2014, 3:00 PM: »

    Please try out the latest version of Plex Media Server (0.9.9.5). Quality and reliability on Chromecast should be significantly improved.

    No improvement here. Video is stuttering to the point where even my kids didn't want to watch their movie. MKV. Bitrate: 5150kpbs. h264 video codec. DCA audio codec. Edit: here's a pastebin of the log when it was skipping. http://pastebin.com/S5EdFwxE

  • ludicrous_larryludicrous_larry Posts: 5Members, Plex Pass Plex Pass
    edited March 2014
    derekross wrote on February 28 2014, 12:02 AM: »

    No improvement here. Video is stuttering to the point where even my kids didn't want to watch their movie. MKV. Bitrate: 5150kpbs. h264 video codec. DCA audio codec. Edit: here's a pastebin of the log when it was skipping. http://pastebin.com/S5EdFwxE

     Add me to the list that 0.9.9.5  did not improve/fix the problem.  

    Here are my details:

    I am running the latest version of Plex Media Server for the Mac (Version 0.9.9.5.411-da1d892) on a Macbook Pro running the latest version of OSX (10.9.1) with 4gb of RAM and having the same issue with Chromecast.  My router is < 1m from the Chromecast and not on a clobbered channel.  I am running 720p mkv files that work fine when I run them on my iPad or iPhone and then send them to my AppleTV using Airplay. Why would it be able to transcode just fine for the Apple and not for Google Chromecast if it is transcoding them both into mp4?  Not sure the general statement in the original post pertains.  Apple is pretty notorious for only accepting mp4 --- which is what led me to Plex in the first place.

     

    This seems to be an issue with Chromecast or the Plex to Chromecast interface.  Any tekkies out there know enough about Chromecast Plex app's internal workings to speculate?  

     

    I figured I'd save some cash by not buying another AppleTv but rather a Chromecast for my other tv.   Looks like a bad investment as of 03 March 2014.

  • DancherBoiDancherBoi Posts: 178Members, Plex Pass Plex Pass
    ludicrous_larry wrote on March 4 2014, 4:37 AM: »

     Add me to the list that 0.9.9.5  did not improve/fix the problem.  

    Here are my details:

    I am running the latest version of Plex Media Server for the Mac (Version 0.9.9.5.411-da1d892) on a Macbook Pro running the latest version of OSX (10.9.1) with 4gb of RAM and having the same issue with Chromecast.  My router is < 1m from the Chromecast and not on a clobbered channel.  I am running 720p mkv files that work fine when I run them on my iPad or iPhone and then send them to my AppleTV using Airplay. Why would it be able to transcode just fine for the Apple and not for Google Chromecast if it is transcoding them both into mp4?  Not sure the general statement in the original post pertains.  Apple is pretty notorious for only accepting mp4 --- which is what led me to Plex in the first place.

     

    This seems to be an issue with Chromecast or the Plex to Chromecast interface.  Any tekkies out there know enough about Chromecast Plex app's internal workings to speculate?  

     

    I figured I'd save some cash by not buying another AppleTv but rather a Chromecast for my other tv.   Looks like a bad investment as of 03 March 2014.

    We need logs in order to help you. Also, the container and encoding details of the files you are trying to play are required too.

  • ludicrous_larryludicrous_larry Posts: 5Members, Plex Pass Plex Pass

    DancherBoi,

      Thanks for taking the time to respond.  I was a bit upset last night after the new version of media server did not resolve  the issue.  Here is the additional data...

    -Log: http://pastebin.com/zvz7NfXj

    -Codec/media info is:

     General
    Format : Matroska
    Format version : Version 4 / Version 2
    File size : 1.37 GiB
    Duration : 42mn 26s
    Overall bit rate : 4 615 Kbps
    Encoded date : UTC 2014-02-18 09:49:42
    Writing application : mkvmerge v6.2.0 ('Promised Land') built on Apr 28 2013 08:01:15
    Writing library : libebml v1.3.0 + libmatroska v1.4.0
     
     Video
    ID : 1
    Format : AVC
    Format/Info : Advanced Video Codec
    Format profile : High@L4.1
    Format settings, CABAC : Yes
    Format settings, ReFrames : 5 frames
    Codec ID : V_MPEG4/ISO/AVC
    Duration : 42mn 26s
    Bit rate : 4 139 Kbps
    Width : 1 280 pixels
    Height : 720 pixels
    Display aspect ratio : 16:9
    Frame rate mode : Constant
    Frame rate : 23.976 fps
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive
    Bits/(Pixel*Frame) : 0.187
    Stream size : 1.23 GiB (90%)
    Writing library : x264 core 140 r2377 1ca7bb9
    Encoding settings : cabac=1 / ref=5 / deblock=1:0:0 / analyse=0x3:0x113 / me=umh / subme=8 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=crf / mbtree=1 / crf=18.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
    Language : English
    Default : Yes
    Forced : No
    Matrix coefficients : BT.709
     
     Audio
    ID : 2
    Format : AC-3
    Format/Info : Audio Coding 3
    Mode extension : CM (complete main)
    Format settings, Endianness : Big
    Codec ID : A_AC3
    Duration : 42mn 26s
    Bit rate mode : Constant
    Bit rate : 384 Kbps
    Channel(s) : 6 channels
    Channel positions : Front: L C R, Side: L R, LFE
    Sampling rate : 48.0 KHz
    Bit depth : 16 bits
    Compression mode : Lossy
    Stream size : 117 MiB (8%)
    Default : Yes
    Forced : No
«13456710
Sign In or Register to comment.