Doesn't recognize DVB card

[Dis]

Yeah in /var/opt/nextpvr there's only one adapter .conf. I included screenshot from settings -> devices.

[mvallevand]

There could still be permission issues, that we are not aware of.

For now you can manually copy the adapter 0 one to the other 3.

sudo -u nextpvr cp /var/opt/nextpvr/adapter0-DVB-C-channels.conf /var/opt/nextpvr/adapter1-DVB-C-channels.conf
sudo -u nextpvr cp /var/opt/nextpvr/adapter0-DVB-C-channels.conf /var/opt/nextpvr/adapter2-DVB-C-channels.conf
sudo -u nextpvr cp /var/opt/nextpvr/adapter0-DVB-C-channels.conf /var/opt/nextpvr/adapter3-DVB-C-channels.conf

I am worried about an error on adapter0 too but let's see if this helps.

Martin

[Dis]

New logs. Still freezes after few times changing channel.

[mvallevand]

That's better but the error that I am worried about still is there so sub will need to investigate

19:56:19:852 [ERROR] dvb_fe_set_parms failed

Martin

[Dis]

These outputs of service nextpvr-server status is taken while channel playback is frozen.

nextpvr-server status before starting channel on webserver

telkka@telkka:~$ service nextpvr-server status
● nextpvr-server.service - NextPVRServer
Loaded: loaded (/usr/lib/systemd/system/nextpvr-server.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2021-08-29 20:13:36 EEST; 7min ago
Process: 1839 ExecStart=/opt/nextpvr/shell/server.sh start (code=exited, status=0/SUCCESS)
Main PID: 1851 (dotnet)
Tasks: 30 (limit: 9322)
Memory: 204.0M
CGroup: /system.slice/nextpvr-server.service
├─1851 /opt/dotnet/dotnet /opt/nextpvr/system/NextPVRServer.dll
└─1935 /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -listen:44029 -typeVB-C -device:adapter3/frontend0 -instance:1 -parent:1>

Aug 29 20:13:34 telkka systemd[1]: Starting NextPVRServer...
Aug 29 20:13:36 telkka server.sh[1839]: Starting server..Done. PID=1851
Aug 29 20:13:36 telkka systemd[1]: Started NextPVRServer.
Aug 29 20:14:49 telkka server.sh[1935]: ERROR FE_SET_PROPERTY: Bad file descriptor

After starting channel on webserver
telkka@telkka:~$ service nextpvr-server status
● nextpvr-server.service - NextPVRServer
Loaded: loaded (/usr/lib/systemd/system/nextpvr-server.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2021-08-29 20:13:36 EEST; 8min ago
Process: 1839 ExecStart=/opt/nextpvr/shell/server.sh start (code=exited, status=0/SUCCESS)
Main PID: 1851 (dotnet)
Tasks: 42 (limit: 9322)
Memory: 232.7M
CGroup: /system.slice/nextpvr-server.service
├─1851 /opt/dotnet/dotnet /opt/nextpvr/system/NextPVRServer.dll
├─1935 /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -listen:44029 -typeVB-C -device:adapter3/frontend0 -instance:1 -parent:1>
├─2286 /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -listen:38285 -typeVB-C -device:adapter2/frontend0 -instance:1 -parent:1>
└─2299 ffmpeg -y -i http://127.0.0.1:8866/live?channeloid=71...b-d3ef-48d>

[mvallevand]

Yes I have seen that error before and sub has looked at it but it isn't resolved. This sequence looks odd to me. The bad file descriptor messge makes me think the tuner is closed when the second tuning call is made.

Code:

19:56:19:841 [DEBUG] starting stream: LIVE&/home/telkka/recordings/live-MTV3 HD-3700-5.ts
19:56:19:841 [DEBUG] slip seconds: 1200
19:56:19:841 [DEBUG]
MTV3 HD
19:56:19:849 [INFO] Tuning: 130000000 Hz
19:56:19:849 [INFO] Changing frequencies
19:56:19:849 [INFO] Stopped recording (/home/telkka/recordings/live-Nelonen HD-3700-4.ts)
19:56:19:852 [INFO] Tuning: 130000000 Hz
19:56:19:852 [ERROR] dvb_fe_set_parms failed

Martin

[Dis]

What is weird is when I look timestamps of log files it looks like it is only using one adapter. 1957 log files it is device-adapter3
Or is that normal behavior?

[mvallevand]

All normal. The default for Live TV is reverse tuner priority order (you set the order via the web app). From the same client the same tuner will become priority as it switches off.

Martin

[Dis]

Okay good to know. So for example if I had recording for different channel, recording can use different adapter than live tv?

[mvallevand]

Yes recording start at the highest priority. Some digital tuners allow multiple mux capture, so you can have more recordings or live tv channels then tuners.

Martin