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

[Robert McNamara]

On Fri, Jul 8, 2011 at 4:02 PM, Eric Sharkey <eric at lisaneric.org> wrote:
> On Thu, Jul 7, 2011 at 4:25 PM, Eric Sharkey <eric at lisaneric.org> wrote:
>> On Thu, Jul 7, 2011 at 4:14 PM, Robert McNamara
>> <robert.mcnamara at gmail.com> wrote:
>>> On Thu, Jul 7, 2011 at 8:12 PM, Eric Sharkey <eric at lisaneric.org> wrote:
>>>> Ok.  I don't see anything clearly labeled as a freqid.  I see:
>>>>
>>>>  <channel id="I14771.labs.zap2it.com">
>>>>    <display-name>128 HISTORY</display-name>
>>>>    <display-name>128 HISTORY NJ67162:X</display-name>
>>>>    <display-name>128</display-name>
>>>>    <display-name>HISTORY</display-name>
>>>>    <display-name>History</display-name>
>>>>    <display-name>Satellite</display-name>
>>>>  </channel>
>>>>
>>>> 128 is the correct virtual channel number.  It is not the correct
>>>> frequency.  How does mythTV populate the freqid column of the database
>>>> for firewire tuners based on this data?
>>>
>>> freqid != frequency.
>>
>> Well, then, what does Mike mean by "if the channel is on the same
>> frequency Schedules Direct says it's on"?  Based on that XML, what is
>> Schedules Direct saying about the frequency?  To me, it looks like
>> it's not saying anything.
>
> Unless I hear otherwise, I'm going to file a bug report.  Mike says
> that mythtv should set the xmltvid when the channel is on the same
> frequency Schedules Direct says its on, Schedules Direct doesn't
> define a frequency, yet mythtv interpreted the virtual channel number
> as a frequency and set the xmltvid based on that.  That's a bug,
> right?  Or am I still missing something?
>
> Eric

Schedules Direct Matches on channel number.  Schedules Direct is not
aware of the frequency, and it is not used as a matching criteria.  It
is behaving as expected.  No bug.

Robert