Hi
On my Apple TV I get “Your connection to the server is not fast enough to stream this video. Check your Network.” It will pause every 2 or 3 minutes with this error, However if I play the same thing on my iPad while I am watching the Apple TV, the Apple TV plays the whole movie perfect.
So everything I have running on my Apple TV I have to have running on my iPad for it to work, I also have gigabit ethernet from server to Apple TV
Any ideas
Thanks
Nick
This isn’t a problem on just Apple TVs. It happens on other clients also and is a result of the newer code added for streaming brain or similar. It’s definitely only happens in later/recent releases.
I too get this message on a gigabyte connected Shield TV when direct playing files (not even that high bitrate either). Sometimes I see it pop up and then go away and other times it can result in a CANCEL/RETRY message. RETRY and it plays fine until the next time it pops up.
More often than not I see this when a video is just started and the buffer is being filled.
To me this is an overly aggressive monitoring check that is not using a long enough sample rate or simply is looking at the wrong info to base an opinion on. If they just watched the state of the buffer and only show the message when the buffer is decreasing (past a point) and never when it’s increasing this problem would go away and work correct.
Personally, I would like to be able to turn off ALL streaming brain functions since I won’t ever have a problem in my home network nor with my Internet access upload speeds. If a client buffers then it’s obvious it needs to be changed to use less bandwidth.
In any account this has been reported in many places around the forums for various clients,
Carlo
Tonight I tried to watch something on just my iPad, pauses and stops,is unwatchable, however playing the same thing on a second iPad at same time, they both work perfect. So now I just have to keep a spare iPad to play whatever I want to watch on my preferred device!
That makes no sense! Not saying you’re wrong, but it just this sounds “wacky”. 
So one device over WIFI buffers but two playing the same thing is OK?
Is one trying to DIRECT PLAY and another set to TRANSCODE?
Can you stop Plex and delete your log files.
Restart Plex and fire up the first client.
Wait 1 minute or 2 minutes (which ever is needed) and then start the 2nd client.
Play for 3 minutes or so.
Stop both players
Wait 1 minutes
Go into Settings/Server/Help and grab the ZIP file of your logs and post them?
This will help us identify the issue and gain knowledge of your situation,
Carlo
@cayars said:
This isn’t a problem on just Apple TVs. It happens on other clients also and is a result of the newer code added for streaming brain or similar. It’s definitely only happens in later/recent releases.I too get this message on a gigabyte connected Shield TV when direct playing files (not even that high bitrate either). Sometimes I see it pop up and then go away and other times it can result in a CANCEL/RETRY message. RETRY and it plays fine until the next time it pops up.
More often than not I see this when a video is just started and the buffer is being filled.
To me this is an overly aggressive monitoring check that is not using a long enough sample rate or simply is looking at the wrong info to base an opinion on. If they just watched the state of the buffer and only show the message when the buffer is decreasing (past a point) and never when it’s increasing this problem would go away and work correct.
Personally, I would like to be able to turn off ALL streaming brain functions since I won’t ever have a problem in my home network nor with my Internet access upload speeds. If a client buffers then it’s obvious it needs to be changed to use less bandwidth.
In any account this has been reported in many places around the forums for various clients,
Carlo
So you can confirm it also happens with 1.5.3? With 1.5.2 i don’t have so many problems, that’s why i’m downgraded. Again.
For me it’s the same roughly speaking. Haven’t noted an improvement or it getting worse.
I could be wrong but I think the last version this didn’t happen with was 1.3.4 (from memory).
@cayars said:
For me it’s the same roughly speaking. Haven’t noted an improvement or it getting worse.I could be wrong but I think the last version this didn’t happen with was 1.3.4 (from memory).
I’ve too noticed similar results. When setting the upload speed to 17Mb, I’ve seen 8Mb files get transcoded despite never peaking above 17Mb video or audio bitrate.
I believe Plex uses 80% of the upload setting. They figure (correctly or incorrectly) 20% overhead to account for things like high latency, lost packets, etc.
As a test try bumping it up to 20Mb and another test set to 0 (unlimited) and see if you get different results when streaming these files that presently get transcoded. Won’t hurt to try!
Carlo
@cayars said:
I believe Plex uses 80% of the upload setting. They figure (correctly or incorrectly) 20% overhead to account for things like high latency, lost packets, etc.As a test try bumping it up to 20Mb and another test set to 0 (unlimited) and see if you get different results when streaming these files that presently get transcoded. Won’t hurt to try!
Carlo
Are you talking “Limit remote stream bitrate”? Cause I had that set to Original (no limit) but se “tInternet upload speed” to 17Mb and this is where I saw issues.
That’s the screen. Internet upload speed.
On that screen try something like 20 and also 0.
Keep the Limit remote stream bitrate at Original.
I’ve had the same issue too with the last few updates. The pausing and saying the stream is not fast enough. Does this to any device. Tablet, computer, FireTV. Also it seems with each of the last 4-5 updates I have a memory leak issue. I’ve turned off optimization and every thing else I could think of. Reinstalled, rebooted, etc. I had it working fine until the recent update. I have to reboot the computer every day now. The computer is only not even 2 years old, 12 gigs RAM, fast, etc.
