[mythtv-commits] Re: Ticket #343: 'Signal 100% (l ) no lock' and no video with DVB-S and DVB-T

MythTV mythtv at cvs.mythtv.org
Tue Sep 27 09:01:34 UTC 2005


#343: 'Signal 100% (l ) no lock' and no video with DVB-S and DVB-T
-----------------------------------+----------------------------------------
 Reporter:  daniel.danner at gmx.net  |        Owner:  danielk
     Type:  defect                 |       Status:  new    
 Priority:  major                  |    Milestone:  0.19   
Component:  mythtv                 |      Version:  head   
 Severity:  high                   |   Resolution:         
-----------------------------------+----------------------------------------
Comment (by malc at porsche.demon.co.uk):

 Hi,

 I'm using a 2.6.9 kernel (Fedora derivative).

 Interestingly the PCI card works fine 100% of the time, the USB card
 struggles sometimes. Seems to be about 50% of the time. Not associated
 with the presence of the second card, purely associated with the presence
 of the USB based tuner. (USB 2 Nova-T - DiBcom tuner - Hauppauge branded).
 It worked fine with 0.18, with extended timeouts in the hardcoded values.
 The failures are purely random, 3 recordings of different episodes on the
 same channel resulted in only the second one working.

 In addition this is purely associated with changes post 7266 (which I did
 'cos I wanted to get both cards working in a single machine.. and I know
 there were problems with 2 DVB tuners).

 Two thoughts

 '''First''' this is a race condition - the timeout occurs after 20, 30 or
 even 60 secs but no tuning / channel selection occurs. Recording is
 cancelled.

 '''Second''' the signal timeout  I get lines like this, with "timeout (0
 ms)" in them.


 {{{
 SML[2]: Name(seen_pat) Val(0) thr(>=1) range(0,1) timeout(0 ms) is set. Is
 NOT good.
 }}}

 '''Daniel,''' I know the core timeouts come from the DB and that the
 signal timeout  should be less than the channel... but there also seems to
 be code that looks for device timeouts from a strucuture of device info...
 what's happening here? Is it possible not all devices / drivers are
 providing correct timeouts?

 -malc-

-- 
Ticket URL: <http://cvs.mythtv.org/trac/ticket/343>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list