My apologies @TabloTV @TabloEngineering I had previously stated I was using the FireTV Cube 1st gen when actually I have the FireTV 2nd gen just as @Seeker336 has.
I’ve spent more time trying to resolve the numerous issues with this device than I have spent in the past 20+ years using Tivo. I’m ready to give up too
That’s funny. Have you actually tried to call them? Lucky you if you were able to reach anyone. (And they have the absolute worse on hold music I have ever heard. Sounds like torture music.
1 Like
@Seeker336 the latest update, which I received a few days ago, seems to have resolved my issues on my FireTV cube. Wondering if you have seen an improvement?
@mkilo67 Are you referring to an update for the FireTV Cube? Or are you referring to the recent firmware update for the Tablo 4th Gen that came out this past week?
To answer your question, though, I must admit that I had good recordings and playback on Wed, Thur, and Fri this past week. Unfortunately, I can’t zero in on the one unique fix or even if there has been one. I applied the Tablo update as soon as I saw it posted in this forum. I also had what seemed like an updating episode on the FireTV Cube on Friday evening where it quit responding to the remote for a while and I had to wait it out. One other variation in the mix is that I have made a habit of doing a Rescan each evening after watching that day’s recording. My theory is that this seems to refresh teh signal strength or “purity” of the station to be recorded the next morning. For the coming week, I plan to do a Rescan on Sunday evening, then leave it alone for the entire week and see if the segmented recording or Failure to Decode errors appear later in the week. Cheers.
@Seeker336 The Tablo update, the one for Wifi issues on setup. Once I got that update earlier this week things seemed good. For whatever reason, whatever was in that package seems to have resolved my issues, so perhaps it was a wifi issue with the FireTV cube.
@mkilo67 Good to know. Will watch for performance over the coming week. Good luck to you. Hope all your recordings continue to play back in good form. Cheers.
@mkilo67 OK, the week-long test session is complete. We recorded our daily show at 10-11 am every day, Monday-Friday, on a moderately-powered channel that uses channel 32 (no know frequency shares in the area). We played back the recorded show daily in the evening.
Every day the recording was complete, not segmented. Playback each evening was rock solid with one slight, brief period of pixelation on one evening. Each playback included thumbnails on the ffwd/rev scroll bar, so we were able to skip through commercials quickly and accurately.
My plan is to continue with current settings and configurations for another week before even performing a channel rescan. Prior to the Tablo firmware update, the 4th Gen device seemed to lose frequency focus without a daily rescan. Hopefully, that is no longer the case and all will proceed as expected.
So, a few growing pains, but seems to be settling in to a good system.
Cheers.
1 Like
Thank you for the info. Things are definitely better on my end after the last update, but not completely resolved. I am still occasionally getting the “Failed to decode” message and typically if I keep pressing “Retry” it will connect and play, but if not, I have found that going into the Application Manager in my FireTV Cube, Force Stopping and then Clearing Cache typically will help. If that doesn’t, I have found restarting my FireTV cube (Select + Play buttons) does it. I also noticed a few other things. Size of the Cache accumulates quickly, 60-120mb, much larger than any of my other apps. Additionally, I notice sometimes when I start the Tablo app I get the Tablo splash screen and other times I do not, just takes my right into the app. So, better, but not quite there. Hoping @TabloTV @TabloEngineering is still looking into this. ty.
Is it still made in Canada or China since EW Scripts owns them now?
The label still says made in china.
But the secret word is 2aor07-tablo020
1 Like