Starting recordings do not stop other subscriptions
Added by Paul Brunniem almost 8 years ago
Hi,
I have a single IPTV auto Network configured with Maximum # input streams set to 1.
When I have a running subscription (Kodi or something direct playing) and a recording starts on an other channel, the recording gets no data because the other subscriptions are not killed. The recording should have higher priority in standard settings (should they?) and even by playing with the priority settings I was not able to change this behavior.
Is this a bug? before the IPTV I had a TV-PCI-Card in the server where tvheadend is running and at this time (without configuring any priority settings), recordings where always killing other subscriptions (The TV-Card was also only able to tune one channel at the same time).
Replies (2)
RE: Starting recordings do not stop other subscriptions - Added by Mark Clarkstone almost 8 years ago
Paul Brunniem wrote:
Hi,
I have a single IPTV auto Network configured with Maximum # input streams set to 1.When I have a running subscription (Kodi or something direct playing) and a recording starts on an other channel, the recording gets no data because the other subscriptions are not killed. The recording should have higher priority in standard settings (should they?) and even by playing with the priority settings I was not able to change this behavior.
Is this a bug? before the IPTV I had a TV-PCI-Card in the server where tvheadend is running and at this time (without configuring any priority settings), recordings where always killing other subscriptions (The TV-Card was also only able to tune one channel at the same time).
Did you set the priority for the recording itself? Also check the stream priority.
RE: Starting recordings do not stop other subscriptions - Added by Paul Brunniem almost 8 years ago
Well yes, I configured a own "passRecord" stream profile with prio Important. I also edited the htsp profile (kodi uses this) with prio low.
The default recording profile uses "passRecord" and the user I create the records with (admin), uses the default record profile (and also stream profile "pass" which has prio normal).
I think the prios are ok. If the prio is to low it should write "no free adapter" or something to the log.
The log shows only a normal try to tune/subscribe to the iptv network a second time without killing/unsubscribing the running stream to kodi.
Here is a log from starting to stream with kodi, then start a record over the webinterface and then stop kodi:
2017-01-20 21:24:15.809 mpegts: services_pipe.m3u - Disney Cinemagic HD in IPTV PIPE - tuning on IPTV 2017-01-20 21:24:15.824 spawn: Executing "/usr/bin/ffmpeg" 2017-01-20 21:24:15.825 subscription: 0014: "host1 [ hostname1 | Kodi Media Center ]" subscribing on channel "Disney Cinemagic (DE)", weight: 75, adapter: "IPTV", network: "IPTV PIPE", mux: "services_pipe.m3u - Disney Cinemagic HD", provider: "Sky", service: "DisneyCinemagicHD", profile="htsp", hostname="host1", username="hostname1", client="Kodi Media Center" 2017-01-20 21:24:36.505 dvr: entry 7cffda98e03a76119c6f345d1cc5b47f "TAGESSCHAU" on "Phoenix" starting at 2017-01-20 19:54:30, scheduled for recording by "admin" 2017-01-20 21:24:36.505 dvr: "TAGESSCHAU" on "Phoenix" recorder starting 2017-01-20 21:24:36.505 mpegts: services_pipe.m3u - PHOENIX HD in IPTV PIPE - tuning on IPTV 2017-01-20 21:24:36.507 subscription: 0015: "DVR: TAGESSCHAU" subscribing on channel "Phoenix", weight: 150, adapter: "IPTV", network: "IPTV PIPE", mux: "services_pipe.m3u - PHOENIX HD", service: "PHOENIX HD", profile="passRecord" 2017-01-20 21:24:52.506 subscription: 0015: service instance is bad, reason: No input detected 2017-01-20 21:24:54.506 subscription: 0015: restarting channel Phoenix 2017-01-20 21:24:56.506 mpegts: services_pipe.m3u - PHOENIX HD in IPTV PIPE - tuning on IPTV 2017-01-20 21:24:56.508 subscription: 0015: "DVR: TAGESSCHAU" subscribing on channel "Phoenix", weight: 150, adapter: "IPTV", network: "IPTV PIPE", mux: "services_pipe.m3u - PHOENIX HD", service: "PHOENIX HD", profile="passRecord" 2017-01-20 21:25:12.507 subscription: 0015: service instance is bad, reason: No input detected 2017-01-20 21:25:14.507 subscription: 0015: restarting channel Phoenix 2017-01-20 21:25:16.507 mpegts: services_pipe.m3u - PHOENIX HD in IPTV PIPE - tuning on IPTV 2017-01-20 21:25:16.509 subscription: 0015: "DVR: TAGESSCHAU" subscribing on channel "Phoenix", weight: 150, adapter: "IPTV", network: "IPTV PIPE", mux: "services_pipe.m3u - PHOENIX HD", service: "PHOENIX HD", profile="passRecord" 2017-01-20 21:25:22.525 subscription: 0014: "host1 [ hostname1 | Kodi Media Center ]" unsubscribing from "Disney Cinemagic (DE)", hostname="host1", username="hostname1", client="Kodi Media Center" 2017-01-20 21:25:32.527 subscription: 0015: service instance is bad, reason: No input detected 2017-01-20 21:25:34.527 subscription: 0015: restarting channel Phoenix 2017-01-20 21:25:36.527 mpegts: services_pipe.m3u - PHOENIX HD in IPTV PIPE - tuning on IPTV 2017-01-20 21:25:36.529 subscription: 0015: "DVR: TAGESSCHAU" subscribing on channel "Phoenix", weight: 150, adapter: "IPTV", network: "IPTV PIPE", mux: "services_pipe.m3u - PHOENIX HD", service: "PHOENIX HD", profile="passRecord" 2017-01-20 21:25:38.317 pass: RECORDPATH/TAGESSCHAU/TAGESSCHAU.mit GebaerdensprachdolmetscherIn2017-01-2020-00-1.ts: Unable to change permissions -- Vorgang nicht zulässig 2017-01-20 21:25:38.318 dvr: RECORDPATH/TAGESSCHAU/TAGESSCHAU.mit GebaerdensprachdolmetscherIn2017-01-2020-00-1.ts from adapter: "IPTV", network: "IPTV PIPE", mux: "services_pipe.m3u - PHOENIX HD", provider: "", service: "PHOENIX HD" 2017-01-20 21:25:38.318 dvr: # type lang resolution aspect ratio sample rate channels 2017-01-20 21:25:38.318 dvr: 1 H264 ? ? 2017-01-20 21:25:38.318 dvr: 2 MPEG2AUDIO ger ? ? 2017-01-20 21:25:38.318 dvr: 3 MPEG2AUDIO mul ? ? 2017-01-20 21:25:38.318 dvr: 4 TELETEXT
You see the weight of the recording is higher.