215 replies to this topic

[Dimitrij]

Rob van der Does

The tuner as motor  is always selected last when no other tuners are available.

If you add 23.5 to tuner A you will never have timer conflicts.

[Huevos]

...

Edited by Huevos, 15 April 2023 - 16:03.

[Dimitrij]

 

And also again: when tuner A = fixed tuner, the problem is gone

Because this tuner(A) has the highest priority.

Prioritize tuner C or D and you'll get the same timer conflict.

 

 

example find best tuner:

 

 

tuner  --> not diseqc--> 15000 - sat count fot this tuner + (5 when not loop tuner )

tuner  -->  diseqc--> 10000 - sat count fot this tuner+ (5 when not loop tuner )

tuner  rotor --> 10000 - (current rotor_position - new orbital_position) - sat count fot this tuner + (5 when not loop tuner )

 

[Rob van der Does]

Let's not make it more complicated then it is:  if a tuner is free for live tv but not for recording that is a false conflict.

[Rob van der Does]

Rob van der Does

The tuner as motor  is always selected last when no other tuners are available.

And that is indeed the case for live-TV. And that's how it should be (if no user assigned priority has been set)
 

 

 

 

Rob van der Does

 

If you add 23.5 to tuner A you will never have timer conflicts.

 

 

I don't think you read what I said above.

Tuner A (motor) is NOT BEING USED for recordings for any satellite that is also on a fixed dish.

 

I've reported a lot of testing to prove that.
 

 

[Rob van der Does]

@Rob, can you switch off conflict checking and then see it it is possible to make the 3 simultaneous recordings.

I have done and reported that: in that case the timer is fine and the resulting recording as well.

[Abu Baniaz]

When viewing and wanting to record 3 services, don't you need 4 tuners? If so, surely this should ignore the actively being viewed channel when recordings are in the future as a channel change will occur? Or if recording takes priority over viewing which is a default setting.

[Huevos]

When viewing and wanting to record 3 services, don't you need 4 tuners? If so, surely this should ignore the actively being viewed channel when recordings are in the future as a channel change will occur? Or if recording takes priority over viewing which is a default setting.

The question is not about viewing live tv. The problem is there are 3 tuners configured, 2 are recording, we now cannot set a recording on the third. The comments about live tv is just to prove the tuner is free and available and could be used for a recording which works fine when conflict checking is disabled. If everything works with timer conflict checking disabled the timer conflict warning must be false.

[Dimitrij]

 

 If everything works with timer conflict checking disabled the timer conflict warning must be false.

This does not work.

The last record will be fake (0 bytes).

[LraiZer]

getBestPlayableServiceReference is currently not simulated in TimerSanityCheck.py, Is this correct?

timer_ref = getBestPlayableServiceReference(timer.service_ref.ref, eServiceReference(), true)

 

[Huevos]

 

 

 If everything works with timer conflict checking disabled the timer conflict warning must be false.

This does not work.

The last record will be fake (0 bytes).

 

That is not true. All recordings were created correctly.

[Abu Baniaz]

 

When viewing and wanting to record 3 services, don't you need 4 tuners? If so, surely this should ignore the actively being viewed channel when recordings are in the future as a channel change will occur? Or if recording takes priority over viewing which is a default setting.

The question is not about viewing live tv. The problem is there are 3 tuners configured, 2 are recording, we now cannot set a recording on the third. The comments about live tv is just to prove the tuner is free and available and could be used for a recording which works fine when conflict checking is disabled. If everything works with timer conflict checking disabled the timer conflict warning must be false.

 

 

If the tuner is used for viewing, it is currently occupied. It may not be be when for when the timer is being set. 

[Rob van der Does]

When viewing and wanting to record 3 services, don't you need 4 tuners? If so, surely this should ignore the actively being viewed channel when recordings are in the future as a channel change will occur? Or if recording takes priority over viewing which is a default setting.

No, you don't if the live-TV service is the same as the recorded service.

Anyway: this is not related to the bug in question.

[Dimitrij]

It looks like we have a misunderstanding.

 

I tried several times to explain the logic as I see it, but they did not understand me.

Maybe I'm wrong too, but then help me.

Because I check everything virtually, and this, of course, is not at all the same.

And we'll fix the bug.

 

First, you need to check this by observing the start time(the main condition is that timer 3 must start earlier than others) and the order in which the timers are assigned:

Add timer 1 OK --> 23.5E NPO1 HD (20:00 -21:01) intended use C

