lincoln at performaplus
May 14, 2012, 8:12 PM
Post #1 of 1
(224 views)
Permalink
|
|
[Mythtv 0.25pre] Cross sourcing of EIT for usage with set top boxes
|
|
Hi all, sorry if this is repeated but I never got any replies (April
30th) and wasn't sure whether it had sent properly, so here it is
again (although I'm now nearly finished but advice is always good :-)
).
---
Hi all. I'm new to the mailing list so I hope I am going about this
the right way... feel free to correct me if I'm not.
In New Zealand there is 8 days of good DVB-S guide data. Since about
0.21 I have modified my mythbackend in each release so that my DVB-S
card gets EIT guide data for my set top box (on another videosource)
as well as its own dvb-s source. This works well but my patch has
always been more of a hack and required tweaking the database. In the
0.25 version I thought I would do it properly and try and submit the
changes.
The aim is to allow for better cross sourcing of EIT guide data for a
set-top-box connected to a 'cross sourcing' video source type. It uses
the analogue video feed mixed with a digital scan to populate
transport info.
- I have added a cross sourcing videosource to mythtv-setup which
allows seperate input selection for both eit data and transport
scanning.
- You can scan and add channels with a dvb-s card to the 'cross
sourced' videosource using the selected 'scan' cardinput but still
have it's video feed mapped to something like an s-video card input.
The sourceid information has been removed from cardinput.sourceid and
placed in a new table videosourcemap which links cardinputs to a
sourceid with a map link type (main, eit, or scan).
I have also found a couple of small type casting bugs (negative int
being passed to uint etc) and have corrected these.
I'm now modifying mythbackend to use the videosourcemap table and
don't have much more to do. EITcache already applies the eit guide
data across multiple videosources provided than channel.serviceid and
channel.mplex idea are specified.
So thats it so far. I'm no expert C++ programmer but have been slowly
working through the task. Does anyone have any thoughts or
suggestions?
As far as patch submission goes, should it just put this with the
trunk version?
Also is just one big diff file containing all the code changes for all
programs ok?
Thanks,
Lincoln
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-dev
|
