[vdr] [RFC] Eliminating the 'summary' field of timers

Klaus Schmidinger Klaus.Schmidinger at cadsoft.de
Mon Feb 20 17:42:55 CET 2006

Some (external) applications require a way of uniquely
identifying timers. Currently some of these use the upper
16 bit of the 'flags' field, while others use the 'summary'
field. In an effort to make things more straightforward
(and simpler, from VDR's point of view ;-) I propose the
following changes:

- The 'summary' field in the timer definition becomes a pure
   string parameter, into which (external) applications can
   write whatever they like. VDR will read and write it, but
   otherwise won't do anything with it. The name of this field
   would be changed to something like 'aux' or so.

- The description of a recording is taken exclusively from its
   related EPG data. If an application wants to use a different
   description it would have to set it with SVDRP/PUTE and use
   table ID 0x00, so that it won't be overwritten (as a side effect,
   however, this would also disable VPS for such an event).
   An added bonus of this method would be that not only the
   'description' can be set, but also 'title' and 'short text'.

- The upper 16 bit of the timer's 'flag' field are no longer
   given any special treatment, and also shouldn't be used.
   Only the flags defined in vdr.5 shall be used.

- The cEvent::eventID is changed to u_int32_t so that fake
   event ids won't collide with real ones (by using values
   greater than 0xFFFF).

- The 'E' record of the recording's EPG data will also be
   written into 'info.vdr'.

- A new record in 'info.vdr' will hold the 'aux' string of the
   timer that created this recording.

If we can agree on these changes until next weekend, I would
incorporate them into the upcoming version 1.4.


More information about the vdr mailing list