I will start off by saying that I’m glad to see that Tablo merged the private and public channels on Roku so that development efforts can be solely focused on one app. I know that Tablo can only know what has been reported to them. Given the outcry of missing recordings, I hadn’t taken the time until now to report the issue as we just let the recordings pile up and watched other unaffected series. My assumption was that they would have fixed the issue by now. There are more important things in life than TV, so I’m not going to berate Tablo on their issues. The information below is to just provide additional information so they can know that there were silent users affected as well and the problem may be larger than expected. Some people may not even realize they were missing recordings.
We were missing recording prior to the most recent Tablo firmware update. The last firmware update to the Tablo did successfully recover those recordings. Since that update, multiple new recordings of multiple different TV shows have not shown up on the Tablo Preview (Roku private channel) or Android app on my phone. However, they were showing on the public Roku channel. With the most recent update to the public Roku channel (replacing it with the preview channel), the recordings have gone missing again and we have no way to watch our shows. Since most shows are a series, we can’t watch any of the series until you resolve this issue. Yes, we could try to watch on the TV networks website, but that is more of a pain than it’s worth. Besides fixing the issue, it would be nice if you would provide a way for users to initiate a recover of the shows like what was automatically done with the latest update.
We have also been affected by the LPW on our Roku 3’s that others are seeing. The Roku’s are hardwired and we are using the highest video setting as sports look better. E.g. - a football doesn’t look as blurry when passed. I don’t want to have to switch back and forth between resolutions. I would prefer if Tablo would either automatically record based on the broadcast resolution or allow customers to set the resolution by channel. We record some kids shows on a channel that broadcasts in 480. I don’t need 1080 recording on that channel.
Tablo did fix a guide issue in our area, so I know that support is focused on customer’s problems. I have been showing the Tablo to others, but I hate adding the caveat to be prepared for issues. I am a supporter of Tablo, but I am concerned that Tablo will lose it’s momentum if major issues cannot be addressed in a timely manner and prevent future major issues from occurring through better QA. I tell my teams at work that I understand they are not perfect. Issues will arise and it’s how you react to the situation that matters.
I believe we are very close to a new firmware version which specifically addresses the problems affecting a some of our customers as outlined above.
The problems can be traced back to firmware update 2.2.2 which was a major feature release and included support for larger drives, smart sync, and back-end connections for the new Roku app.
Unfortunately the release also introduced a few bugs that were not evident until after an extended period of use.
For some users with a very large collection of channels and client apps, Tablo’s internal database could grow to a size that would slow down the operation of the user interface.
We also discovered that if all recordings were deleted in a series, new recordings were not being displayed within the apps even though the recordings were stored on the disk.
Lastly we have discovered that the congestion management strategy used by Roku devices could cause a random reduction in throughput due to an issue with the network stack of the Tablo. This resulted in frequent “Loading, please wait” messages, even on good quality networks.
These issues have all been addressed, have passed internal QA testing, and are now in testing with our beta community. Once these updates have been appropriately reviewed by our beta team, we will distribute the firmware as a 2.2.8 maintenance release.
As Nuvyyo grows, one of the toughest challenges is to balance the pace of new feature introduction with the need to maintain and enhance the stability of the platform. In retrospect, we were probably too ambitious with our 2.2.2 update and despite months of QA and beta testing some significant issues slipped through.
Customer satisfaction is our number one priority and we have taken action to review and update our internal quality processes to ensure that these issues do not arise in the future.
Thank you for your patience and continued support.
@TabloCEO@TabloTV@TabloSupport
Just wanted to say Thank You for the dedicated attention to getting the issues straightened out. As a beta tester with 2.2.7 I can attest that things are working again.
Look forward to a long future with Tablo!
I’ve been holding off telling more people about Tablo, since I didn’t think the people I would recommend the Tablo to could handle the technical issues, but with these fixes I’m ready again to spread the word.
The last 5 months hasn’t been the best time for us Tablo users, with Black Friday just around the corner is there a chance you will reward us loyal and patient customers with good deals for lifetime subscriptions or any of the other subcriptions forms?
@TabloCEO@TabloTV@TabloSupport And this is exactly why I recommend people to get a TABLO … hey nothing is perfect and you guys really do try to make things right… this is more than anyone can ask … an active development team and company that interacts directly with their user/(dare I say fan? base) …
The legacy app did bring back some of the shows. Support had also responded back with a similar link. There appears to be more missing, but it may be due to the delete series issue described in the CEO update.
We are getting the LPW more frequently now so looking forward to that next firmware release.
@TabloCEO@TabloTV@TabloSupport Thanks for getting the fix done so quickly. I am experiencing the LPWs, long load times and delays on all 3 of my Roku 3’s. Is there an ETA for releasing the fix? I understand and applaud the caution being used on the roll out to production but the LPW bug is starting to get real annoying for me and the wife. It’s worse than commercials! So I need to make a decision do I go beta (which some have commented on going real well and I would be fine with) or just wait a few more days for the release? A solid commit date for the release with a variance would be greatly appreciated if possible. Keep up the good work - it’s really starting to take shape nicely. It’s been a fun ride I bought the 4 tuner as soon as it came out and I must say your product keeps improving.
@gprzybyl - Sorry, we can’t provide a specific target for the 2.2.8 release. It really depends on the feedback from the beta team and our internal testing. It seems to be going decently well so far but we may decide to do one more test ‘load’ before moving forward because we want to make sure it’s 100% awesome.
Thanks for the reply @TabloTV that is exactly what I needed to know. I will go ahead and sign up for the beta tonight then and put it through it’s paces!
This is very encouraging. As someone who isn’t a part of the beta program (although I probably should) I appreciate those who are doing all the testing.