As I posted, you possibly may need to delete and re-create the guide database to ensure the guide data gets mapped to the new channel numbers. See my post above with where to find that option.
(Also, after you delete and re-create the database, it may be beneficial to restart your DVR server, and then ensure that you are starting your clients fresh—force close/quit the Channels app, and then relaunch it on your streaming device.)
Most broadcast/cable systems do not have any channels in that range. And I imagine it was also driven by the fact that HDHomeRun tuners will automatically assign channel numbers 5000 and above for channels without PSIP data. So, to avoid possible conflicts, 6000+ was chosen.
(Of course, that's my WAG; but seems more than reasonable.)
this is awesome...now i can go back to the native locast integration and have my wife be ok with it rather than having to use fHDHR to get the channel numbers.
any chance the ability to change channel numbers for the rest of the channels is coming any time soon? would be great to be able to change to a numbering scheme we're more familiar with (like directv, for example)...
quick question: in order to go from the fHDHR locast implementation to the native one, do i need to do anything other than remove the fHDHR and turn on preserve channel numbers in the latest build? will all of my recordings translate to the new channel numbers?
Channel aliasing is about the only thing that I can think of that would make Channels perfect now. You and your team have a fantastic product!
I provide in-law or buddy down the street tech support for a number of non-overly technical folks, most of them are used to finding ESPN on channel 206, for example, or whatever ATT Uverse had it. This would make for a smooth adoption.