[vdr] Re: Timer does not record in 1.3.11 (wrong event handling)

[Thomas Schorpp <t.schorpp@gmx.de>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Klaus Schmidinger wrote:
| Peter Evertz wrote:
|
|>I have vdr 1.3.11 running. VPS in OSD is switched off.
|>With vdradmin i have a autotimer to record als StarTrek stuff.
|>
|>Once a week there is first "DeepSpaceNine" (16:00-17:00) then "Voyager"
|>(17:00-18:00).
|>Vdradmin adds two timers 15:55-17:15 and 16:55-18:15.
|>
|>It happens that Voyager will not be recorded most of the time.
|>
|>The first timer runs normaly. Then the log shows this:
|>
|>Jul 11 16:59:40 pec4 vdr[758]: channel 30 (SAT.1) event 17:00 'Star Trek -
|>Raumschiff Voyager' status 2
|>Jul 11 17:00:01 pec4 vdr[711]: timer 1 (30 1555-1715 'Star Trek  Deep
Space
|>Nine~Wettkampf in der Holosuite') set to event Son 11.07.2004 17:00-18:00
|>'Star Trek - Raumschiff Voyager'
|>
|>after Recording:
|>Jul 11 17:15:00 pec4 vdr[711]: timer 1 (30 1555-1715 'Star Trek  Deep
Space
|>Nine~Wettkampf in der Holosuite') stop
|>Jul 11 17:15:00 pec4 vdr[711]: deleting timer 1
|>
|>and so the timer for "Voyager" is gone.
|>
|>Any Idea what is going wrong ?
|
|
| There may be something wrong with assigning events to timers, but that
can't
| explain why the second timer didn't record anything.
|
| Are there no log entries regarding the second timer?
|
| Klaus
|
|
|
cause the programmed event doesnt exist anymore.
sat.1 shifted schedule for "voyager" to 1730 MESZ since 2 weeks.

y
tom








-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iQCVAwUBQPlUgGqsze5HSzyoAQKtcgQAotFuUlk6bpbXJPEZkikAZT+twmzh13Gr
DqUrvyPMPSsyLHdvim90fF6+1E7MX93u1uXpaWJLMwa9V2g7U9yVALGjFDb6aRpn
nTgYhYYX2N9ir5imkJwFsRtRKMUIOipxckZ3B7/BkU3QyT4VcUrJbsmf4DwLezx2
REQW6Xti62E=
=Oz08
-----END PGP SIGNATURE-----