Whenever I watch a tv-channel, an additional mux (always 266MHz) is subscribed

Wim K

First of all: Happy New Year!

Now my problem: I don't know when this started (maybe when I switched oscam to dvbapi?), but when I watch a tv-channel (or make a tv-recording) an additional and always the same mux (266MHz) is being subscribed to (see below 2 instances in the logs). This does NOT happen when epg grabber is running.

1. Recording "North to Home" on mux 394MHz: Jan 2 21:31:42 raspberrypi tvheadend[903]: dvr: entry 95e15971c0f24a11c11a441079ed6b0f "North to Home" on "RTL 8" starting at 2024-01-02 20:17:30, with broadcast id "<noid>", scheduled for recording by "tvheadend"
Jan 2 21:31:42 raspberrypi tvheadend[903]: dvr: "North to Home" on "RTL 8" recorder starting
Jan 2 21:31:42 raspberrypi tvheadend[903]: mpegts: 394MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #0 (192.168.2.5)
Jan 2 21:31:42 raspberrypi tvheadend[903]: tvhdhomerun: tuning to a8qam256-6900:394000000
Jan 2 21:31:42 raspberrypi tvheadend[903]: subscription: 0216: "keep" subscribing to mux "394MHz", weight: 1, adapter: "HDHomeRun DVB-C Tuner #0 (192.168.2.5)", network: "Ziggo", service: "Raw PID Subscription"
Jan 2 21:31:42 raspberrypi tvheadend[903]: mpegts: 266MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #3 (192.168.2.5)
Jan 2 21:31:42 raspberrypi tvheadend[903]: tvhdhomerun: tuning to a8qam256-6900:266000000
Jan 2 21:31:42 raspberrypi tvheadend[903]: subscription: 0217: "keep" subscribing to mux "266MHz", weight: 1, adapter: "HDHomeRun DVB-C Tuner #3 (192.168.2.5)", network: "Ziggo", service: "Raw PID Subscription"

Jan 2 21:31:42 raspberrypi tvheadend[903]: capmt: dvbapi: Starting CAPMT server for service "RTL 8" on adapter 0

2. Recording "112 Vandaag" on mux 458MHz: Jan 2 21:42:56 raspberrypi tvheadend[903]: dvr: entry f5616c7ba469a3f4ae01c78449d858ea "112 Vandaag" on "RTL 5" starting at 2024-01-02 21:29:30, with broadcast id "<noid>", scheduled for recording by "tvheadend"
Jan 2 21:42:56 raspberrypi tvheadend[903]: dvr: "112 Vandaag" on "RTL 5" recorder starting
Jan 2 21:42:56 raspberrypi tvheadend[903]: mpegts: 458MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #0 (192.168.2.5)
Jan 2 21:42:56 raspberrypi tvheadend[903]: tvhdhomerun: tuning to a8qam256-6900:458000000
Jan 2 21:42:56 raspberrypi tvheadend[903]: subscription: 021F: "keep" subscribing to mux "458MHz", weight: 1, adapter: "HDHomeRun DVB-C Tuner #0 (192.168.2.5)", network: "Ziggo", service: "Raw PID Subscription"
Jan 2 21:42:56 raspberrypi tvheadend[903]: mpegts: 266MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #3 (192.168.2.5)
Jan 2 21:42:56 raspberrypi tvheadend[903]: tvhdhomerun: tuning to a8qam256-6900:266000000
Jan 2 21:42:56 raspberrypi tvheadend[903]: subscription: 0220: "keep" subscribing to mux "266MHz", weight: 1, adapter: "HDHomeRun DVB-C Tuner #3 (192.168.2.5)", network: "Ziggo", service: "Raw PID Subscription"

Jan 2 21:42:56 raspberrypi tvheadend[903]: capmt: dvbapi: Starting CAPMT server for service "RTL 5" on adapter 0

Edit: HDHOMERUN 4 tuners, raspberry pi 4B, Tvheadend 4.3-1964~g637844055

Wim K

I was looking at another instance tonight and saw in the logs a bit further down:

Jan 3 19:18:15 raspberrypi tvheadend[17806]: mpegts: 346MHz in Ziggo scan complete

Jan 3 19:18:15 raspberrypi tvheadend[17806]: mpegts: 266MHz in Ziggo scan complete

and again further down:

Jan 3 19:27:45 raspberrypi tvheadend[17806]: epggrab: EIT: DVB Grabber - data completion timeout for 266MHz in Ziggo

Jan 3 19:27:45 raspberrypi tvheadend[17806]: epggrab: EIT: DVB Grabber - data completion timeout for 346MHz in Ziggo

It seems indeed that when a recording is started, 2 epg-grabbings are starting. On the channel I'm recording AND on 266Mhz. The one on 266MHz doesn't disconnect or something??

I don't know what PID list means but with the current recording on 346MHz the PID list is "0,1,16,17,18,103,2900,2901,2911,2912,2951,3001,3002,3002"

and on 266MHz the pid list is "0,1,16,17,18". Does this mean anything (being partly the same)? Is this normal?