215 replies to this topic

[Dimitrij]

 

When "Preferred tuner DVB-S" is 'disabled -->used global option "Preferred tuner"

And 'auto' means?

 

When "Preferred tuner DVB-S"i= 'auto' same as  global option "Preferred tuner"= 'auto',  but only DVB-S tuners are taken into account

 

example find best tuner:

"Preferred tuner DVB-S"/ "Preferred tuner" 'auto'--> LNB 19.2

 

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

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

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

+

LNB rotor  --> "Priority" not auto( -1):

    + or - this value

    0 - disabled this LNB

 

or

global "Preferred tuner DVB-S" or "Preferred tuner"

Edited by Dimitrij, 14 April 2023 - 09:44.

[Huevos]

 

A maybe related setting: what is the difference between 'disabled' & 'auto' in tuner priority settings? To me it sounds as if both are the same.

When "Preferred tuner DVB-S" is 'disabled -->used global option "Preferred tuner"

 

 

Do you want to see the joke ?

Set LNB 19.2 rotor  --> "Priority" 19064(higher than any auto)

 

Not sure what you mean by this. Auto == -1 which is sent to c++ and means ignore. Code goes like this:

# in frontend.h
static void setPreferredFrontend(int index) { PreferredFrontendIndex = index; }
static int getPreferredFrontend() { return PreferredFrontendIndex; }

# in frontend.cpp
int eDVBFrontend::PreferredFrontendIndex = -1;
[...]
int eDVBFrontend::isCompatibleWith(ePtr<iDVBFrontendParameters> &feparm, bool is_configured_sat)
{
	[...]
	bool preferred = (eDVBFrontend::getPreferredFrontend() >= 0 && m_slotid == eDVBFrontend::getPreferredFrontend());
	[...]
	if (score && preferred)
	{
		/* make 'sure' we always prefer this frontend */
		score += 100000; /* the offset has to be so ridiculously high because of the high scores which are used for DVB-S(2) */
	}

eDVBFrontend::getPreferredFrontend() >= 0

so nothing happens with auto because -1 < 0.

 

By the way, where is the problem you have found? Is it in c++?

Edited by Huevos, 14 April 2023 - 09:28.

[Dimitrij]

 

By the way, where is the problem you have found? Is it in c++?

It seems that yes, and this applies to the entire chain of checking the availability of the service.

[Dimitrij]

My findings...

Looking at this error, I realized that the problem is not only in the tuner with the motor.

This is just the tip of the iceberg.

This is a fundamental problem(just a flaw) with recording timers that has existed since the birth of Enigma2.

The problem is not very visible unless you record very little and don't have a complex/large combination of tuners.

But fans of recordings for sure faced a constant error of conflicting timers / double timers, etc.

I've noticed this before when working with the autotimer plugin code, but I thought it was a plugin problem.

 

The main thing is that I understood the direction.

I'll try to rewrite the code for checking timers.

We'll have to add more variables to the existing code that, when virtual timers are assigned, will alert E2 that this tuner is being excluded from the assignment because it is busy at that time.

 

All my conclusions are wrong. In their trash. There is no error in the enigma code. The problem is with your tuner configuration.

 

Example:

 

Tuner A is DiSEqC motor for many positions  --> Warning! Not 23.5E in rotor sat list

 

 

Tuners C & D are from a static dish with 3 LNB (13.0E, 19.2E, 23.5E) and diseqc_a_b_c_d switches.

 

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

 

Cause if reality starts recording:

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

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

start 23.5E NPO2 HD (20:00 -21:01) no free tuner

 

How to fix it?

1)Add 23.5E in tuner A

2)Set LNB 19.2 rotor  --> "Priority" higher LNB tuners C/D

3)"Preferred tuner" set A

4)Set timer 3 --> 19.2E TV5MONDE (20:01 -21:01)

 

 

You can think of some kind of automatic solution. But I'm afraid it will break everything else. Your suggestions?

[Rob van der Does]

NoNoNo! There is nothing wrong with my tuner configuration!

The motorised dish should never have the highest priority. That would be totally wrong!

 

E2 should first use a tuner with the lowest number of satellites.

 

And the reason 23.5 is not configured on my motor is for exactly the same reason as 19.2 is not configured on tuners C&D: to work-around this bug.

[Huevos]

How is it relevant that 23.5E is not on the motor? He is trying to record from 19.2E. All tuners can record from 19.2E so why does it report a conflict? Tuner A is available for 19.2E  and plays live TV ok, but reports a conflict for recording.

Edited by Huevos, 14 April 2023 - 19:05.

[Abu Baniaz]

Can he select the channel on 19.2 (i.e use motorised dish). Once selected, is he able to record it?

Edited by Abu Baniaz, 14 April 2023 - 19:18.

[Dimitrij]

That's right, at the beginning, the tuner with the highest priority is selected for recording.

So, the first entry is 19.2 (tuner C).

So for 23.5 there is no longer a free tuner, so at this time there is a recording.

 

That's what the LNB priority setting is for.

 

 

Let's think together what we can think of to remedy this situation.

Let's say the conflict of timers, I'll fix it.

But what will happen with the real start of the records, because one record will not start?

Edited by Dimitrij, 14 April 2023 - 19:40.

[Dimitrij]

Can he select the channel on 19.2 (i.e use motorised dish). Once selected, is he able to record it?

 

 

1)Add 23.5E in tuner A

2)Set LNB 19.2 rotor  --> "Priority" higher LNB tuners C/D

3)"Preferred tuner" set A

4)Set timer 3 --> 19.2E TV5MONDE (20:01 -21:01)

 

[Huevos]

