Tvheadend-24 » History » Version 1
trac -, 2011-01-01 20:52
Milestone
| 1 | 1 | trac - | Minor feature / bugfix release |
|---|---|---|---|
| 2 | |||
| 3 | == Changelog == |
||
| 4 | |||
| 5 | * Due to a bug, the polarisation of DVB-S muxes was not correctly |
||
| 6 | stored internally. This has now been fixed. |
||
| 7 | |||
| 8 | * Fix compilation on 64bit systems |
||
| 9 | |||
| 10 | * Make sure channel <> service mappings are saved when edited from |
||
| 11 | DVB service grid |
||
| 12 | |||
| 13 | * Add support for merging one channel into another. |
||
| 14 | Useful if you have multiple providers offering the same DVB service |
||
| 15 | but with different names. |
||
| 16 | |||
| 17 | * The embedded HTTP server now logs failed requests |
||
| 18 | |||
| 19 | * Use absolute paths when serving static content (the web app itself) |
||
| 20 | This was only a problem when fork()ing a development build |
||
| 21 | |||
| 22 | * Rework the CWC reconnection strategy. |
||
| 23 | If there are active subscription, Tvheadend will attempt to reconnect |
||
| 24 | immediately and then retry every three seconds. |
||
| 25 | If no subscription is active a reconnection attempt is performed |
||
| 26 | every minute. |
||
| 27 | Also, if any CWC configuration changes are made from the UI, Tvheadend |
||
| 28 | will try to reconnect directly. |
||
| 29 | |||
| 30 | * If the EPG receives an updated description for an even that is shorter |
||
| 31 | than the current description it will be ignored. |
||
| 32 | This typically happens if the XMLTV and DVB EIT (Event Information Table) |
||
| 33 | differs. In other words, we assume that a longer description of an |
||
| 34 | event is better than a short. |