Author Topic: Timer conflicts  (Read 945 times)

Offline prl

  • Guru
  • *****
  • Posts: 3430
    • View Profile
Re: Timer conflicts
« Reply #15 on: June 08, 2020, 10:49:32 AM »
On a T4, a recording conflict should normally involve at least 5 recordings. I'm not sure how there could be a conflict for only two recordings, unless some tuners are out to lunch.
Peter
Beyonwiz T4 in-use
Beyonwiz T2, T3, T4, U4 & V2 for testing

Offline Nistrod

  • Junior Member
  • **
  • Posts: 14
    • View Profile
Re: Timer conflicts
« Reply #16 on: June 09, 2020, 07:56:08 AM »
OK, this was resolved. It is weird, but some of my timers on the T4 did not have a channel associated with them. IceTV had a channel in all its entries, but the T4 did not. In particular, there was one at the same time as the shows giving the errors.

Editing the timers to add the correct channel gave lots of errors, but did the correct thing, and all the problems disappeared.

I did retune the T4 a few days ago, after an antenna move, so perhaps these were existing timers, whose channels moved somehow and disappeared - I don't know how the T4 identifies a channel internally.

All good. Thanks to all those who made suggestions.
BeyonWiz T3

Offline prl

  • Guru
  • *****
  • Posts: 3430
    • View Profile
Re: Timer conflicts
« Reply #17 on: June 10, 2020, 02:38:42 PM »
I don't know how the T4 identifies a channel internally.

By a thing called a service reference. For DVB services, the important parts that identify a channel (and the only parts that are used by IceTV to indicate a channel) are the DVB ONID (Original Network IDentifier), TSID (Transport Stream IDentifier) and SID (Stream IDentifier). The full identification also includes the ID Namespace, but that's fixed for all terrestrial digital broadcast services.
Peter
Beyonwiz T4 in-use
Beyonwiz T2, T3, T4, U4 & V2 for testing

An Error Has Occurred!

Call to undefined function seo_social_bookmarks()