[mythtv-commits] Ticket #8501: DVB-S: Same transponder frequency, different polarity (h/v) problems

[MythTV]

#8501: DVB-S: Same transponder frequency, different polarity (h/v) problems
--------------------------------+-------------------------------------------
 Reporter:  frozball@…          |       Owner:  stuarta   
     Type:  defect              |      Status:  accepted  
 Priority:  minor               |   Milestone:  0.24      
Component:  MythTV - General    |     Version:  0.23-fixes
 Severity:  medium              |     Mlocked:  0         
--------------------------------+-------------------------------------------

Comment(by frozball@…):

 That patch had a number of problems. I've attached a modified patch which
 I've tested to work on DVB-S2 only using your patch as a starting point.
 Please feel free to change it to suit the style of MythTV etc (I'm mostly
 a python developer):

 * First of all, the polarity signed char needed to be added as a string of
 v/h in the SQL queries (it was being added as an integer)
 * My Twinhan AD-SP400 with the alpha mantis drivers (DVB-S2) wasn't being
 scanned in "DVB" mode ("sistandard" was a blank string when scanning using
 channels.conf) so I made it to always check polarity if it's > 0
 * I modified the UPDATE query in "insert_dtv_multiplex()" so that it
 doesn't overwrite every mux at that frequency with the supplied polarity
 when inserting additional new channels

 Also, was there a reason for using 'QString("%1").arg((char)polarity)'
 instead of the shorter "QString(polarity)"? If there was, please change it
 in "get_dtv_multiplex" :-)

 One possible side effect is if the polarity it is case insensitive - if
 polarity can be V/H as well as v/h please take that into consideration.

 Thanks,
 - David Morrissey

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