I don't think this is a good approach. It is better to handle the problem automatically (during the tunning procedure).
It is working during the tuning procedure and, no need to modify the xml.I don't think this is a good approach. It is better to handle the problem automatically (during the tunning procedure).
And you don't have to modify the existing xml files(tunning lists).
Yes, but only for single transponder!It is working during the tuning procedure and, no need to modify the xml.
Simply change 4 digits to 7 digits.
Also working for transponder list.Yes, but only for single transponder!
Consider a new user not knowing anything about this issue. It will not work for standart scanning process (by Country).
But how? If the list uses value 6900(standard ksymbol), then this value wil be used for BDA tunning setting. And this is why it currently doesn't work for the Huppague devices.Also working for transponder list.
As far I know, the standartd represenation is in 'kilo' format (just like frequency). The problem is somehow specific to the Hauppague devices. You can find on the google, that some other applications have similar issue.OK, I agree with.
Then, why reduce this opportunity only for hauppauge cards ? (Maybe there are others ?)
And, why, instead of x1000, not give a way for a personal user value ?