Hey @RTR We’d like to confirm that this is the picture/frame issue by grabbing some video from your Tablo. The support team has requested remote access so we can do that but haven’t heard back from you. Can you check your inbox for instructions?
Once we confirm, we’ll be able to touch base with KPHE.
Yes, I heard back yesterday afternoon from support, but am busy with family and holiday preparations and probably won’t be able to follow the requested procedure until this Thursday at the earliest.
Remote access has been activated and I’ve returned the email to the support team indicating so.
I noticed yesterday that 44 has shuffled things a bit. It seems like they are now simulcasting a 720p signal on 44.2 and they have moved Rewind TV to 44.3. You might want to rescan and see if watching on 44.2 does the trick.
Thanks for posting this. Yes, from what I’ve been able to gather, 44.2 is apparently coming as a sub-channel from KPHO (like KUTP re-transmits KSAZ on 10.2 for those that can’t pick up 10.1 VHF), so it doesn’t have anything to do with KPHE’s transmitter. For me, 44.1 still crashes the Tablo. Plus, KPHE moved Rewind to 44.3, Fido to 44.4, added a new diginet called The 365 to 44.5, moved the DRTV channels to 44.6 and 44.7, and now the guide data is incorrect on the Tablo and my Fire TV (except for 44.1). Oh, time was tight over the holidays and I forgot to post that tech support told me “We can confirm that this is an issue that is caused on the broadcaster’s end. We were able to collect the necessary data so that we can try to contact the broadcaster responsible, unfortunately, we will not be able to guarantee they will respond, or an ETA for when this will be resolved.”
I put in a ticket a couple of days ago to have the guide data updated (corrected)
Outsourced and not David like 2015
PHX area KPHE channel 44.2 now working perfectly. Watching SUNs pregame and SUNs game WITHOUT any issues. 1-16-24.
Now if we could only get the guide data updated. This was the last ticket response:
Our guide data provider doesn’t have access to these channels in your area, and we, unfortunately, do not have an ETA on when or if they will be added. We are actively working with our guide data provider to attempt to resolve this issue, but do not have more insight to offer at this time.
This makes no sense. The stations were populating guide data before the lineup changes, so why would they only now not have access to 44 and it’s sub-channels
Yeah, they asked me today to do the recommit procedure…like that is going to work. 
Update: And it didn’t.
I live in Gilbert around the Chandler Heights & Higley area and I get 155 channels. Let me preface that any antennae in the Phoenix valley needs an unobstructed view of South Mountain or forget getting good reception for most channels. I have a two story house and put a cheap powered RCA antennae in my upstairs window that faces South Mountain and I get great reception. Luckily the window is by my router so I don’t have a huge issue with setup. Now my problem is the app crashing on my Roku unless I am recording the program I am watching.
Update. As someone here has suggested before, I submitted the same information to “Zap2it”. I noticed this morning that Zap2it has the corrected channel lineup/guide data. If you follow the standard Tablo process (unselect the channels, save and then do a rescan), the guide data for 44.2, 44.3 and 44.4 should be accurate now (at least on a LegacyTablo).
And as a reminder, anyone having issues with 44.1 can now view the same programming on 44.2 (hopefully without the same tech issues)
Confirmed. They are correct now (except for 44.7, which is blank, but they’re infomercials, so who cares?). And I removed 44.1 from my guide, so no more accidentally choosing that channel and causing a crash and reboot anymore.
Hooray, a workaround that works!
No thanks to Tablo.
I don’t care what a broadcaster sends in it’s signal. If it works correctly on any TV (and it does) it should not cause my Tablo to puke and reboot.
I get it that there is some bit flag set incorrectly, but the Tablo should behave better.
Again, Kudos to the broadcaster for the 44.2 workaround.
TBH, I don’t think 44.2 is a workaround to the 44.1 broadcast flag issue. 44.1 is a low-power station with limited reach, and by utilizing a subchannel of full-power KPHO to broadcast the same programming, who knows how much they are able to increase their audience? And to be fair, I think my legacy Tablo works remarkably well considering I can receive 82 channels at my location and only have an issue with one of them. I’m not defending or making excuses for Tablo, but no matter how you look at it, it is a specialty device compared to a regular TV, and I expected to see a quirk or two during use when I bought it.
Sure, Sure…We can consider it a firmware feature just for us in the Phoenix Metro area.
Whenever you want to reboot your Tablo, simply tune to 44.1 and wait.
I see Gen-4 users are requesting this feature, so we are lucky to already have it.
Putting aside others’ sarcasm, I’m curious now. Fourth-generation users in the Phoenix area: Do you also have this problem, or is it an issue with legacy devices only?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.