This is a new BDA interface wrapper for AltDVB v2.2.

The configuration file (Dev_Bda2Driver.cfg) should be placed in the same folder
as the interface (Dev_Bda2Driver.int). If this file doesn't exist, the interface driver
will create a new one with default values.

DVB-S2 signalling:
TechnoTrend users - no change neccessary (DVBS2Signalling signalling value is the default 8VSB)
KNC One users     - change the DVBS2Signalling signalling value to: 8PSK
Hauppauge users   - change the DVBS2Signalling signalling value to: NBC_8PSK
all other         - try 8VSB or 8PSK

S/S2 Pilot and S2 Roll Off:
these values are for the Haupppauge drivers and practically should not be changed

v 0.1.0.11 - 2008.01.28
----------

- new implementation of raw DiSEqC support for Technotrend budget
  warning: DiSEqC works only with Technotrend BDA drivers v.4.4.10.x! The v5.0.0.x series does NOT
           support DiSEqC
- Hauppauge DVB-S2 tuning still in beta phase

v 0.1.0.10 beta - 2008.01.25
----------

- added support for Hauppauge proprietary interface (8PSK tuning
  and DiSEqC)
 
v 0.1.0.9
---------
- private TT DiSEqC test release

---------
v 0.1.0.8 - 2007.11.24
---------

- fixed tuning for Airstar-2 with final BDA 4.4.1 drivers
- removed "failed put_FrequencyMultiplier" message, most drivers don't implement it

v 0.1.0.7 - 2007.11.20
---------

- fixed bug when tuner reports signal statistics on more than one topology node

v 0.1.0.6 - 2007.11.19
---------

-code cleanup

v 0.1.0.4 - 2007.11.15
---------

- fixed bug for TwinHan AD-SP400 CI
- fixed bug for DVB-C Twinhan 2033 Mantis
- fixed bug in put_Range introduced in a private release
- code cleanup

v 0.1.0.2 - 2007.11.14
---------

- fixed bug for KNC One
- added configuration file
  a) those that can't tune to DVB-S2 channels try changing the default 8VSB
     to 8PSK value - newer drivers use new value for 8PSK signalling
  b) DiSEqC configuration for now is always COMMITED

v 0.1.0.1 - 2007.11.12
---------

- fixed bug when there is no seperate Capture filter
- fixed bug with hard-coded LowBandF, HighBandF, SwitchF for DVB-S tuning
- added more error logging
- tweaked tuning


v 0.1.0.0 - 2007.11.09
---------

A few weeks ago I have decided to try to write an alternative BDA device interface
for AltDVB v2.2.0 build 3912 for my TT S2-3200 card with v5.0.0.x BDA drivers.
It might work with other BDA compatible devices (DVB-S/T/C), but no guarantee is given.

1) please don't ask me for the device interface SDK for AltDVB v2.2 since I
   simply don't have it (the knowledge to write this implementation was gathered
   just by observing when and which information is exchanged between the main
   application and the original Dev_BdaDriver.int)
   - I might release in the future my knowledge on the device interface
   - if AltX wishes that this information shall not ever be disclosed I will honor
     his decision
   - no, I am not in any contact with AltX, nor know his whereabouts
     (wish him all the best though :)

2) it might work with other BDA compatible devices, but no guarantee is given

3) Technotrend's BDA drivers (still) have difficulties with DiSEqC 1.0 under BDA,
   especially when tuning to 8PSK transponders

4) DVB-S support has been tested only with the TT S2-3200 card (aka SkystarHD)

5) DVB-T support has been tested only with the TwinHan MagicBox Pro VP-704A
   (aka Pinnacle PCTV-310e)

6) don't have access to DVB-C hardware, so it's not tested at all

7) if you want to report an anomaly/bug/strange behavior please be specific, provide
   as much information as possible about your configuration/ devices etc and
   the log from http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx
   I will try, if my free time permits, to look into the problem

8) CI & IR remote will probably not ever be supported


Parts of my work are based on the work of DCoder, nate et al from the
the DVB Owners Discussion Forum. Good work guys! Cheers.


Diodato

