Bummer. It seems if the tablo can do different resolutions for recording versus live, then it should be able to send out two different live resolutions to different devices.
So, when a tuner is used, it’s recording… even if Live. So, if you have to do “tuner math” to figure out, for example, how many people can actually watch Live TV at the same time. Basic logic says if you have 2 tuners, the most you can have is 2. There are a lot of reasons why you can’t get 2 though depending on whether or not the Tablo needs to use a tuner for other processing.
But the point here is that for different people to watch Live TV at different “resolutions”, that would mean dedicated tuners (different file streams and not necessarily based on “viewer” but on “viewer” and/or “device”). Now I can’t tell you the answer to this… if on the Tablo today and two people (assume local net) are watching the same channel “Live TV” do they just get pointers off the same m3u until they diverge enough (e.g. somebody pausing for a really long time)?
The answer to that question would help to make an absolute determination about what can and cannot be done on the Tablo with today’s software.
I think it technically could, if it used two tuners for the same channel (or more tuners, depending on how many devices were viewing it). Although I think to better manage customer expectations, it might be necessary to make that an advanced option with an explanation that enabling it can possibly require 1 tuner per device watching that channel “live” (in other words, watching the live buffer although some may be several minutes behind).
I still don’t have 2.2.20. Are this version been release to Tablo Dual Lite yet? If not when? Thanks.
Soon!
One problem that I have not seen since 2.2.20 upgrade or possibly Tablo channel on Roku upgrade to 2.5.1. Periodically both audio and video would stop for a few seconds and then resume. It has been awhile since that has happened to me. Roku Ultra.
If this was a fix, thank you.
Would you get a ‘loading please wait’ message on the screen during that time? Or was it super short?
Did I miss something?
I thought 2.2.20 introduced the condition where the WEB browser app would only connect using Chrome and Safari.
Yesterday I noticed that the WEB app had been updated 6/18/2018. So I tried to connect again using Firefox.
I seems everything is back to where it was before 2.2.20. I can even connect using my old Samsung tablet running gingerbread and Firefox version 41. And while it could never play the video I can still sit on patio, coffee in hand, and schedule and check up on things.
As you mentioned “it works” in Firefox with tons of bugs and limitations today. And yes, it was broken there for a bit.
Short but some times several times a night then not at all for awhile. It is usually when multiple recordings are also taking place. Once I figured it out, I just wait. I think it was probably an issue with the hard drive but I have not had the issue lately and it just occur to me that 2.2.20 may have fixed it.
An other issue is that some times after I have not watched for awhile, my selection does not load until I hit the back arrow and select the episode again. It is like the hard drive is sleeping and needs a wake up call. Not a problem because work good once I click out and back in.
I have only had the loading message a few times and backing out snd signing in seems to resolve it for me.
HD Elements with External power supply.
I kind of remember the thread about IE and Firefox not even connecting after 2.2.20. I don’t remember any tablo posting about any WEB app changes that corrected that. And if pre tablo version 2.2.20 IE and Firefox functionality meet your expectations then that’s all that should matter.
While Firefox is still officially still unsupported, we issued a patch to solve the connectivity problems that users were experiencing post 2.2.20. It should be back to where it was prior to that release now.
Does www.tablotv.com say FireFox, IE, and Edge are unsupported.
While it does suggest “PC & MAC computers running Chrome or Safari” it also says “Optimized for Chrome & Safari browsers”. There is a big difference between unsupported and optimized.
Maybe the “Optimized” phrase should be removed. And does tablo really test and support all versions of Chrome and Safari?
Hi folks -
If you have a Tablo DUAL LITE we are beginning a staged rollout of 2.2.20 firmware for you.
This includes some of the same fixes that have already been distributed to older Tablo DVR models, as well as a few tidbits especially for this model.
More importantly, this will also bring all Tablo DVRs onto the SAME firmware branch so we can start rolling out some new features to everyone in the coming months!
Release Notes for 2.2.20 ** DUAL LITE ONLY ** – Maintenance Release
• Fix for Auto-Delete function on Cloud DVR storage
• Brings Tablo DUAL LITE firmware version in line with other Tablo models
• Small bug fixes and performance improvements
NOTE: Post-upgrade database processes (if needed) may take several minutes to complete. During this time the LED will be blinking. Do not power down the Tablo until the LED is solid again.
If you have a Tablo DUAL LITE and you haven’t been prompted to update yet, you should have access to 2.2.20 by this evening!
Can anyone show a video of the speed enhancements for Live TV tuning?
Do you mean 2 videos: before speed enhancements; after speed enhancements?
The current Live TV tuning time is around 8 seconds per untuned channel, and around 1 second for tuned channels.
I found that tuning a non-tuned channels took about 17 or so seconds before. And now it’s probably down to 10 to 12 maybe less. It does make a huge difference, but not going to make people dance in the streets…
Thanks that’s what I was looking for. Still too slow for me 
I’m specifically wondering about tuning to a previously untuned channel after the speed enhancements.
6 seconds is the fastest I’ve experienced.