Recording priority 2026.05.12.0935

updated yesterday to 2026.05.12.0935. it seems my directv stream TVE source is not being respected as the highest priority source. Logs have been submitted as 5dd286c3-945d-4aa8-b588-e6f9cf74bc73 .

it's possible it's something i did, but I've tried re prioritizing the sources, disabling/re-enabling, deleting/recreating the db. I have not done a pc reboot, but that I can do that if anyone thinks it'd help.

while grabing this screen shot I noticed bill maher did not get sheduled on tve with the db rebuild several hours ago. so that explaines it, but not the new pass I just setup for 'Kara Swisher Wants to Live Forever'


iirc the channel #'s are showing in priority order and should be 6030, 202


ok, so jobs in progress only show the channel it is actually using.
the later bill maher was a manually set recording via the guide only showing the tve source.

also these recording passes are set with series id, not channel.

So problem, or not ?

For scheduling passes where an airing is on multiple channels;
Favorited channels get HIGHEST priority
Source priority is the NEXT consideration
Higher numbered channels have higher priority

Priority Source Channel Favorite
#1       HDHR   2
#1       HDHR   202
#2       TVE    6030
#3       M3U    22      YES

Scheduled priority would be 22, 202, 2, 6030

1 Like

HUH! this is new info to me.. lol.. I had no idea favorites affected passes.
that explains why my schedule looks correct now, since my last post I went ahead and favorited all the wrongly numbered tve channels I care about. (6###)

Yep.
Favorites and Source Priority ON THE DVR WEB UI SETTINGS.
Those settings can be different on each client and will not affect DVR scheduling.

just noticed you said higher # is higher priority (also new info)
wouldn't your example be 22, 6030, 202, 2 ?
edit; I see higher # is 3rd sort order after source priority.

No.
It searched in this order.
Looks through Sources in Priority order, from highest ch# to lowest ch# until it finds one.
Looks for a Favorite channel first [#3-22]
Looks for an HD channels next [#1-202, #1-2, #2-6030]
Looks for an SD channels last

ok. do you see how that confuses me? apparently there are 2 stages to this where it re-sorts by group after it indexes all the sources..?

1 Like

No, but I'm confused by this statement

Break it down into a simple example.
3 sources with 2 channels each
Source#1 Channel#1
Source#1 Channel#2
Source#2 Channel#21
Source#2 Channel#22
Source#3 Channel#31 Favorite
Source#3 Channel#32
Scheduled priority is 31, 2, 1, 22, 21, 32

1 Like

to me it's better described as
Looks through groups in order Favorites, HD, SD, none
each group looks by source priority in reverse channel # order.

thanks for the help. language and logic are hard to mix. :disguised_face:

Whatever "floats your boat".
I agree that if we don't use the same terminology, it's hard to communicate things.
To me, groups are SeriesID's.

Like PrismCast confusing auth Providers with stream sources.