Closed psyborg55 closed 2 years ago
Should be fixed now and/or occurs because of non-blindscan-supporting driver
still there
Which card is this? m88rs6060 has some missing features. Of course it could be a bug, but on stid135 it is correct. You can check /var/log/debug to find some clues about what might be wrong. Specifically the matype value seems to be wrong. Or perhaps you are using outdated versions of software
still m88ds3103. latest revision built yesterday, and latest drivers as well. did you check other cards like stv or tas2101? if it is driver problem i'll look into that, its just i thought more likely a neumodvb problem
I do not have time to check all cards all the time and each time I do there are problems to be found.
I would advise first to see what matype NUMBER the drivers return to user space. The idea is to use this as the "normative" value. Usually this is read from the stream. In some cases I had to reconstruct it (in the drivers) from other pieces of information. I usually trust the value of tbs6909x most
Note that from time to time the cards return wrong information. It is rare though
in positioner dialog there is ACM/VCM indication highlight for all streams (CCM) see screenshot in https://github.com/deeptho/neumodvb/issues/15