Just curious if anyone else has seen this happen.
After scanning and adding all of my ATSC channels, sometimes the data is not stored correctly in the channel list and a few will show up with the wrong physical , major, and/or minor channel number. This is not a big deal because I have a list of channels by physical number. The problem is that when I try to manually edit the channel and hit save, I am presented with a message that says something along the lines of "invalid frequency specified." This is caused by the frequency being set to -1 for every channel after scanning. The other channels that have -1 for the frequency but have the correct physical, major and minor numbers all work fine for recording and viewing, but I am unable to edit channels manually if needed. The only option I have is to delete the channels and scan again in hopes that it will get the correct information the second time around.
I thought I read something a few weeks ago where someone else saw the same thing, but I searched the forums without any luck. I also checked if this was an existing bug but couldn't find anything in Mantis.
Thanks!
-Steve
After scanning and adding all of my ATSC channels, sometimes the data is not stored correctly in the channel list and a few will show up with the wrong physical , major, and/or minor channel number. This is not a big deal because I have a list of channels by physical number. The problem is that when I try to manually edit the channel and hit save, I am presented with a message that says something along the lines of "invalid frequency specified." This is caused by the frequency being set to -1 for every channel after scanning. The other channels that have -1 for the frequency but have the correct physical, major and minor numbers all work fine for recording and viewing, but I am unable to edit channels manually if needed. The only option I have is to delete the channels and scan again in hopes that it will get the correct information the second time around.
I thought I read something a few weeks ago where someone else saw the same thing, but I searched the forums without any luck. I also checked if this was an existing bug but couldn't find anything in Mantis.
Thanks!
-Steve