Mailing List Archive

Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card
On 08/16/2010 06:23 PM, MythTV wrote:
> #7672: Guide not populated with EIT from 2nd card
> ---------------------------+------------------------------------------------
> Reporter: jan@… | Owner: stuarta
> Type: defect | Status: assigned
> Priority: minor | Milestone: unknown
> Component: MythTV - EIT | Version: 0.22-fixes
> Severity: medium | Resolution:
> Keywords: | Ticket locked: 0
> ---------------------------+------------------------------------------------
>
> Comment (by jan@…):
>
> Quoting Gavin: "To me it's not clear if the issue is that EIT isn't being
> received from the second card, or if it is and your attempts to combine it
> have not worked out. Those are two separate issues, and will require
> different debugging efforts, I'm sure."
>
> The EIT is received on both cards, AFAICT. At least it works on both cards
> for any channels that are only available on one of those cards. It just
> doesn't work if a channel exists on both cards. In this case the EPG is
> only filled for the channel on one of those cards. I can't easily test
> this at the moment, because in the meantime the affected channel's data is
> provided by my xmltv provider, so I no longer have to rely on EIT. But if
> necessary for any debugging purposes, I can probably set this up.

And you have disabled cross-source EIT, right? Otherwise, TTBOMK, it
would (and should) do exactly what you're saying it does.

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
Zitat von "Michael T. Dean" <mtdean@thirdcontact.com>:

> On 08/16/2010 06:23 PM, MythTV wrote:
>> #7672: Guide not populated with EIT from 2nd card
>> ---------------------------+------------------------------------------------
>> Reporter: jan@… | Owner: stuarta
>> Type: defect | Status: assigned
>> Priority: minor | Milestone: unknown
>> Component: MythTV - EIT | Version: 0.22-fixes
>> Severity: medium | Resolution:
>> Keywords: | Ticket locked: 0
>> ---------------------------+------------------------------------------------
>>
>> Comment (by jan@…):
>>
>> Quoting Gavin: "To me it's not clear if the issue is that EIT isn't being
>> received from the second card, or if it is and your attempts to combine it
>> have not worked out. Those are two separate issues, and will require
>> different debugging efforts, I'm sure."
>>
>> The EIT is received on both cards, AFAICT. At least it works on both cards
>> for any channels that are only available on one of those cards. It just
>> doesn't work if a channel exists on both cards. In this case the EPG is
>> only filled for the channel on one of those cards. I can't easily test
>> this at the moment, because in the meantime the affected channel's data is
>> provided by my xmltv provider, so I no longer have to rely on EIT. But if
>> necessary for any debugging purposes, I can probably set this up.
>
> And you have disabled cross-source EIT, right? Otherwise, TTBOMK,
> it would (and should) do exactly what you're saying it does.

No, I have it enabled, like written earlier in the ticket. That's
exactly why I considered it a bug, I expected this setting to do what
I expected.

Jan.

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

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
On 08/17/2010 04:57 PM, Jan Schneider wrote:
> Zitat von "Michael T. Dean":
>> On 08/16/2010 06:23 PM, MythTV wrote:
>>> #7672: Guide not populated with EIT from 2nd card
>>>
>>> Comment (by jan@…):
>>>
>>> Quoting Gavin: "To me it's not clear if the issue is that EIT isn't
>>> being
>>> received from the second card, or if it is and your attempts to
>>> combine it
>>> have not worked out. Those are two separate issues, and will require
>>> different debugging efforts, I'm sure."
>>>
>>> The EIT is received on both cards, AFAICT. At least it works on
>>> both cards
>>> for any channels that are only available on one of those cards. It
>>> just
>>> doesn't work if a channel exists on both cards. In this case the
>>> EPG is
>>> only filled for the channel on one of those cards. I can't easily test
>>> this at the moment, because in the meantime the affected channel's
>>> data is
>>> provided by my xmltv provider, so I no longer have to rely on EIT.
>>> But if
>>> necessary for any debugging purposes, I can probably set this up.
>>
>> And you have disabled cross-source EIT, right? Otherwise, TTBOMK, it
>> would (and should) do exactly what you're saying it does.
>
> No, I have it enabled, like written earlier in the ticket. That's
> exactly why I considered it a bug, I expected this setting to do what
> I expected.

So if you disable cross-source EIT, do you get data for all channels in
both sources? 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?

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
On Tue, Aug 17, 2010 at 2:04 PM, Michael T. Dean <mtdean@thirdcontact.com>wrote:

> On 08/17/2010 04:57 PM, Jan Schneider wrote:
>
>> Zitat von "Michael T. Dean":
>>
>>> On 08/16/2010 06:23 PM, MythTV wrote:
>>>
>>>> #7672: Guide not populated with EIT from 2nd card
>>>>
>>>> Comment (by jan@…):
>>>>
>>>> Quoting Gavin: "To me it's not clear if the issue is that EIT isn't
>>>> being
>>>> received from the second card, or if it is and your attempts to combine
>>>> it
>>>> have not worked out. Those are two separate issues, and will require
>>>> different debugging efforts, I'm sure."
>>>>
>>>> The EIT is received on both cards, AFAICT. At least it works on both
>>>> cards
>>>> for any channels that are only available on one of those cards. It just
>>>> doesn't work if a channel exists on both cards. In this case the EPG is
>>>> only filled for the channel on one of those cards. I can't easily test
>>>> this at the moment, because in the meantime the affected channel's data
>>>> is
>>>> provided by my xmltv provider, so I no longer have to rely on EIT. But
>>>> if
>>>> necessary for any debugging purposes, I can probably set this up.
>>>>
>>>
>>> And you have disabled cross-source EIT, right? Otherwise, TTBOMK, it
>>> would (and should) do exactly what you're saying it does.
>>>
>>
>> No, I have it enabled, like written earlier in the ticket. That's exactly
>> why I considered it a bug, I expected this setting to do what I expected.
>>
>
> So if you disable cross-source EIT, do you get data for all channels in
> both sources? 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?
>
> Mike


