Tvheadend

I'm not quite sure where to post this, but this category seemed the most appropriate.

I'm in the process of trying to add/create a CableCARD network and associated support types, but am running into several roadblocks based upon Tvheadend's heritage. It's quite obvious when looking at the sources that Tvheadend was primarily/originally developed for DVB inputs. While ATSC and similar broadcast types have been supported, the needs of these other broadcast types have shown up in the source as DVB derivatives.

Even while looking at the IPTV sources, or even the newer TS file types, the heritage for DVB is quite evident. Even attempting to subclass (for lack of a better term) the generic mpegts_network type necessitates bringing in DVB specific headers for what should be TS/PS/ES/PES only needs. Similarly, while trying to look at EPGGrabbers, especially for internal structures, the reliance on DVB is still evident.

I know that separating the generic MPEG-TS structures is mostly done, but the overall structures of network/mux/service still favor the DVB origins. As such, it makes extending TVH to include similar MPEG-TS networks (and their associated inputs), such as CableCARD, difficult as it introduces more points for error than necessary. While I have a rough skeleton of how such a network would work, it does include working around the DVB-specific bits of code inherent to Tvheadend's paradigm.

While this isn't necessarily a call for refactoring, such a result would not be remiss. TVH's documentation is lacking (XML/JSON HTTP, current HTSP ...), and as such, perhaps after 4.4, it's time to look at the project's structure. A more general look at networks, inputs, streams and subscriptions might help to make both configuration easier for end users, as well as making the platform easier for developers to contribute.