AutoTimer Concerns

[ghines]

Hi all,

I recently asked this question but the answer got deleted, along with the question, during the recent website issues. So I will ask the question again.

I have an Autotimer setup for a program on Channel 7. This gets one entry in the Timers as I would expect however it is being recorded a couple of times. Could this be because Channel 7 appears in a couple of Bouquets? There is no Bouquet restriction in the Autotimer.

TIA

Greg

[prl]

Do you mean that there's only one timer showing for the AutoTimer in the AutoTimers list, or only one entry in the Timers list (TIMER from live TV)?

If the latter, was that at the time the AutoTimer created the timers, or at about the time the recordings were made? Do you still have the completed timer(s) in the timer list? Is there still only one, or are there several? Were all the recordings started at the same time, or at different times?

A timer (no matter how created, including from an AutoTimer) can only record on a single service. It doesn't matter how many times that service appears in bouquets. All the recordings we make (using IceTV-generated timers) on our in-use T4 use services that appear in three bouquets, but there's only ever one timer created.

What is your setting of MENU>Channels>AutoTimer, MENU>Setup>Guess existing timer based on begin/end? It's strongly recommended to turn it off, because having it on is known to cause multiple recording problems.

[Grumpy_Geoff]

Hi Greg,

Does your T4 still have the completed timer? If so, can you post its log entries, or copy them from \\BEYONWIZT4\Root\etc\enigma2\timers.xml

Cheers
Geoff

[ghines]

Hi Greg,

Does your T4 still have the completed timer? If so, can you post its log entries, or copy them from \\BEYONWIZT4\Root\etc\enigma2\timers.xml

Cheers
Geoff

Unfortunately not, I have done a clean up. Can wait until the next multiple recordings and will then post the result. What are you looking for??

Greg

[Grumpy_Geoff]

... What are you looking for??

To see when each recording began (as what you see in the media list isn't necessarily the actual recording start time).
Also to see if there were EPG time changes, as that can also initiate another copy of the recording (*_001, *_002 e.t.c.)

[ghines]

... What are you looking for??

To see when each recording began (as what you see in the media list isn't necessarily the actual recording start time).
Also to see if there were EPG time changes, as that can also initiate another copy of the recording (*_001, *_002 e.t.c.)

Thanks. We don't have to wait long as the timer is for tomorrow night.

I'm assuming that I should not get multiple recordings if the same channel is in several bouquets. Yes/No?

Greg

[Grumpy_Geoff]

...
I'm assuming that I should not get multiple recordings if the same channel is in several bouquets. Yes/No?

Yes, as far as I know.
Can you extract the AutoTimer entry or grab an OpenWebif screenshot of it as per this post
I'll then set up an A/T for it here as a test


Cheers
Geoff

[simoncasey]

It could be because channel 7 is simulcast on a number of channels 7,70 and 71. So you may be getting those and would explain the issue if it only happens on channel 7. Setting a bouquet as well as a channel would fix it.

[ghines]

Can you extract the AutoTimer entry or grab an OpenWebif screenshot of it as per this post

Will this do?
Autotimer.xml

Code: Select all

 <timer name="Wanted - Season Premiere" match="Wanted" enabled="yes" from="20:00" to="22:00" searchCase="sensitive" overrideAlternatives="1">
  <serviceref>1:0:1:520:502:1013:EEEE0000:0:0:0:</serviceref> <!-- 7 Digital -->
  <afterevent>shutdown</afterevent>
  <exclude where="dayofweek">weekend</exclude>
 </timer>

Timers.xml

Code: Select all

 <timer name="Wanted - Season Premiere" match="Wanted" enabled="yes" from="20:00" to="22:00" searchCase="sensitive" overrideAlternatives="1">
  <serviceref>1:0:1:520:502:1013:EEEE0000:0:0:0:</serviceref> <!-- 7 Digital -->
  <afterevent>shutdown</afterevent>
  <exclude where="dayofweek">weekend</exclude>
 </timer>

[prl]

It could be because channel 7 is simulcast on a number of channels 7,70 and 71. So you may be getting those and would explain the issue if it only happens on channel 7. Setting a bouquet as well as a channel would fix it.

The autotimer in ghines posted example has an explicit serviceref. The 7 Digital "clones" all have different servicerefs.

E.g. for Sydney (which I think is where ghines is, from the Seven serviceref):

Code: Select all

1:0:1:520:502:1013:EEEE0000:0:0:0: 7 Digital
1:0:1:521:502:1013:EEEE0000:0:0:0: 7 Digital 1
1:0:1:524:502:1013:EEEE0000:0:0:0: 7 Digital

The third number is different for the three different LCNs for 7 Digital, and it's the first one in ghines's posted timers..

I rather think that having "Guess existing timer based on begin/end" enabled is the culprit, but there's been no confirmation of te setting from ghines.

[Grumpy_Geoff]

Can you extract the AutoTimer entry or grab an OpenWebif screenshot of it as per this post

Will this do?
Autotimer.xml

Code: Select all

 <timer name="Wanted - Season Premiere" match="Wanted" enabled="yes" from="20:00" to="22:00" searchCase="sensitive" overrideAlternatives="1">
  <serviceref>1:0:1:520:502:1013:EEEE0000:0:0:0:</serviceref> <!-- 7 Digital -->
  <afterevent>shutdown</afterevent>
  <exclude where="dayofweek">weekend</exclude>
 </timer>

Hi Greg,

How did "Wanted" go?
My test AutoTimer generated the expected timer, and that timer had no issues producing a single recording with start time 20:55. I used the same criteria as you had, apart from my 'Custom offset - offset before recording' to differentiate this from my other copy of "Wanted" that is from my IceTV series recording.
Below is the AutoTimer definition, and the resultant timer execution log, and recording files.

Wanted - files.png (12.99 KiB) Viewed 2305 times

Cheers
Geoff

[ghines]

Can you extract the AutoTimer entry or grab an OpenWebif screenshot of it as per this post

Will this do?
Autotimer.xml

Code: Select all

 <timer name="Wanted - Season Premiere" match="Wanted" enabled="yes" from="20:00" to="22:00" searchCase="sensitive" overrideAlternatives="1">
  <serviceref>1:0:1:520:502:1013:EEEE0000:0:0:0:</serviceref> <!-- 7 Digital -->
  <afterevent>shutdown</afterevent>
  <exclude where="dayofweek">weekend</exclude>
 </timer>

Hi Greg,

How did "Wanted" go?
My test AutoTimer generated the expected timer, and that timer had no issues producing a single recording with start time 20:55. I used the same criteria as you had, apart from my 'Custom offset - offset before recording' to differentiate this from my other copy of "Wanted" that is from my IceTV series recording.
Below is the AutoTimer definition, and the resultant timer execution log, and recording files.

Wanted - AT-test .png

Wanted - timer log.png

Wanted - files.png

Cheers
Geoff

You would not believe it Geoff. Only recorded once last night, and that's the first time it only recorded once since the series started. The series is finished now so I guess we will just have to wait until something happens again. Thanks for all your effort.

Greg