[mythtv] [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card

[Jan Schneider]

Zitat von "Michael T. Dean" <mtdean at thirdcontact.com>:

>  On 08/21/2010 02:56 PM, Michael T. Dean wrote:
>> On 08/21/2010 02:21 PM, Jan Schneider wrote:
>>> Zitat von "Michael T. Dean":
>>>> So if you disable cross-source EIT, do you get data for all  
>>>> channels in both sources?
>>> I tried that, and yes, then it's working fine.
>>>> Or are you saying that some channel that exists on one of your  
>>>> sources does not have EIT data on that source--so you would like  
>>>> a new feature to allow collection of EIT data from one source for  
>>>> use in populating channels on multiple sources?
>>> Isn't that was cross-source EIT is supposed to do? To grab the EIT  
>>> from one source and distribute it to the same channel on any other  
>>> sources?
> ...
>> For what you want--EIT data from one source used on multiple  
>> sources--the currently "supported" approach is to use your external  
>> listings programs to accomplish the goal.
>
> OK, so I started thinking about the "why" of what you're doing and  
> I'm not sure what your goal is.  If you get all the data on all the  
> channels when you disable cross-source EIT, then I'm assuming you're  
> only enabling cross-source EIT in hopes that it will do EIT scanning  
> more efficiently (only having to scan one video source or only  
> having to use one card for EIT scanning or whatever).
>
> If that's the case, there are some planned improvements to the EIT  
> scanner that should make EIT much more efficient than the current  
> "scan everywhere all the time" approach.  It will give the same type  
> of benefits as http://svn.mythtv.org/trac/ticket/5754 , but with a  
> different (and simpler) design.

Actually I didn't want to accomplish anything with enabling this  
setting. I was going through the settings after adding a 2nd source,  
and its description sounded like it did what I explained above. I  
suggest to make this description a bit more specific until the DiSEqC  
hack is no longer required.

As far as I am concerned, everything is working as it should now.  
Thanks for the explanations.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/