@Wolfpack - The documentation for Roku is light but it seems to imply that this message is thrown when the Roku is waiting for enough data to buffer... Unfortunately that doesn't give us much to go on.

It could be one (or more) of these issues:- The signal strength of the broadcast is bad or inconsistent- The antenna connection/strength is inconsistent- The connection between the Tablo and the router is bad or inconsistent- The connection between the router and the Roku is bad or inconsistent- The Roku is doing something unexpected - The Tablo is doing something unexpected

When I was troubleshooting my issues, I was watching the MNF on Sling and Roku 4. When I unplugged my router the game continued on for a good 10 seconds before it finally stopped. That tells me there's a good bit of caching that happens.

Also, then issue is being seen on recordings and live tv. This should take any question of signal quality off the table.

Understandable that a recorded video could be corrupted, which causes loading issues on the Roku.However, the same recording plays back fine via MS Windows 7 using Google Chrome Browser, and Android OS using the Tablo app.This implies the player apps on the latter two are handling the corruption problem without experiencing the loading issues.There's gotta be a way to do the same for the Roku app.

And it is the NATURE of the recorded file "corruption" that is throwing a monkey wrench into the Roku players that has us all mystified. If it were Network issues I doubt the disturbances would continually happen at exactly the same places during recording playback.

I have a PLEX media server on my network. Last night, I installed the Tablo channel in PLEX and watched live tv via the PLEX web interface and Tablo channel; absolutely no problems at all for hours.. well, until I passed out. lol

So, I thought, if this is a communication issue between Roku4 and Tablo, what if I were to watch content via my PLEX server? This morning I used Roku4 PLEX app to watch the Tablo channel on my PLEX server for a TV show recording I had; the issue still exists, but manifests in a different way, probably due to the PLEX server being in between. Basically, instead of getting the "Loading ... Please Wait" message, the video/audio stream freezes for a few seconds, and then continues playing. In summary:

1.) The Roku H.264 decoder is less permissive about slightly non-conforming H.264 streams as compared to other players.

Or

2.) The Roku H.264 decoder is even stricter than the H.264 spec and in fact will balk at some conforming H.264 streams that don't generate issues on other players.

In either case, it would seem that the Tablo H.264 codec is making as stream that might be on the "hairy edge" of what the Roku will play in the best of conditions, and that any networking or OTA signal quality issues might throw it over that edge.

As TabloTV rightly pointed out, Netflix, Hulu, Amazon, etc. have an inherent advantage in that they are generating their stream one time, and can do so NRT - Non Real Time - so they can make as perfect of a stream as they desire. Tablo on the other hand is generating these streams on the fly in real time - a much more difficult task.

You wonder if Tablo has made any changes in the 264 encoder in their device recently.

@TabloTVI believe it works this way for Tablo recordings...1. Tablo receives the TV broadcast stream, transcodes the stream from MPEG-2 to MPEG-4, saving the resulting MPEG-4 file on the hard drive attached to the Tablo.This transcoding process is performed once.Transcoding, by the way, just means encoding to a different format.2. At this point the recorded file is ready for playback on any Tablo supported playback device.

And, I see @TabloTV responded stating recordings are only re-encoded (transcoded) if you're watching away from your home network.