Adam Sutton [Sat, 21 Dec 2013 22:06:15 +0000 (22:06 +0000)]
mpegts: update to the way init scan table completion is handled
Should be a bit better at handling tables that may or may not exist.
We have an initial timeout after which we check if data for any tables
has been received but incomplete.
This is still far from ideal, really what is needed is to make this
all more async based on when we sync etc... but this will do for now.
Adam Sutton [Wed, 18 Dec 2013 18:53:02 +0000 (18:53 +0000)]
capmt: attempt to avoid confusion over validity of configuration
UI now has 3 possible colours, red - not working, orange - not connected
(but will probably work, used for new non-persistent mode 2) and green -
actively connected.
Adam Sutton [Wed, 4 Dec 2013 23:28:29 +0000 (23:28 +0000)]
tvhlog: stop full debug by default if --trace specified
Often I want to enable trace (and debug) for a specific set of subsys,
but I had it configured to enable ALL debug if any debug related options
were spec'd (for compat). But this was a PITA and I kept doing
--trace blah --debug none just to get around it!
Adam Sutton [Wed, 4 Dec 2013 22:38:44 +0000 (22:38 +0000)]
subscriptions: reverse EPG and initscan priorities
For networks with extended EIT, having EPG take precdence causes chaos
during init scan. The reality is that forcing an EPG scan to stop because
someone wants to scan a new mux is probably the right thing to do anyway.
Adam Sutton [Wed, 4 Dec 2013 22:17:22 +0000 (22:17 +0000)]
tsfile: cmdline flag to specify ATSC input
Previously all standard DVB and ATSC tables were installed, this
would cause the initscan to time out. We try and be more clever
with determining the type, but this will do for now.
The code allows the option to be per mux (file), but the cmdline
is currently limited to a global setting, which is likely to be
more than enough.
The commit fixes simultaneous channel decryption.
We are enumerating services based on the generated seq value.
In fact it should be elementary stream PID, but currently
we can leave it until PMT code rework.
The CA_SET_PID and CA_SET_DESCR from OSCam was always set with
seq=0 leading to setting all keys always to first subscribed
service.
Adam Sutton [Mon, 2 Dec 2013 13:30:59 +0000 (13:30 +0000)]
imagecache: migrate configuration to new API
I started to do this as there was a possible issue with imagecache as a result
of updates. However this has thus far not been proved, but still a useful
update. Hopefully not too broken!
capmt: add simplified OSCam dvbapi protocol as new capmt mode
The new mode uses one domain socket connection for all subscribed
services. The CA_SET_PID and CA_SET_DESCR are received over same
socket connection instead of one UDP socket per adapter.
The minimum OSCam version for use with this mode is svn rev 9063.
Dave Chapman [Thu, 28 Nov 2013 00:50:39 +0000 (00:50 +0000)]
Merge relevant parts of PR#255 to complete the implementation of PAT/PMT passthrough, with the option of rewriting the PAT and PMT so the PAT only contains a reference to the included service, and the PMT only contains references to the included streams. This still needs more work - the PMT PID is being passed to the muxer as zero the first time a channel is streamed after tvh starts, and the PMT rewrite code fails if the PMT spans multiple TS packets
Adam Sutton [Sun, 24 Nov 2013 20:32:15 +0000 (20:32 +0000)]
iptv: added new configuration to allow subs and bandwidth limitations
The bandwidth limit is a soft one, it will stop any new subscriptions if
the peak bandwidth on the current services exceeds the limit. Possibly
this will need a bit of additional averaging in future to stop false
triggers.
Adam Sutton [Mon, 18 Nov 2013 09:21:35 +0000 (09:21 +0000)]
linuxdvb: old code would update tuning params even without auto-discovery
This is important for correcting mistakes in the pre-defined configuration
files, and also picking up potential changes (not sure that will quite work).
The one thing that is left untouched is the frequency, a) to not confuse people
and b) I've seen 2 transponders sending slightly diff freq and this can cause
the config to be constantly updated.
The one thing this will also do, for better or worse, is remove an AUTO
settings. Cons are it could be less flexible an tuners may automatically deal
with small changes in settings, Pro's are if you have some tuners that accept
AUTO and some that don't, once its scanned on something that does it will get
updated. Plus its probably better, where possible, to have the full settings.