I don't understand your logic. C and D are in use. Tuner A has access to 19.2E. Why can't this tuner be selected for a recording? It can be selected for live TV. Recording should always take priority unless the user has changed from the default setup.

Edited by Huevos, 14 April 2023 - 21:12.

[Rob van der Does]

I don't understand your logic. C and D are in use. Tuner A has access to 19.2E. Why can't this tuner be selected for a recording? It can be selected for live TV. Recording should always take priority unless the user has changed from the default setup.

Exactly. Adding 19.2 to tuners C&D in fact decreases recording options, instead of increasing them.

 

Going by all the above results, it's a flaw in the timer sanity logic.

[Dimitrij]

 

I don't understand your logic. C and D are in use. Tuner A has access to 19.2E. Why can't this tuner be selected for a recording? It can be selected for live TV. Recording should always take priority unless the user has changed from the default setup.

Again...

 

Tuner A is DiSEqC motor for many positions  --> Warning! Not 23.5E in rotor sat list

 

Tuners C & D are from a static dish with 3 LNB (13.0E, 19.2E, 23.5E) and diseqc_a_b_c_d switches.

 

 

 

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

 

 

Pay close attention to the recording start time!

 

 

Cause if reality starts recording(if we disabled detect conflict in timer TV5MONDE):

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

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

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

Edited by Dimitrij, 15 April 2023 - 06:22.

[Dimitrij]

 

Exactly. Adding 19.2 to tuners C&D in fact decreases recording options, instead of increasing them.

 

Going by all the above results, it's a flaw in the timer sanity logic.

 

This is not an enigma error, this is your complex tuner configuration that needs fine tuning.

And there are such tools in Enigma.

 

 

The simplest solution...

Add satellite 23.5E to tuner A on the motor

 

and

this is not a mandatory item...

set 23.5E LNB Priority" lowest priority, e.g. (lower than any auto).

 

In this case, you expand the possibility of using up to three tuners for 23.5.

What's bad about it?

 

In short, it's your choice.

 

P.S.It's like an autotimer plugin, which has a lot of fine-tuning and who knows how to use it, gets undoubted benefits.

For others, it's just useless.

Edited by Dimitrij, 15 April 2023 - 06:50.

[Rob van der Does]

No: E2 should, exactly as it does for live-tv, use the rotor as a last resource.

 

And again: when tuner A is free (not greyed out) and can be used for live-TV but not for a recording then something is amiss.

 

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

 

So: E2 refuses to use the motor for a recording on a satellite that is also on a fixed dish, even if this fixed dish is occupied (--> timerconflict while tuner A is available).

 

And regardless of tuner priority: a free tuner should be available for recording, which is not the case.

[Rob van der Does]

To be clear: of course my preferred LNB-config would be to match my physical setup (i.e. both 23.5 & 19.2 on A (=motor) and C&D (via DiSEqC 1.0). But I soon discoverd that I had a lot of timer conflicts, because of the fact that E2 refuses to use the motor. My work-around was and is to split the setup: 23.5 only on C&D (which is sufficient for my recordings on 23.5) and 19.2 on A.

Since doing so the timer conflicts are gone (i.e. if I have any, it's a real one).

If this bug would be fixed, I would of course revert to a 'normal' setup.

 

Giving priority to the motor, as you suggest, is the very last thing one wants to do. In that case any recording would occupy my most valuable feed.

[luisteraar]

I think E2's behavior is deliberate.
A rotatable dish deliberately has a low priority during recording, so there is a chance that the dish is not aligned with the satellite that is needed for the recording.
The recording can only be started when the dish is aligned and the transponder is locked.
is there a delay in the timer function until the dish is aligned?
Just my conclusion for what I read here.

[Huevos]

 

 

I don't understand your logic. C and D are in use. Tuner A has access to 19.2E. Why can't this tuner be selected for a recording? It can be selected for live TV. Recording should always take priority unless the user has changed from the default setup.

Again...

 

Tuner A is DiSEqC motor for many positions  --> Warning! Not 23.5E in rotor sat list

 

Tuners C & D are from a static dish with 3 LNB (13.0E, 19.2E, 23.5E) and diseqc_a_b_c_d switches.

 

 

 

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

 

 

Pay close attention to the recording start time!

 

 

Cause if reality starts recording(if we disabled detect conflict in timer TV5MONDE):

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

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

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

 

Please explain how you think overlaps are relevant. If we have 3 tuners and want to record 3 different services there is no conflict and this is proved by being able to watch the third service on live TV.

 

If you can watch a service but not record it that is a false conflict.

[Huevos]

I think E2's behavior is deliberate.
A rotatable dish deliberately has a low priority during recording, so there is a chance that the dish is not aligned with the satellite that is needed for the recording.
The recording can only be started when the dish is aligned and the transponder is locked.
is there a delay in the timer function until the dish is aligned?
Just my conclusion for what I read here.

Sorry but this is nonsense.

[Huevos]

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

[Dimitrij]

Let's explain the logic again.

 

 

1)start  record 19.2E TV5MONDE (19:55 -21:01) use  C (because the priority is higher), not use A rotor

 

2)start record 23.5E NPO1 HD (20:00 -21:01)  use D (because this is the only free tuner for 23.5 at the moment)

 

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

 

When add satellite 23.5E to tuner A on the motor

3)start record 23.5E NPO2 HD (20:00 -21:01) use A (because this is the only free tuner for 23.5 at the moment)

 

 

Enigma selects the first free tuner with the highest priority for the record and enigma does not know that there is another record that needs the same tuner.

Edited by Dimitrij, 15 April 2023 - 14:35.