…e CI menu callbacks are not available*.
…hanges are based on feedback from paalkr's tests with a TerraTec H7 and a Twinhan AD-TP300.
…er. This seems to have been causing problems for the TerraTec H7.
1. Fix CI state handling for tuners using CI API v1. 2. Add hack to support old stable TerraTec and TechniSat drivers that incorrectly register the tuner filter as a capture filter.
…neState() to use the new generic tone state enums merged from my main branch.
…rt_cleanup_and_extension' into Twinhan
…hese as interface parameters and in places where generic references to these states are required. Many hardware providers will have their own slightly different versions of these enums so values may need to be translated. Note: I'm not sure if I've put these in the right place, however they can easily be moved later if necessary.
… SVN working copy.
…s basically a complete rewrite. Improvements: - fix/add CAM menu support for devices using version 2 of the Twinhan CI API - experimental support for PID filtering (not enabled) - experimental support for custom tuning interface (not enabled) - logging of tuner hardware, driver and CAM information Changes: - refactor SendPmt() to support multi-channel decryption easily in the future - fix conditional access AllowStopGraph() logic for paalkr's TerraTec H7 Still TODO: - find a solution for paalkr's H7 problems. I don't like the AllowStopGraph() hack at all even if it does work. - move the Twinhan tuning parameter translations into the Twinhan class - improve CAM state change detection when the MMI handler loop is not running - attempt to fix TerraTec Cinergy C/S2 CAM menu support - unfortunately TerraTec seems to have customised their drivers to use a different interface for GetMmi(). This breaks CAM menu handling completely. I've emailed and requested an updated SDK (again).
…n to new
…cause_black_screen' into Release_1.2.x