[mythtv-users] HDHR Prime Channel Tuning Failure

[Kirk Bocek]

On 10/3/2014 10:14 PM, Gary Buhrmaster wrote:
>> On Sat, Oct 4, 2014 at 4:49 AM, Kirk Bocek <t004 at kbocek.com> wrote:
> ....
>> Short answer, replace mplexid in the broken channels with 32767 and they
>> work again.
> The mplexid is a reference to the dtv_multiplex table.  Most likely
> your "1" did not exist in that table (so, another fix might have been
> to further "improve"(?!) your DB by creating such an entry). 32767
> is apparently still special, and so would be a value of NULL (I
> have not looked at the code, but I presume 32767 in current
> code is treated somewhat equal to a NULL, in that it indicates
> that the value is not actually valid, and a lookup in dtv_multiplex
> should not occur).
>
> Glad it is working for you now.  Oh, and by the way, you
> really need to schedule an upgrade to 0.27.4 :-)
> _______________________________________________
>

Yes, I am familiar with dtv_multiplex through my old script. But again, 
I had mentally written it off because of the vchannels. Guess I was wrong.

Yes I need to upgrade. My problem is I am running mythbackend on a 
CentOS 5 host. I have to perform the host migration process documented 
on the wiki to a CentOS 6 host so I can upgrade. Just have been afraid 
to do it.

BTW, sorry to change subjects here: seeing the Schedules Direct traffic. 
I'm late to this subject. They are changing their data format November 
1? Will this break 24.3? If so, I now have my motivation for migrating 
and upgrading.