On 28.11.2017 21:12, Marko Mäkelä wrote:
Hallo Klaus,

On Tue, Nov 28, 2017 at 11:28:13AM +0100, Klaus Schmidinger wrote:
On 27.11.2017 19:55, Marko Mäkelä wrote:
On Sun, Nov 26, 2017 at 07:21:58PM +0200, Marko Mäkelä wrote:
Hi all,

I recently got a USB adapter "Astrometa DVB-T2" that I would like to use with 
VDR. It comprises two frontends:

/dev/dvb/adapter0/frontend0: Realtek RTL2832 (DVB-T)
/dev/dvb/adapter0/frontend1: Panasonic MN88473 (DVB-T2 and DVB-C)

Apart from these files, in /dev/dvb/adapter0 I can see the following:
demux0 dvr0 net0

It seems to me that the dvbdevice.c of VDR 2.3.8 assumes that all these files 
exist for all frontends. But there is no demux1, dvr1, or net1 on my system.

That's right, VDR assumes that if there is a frontend1 there is also demux1
and dvr1.

In dvbdevice.h, I think that the macros DEV_VIDEO, DEV_DVB_VIDEO, DEV_DVB_AUDIO 
are unused and the definitions could be removed.

DEV_DVB_VIDEO is still used by the dvb[sh]ddevice plugins.

Sorry, I should have thought of output plugins. rpihddevice does not refer to 
any of these.

For cDvbTuner::SetFrontend() the cDvbTuner::adapter and cDvbTuner::frontend are already fixed. For my device, frontend0 should only be valid for DVB-T, while frontend1 is valid for DVB-T2 and DVB-C. How to handle these known-invalid combinations? By 'return true'?  Or should I rather hack cDvbTuner so that it opens a file descriptor for each frontend, and then chooses the appropriate one in cDvbTuner::SetFrontend() based on frontendType?

Which devices does VDR create at startup?
Please post the related log entries.

Attached are two complete logs from /var/log/messages for plain VDR 2.3.8 

On both startup attempts, channels.conf (attached) contains only DVB-T2 
entries, and the default channel is free-to-view (YLE TV1 HD). The 
channels.conf was converted by dvb-format-convert version 1.12.3:
dvb-format-convert -I DVBV5 -O VDR dvb_channel.conf channels.conf

The first attempt is with the /dev/dvb/adapter0 as is. VDR expectedly claims 
that it cannot tune to the channel with the DVB-T frontend.

The second startup is for a tweak where I removed /dev/dvb/adapter0/frontend0 and renamed frontend1 to frontend0. On this startup, VDR will not complain anything, but it will not find any signal either. It properly detects the MN88473, but perhaps improperly claims that it provides DVB-T along with DVB-T2 and DVB-C.

Well, from the information that VDR gets from the driver, it does support 
DVB-T, -T2 and -C:

  frontend 0/0 provides DVB-T,DVB-T2,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 
("Panasonic MN88473")

If this is not correct, I assume it's a driver problem.

But since the channel you are initially tuning to is DVB-T2, anyway, it doesn't 
matter if VDR thinks the frontend can handle DVB-T, too.

I'm afraid I can't say why tuning fails, though.


vdr mailing list

Reply via email to