Open masjerang opened 4 years ago
Hi,
the warning message "WARNING Detected dvbloopback" got my interest. I had a quick look into the source code and found this interesting comment:
https://git.linuxtv.org/v4l-utils.git/tree/lib/libdvbv5/dvb-dev-local.c#n453
So it seems that the developers are aware that dvbloopback is (was?!) broken at some point in time ("in recent kernels"). Maybe there are some fundamental issues with dvbloopback, or dvbloopback is no longer broken but a check for dvbloopback stops it from being used as intended.
Regards, Florian
Hi Florian,
There a couple of references to dvbloopback. I believe the FE_GET_FRONTEND issue they mention should be fixed now. Let me play around with this libdvbv5 and see if things still work without the special dvbloopback conditions/clauses. Not sure if it is related to the CRC mismatch, but again something interesting to find out. Thanks!
Just a quick comment: I've removed the dvbloopback specifics out of libdvbv5 and nothing changes. 'dvbv5-scan' gives the same results, including CRC error. Even by bypassing the CRC check, the scan does not report any proper channels.conf, while doing this on the physical adapter works perfectly. Using the 'scan' utility on the dvbloopback adapter does give good results.
I believe this is a descrambler issue, but could also be dvbloopback. CRC of certain tables is failing using descrambler/dvbloopback, doing a channel-scan using dvbv5-scan. In the example it below, it fails with 'table ID 0x00, program ID 0x00', but it fails also with other tables.
See response of virtual adapter:
See response of physical adapter:
< break >