Project

General

Profile

Bug #3973

TV Service priority not respected in autorec scheduling

Added by el Paraguayo about 8 years ago. Updated over 7 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
Configuration
Target version:
-
Start date:
2016-09-10
Due date:
% Done:

0%

Estimated time:
Found in version:
4.0.9-12~ge5400e2~trusty
Affected Versions:

Description

I have both SD and HD channels broadcasting the same program. I typically want to record the SD version.

When scheduling an autorecording using just the title (e.g. "Match of the Day") the scheduler sets the recording to the HD channel even though I set the HD channel to a lower priority (via Config --> DVB Inputs --> Services).

I would expect the scheduler to prefer the SD channel based on the priority settings.

History

#1

Updated by Jaroslav Kysela about 8 years ago

Use 'Preferred service video type' in streaming profiles... The priority might be overriden by other rules like 'mux resharing'. If you look to the debug output, you should see the prio / weight lines to check.

#2

Updated by el Paraguayo about 8 years ago

Jaroslav Kysela wrote:

Use 'Preferred service video type' in streaming profiles... The priority might be overriden by other rules like 'mux resharing'. If you look to the debug output, you should see the prio / weight lines to check.

Thanks. Unfortunately I can't find that option in "Streaming Profiles". I guess this is because I'm running 4.0 though!

#3

Updated by Thomas Spalinger about 8 years ago

probably a general problem with service priority?
I try to get it working for the following sceanario:

two services for the same channel. One is HD and encrypted, the second is SD and unencrypted. I set the priority 1 on the HD encrypted one.
As i read in several forum posts, tvheadend should automatically switch to the second SD unencrypted service if oscam is down or could due any other reason not be descrambled.
But it I don't get it to work like that. It keeps trying to serve the encrypted channel even oscam stopped.
Do I miss something or is it probably the same problem?

Let me know if I should create a ticket if it's not the same.

info: using current unstable debian package.

#4

Updated by Jaroslav Kysela over 7 years ago

  • Status changed from New to Fixed

It's fixed in 4.2.

Also available in: Atom PDF