All,
Some of you have already noticed that the new DVB rewrite has been merged with master. Apologies that I forgot to post something about it before doing the merge.
The DVB engine has been completely re-written, and this has required a complete shift in configuration. Far too significant for the code to easily auto-migrate.
Clearly its caused some significant confusion to some users, since things are quite different and configuration appears to disappear etc..
I would strongly recommend that unless you're interested in testing out and helping to improve the new code, which is certainly a departure from the old and therefore still needs time to mature before its ready for release, that you switch to something more stable. To appease those that were used to the previous state of master I build a new DEB and placed it in the beta repository.
For those that still want to try the new code, you have 2 options:
1. Start again, completely fresh DVB configuration. There are some advantages to this, not least to me as it'll tell me what might be broken/difficult to understand about that. However I can appreciate that many of you, myself included, may have nicely crafted channel lists etc.. and not want to lose these.
2. Migrate the configuration, this is currently a semi-automatic process. Given the rather dramatic change in DVB configuration, it has been decided that an external script will do the migration (or at least most of it). Eventually I might build this into the DEB install (at least for the standard location), but not yet.
Migration
To run the migration script you will need to download the script (I've not yet included into the deb), https://github.com/tvheadend/tvheadend/raw/master/support/conf_migrate.py
./conf_migrate.py PATH_TO_TVHEADEND_CONF_FOLDER
Note: the above is not .hts, but the tvheadend subfolder.
After this all your channels and related configuration will have been migrated. All DVB multiplexes and services should also have been migrated. However you will need to re-configure your tuners (including Satellite config). Unfortunately migrating these isn't trivial, but setup shouldn't be too hard. See the next section for detail and just skip the bits you don't need.
New Setup
For the new DVB code, things have been re-organised with the hope of trying to make it easier to manage the DVB configuration. In particular where users have multiple tuners. The DVB config is now split into 4 sections:
* Inputs - DVB tuners
* Networks - The collection of muxes that a tuner can receive (or in the case of DVB-S, can receive from a given orbital position)
* Muxes - Standard DVB definition, a collection of services sent by the provider
* Services - Standard DVB definition, a given service/channel within a mux
To configure a single DVB network do the following:
1. Go to Configuration -> DVB Inputs -> Networks
2. Click "Add"
3. Select the type (DVB-S/T/C, ATSC)
4. Fill in a name, just for your own sanity and debug output. You can usually leave the defaults.
5. If you want to add a pre-configured network (set of muxes) then select from drop down.
6. If not, the go to Configuration -> DVB Inputs -> Muxes
7. Click "Add"
8. Select the network you're adding to.
9. Fill in the Mux settings (if you don't know these, you probably should use a pre-configured set)
This will be roughly the point at which the migration script will leave you, for those that have gone down that route.
10. Go to Configuration -> DVB Inputs -> Tuners
11. Select the relevant frontend device and tick enabled.
12. For non-DVB-S you should select network you want to link to this tuner.
13. If this is DVB-S then select the type of DiseqC arrangement (if you don't know what that should be, just select LNB only, default).
14. Hit Save
15. For DVB-S you need to select the appropriate sub-entry for your DiseqC config (either switchport or LNB)
16. Select appropriate network
17. Hit Save
If you have multiple tuners receiving the same network, then repeat the steps for each.
For those with DVB-S rotors or uncommitted switches I'm afraid the config is still a bit cumbersome. I will try and document it, but for now best to pop along to #hts.
If you go to the "Network" configuration tab, you should be able to watch the progress of the initial scan.
Well I'm sure there will still be plenty of teething problems, and I wouldn't expect a 4.0 release for sometime yet. But hopefully this will be enough to get people going.
Adam
