Project

General

Profile

Tvheadend dvb config revamp » History » Revision 3

Revision 2 (Andreas Smas, 2010-03-13 22:46) → Revision 3/15 (Andreas Smas, 2010-07-04 09:12)

There are a few problems with how the TV adapter tab is implemented today 

  * It cannot handle a large amount of services. With DVB-S you can easily hit >1k services. Ticket #100 
  * It's hard (but possible via sorting) to see which services that is transmitted on which mux. 
  * The DVB satconf solution is a bit cumbersome 
  * Updates to the quality meter indicator refreshed the grid in a way that is bad UX. Ticket #108 

 = A rough plan how to redesign improve the DVB configuration TV adapter tab = 

 == Device tree Phase 1 == 

 This 

  * Switch to a [http://remotetree.extjs.eu/ tree will present the available devices to the user view]. 

 {{{ 
   + DVB DVB-C Adapter #1 
   | + DVB-C Frontend 390kHz 
   |     + BBC 
   |     | + DVB Adapter #2 Video (PID 1000) 
   |     | + DVB-T Frontend Audio (PID 1001) 
   |     + DVB-C Frontend CNN 
   | 
         + DVB Adapter #3 Video (PID 2000) 
   |       + Audio (PID 2001) 
   + DVB-S Frontend Adapter #2 
   | | + Switchport 1 
   | | + Switchport 2 11,5GHz Vertical 
   | |     + Switchport 3 Canal+HD 
   | |       + Switchport 4 Video (PID 1231) 
   | |       + Audio (PID 4441) 
   | + Switchport n 2 
   | | + DVB-T Frontend 11,5GHz Vertical 
   | |     + Canal+HD 
   | |       + V4L Adapter #1 
     Video (PID 1231) 
   | |       + Tuner 
     + Composite 
     + S-Video Audio (PID 4441) 
 }}} 

 Pressing 


  * When clicking on a node in the tree a pane to the right will present the user open with information about parameters configurable for that particular node. 

  * Another side effect of this change is that the entry and a few on disk configuration options as follows: 

 === DVB / ATSC Adapter === 
 ==== Info ==== 
 Various information about will be redesigned so the hardware 
 ==== Config ==== 
  * Enable/Disable adapter 


 === DVB-C / DVB-T / ATSC Frontends === 
 ==== Info ==== 
 TBD 
 ==== Config ==== 
  identifiers are not bound into the transport and mux identifiers 

 == Phase 2 == 

  * Network Slave devices. 
    Any point in the frontend is attached tree that have muxes underneath it (DVB-C adapters, or DVB-T switches, etc) it will be possible to 
  * reconfigure that node into a slave mode meaning that it will follow another node in the tree. In other words. If this device may update you have 3 DVB-C adapters all connected to the same network configuration 


 === DVB-S Frontends === 
 ==== Info ==== 
 TBD 
 ==== Config ==== 
  * Number of Diseqc switchports 
  or  
  * Network you can make the frontend is attached to 
  * LnB configuration 

 === Switchport === 
 ==== Info ==== 
 TBD 
 ==== Config ==== 
  * Network second and third just follow the switchport is attached to 
  * LnB configuration 
 

 === V4L adpater === 
 ==== Info ==== 
 Various information about the hardware 
 ==== Config ==== 
  * Enable/Disable first one in terms of configuration. Note, there will still be separate instances of each other so if one adapter 
 

 === V4L frontends === 
 ==== Info ==== 
 Various information about get signal reception problems for whatever reason it will be ranked down by the hardware 
 ==== Config ==== 
  * TV system type (PAL, NTSC, etc) (for tuners) 
  * Network the frontend is attached to scheduler.