[mythtv-users] how to set xmltvid to unknown and keep it there?

[Robert McNamara]

On Fri, Jul 8, 2011 at 8:04 PM, Eric Sharkey <eric at lisaneric.org> wrote:
> On Fri, Jul 8, 2011 at 3:05 PM, Robert McNamara
> <robert.mcnamara at gmail.com> wrote:
>> So, to summarize:
>>
>> channum = for the user's benefit, not used for tuning, could be anything.
>> freqid = "true" virtual channel number, used for external channel
>> changing and analog tuning.
>> mplexid = Reference to a multiplex, used for digital tuning.
>> servicesid = "Reference to a service *on* a multiplex, used for digital tuning.
>>
>> Mythfilldatabase uses the "true" virtual channel number, since it's
>> the only piece of information schedules direct can provide us about
>> your cable lineup.
>
> Ok, I accept that, but you're just changing my opinion of where the
> bug is, not that there's no bug.  If what you say is true, isn't it
> then the case that the mythtv channel scanner for the HDHR is broken
> because it's populating the freqid field with completely wrong values?
>
> Are you saying that I should fix this problem by doing this:
>
>  UPDATE channel set freqid = channum where sourceid = 5;
>
> and then everything will work from then on as long as I don't re-run
> the channel scanner?

No, because the HDHR and other digital tuners have *no concept* of
what the virtual/box channel number is-- it doesn't have the
information you want it to put there!  This is why most people simply
edit the channels and put the xmltvid's in-- then you can run
mythfilldatabase --do-channel-updates and it will fix the visible
values to be what you expect.  You are trying to do it the opposite
way of how most people try, by getting mythfilldatabase to match
channel number instead of simply telling it which xmltvid applies to
the channel.

Regarding your SQL. yes, assuming you haven't changed any channel
numbers, that would clone them into the freqid table.

Robert