Add timer 2 OK --> 23.5E NPO2 HD (20:00 -21:01) intended user D

 

Add timer 3 conflict!!!--> 19.2E TV5MONDE (19:55 -21:01) ---> conflict timer1/timer2

Then turn off the timer 3 conflict and wait for the recording to start, and check for one minute.

 

 

 

The second thing I am sure of at the moment is that if you add 23.5 to the motor, then there will be no timer conflicts.

Can this be verified?

Add timer 1 OK --> 23.5E NPO1 HD (20:00 -21:01) intended use C

Add timer 2 OK --> 23.5E NPO2 HD (20:00 -21:01) intended user D

 

Add timer 3 OK--> 19.2E TV5MONDE (19:55 -21:01) ---> intended user А

And yes. I also think that the live-TV viewing channel can affect the assignment of tuners in case of conflict, today I will study this.

 

By the way, we took on a very difficult task.

Teach a machine to think like a human .

Edited by Dimitrij, 16 April 2023 - 06:49.

[Rob van der Does]

Add future, simultaneous timers: first one on 23.5, second one on 23.5, third one on 19.2.  There is no timer conflict, and the resulting recordings are fine.

 

Next tests will have to wait a bit.

 

[Dimitrij]

Regarding the live TV channel.

It really affects the choice of tuner at the start of recording.

 

Example 1:

Live TV any service tuner C

 

start 19.2E TV5MONDE (19:55 -21:01) use A when   Live TV not  transponder TV5MONDE

start 23.5E NPO1 HD (20:00 -21:01)  use D

start 23.5E NPO2 HD (20:00 -21:01) use C (when  Live TV not  transponder NPO2 HD --> zap to NPO2 HD)

 

 

Example 2:

Live TV any service tuner A

 

start 19.2E TV5MONDE (19:55 -21:01) use C when   Live TV not  transponder TV5MONDE

start 23.5E NPO1 HD (20:00 -21:01)  use D

start 23.5E NPO2 HD (20:00 -21:01) not free tuner,because not 23.5E in A rotor sat list

[Rob van der Does]

LiveTV is of no importance for this issue. In the first place I never watch live, in the second place recordings take precedence over liveTV.

[Rob van der Does]

@Dimitrij: I think I'm beginning to understand what you try to explain:

For immediate timers: adding them in the order 23.5, 19.2, 23.5 there would be a conflict, as tuner A doesn't have 23.5.

0

My point is however: this conflict should not apply to future timers. SO when making the above mentioned timers for a future time, E2 should not see it as a conflict, as it knows what's going to be recorded next.

If you say that this is intended behaviour, then E2 is much less smart then I always thought. And then I should keep my config, as a manual way to avoid conflicts.

[Dimitrij]

 

@Dimitrij: I think I'm beginning to understand what you try to explain:

For immediate timers: adding them in the order 23.5, 19.2, 23.5 there would be a conflict, as tuner A doesn't have 23.5.

 

You understood correctly, but with future timers it is even more difficult.

 

1)First, the check only happens once when you add a new timer.

Moreover, they are checked by the start time, and for each, the first free tuner with the highest priority is selected.

Example for  future timers(TimerSanityCheck.py):

 

Add 23.5E NPO1 HD (20:00 -21:01)  use C -->OK

Add 23.5E NPO2 HD (20:01 -21:01) use D-->OK

 

tmer list(NPO1 HD, NPO2 HD)

 

Add 19.2E TV5MONDE (19:55 -21:01) --> checking conflict

 

timer check order (TV5MONDE,NPO1 HD,NPO2 HD)

19.2E TV5MONDE (19:55 -21:01) --> use C -->OK

23.5E NPO1 HD (20:00 -21:01)  use D -->OK

23.5E NPO2 HD (20:01 -21:01) not free tuner-->conflict

 

 

2)When recording starts, there is no check at all, just the first available tuner with the highest priority is selected.

That is, if I fix (in some way, I really don’t know how) the conflict in TimerSanityCheck.py, then when the records start, this problem will arise again.

 

 

Try adding 23.5 to A for a test. My opinion is that there will be no conflicts.

Edited by Dimitrij, 17 April 2023 - 17:25.

[Dimitrij]

I checked the openVTV image, the default behavior is the same.

But there are some very interesting tuner priority settings.

I cannot fully check them, so I only have one 36e satellite available now.

 

Preferred tuner: added multiple selection option

If  check this helps to solve the problem, then you can add it to openPli.