That’s a great point/selling feature for Tablo Ripper which I hadn’t really considered. I didn’t see the need to convert it to use on Plex, but to use it for backups is interesting. Then I can just use the Plex app on the Roku. Two birds. One stone.
It looks like I’ll be spinning the Plex server up again 
Sorry to bump it up, but I gotta confess I was had. It turns out that the Tivo app turns the wifi back on! So I thought I was getting it through the cell tower, but was not. I walked down the street, and nada. So not available yet.
Unfortunately every speech/rant can’t be as effective as William Wallace’s 
As a frequent reader of this forum, I can say that many others, including the Tablo folks, have been very helpful. Lots of great advice hidden in these archives. And yes, there are still issues that need to be fixed. Tablo of course is doing their best to resolve them - they don’t want to see threads like this, and they don’t want to go out of business. Hopefully they get everything resolved soon so that threads like this are no longer necessary, and we can all share fun animated gifs with each other instead. 
Don’t know of any issues with PLEX and Roku. I have Roku on my home theater but my Samsung Blu-ray has built-in up-scaling so I mostly access PLEX through that. I do use Roku though, but for things like Netflix, Amazon Prime and such at times.
-Rodger
I’m new to the whole Tablo game, just got my unit a week or so ago.
I’m already leaning away from Roku, the new AppleTV is providing almost everything I need, except OTA which was MythTV but others have mentioned how unfriendly it can be to non-geeks.
I saw that Tablo was coming out with an AppleTV app so I jumped on it.
What I’d like to mention is now that I finally got the bugs out of my system (my issues, not Tablo’s) I was able to try and plain old watch something.
I used Airplay from my iPhone and it was an amazingly simple experience.
Told the iPhone to airplay (nor mirror, just airplay), and told the Tablo app I wanted to watch the news and away it went on the TV, (6 seconds from tapping play until active on the TV)
Hit pause on the Apple remote, the show stops.
Tap ‘advance 10 seconds’ on the remote, immediately up 10 seconds.
Ask Siri (on the remote) ‘what did they say?’ and back I go.
Skew ahead on the ATV’s touchpad and ahead I go, with thumbnails.
It seems to work exactly as I would expect with a native app, except no front-end.
I was pondering extracting shows and using Plex to play them, but seeing how well airplay works, I don’t think I need to, this is perfectly fine until Tablo gets their app ready.
Just another option for you if you already have a new ATV.
Looks like I have some catching up to do on reading… in the meantime, an update with some success.
Since I installed the 2.2.7 beta, and things got worse, I opened a ticket. Tablo responded, and asked me to try hard wiring the Roku and the Tablo, and as well to put the Tablo into ‘remote access’ mode so they can take a look at it.
I ran wires around the living room, and hard wired both, and things got way better. 3-4 second waits when skipping, and fairly consistent - as I think it should be. Thinking then that my Wifi (Rogers Hitron router) may be an issue, I set up a separate Wifi network, using an Apple Airport Extreme base station, and connected each to it.
No luck. It was just as bad.
Then I tried something else. I separated the Roku and the Tablo by 4 feet - as far as my wiring will allow (they had been side by side). Aha!.. it is now averaging 10 seconds delay when skipping ahead. It had been 60 seconds or so. Still slow to start playback, but this is way better. I also noticed that putting my hand on the unit while moving it caused the connection to drop completely once, and cause an interruption (please wait) another time. It seems that the wifi antenna is extremely sensitive.
Moving them closer together caused longer times again.
I then put the upstairs Roku onto the same Wifi, and it is showing the same improvement.
I will try doing some rearrangement of wiring, and try to move these things further apart and see if it can get better.
Huzzah!! Awesome glad to hear it
Some timings from another 20 minutes of testing:
Live TV - 17 seconds to start
Recorded show - 35-40 seconds to start
10-20 seconds pause after skipping ahead
1 reboot (Roku 7.0)
(1 reboot last night on a Ruku 6.2)
My Live TV timed tests spot (agreed) on at about 17 secs from pressing Watch
However, playback of something recorded started within 3 secs.
Almost immediate start after skipping ahead or going back.
Roku 3, running 7.0 build 9021
A video is worth a thousand words: http://endlessnow.com/ten/Video/tablo-delays.mp4
Roku is set at 1080p, but I record at recommend 720p setting. And my inline frame grabber is 720p.
The channels viewed are 1080i
You guys should avoid saying things like this. It’s abundantly clear that you believe you do thorough testing. The problem is likely a nearly indefensible lack of understanding of what “thorough” means. This is the first problem you should solve.
You can. It requires very normal product management and product development practices. Not having these practices / procedures in place is another reason why you make promises you can’t keep. It’s okay to be a young company with limited resources - it’s also okay to act like one. Unfortunately, Tablo seems to only act like a young company with limited resources when it’s making excuses for under-delivering. Just stop making the promises. If you want people to expect less of you, make fewer promises. Otherwise, don’t make announcements of any kind until you have a product plan in place that is reasonable.
These are normal characteristics of pretty much every successful company in the world.
Jestep - I’m not beating you up here (my second reply to you) - but the mix that Tablo has to deal with is EXTREMELY modest in comparison to even PC application vendors, system integrators, enterprise software companies, etc. Quality assurance is not easy - and nobody with any firsthand knowledge would say it is. Quality is hard. Quality is hardest when you don’t have enough respect for it - and that is the problem here.
Beta testing is an important part of the software development life cycle. But, it’s far from the most important part.
GASP!! Why would all those people that bought a product designed and advertised to work with a another product (Roku) that really is the standard for streaming devices, expect it to work? It must be that damn entitled generation…
Philsoft, you say the same thing over and over and over again - your one configuration works for you - so therefore it’s not a problem. Why do you do this? Why are you here day after day after day after day saying your Roku and your Tablo work without issue - therefore everyone else is whining. Did you read the original post? Man… that’s not a rant… that’s a very real … very broad, excellent assessment of where things are. Your response? “mine works, stop being an entitled whiner” Why bother?
Wow! That’s fast! I want one like yours! And I want all those channels!
Thanks for posting.
Sums it up nicely.
Definitely will try this on the new ATV. Thanks.
xxx ccc xx cc
When you have the delays are you running with both the Tablo and Roku wireless? Most WiFi routers really can’t handle that we’ll. They are trying to juggle both an incoming and outgoing stream at the same time. It works much better to have one of the two wired, preferably the Tablo. If you can run your antenna line there, it works well to just put the Tablo near your router or switch and wire it.
Interesting thought - but then I would have to ask, why the same Roku works extremely well streaming HD content from my wifi-connected iMac - with no response-time issues, or dropped frames? At the same time, someone else can be streaming different content from the same computer to another Roku.
Also, my WiFi iPad can be a “middle man” and AirPlay stream from Plex on the computer, through the iPad to the Apple TV - all 3 devices are Wifi-connected and nothing fails.
How is going from a Wifi Tablo to a Wifi Roku different from these scenarios - and nothing else going on with the Wifi during testing?
We could continue a back and forth on this, but that would be fruitless. Lets agree to disagree