Yesterday, 09:06 PM
Hello ppl,
Summary
I am running the latest ARM64 Docker image of NextPVR on a Raspberry Pi 5.
The DVB-C scan succeeds and channels are imported correctly, but Live TV and recordings always fail with:
The DeviceHost logs show:
The file is either never generated by NextPVR or the DeviceHost expects a different format than the standard DVBv5 tuning files.
Environment
Hardware
Kernel:
NextPVR
Docker image:
Version:
Docker Compose
DVB Devices detected
NextPVR detects both tuners correctly.
Both are shown as
Driver
Kernel modules load correctly.
After reboot there are no I²C errors anymore.
Signal
Signal quality is 37dB.
Example:
DVB Utilities
Tunes correctly.
Works.
It finds over 220 TV services.
is generated.
NextPVR Scan
The channel scan succeeds.
Example from device log:
Channels are found and imported.
Example:
Around 220 channels are imported.
Problem
When starting Live TV:
nrecord.log
NextPVR launches DeviceHost correctly.
Example:
DeviceHost receives:
DeviceHost error
Immediately afterwards:
Then:
Finally:
Important observation
Originally there was no
or
inside
.
The DeviceHost still expects them.
Experiments
I manually created
using:
Parser accepts the syntax (no parsing errors),
but DeviceHost still reports:
which suggests it expects a different internal format.
Additional information
Missnet (Bosnia)
DVB-C
Frequencies:
394 MHz
402 MHz
410 MHz
418 MHz
426 MHz
434 MHz
442 MHz
450 MHz
458 MHz
466 MHz
474 MHz
482 MHz
490 MHz
498 MHz
506 MHz
514 MHz
522 MHz
530 MHz
538 MHz
546 MHz
554 MHz
562 MHz
570 MHz
578 MHz
586 MHz
594 MHz
602 MHz
610 MHz
618 MHz
626 MHz
634 MHz
Question
Should NextPVR automatically generate
after scanning?
Since scanning succeeds and
works perfectly, the tuner and driver appear to be functioning correctly. The failure seems to occur only when DeviceHost attempts to resolve tuning parameters for live streaming.
Thank you for your help.
Summary
I am running the latest ARM64 Docker image of NextPVR on a Raspberry Pi 5.
The DVB-C scan succeeds and channels are imported correctly, but Live TV and recordings always fail with:
Code:
No tuner was available for the requested channel.The DeviceHost logs show:
Code:
Failed to get tuning params for (...) from /config/adapterX-DVB-C-channels.confThe file is either never generated by NextPVR or the DeviceHost expects a different format than the standard DVBv5 tuning files.
Environment
Hardware
- Raspberry Pi 5
- 8 GB RAM
- Hauppauge WinTV-dualHD (dual DVB-C/T/T2)
- USB 3.0 connection
Code:
Linux dino-pi 6.18.33+rpt-rpi-2712
Debian 13 (Trixie)
64-bit ARMKernel:
Code:
Linux dino-pi 6.18.33+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.33-1+rpt1NextPVR
Docker image:
Code:
nextpvr/nextpvr_arm64:stableVersion:
Code:
7.1.1.260616Docker Compose
Code:
nextpvr:
image: nextpvr/nextpvr_arm64:stable
container_name: nextpvr
environment:
- TZ=Europe/Vienna
devices:
- /dev/dvb/adapter0:/dev/dvb/adapter0
- /dev/dvb/adapter1:/dev/dvb/adapter1
volumes:
- /opt/nextpvr/config:/config
- /mnt/media/tv-aufnahmen:/recordings
- /mnt/downloads:/buffer
ports:
- "8866:8866"
restart: unless-stoppedDVB Devices detected
NextPVR detects both tuners correctly.
Code:
adapter0/frontend0 (Silicon Labs Si2168)
adapter1/frontend0 (Silicon Labs Si2168)Both are shown as
Code:
Present = true
Enabled = trueDriver
Code:
em28xx
si2168Kernel modules load correctly.
After reboot there are no I²C errors anymore.
Signal
Signal quality is 37dB.
Example:
Code:
C/N = 37.5 dBDVB Utilities
Code:
dvbv5-zapCode:
w_scanIt finds over 220 TV services.
Code:
channels.confNextPVR Scan
The channel scan succeeds.
Example from device log:
Code:
Scanning 474000000
Scanning 482000000
Scanning 490000000
Scanning 498000000
Scanning 506000000
Scanning 514000000
Scanning 522000000
Scanning 530000000
Scanning 538000000
...Channels are found and imported.
Example:
Code:
Arena Sport 1 HD
Arena Sport 2 HD
Arena Sport 3 HD
Pink Kids
BN 2 TV
...Around 220 channels are imported.
Problem
When starting Live TV:
Code:
No tuner was available for the requested channel.nrecord.log
Code:
checking: adapter1/frontend0
enabled and present
has channel
live tv is possibleNextPVR launches DeviceHost correctly.
Example:
Code:
DeviceHostLinux
-listen:39823
-type:DVB-C
-device:"adapter1/frontend0"DeviceHost receives:
Code:
<tuning>
<type>DVB-C</type>
<name>Arena Sport 3 HD</name>
<locator>
<conf>514000000OFF</conf>
</locator>
<service_id>2320</service_id>
</tuning>DeviceHost error
Immediately afterwards:
Code:
Failed to get tuning params for
(Arena Sport 3 HD)
from
/config/adapter1-DVB-C-channels.confThen:
Code:
HTTP 404Finally:
Code:
No tuner was available for the requested channel.Important observation
Originally there was no
Code:
adapter0-DVB-C-channels.confor
Code:
adapter1-DVB-C-channels.confinside
Code:
/configThe DeviceHost still expects them.
Experiments
I manually created
Code:
adapter0-DVB-C-channels.conf
adapter1-DVB-C-channels.confusing:
- DVBv5 format
- frequency sections
- standard NextPVR tuning format
Code:
[514000000OFF]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 514000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/256
INVERSION = AUTOParser accepts the syntax (no parsing errors),
but DeviceHost still reports:
Code:
Failed to get tuning paramswhich suggests it expects a different internal format.
Additional information
Missnet (Bosnia)
DVB-C
Code:
6900 KS/s
QAM256Frequencies:
394 MHz
402 MHz
410 MHz
418 MHz
426 MHz
434 MHz
442 MHz
450 MHz
458 MHz
466 MHz
474 MHz
482 MHz
490 MHz
498 MHz
506 MHz
514 MHz
522 MHz
530 MHz
538 MHz
546 MHz
554 MHz
562 MHz
570 MHz
578 MHz
586 MHz
594 MHz
602 MHz
610 MHz
618 MHz
626 MHz
634 MHz
Question
Should NextPVR automatically generate
Code:
adapter0-DVB-C-channels.conf
adapter1-DVB-C-channels.confafter scanning?
Since scanning succeeds and
Code:
w_scanThank you for your help.