Hi,
I know that there is already a subject opened about a similar issue (link), but this one is actually a bit different.
This card has 2 signal inputs (one for terrestrial and one for Sat).
At the end, the TBS driver creates only 1 adapter but with 2 frontends.
VDR seems to discover them well:
Code
Oct 9 15:16:18 nuc vdr: [11352] probing /dev/dvb/adapter0/frontend0
Oct 9 15:16:18 nuc vdr: [11352] frontend 0/0 provides DVB-T,DVB-T2,DVB-C,ISDBT,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("TurboSight TBS 5520SE DVB-T/T2/C/C2/ISDB-T")
Oct 9 15:16:18 nuc vdr: [11356] frontend 0/0 tuner thread started (pid=11352, tid=11356, prio=high)
Oct 9 15:16:18 nuc vdr: [11352] probing /dev/dvb/adapter0/frontend1
Oct 9 15:16:18 nuc vdr: [11352] frontend 0/1 provides DVB-S,DVB-S2,DSS with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("TurboSight TBS 5520SE DVB-S/S2/S2X")
Oct 9 15:16:18 nuc vdr: [11359] frontend 0/1 tuner thread started (pid=11352, tid=11359, prio=high)
The thing is that it does not handle them well.
When switching from one to the other, it seems to think that there are actually 2 demuxes...
Code
Oct 9 15:18:54 nuc vdr: [11612] switching to channel 4 S19.2E-1-1080-8801 (CANAL+)
Oct 9 15:18:54 nuc vdr: [11612] ERROR (dvbdevice.c,1636): /dev/dvb/adapter0/demux1: No such file or directory
Oct 9 15:18:54 nuc vdr: [11612] ERROR (dvbdevice.c,1940): No such file or directory
Oct 9 15:18:54 nuc vdr: [11612] ERROR: can't set PID 110 on device 2
Oct 9 15:18:54 nuc vdr: [11612] ERROR (dvbdevice.c,1955): Bad file descriptor
Oct 9 15:18:54 nuc vdr: [11675] VAAPI-ERROR: audio/alsa: broken driver 0 state 'RUNNING'
Oct 9 15:18:54 nuc vdr: message repeated 3 times: [ [11675] VAAPI-ERROR: audio/alsa: broken driver 0 state 'RUNNING']
Oct 9 15:18:54 nuc vdr: [11695] device 1 TS buffer thread ended (pid=11612, tid=11695)
Oct 9 15:18:54 nuc vdr: [11694] buffer stats: 155852 (2%) used
Oct 9 15:18:54 nuc vdr: [11694] device 1 receiver thread ended (pid=11612, tid=11694)
Oct 9 15:18:54 nuc vdr: [11675] VAAPI-ERROR: audio/alsa: broken driver 0 state 'RUNNING'
Oct 9 15:18:54 nuc vdr: [11616] frontend 0/0 lost lock on channel 1 (TF1), tp 234
Oct 9 15:18:54 nuc vdr: [11675] VAAPI-ERROR: audio/alsa: broken driver 0 state 'RUNNING'
Oct 9 15:18:54 nuc vdr: message repeated 2 times: [ [11675] VAAPI-ERROR: audio/alsa: broken driver 0 state 'RUNNING']
Oct 9 15:18:54 nuc vdr: [11682] VAAPI-ERROR: video: slow down video, duping frame
Oct 9 15:18:54 nuc vdr: [11682] VAAPI-ERROR: video: decoder buffer empty, duping frame (-424690432/0) 0 v-buf
Oct 9 15:18:54 nuc vdr: [11682] VAAPI: video: --:--:--.--- +0 0 0/\ms 0+1 v-buf
Oct 9 15:18:55 nuc vdr: [11620] ERROR: can't open filter handle on '/dev/dvb/adapter0/demux1'
Oct 9 15:18:55 nuc vdr: message repeated 4 times: [ [11620] ERROR: can't open filter handle on '/dev/dvb/adapter0/demux1']
Oct 9 15:18:56 nuc vdr: [11616] frontend 0/0 timed out while tuning to channel 1 (TF1), tp 234
Oct 9 15:18:56 nuc kernel: [ 4475.589721] si2183 6-0067: read_status fe1 cmd_exec failed=-121
Oct 9 15:18:56 nuc kernel: [ 4475.589729] si2183 6-0067: read_status failed=-121
Oct 9 15:18:56 nuc vdr: [11619] frontend 0/1 lost lock on channel 4 (CANAL+), tp 212012
Oct 9 15:18:56 nuc vdr: [11616] frontend 0/0 regained lock on channel 1 (TF1), tp 234
Oct 9 15:18:58 nuc vdr: [11619] frontend 0/1 timed out while tuning to channel 4 (CANAL+), tp 212012
Oct 9 15:18:58 nuc vdr: [11619] frontend 0/1 regained lock on channel 4 (CANAL+), tp 212012
Alles anzeigen
Has anyone experienced this ?
Thanks!