[mythtv-commits] Ticket #5882: S2API support

[MythTV]

#5882: S2API support
-------------------------+--------------------------------------------------
 Reporter:  wagabunda    |        Owner:  janne   
     Type:  enhancement  |       Status:  accepted
 Priority:  major        |    Milestone:  0.22    
Component:  dvb          |      Version:  head    
 Severity:  medium       |   Resolution:          
  Mlocked:  0            |  
-------------------------+--------------------------------------------------

Comment(by anonymous):

 Replying to [comment:16 wagabunda]:
 > > Some more checks in the database reveal that the S2 scan hasn't got
 mplexid right [...]
 >
 > Very important information - thank you. I have to repair.
 >
 >

 There was some confusion about the mplexid. When reporting this I wasn't
 aware that mythtv-setup adds duplicate transports for any transport that
 is manually added in the GUI. Further, one of the transponders I was
 testing with was listed on lyngsat.com to operate at 12130kHz, while after
 manual add and scan it was found to operate at 12128kHz instead which led
 me to suspect this patch. It's probably an error in lyngsat's table
 instead.

 I can now, with trunk (rev 19188) and the latest s2api-patch, scan and
 tune all s2 channels. What remains it to get the back-end to accept and
 store the streams. It may be an issue with my CAM, although it delivers
 good streams when tuned with szap-s2 which can be recorded or played back.
 Mythbackend complains about "PID <varying PID> discontinuity detected",
 "Saw PMT but did not write to disk yet" and "Saw PAT but did not write to
 disk yet". There is unfortunately no unencrypted HD channel available for
 test that would allow me to eliminate possible problems with the CAM.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/5882#comment:38>
MythTV <http://www.mythtv.org/>
MythTV