xxx ccc xx cc
Let’s calm down, everyone. This is not a forum that needs a flame war.
4 Likes
Firmware 2.2.6 works fantastic for me but I have not really recorded anything. Now I did have to reset my Tablo though from firmware 2.2.2 to 2.2.6 (for some reason the firmware upgrade caused it to not function) and it made a world of a difference on how it worked once I did the reset. The only bad side is I lost my only recording which was of last years Super Bowl.
Thank you for the updates! I appreciate the insight and detail into the background goings-on.
Rather than build a workaround into the Tablo firmware, could you just report the issue to the Roku developer program? Since you’ve found a repeatable, demonstrable flaw in their firmware, I’d think they’d probably want to hear about it and address it themselves.
Fear not, we ALWAYS report anything we find to Roku and work with them to provide reproducible scenarios. They do their best to make fixes in a timely manner but in the meantime, we do our best to find ways we can solve issues for our users ASAP.
3 Likes
I’m surprised you guys have never managed to reproduce the LPW issue in your lab test.
If you bring a Roku and can drive for 2 hours I can show you it probably in less than 10 minutes, if we’re lucky you’ll also get a reboot.
However given the number of people affected and that’s it’s been going on for more than 3 months now, it doesn’t look good on your company that your engineers were unable to reproduce it, at least from my standpoint.
@jayeffgee We have been able to reproduce it.
Our last update on this is here: A Message from the CEO of Nuvyyo
We are still up to our eyeballs in packet captures trying to reproduce it on Roku 2 now as well.
Oh ok I must have missed it.
Still took you guys too long to reproduce it in my mind.
For what it’s worth the issue was happening to me in both wired or wireless, with Roku 3.
@TabloTV - I see that you’ve isolated the issue on the Roku3, but have you been able to reproduce the LPW issue on Roku4? I’m still having issues with Roku4 + Tablo with LPW happening very frequently.
@Designer - Did you see this message above re: Roku 4? A Message from the CEO of Nuvyyo
It is possible that the condition that exists on Roku 3 also exists w/ the Roku 4 on WiFi (or even on Ethernet). We believe we have a congestion algorithm that will reduce this significantly that will be going into testing today.
@TabloTV - thanks for the reply and pointing me to the post about Roku4. yes I did see it. however, i have never configured my Roku4 for WiFi; i have only ever used it with ethernet. And I have power cycled my Roku4 a few times and still have the LPW issue with my Tablo. So the sequence of events that you guys have identified doesn’t explain the symptoms I’m experiencing. I do hope your congestion algorithm helps…
+1 - exact same situation, and have seen LPW’s, but the frequency is low for everything but 720p/60fps NFL games.
I just started getting the loading please wait on an older roku 2 wifi using 720p 3mbps setting.
@Designer @ChrisFix - It could be the 4 is suffering from the issue the Roku 3 has as well. We’ve been doing testing on the congestion algorithm that seems positive so far.
1 Like
I think I can speak for the majority of users in saying we’re looking forward to testing your solution as soon as it’s ready!
@TabloCEO @TabloTV it’s nice that you spending time to do a throughout test, but in the mean time could you roll back to the old version of firmware (2.2.2). Why not to make a new release with old firmware to avoid any issues. Because as much as I appreciate your time testing, it’s impossible to watch something on Tablo with “loading” interpretation for live TV or up to 2 minutes loading recorded content (from start or when fast forwarding).
You have to remember some folks are beta testing and thats the nature of beta. Also the more beta testers there are the better chances of finding problems before deploying as normal release.
I think this would be just as problematic. 2.2.6 fixed the missing recordings issue for many of us. I am fortunate in that I don’t experience any problems introduced with this firmware (likely because I don’t use Roku - although my husband does and he hasn’t mentioned these problems other than the FF reboot which is not related to 2.2.6). I would not want to go backwards and have to deal with all of those inaccessible recordings all over again.
That is not to say that I don’t understand the frustration of those experiencing issues now or that I downplay the importance, but I don’t think rolling back to old buggy firmware is a solution (even a temporary one) for correcting current bugginess in the firmware.
@Vounda_Z That’s a good point. However, if everything works for you with 2.2.6, you can just ignore the “upgrade” to the old version request. And keep using the one you have. The problem is that there is no choice for the users who have these issues. Another big issue is that there is no time line when to expect the fix for the issues introduced by 2.2.6 How long would it take couple days, weeks or months?
I am not thinking of myself so much as the general customer base, with a certain proportion of that base having suffered through the disappearing recordings bug and having experienced a fix in 2.2.6. Yes, I could ignore the upgrade. But what about those with a similar experience who do not frequent the forum? Most of these people will get the upgrade notification and upgrade, not realizing that the “upgrade” will bring them back to the state where they were “losing” all of their recordings. No matter what precautions you take, a large percentage of those people are going to see the upgrade notification and automatically hit upgrade.
If Tablo were to roll back the firmware, I could only see that being feasibly done on a request only basis, since there is still a large subset of users who benefited from 2.2.6 who are not having the current issues.