First a big thank you to everyone who posts in these forums. I have been an avid Tablo user for most of the year and your comments and advice have immeasurably enhanced the experience, and offered very practical help. You have also allowed me to be part of a community, even as a silent participant to have modern kind of “water cooler moments” about TV. Second, a huge thank you to the folks behind Tablo. It is brilliantly conceived and provides exactly the base of core services I wish.
I have signed in, though, to add my voice, and to add another customer’s request to @tabloceo and @tablotv. I am a veteran software company CEO and I know how exhilarating, challenging, rewarding, and uncertain these kinds of things are. I’ve deeply admired the spirit of good will and relative openness you’ve shown in Nuvyyo (such as this forum). I think what is called for now - and you are seeing a rising chorus for it - is a new level of comprehensive candor.
I am very lucky in that I have a very high-end, robust installation and I have stayed on the pre-2.2.2 firmware from past experience of waiting to see what happens - which incidentally works very well with the beta Roku app. As a result, my Tablo experience on all receiver platforms (and I use all platforms) continues to be excellent. Of course I am stuck until and unless the new firmware’s bugs are sorted, and although I understand why you are profoundly reluctant to offer the option of rolling back to firmware 2.1.30 (let alone the possible technical challenge of making different firmwares loadable), I deeply feel for all those whose Tablo experience is now so degraded (even with some feature upgrades).
My hunch is two things are going on inside the company: 1) you have to watch your competition and not give them any competitive sticks to hit you with, especially with the holiday sales season upon us, and 2) you don’t know how to solve (perhaps even to isolate) the problems introduced, or let loose, with 2.2.2 and 2.2.6. Whether that is right or not, I empathize with the situation your are in.
You really, I think, need to give us champions of your product and company a way to keep the faith, though. You are at a tipping point, I think. So, one customer’s advice is to either tell us the clear roadmap you are following to fix this (pull back the curtain, as difficult as this is, and let us know really, in detail, where you are), or, tell us that you don’t know what’s wrong, but outline the kinds of steps you are taking (other than asking for bug reports) and what your fallback is if you cannot resolve it by X date. One possibility: re-releasing old firmware 2.1.30; I know you don’t want to do that after all the effort of rewriting the operating system, and the reasons for a new OS, but by some X date, you’ve go to get back to a pretty much universally stable product.
We’re at the point that business openness is the most important thing for Nuvyyo’s future, I think. I am fairly sure you don’t have the resources many imagine you do (or that you wish to have some day), and I know what’s it’s like trying to project confident scale (like painting Number 7 on the side of a company’s only truck), but we admire what you have done and you are past the point that you can afford more negative reviews on Amazon. Let your community of supporters inside the tent and give us a reason to cheer you, instead of hoping we’ll stand by.
It is time for something real from @tabloceo - first a candid statement of where you are, what you are doing, and what your fallback plans are, and then even something as radical as moving Roku out of main product support, if the rest of the bugs with other receivers are genuinely rare or clearly fixable with time, or rolling back the firmware for Roku users. My external sense is that you’ve about used up the time prior goodwill will buy you, and you need to build some more. Seeing the spirit with which you have run things to date, I know you will receive this in the spirit of best wishes it is offered.
This is a brilliant innovation. Thank you for it.
(And thanks to the Community for tolerating the long post.)