T2 Generating IceTV Timer Conflicts

[MrQuade]

What I don't understand is why a nexus between two programs on the same channel/network/service should cause this problem?

The answer is, they shouldn't.

If you lay out just those timers in a timeline as you have given them, there is no point at which more than 3 tuners should be requested, so there is no conflict, even accounting for back-to-back recordings, and something is going wrong.

Have you edited any of the preferred tuner items in MENU->Setup->Tuners->Tuner allocation? And do all of the tuners show up in MENU->Setup->Tuners->Tuner configuration?

And when you have no recordings running, does the tuner usage in the Infobar show only the one tuner in use?

[MrQuade]

If IceTV is sending the PVR data that has seconds data and that seconds data is overlapping then it is very relevant. Users on the Beyonwiz won't see the seconds data so they can't identify that the overlap is genuine.

Be that as it may, in this instance, and the timeline provided by vader1111, there is more than enough of a gap between any potential tuner conflicts, so this is not a factor here.

[prl]

...
When I had this problem the first time, I had timers set to record the following programs (times include padding):
1955-2055 Hard Quiz (ABC)
2055-2155 Rosehaven (ABC)
2025-2155 Tutankhamen
2125-2255 Madam Secretary
2225-2355 Blindspot

The only "nexus" present was between the two ABC programs. The T2 rejected the Tutankhamen until I modified the post-padding on Hard Quiz, eliminating the "nexus".

I can't find any reference to Blindspot in your earlier posts in this topic.

However, if I set timers for:
1955-2055 Hard Quiz (ABC)
2055-2155 Rosehaven (ABC)
2025-2155 Tutankhamen (SBS)
2125-2255 Madam Secretary (WIN)
2225-2355 manual times, since Blindspot isn't currently running (Prime)

There are no problems in setting those timers on a 3-tuner box, as I'd expect. There are only ever a maximum of 3 tuners needed, and that occurs from 21:24:40 - 21:55:00, and the tuners will be used for Rosehaven (ABC), Tutankhamen (SBS) and Madam Secretary (WIN).

What I don't understand is why a nexus between two programs on the same channel/network/service should cause this problem?

I've not been given a scenario where I can replicate that as a problem.

[prl]

The timing adjustments can only be done on an individual basis if the timers aren't set by IceTV. To resolve the problem within IceTV, either the pre- or post-padding needs to be reduced by 1 minute. It may help avoid similar IceTV problems more generally if the total amount of padding was set to 29 minutes, but of course that won't resolve all possible similar conflicts where "back-to-back" timers are involved.

It might come pretty close as it will be less likely to coincide with a program start and finish times as most would be in multiples of 5 in IceTV ...

Very good point.

[vader1111]

** It is possible to determine the order in which timers are sent by IceTV, though it's a bit time consuming. You add them sequentially in IceTV, and wait for them to appear on the T2 before adding the next timer in IceTV.

You can manually refresh IceTV to save the 15 minute delay between automatic updates.

I know. Still time consuming, having to repetitively iterate between adding the timers in Ice, then refreshing the T2.

[vader1111]

What I don't understand is why a nexus between two programs on the same channel/network/service should cause this problem?

The answer is, they shouldn't.

If you lay out just those timers in a timeline as you have given them, there is no point at which more than 3 tuners should be requested, so there is no conflict, even accounting for back-to-back recordings, and something is going wrong.

Have you edited any of the preferred tuner items in MENU->Setup->Tuners->Tuner allocation? And do all of the tuners show up in MENU->Setup->Tuners->Tuner configuration?

And when you have no recordings running, does the tuner usage in the Infobar show only the one tuner in use?

I agree that they shouldn't... but they do.

I haven't changed any of the standard settings in Tuner Allocation. It's definitely happy to record on all 3 tuners, because it does so on Monday nights without complaint - it's only when there's a "nexus" point that I have problems.

Yes, the Infobar only shows 1 tuner in use when there are no recordings in progress.

[vader1111]

