Separate names with a comma.
Discussion in 'TiVo Help Center' started by duhmel, Oct 24, 2020.
could have been a signal issue no issues with cox omaha and 1987
Today my Tivo Premier Pro rebooted and thought I would check 1987. Shows CSPAN channel clearly now. Not sure if the Tivo reboot is related or Cox decided to start to send the signal, either way it appears I shouldn't be worried about the transition.
Received the latter from Cox Phoenix yesterday. The test channel shows fine on my Roamio. It would sure be nice that once they make the switch that they get rid of SDV and tuning adapters but I know that is a pipe dream.
I think that anybody, including me, who tunes to 1987 and sees C-Span and thinks that they don’t have a problem have a problem. Check your “Guide” and I think you will see that since there was nothing on 1987 the system flipped you to Channel 1, which is C-Span. When I tune to 1987 I get a statement that says that I am not subscribed to this channel, and then it takes me to Channel 1.
How come nobody can answer the question about finding out which Roamio box we have?
Where was that question asked? That aside, just check the model number against TiVo's matrix: TiVo Service Number and Model Number Table
It was asked several times in the thread that you referred me to. Thanks for the info. I’ll check and see which model I have.
Edit: I’m in that thread I guess.
There was also this reply (I'm assuming to you) in the Cox support forums (link)...
No, not a reply to me. I actually don’t think it is a false alarm. The people in this thread who feel that it is are comforted by the fact that they can see C-Span on Channel 1789. On my Cox, C-Span comes in on Channel 1 and when I select 1789 it initially tells me that I am not authorized to view this channel, then it flips to C-Span. And then i check the Guide, and it shows that I am tuned to Channel 1.
Yes, I saw that information in your earliier post.
It *would* make sense to check w/ Cox as to whether *you* have such a test station available, and then determine why you aren't able to access it, if such is the case.
I will. But first I’ll go to the source you gave me and see what Roamio I have.
You can, but all Roamios have MPEG4 support, generally. Any statement that some version of Roamio would differ from others in MPEG4 support was erroneous.
Thumbs up, krkaufman! I should be OK then, and likely won’t have to do anything.
tuning adapters are for sdv only not mpeg4
what models of tivo's do you have? if you can't view the test channelI would call cox first and make sure the channel is working in your area.
All I know is in Nov I got an error message on 1987 and now it is a c-span channel. Tivo continues to confirm no problems with MPEG4 conversion on my Bolt.
channel 1 might be Cspan in your area , but channel 1 in our area is onemand barker/launch channeel
It is now past time for any changes to have been made in Tulsa area. I see no effect on Bolts or Premier at this point. Is there a way to check to see if conversion has been made to MPEG4?
I read in either the Cox forum or the DSL reports Cox forum that the changes were done and that copy protection was now being enforced on all channels but locals in Tulsa. Then a few days later that supposedly changed and it was only on premiums again.
Check some files with pytivo or kmttg and see what it shows.
Is your Tivo still working fine here in Omaha? Over this past week, I have lost signals to several channels (5, 28, 34, 35, 36, 37, 50, 51, & 64 along with their HD versions 1005, 1034, 1035...)
and things are all wonky on others. For example, all day today on ABC (1009) WGN was broadcast, and was all my TIVO recorded. NBC (1008) was broadcasting BET and MSNBC (1066) was broadcasting Tru TV.
Cox online support is useless as usual. A ticket was started on Wednesday but nothing since. On Wednesday the issues were also happening on the TVs without a TIVO but now it's back to just TIVO issues.
I have a 6-tuner Roamio that we bought in 2013 that was working just fine.
yes still working fine in omaha, but did notice same issues you did though