[mythtv-commits] Ticket #13121: Sat>IP client support

[MythTV]

#13121: Sat>IP client support
--------------------------------+-------------------------------
 Reporter:  cg@…                |          Owner:  Klaas de Waal
     Type:  Patch - Feature     |         Status:  assigned
 Priority:  minor               |      Milestone:  32.0
Component:  MythTV - Recording  |        Version:  Master Head
 Severity:  low                 |     Resolution:
 Keywords:                      |  Ticket locked:  0
--------------------------------+-------------------------------

Comment (by Klaas de Waal):

 Current status:
 - Supports DVB-C/T/T2/S/S2
 - Does NOT support DiSeqC yet
 - Supports channel scans
 - Tested with minisatip (DVB-C/T2/S/S2) and with the Telebit Digibit R1
 box (DVB-S/S2)
 - No crashes observed for some time now

 Implementation details that might be improved:
 - Open/close code. Channels are always kept open because opening and
 closing gives all kinds of errors.
 - Reducing the RTP packet processing interval from 200 to 20 ms does fix a
 problem with missing RTP packets in MPTS recordings but there is no
 logical reason why this should make a difference. A possible reason can be
 the implementation of the underlying packetbuffer code because random
 numbers are used to identify packets and there is always a risk of
 collusion when storing a large number of packets.
 - Channel scans work OK but sometimes the PAT of the previous transport is
 processed. This does cause a timeout but the scan results are OK. The
 difficult part is here that MythTV assumes that as soon as a tuning
 command is given that everything that is received after that is from the
 requested frequency. This is not really true in networked environments
 where packets are buffered. One possible solution, which would improve
 scanning for all tuner types, is to filter on transport ID when that is
 known. This requires storage of the transport ID in table dtv_multiplex
 and it somehow changes the concept of tuning from tuning to a frequency
 into tuning to a transport ID.
 - Tuning timeout default values are quite high and are correct for
 DVB-S/S2 but could be reduced for DVB-C and DVB-T2. The actual values can
 of course be configured in the Capture Card page of mythtv-setup.

-- 
Ticket URL: <https://code.mythtv.org/trac/ticket/13121#comment:37>
MythTV <http://www.mythtv.org>
MythTV Media Center