...
When I had this problem the first time, I had timers set to record the following programs (times include padding):
1955-2055 Hard Quiz (ABC)
2055-2155 Rosehaven (ABC)
2025-2155 Tutankhamen
2125-2255 Madam Secretary
2225-2355 Blindspot

The only "nexus" present was between the two ABC programs. The T2 rejected the Tutankhamen until I modified the post-padding on Hard Quiz, eliminating the "nexus".

I can't find any reference to Blindspot in your earlier posts in this topic.

However, if I set timers for:
1955-2055 Hard Quiz (ABC)
2055-2155 Rosehaven (ABC)
2025-2155 Tutankhamen (SBS)
2125-2255 Madam Secretary (WIN)
2225-2355 manual times, since Blindspot isn't currently running (Prime)

There are no problems in setting those timers on a 3-tuner box, as I'd expect. There are only ever a maximum of 3 tuners needed, and that occurs from 21:24:40 - 21:55:00, and the tuners will be used for Rosehaven (ABC), Tutankhamen (SBS) and Madam Secretary (WIN).

What I don't understand is why a nexus between two programs on the same channel/network/service should cause this problem?

I've not been given a scenario where I can replicate that as a problem.

I didn't mention Blindspot before for two reasons..
[*] It wasn't mentioned in the IceTV "Failed Timer" email, so presumably wasn't responsible for the timer conflict preventing the Tutankhamen timer from being accepted.
[*] The Blindspot timer only results in 2 tuners being used - Rosehaven & Tutankhamen have both finished recording before the Blindspot timer started. The only overlap was Blindspot & Madam Secretary

I have no idea why this would be a problem with my T2, but cannot be replicated on yours. That's just weird.

[prl]

BTW, lists are done with:
[list]
[*] item 1
[*] item 2
[/list]

giving:

• item 1
• item 2

[prl]

... I have no idea why this would be a problem with my T2, but cannot be replicated on yours. That's just weird.

I'd actually been testing today on a 3-tuner T3, but this is from a 3-tuner T2. I've had to adjust the start time of Tutankhamun to match your original times, but it doesn't matter, Tutankhamun starting at 20:25 and 20:35 both work.

All I can think of was that there was something relevant that was missing from the original posts, but I can't think what it might have been.

[Grumpy_Geoff]

... I have no idea why this would be a problem with my T2, but cannot be replicated on yours. That's just weird.

I'd actually been testing today on a 3-tuner T3, but this is from a 3-tuner T2. I've had to adjust the start time of Tutankhamun to match your original times, but it doesn't matter, Tutankhamun starting at 20:25 and 20:35 both work.

All I can think of was that there was something relevant that was missing from the original posts, but I can't think what it might have been.

A difference between 4.4 and 16.1?

[prl]

... I have no idea why this would be a problem with my T2, but cannot be replicated on yours. That's just weird.

I'd actually been testing today on a 3-tuner T3, but this is from a 3-tuner T2. I've had to adjust the start time of Tutankhamun to match your original times, but it doesn't matter, Tutankhamun starting at 20:25 and 20:35 both work.

All I can think of was that there was something relevant that was missing from the original posts, but I can't think what it might have been.

A difference between 4.4 and 16.1?

The original testing I did would have been on 4.4.

[prl]

... I have no idea why this would be a problem with my T2, but cannot be replicated on yours. That's just weird.

I'd actually been testing today on a 3-tuner T3, but this is from a 3-tuner T2. I've had to adjust the start time of Tutankhamun to match your original times, but it doesn't matter, Tutankhamun starting at 20:25 and 20:35 both work.

All I can think of was that there was something relevant that was missing from the original posts, but I can't think what it might have been.

A difference between 4.4 and 16.1?

No, not that. Just retried vader111's original scenario (including a manual timer in Blindspot's place) on firmware 2016-08-17 (4.4).

[MrQuade]

No, not that. Just retried vader111's original scenario (including a manual timer in Blindspot's place) on firmware 2016-08-17 (4.4).

Likewise, running 4.4 (2016-08-18 beta feed) on a T2 with an operating USB tuner.

I set all the timers manually as I am not running IceTV on this box.