[mythtv] MythTV DVB Implementation (What's needed & What's not)

[Kenneth Aafloy]

Hi All,

I'm trying to figure out everything DVB related that is required
to match or even superseed comercially available boxes.

           MythTV Digital Video Broadcast Implementation Checklist
******************************************************************************
 
Actual DVB & DiSEqC Configuration:
 
 The configuration interface for DVB should be automatic wherever possible,
 but also allow the possibility of manual configuration.

    - Probing of the four cards possible.
    - Automatic entrance into unconfigured cards.
    - Interface for entering configuration for previously configured cards.
 
 Main cardsetup screen.
    In DVB-T or DVB-C this would go straight to a view of channels, DVB-S:
    - Automatic probing for DiSEqC v2.0 compatible devices.
    - Manual 'Tree Like' view of equipment, also with the posibility of
        adding/deleting and configuring existing equipment.
 
 Switch configuration screen.
    - Switch type (DiSEqC 1,1.2,2 / Tone Burst).
    - Number of ports.

 LNB configuration screen.
    - LNB Type (Universal/Old).
    - Satelite ID (0=motor).

 Motor configuration screen.
    - Current position and satelite ID.
    - Listview of Satelites configured.
    - Steering Motor East/West.
    - Setting East/West Limits.

 Satelite configuration screen.
    - Listview of channels.
    - Load channels from external source.

 Channel configuration screen.
    - Frequency.
    - (DVB Type specific options).


                            COMMENTS & NOTES
*******************************************************************************


1. Rebuild of Configuration Interface in MythTV

 Moving the backend configuration interface to mythfrontend would increase
 configurability both for the user and for the developer
    (Yes, I know it's possible to just modify the menu).

 Benefits for the users would be that hardware setup of any local/remote backend
 is configurable from any frontend.

 Developer benefit would be that one could incorporate the player into the setup
 process, and at any point in the configuration process show to the user what
 results the configuration gives. This could be when a user wants to realign
 a satelite position on a DiSEqC motor, or act just as a visual aid when
 setting up preferences for encoding.

 Also, the need for a more flexible dynamic configuration interface is needed,
 as the current implementation is extremly static, once the ui is shown to the
 user (this could be done in Myth's base classes, so that all of the UI could
 benefit from this extension).

 I would suggest a more linear method of setting up a card configuration,
 where the first screen (with new setup|card) would be a plain screen
 with buttons for each of the cardtypes currently supported.

 The user would then be brought through the configuration for this specific
 cardtype and other common setup options from start-to-end.

 With reusable objects in mind, this would be a very solid method for
 configuring both cards and backends.

2. ____


Kenneth