Ping.

Closing ticket in 72 hours if there is no further discussion.

Robert
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
Zitat von "Michael T. Dean" <mtdean@thirdcontact.com>:

> On 08/17/2010 04:57 PM, Jan Schneider wrote:
>> Zitat von "Michael T. Dean":
>>> On 08/16/2010 06:23 PM, MythTV wrote:
>>>> #7672: Guide not populated with EIT from 2nd card
>>>>
>>>> Comment (by jan@…):
>>>>
>>>> Quoting Gavin: "To me it's not clear if the issue is that EIT isn't being
>>>> received from the second card, or if it is and your attempts to combine it
>>>> have not worked out. Those are two separate issues, and will require
>>>> different debugging efforts, I'm sure."
>>>>
>>>> The EIT is received on both cards, AFAICT. At least it works on both cards
>>>> for any channels that are only available on one of those cards. It just
>>>> doesn't work if a channel exists on both cards. In this case the EPG is
>>>> only filled for the channel on one of those cards. I can't easily test
>>>> this at the moment, because in the meantime the affected channel's data is
>>>> provided by my xmltv provider, so I no longer have to rely on EIT. But if
>>>> necessary for any debugging purposes, I can probably set this up.
>>>
>>> And you have disabled cross-source EIT, right? Otherwise, TTBOMK,
>>> it would (and should) do exactly what you're saying it does.
>>
>> No, I have it enabled, like written earlier in the ticket. That's
>> exactly why I considered it a bug, I expected this setting to do
>> what I expected.
>
> 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?

Jan.

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

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
On 08/21/2010 02:21 PM, Jan Schneider wrote:
> Zitat von "Michael T. Dean":
>> On 08/17/2010 04:57 PM, Jan Schneider wrote:
>>> Zitat von "Michael T. Dean":
>>>> On 08/16/2010 06:23 PM, MythTV wrote:
>>>>> #7672: Guide not populated with EIT from 2nd card
>>>>>
>>>>> Comment (by jan@…):
>>>>>
>>>>> Quoting Gavin: "To me it's not clear if the issue is that EIT
>>>>> isn't being
>>>>> received from the second card, or if it is and your attempts to
>>>>> combine it
>>>>> have not worked out. Those are two separate issues, and will require
>>>>> different debugging efforts, I'm sure."
>>>>>
>>>>> The EIT is received on both cards, AFAICT. At least it works on
>>>>> both cards
>>>>> for any channels that are only available on one of those cards. It
>>>>> just
>>>>> doesn't work if a channel exists on both cards. In this case the
>>>>> EPG is
>>>>> only filled for the channel on one of those cards. I can't easily
>>>>> test
>>>>> this at the moment, because in the meantime the affected channel's
>>>>> data is
>>>>> provided by my xmltv provider, so I no longer have to rely on EIT.
>>>>> But if
>>>>> necessary for any debugging purposes, I can probably set this up.
>>>>
>>>> And you have disabled cross-source EIT, right? Otherwise, TTBOMK,
>>>> it would (and should) do exactly what you're saying it does.
>>> No, I have it enabled, like written earlier in the ticket. That's
>>> exactly why I considered it a bug, I expected this setting to do
>>> what I expected.
>> 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?

No, cross-source EIT was added specifically for DVB-S users, where it's
not uncommon for the EIT data for a particular mux to be available on a
different mux that, due to MythTV's DiSEqC configuration, is on a
different MythTV video source. So, when enabled, cross-source EIT just
says to put the listings data in the first matching channel--regardless
of video source--and then to stop. It's "cross-source" not
"all-sources", and it's actually a workaround for a design limitation in
the current MythTV.

Daniel explains the details much better than I:
http://www.gossamer-threads.com/lists/mythtv/dev/426781#426781 (and also
provides the approach required to make the workaround unnecessary for
those DiSEqC users).

While "cross-source" and "all-sources" sound very similar, one of the
EIT experts would have to explain why it's not as simple to get
"all-sources" as just not stopping after the first matching channel is
found.

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. So, basically, you would
write a script to use something like tv_grab_dvb or tvgrabeit (which
seems to be called tv_grab_dvb_plus, now) to grab the EIT data from your
source. Then, you would use mythfilldatabase --file to load the data
multiple times, once for each source that contains the channel(s) for
which you need listings. I wouldn't be surprised if someone out there
has scripts for making sure that tv_grab_dvb* runs at a time that won't
affect MythTV recordings and such.

Thanks for the follow-up.

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
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.

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
On Sat, 2010-08-21 at 20:21 +0200, Jan Schneider wrote:
> > 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?

No, it's intended to allow you to fill in the program information
for one channel on one source. It is a hack to allow you to get
program information when in a DVB-S situation where you need to
define multiple sources in MythTV for programming source distributed
across two, three or four LNB polarizations; where all the EIT
information is sent on one channel in one of those sources.

The cross-source EIT hack will be removed once the DiSEqC info is
linked more intelligently to the dtv_multiplex rows and one source
can be defined for all polarizations on the same bird & frequency.

-- Daniel

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: [mythtv-commits] Ticket #7672: Guide not populated with EIT from 2nd card [ In reply to ]
Zitat von "Michael T. Dean" <mtdean@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/

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev