Comparing streaming only services to an OTA solution isn’t really an apples to apples comparison since I would guess most of those services aren’t starting with MPEG2 content as the source content. I’m not arguing the reality issues that still need to be addressed by Tablo, just the comparison.
2 Likes
I agree…
It’s mostly client to client transfer. From what I can see on my network, it runs about 9-15mbps (give or take) while active (non-fast traffic).
It looks like when you open the tablo APP… the tablo reaches out to:
api.tablotv.com
lighthousetv.ewscloud.com
cdn-uw2-prod.tsv2.amagi.tv
It hits other sites when the fast channels are accessed too.
I’m sure this is some guide data, TV channel data. Small amounts of data (excluding the FAST channels, again) Blah blah blah.
When you hit that play button on a recorded show/movie and or live OTA TV… there is a straight client to client data there. It ramps up quickly. At that moment, very little data is being pulled from the net. (mentioned above).
3 Likes
After further use of the Tablo App after the Roku 12.5.5 update on my Roku Ultra 4802X, I’m still getting the “Shutdown to Roku Home Screen” events. I also had one “Tablo Video Freezes and reboots Roku” problem happen again too. So problems are still there.
After reading work arounds others have posted, I’ve deleted the Tablo App, rebooted the Roku and re-installed the Tablo App. I’ll also try the pause Live TV for 30 seconds trick too.
The more I thought about this… My ultra gave me app closing issue. But last night it didn’t. I wonder if it crashes when the data isn’t finished loading, and you try to stream too quickly?
Some type of payload error and it bombs.
My wife mentioned that it crashed on her the other day, when she went to “quickly” through the menus. Last night she “gently” took her time through the menus and all, and had no issues.
Just a thought.
1 Like
I’m a new customer, approximately a month now. I don’t see any real progress on Tablo crashes, especially when you select live TV via the Guide.
@TabloSupport when is this going to be fixed? I haven’t seen much improvement in the last month.
I think you have the potential for a great product, but these crashes must be fixed!! How about some updates on this situation?
Found this in the reviews of the gen 4.
Seems Nuvyyo’s developers did not read the specs for Rokus.
https://developer.roku.com/docs/specs/hardware.md
Thanks for that info. That could be very helpful. I have an older Roku stick, but I also have a newer one installed on a different TV. If I can swap it out to the newer one (without much trouble), I may give that a try.
Don’t get too excited, my brand new Roku Ultra has the same problem: While watching Live OTA TV after some seemingly random amount of time Tablo app apparently crashes and I’m back at Roku Home Screen.
1 Like
Thanks for that info Jim. I was hoping we were on to something in that a newer Roku might solve the problem.
What say you @TabloSupport ?? We need feedback and progress updates please.
I have the very latest Roku Ultra, recently purchased and it still happens to me. I just use the pause for 15 seconds trick and it works fine for live OTA tv.
@Jim_Lau Yes, the pause work-around works! Just tested this on my new Roku Ultra.
Began viewing LIVE OTA TV channel (local NBC station), almost immediately paused for maybe 30 seconds then unpaused. Watched same channel for 2+ hours perfectly WITHOUT Roku Tablo app crashing, being thrown back to Roku Home Screen or Tablo guide/grid.
This is not a fix but it is a work-around that actually seems to work.
3 Likes
@jman4531, I don’t understand what you did. The pause “work-around”? You paused for 30 secs then unpaused? I appreciate the info, but how does this ‘fix’ the Live TV crashing? I don’t want to do these steps anytime Tablo crashes. They need to fix this entire issue and now!
It doesn’t fix the problem. It’s a temporary fix until Tablo gets the app problem resolved. The pause will prevent the crash so it won’t crash after 10 minutes. You should be able to watch for at least 2 hours or so.
@Buzz56 That’s right, on the Tablo app on my Roku Ultra, I tuned to the OTA channel I wanted to watch, hit pause, waited 30 seconds then resumed. I was then able to watch that channel for 2+ hours without experiencing the Tablo app crashing and taking me back to the Roku Home Screen.
AFTER 2+ hours of uninterrupted, successful and satisfying viewing, I decided to shut off the TV and go read a book 
I also don’t want to do this EVERYTIME I watch Live OTA TV but this is a work-around that works for me for now.
Hopefully Tablo gets its Roku act together and we get an update that addresses this bug and other Roku Tablo issues.
2 Likes
I am one of the fortunate people who never experienced some of the problems with Roku, even my older models. The pause work-around reminds me of an issue that I ran into many, many, many years ago.
Even though you are watching a live program, you are not really watching a live program. You are actually watching the data played from the storage. The ability to pause and rewind a program can only be accomplished if you are watching playback from the disk. You can pause a program, run to the store and get some beer, come back and resume watching at the point where you paused it. You can even rewind it back to a part that you remember before leaving. This is possible because the program doesn’t go directly to the TV but is recorded to the disk. What you watch is a recording as playback.
What I found years ago is that pulling data from the disk as soon as it is written causes buffering issues, buffer under-run. It’s cured by actually putting in a delay before reading data from the disk. That keeps us from draining the buffers while they are filling up.
Buffer locations:
The TV
The Roku
The Tablo
The disk storage
Buffers are everywhere. Any of the buffers could be the problem.
If, and it’s a big if, buffering is the problem then the programmers at Tablo can solve it by just putting in a delay that’s long enough to cover spinup time, etc…
5 Likes
No the older Roku Express + has both a composite and HDMI connection.
Roku product naming could be an Abbott and Costello routine.
“What do you have?”
A roku 2.
“So a 2nd gen Roku?”
No a 2.
“Not the 1st gen?”
No, a 3rd gen.
“Why not buy a 1?”
Better features with the 2.
“That and it’s second gen, right?”
Not, it’s 3rd gen.
“So, better than the 1, a first gen device?”
No, the 1 is 3rd gen.
“What is a first gen Roku called?”
A Roku.
“So, what did they call 2nd gen?”
Roku XS, XD…
“The high end being the XD?”
No, the high end being the XS.
“But 2nd gen?”
Correct.
“And the 1 and 2 are 3rd gen?”
Correct.
“What’s the high end of the 3rd gen called?”
The 3.
“But your 3rd gen Roku 2 is no longer supported.”
Correct, but the 3 is.
“What’s the high end of the 4th gen called?”
Roku 4.
“So you’d buy that instead of a 4th gen 1, 2 or 3?”
There was no 1, 2 or 3, just the 4.
“But at least it’s still supported.”
No, the Roku 4 is no longer supported.
“Because it’s 4th gen?”
Correct.
“What is the highest end of the 5th gen called?”
The Ultra.
“What about 6th gen?”
The Ultra
“So, there was no 6th gen?”
No, it’s a 6th gen Ultra.
“What about 7th gen on the high end?”
The Ultra
“So, you want to get a 7th gen Ultra?”
Well, no, you’d want the 9th gen Ultra.
“The latest generation.”
No, the latest is 10th gen.
“Roku 2 (sigh)”
6 Likes
Anyone else having problems getting the 4th Gen Tablo to work with a Roku Express + connected via the composite connection on an older pre hdmi TV? I get a spinning circle then channel info then the screen freezes and Roku reboots. I’ve tried using a HDMI to composite converter and get the same results.
The Tablo App gives you the spinning circles?
If so, I dont think the video cables or how the Roku is physically connected to your TV relates to the spinning circles from the Tablo APP.
Lets get more deets about your setup? Roku and your Tablo Wirelessly connected?
@TabloSupport can you give us an update and ETA on fixing the problem of Tablo crashes, especially when you select “live tv”???
1 Like