* Avoid extracting persistent data (such as video width*height) from
received data if we suspect that an error has occured (MPEG-TS TEI or
continuity counter errors).
* Add src/plumbing/tsfix.[ch]: Streaming code that fixes up missing
timestamps and normalize timecode to start at 0.
* Move PTS estimation code and timestamp normalization out from central
parse code. Subscribers that really needs it should use tsfix plumbing
instead.
* Let DVR code use tsfix plumbing.
* Don't send "pts" and "dts" over HTSP if timestamps are missing.
- Each adapter have three (or four) tabs
o General setup and information
o Grid of multiplexes
o Grid of services
o For sattelite adapters, a sattelite configuration tab.
* Add support for disabling / enabling an entire DVB multiplex
* Add support for multiple DiSEqC switchports on a single adapter
* Add support for different sattelite LNBs
* Graceful handling of DVB adapters that does not support many
table filters in hardware. Tvheadend will rotate among the available
ones.
* Add support for enabling / disabling transports from the DVB configuration
* Make it possible to remove DVB multiplexes from the web ui
* Add 'Revert changes' button to all editable grids in the web ui
* Make it possible to disable the idle scan on per-DVB adapter basis.
The idle scan is a process to cycles through all multiplex to check
the quality for each mux continously.
No streaming support yet but we are able to do these things:
* Notify clients about channel add/update/delete
* Notify clients about tag add/update/delete
* Respond to EPG queries
poll/dispatcher framework.
The top reasons for going multithreaded is:
* Take adventage of multicore CPUs
* No need to put slow operations in ugly helper threads now that the entire app is designed for multithreads
* Some of the timing sensetive tasks (IPTV output / RTP / UDP pacing) can run on RT priority.
