frodovdr/vdr
1
0
Fork 0
mirror of https://github.com/VDR4Arch/vdr.git synced 2023-10-10 13:36:52 +02:00
Code Issues Releases Wiki Activity

Added a note to vdr.5 about event ids possibly changing when an event moves from one table to another

Browse Source
This commit is contained in:
Klaus Schmidinger 2022-12-26 13:24:09 +01:00
parent 4372d55dd1
commit a0f79bdd5f
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
HISTORY
View File

@ -9833,10 +9833,12 @@ Video Disk Recorder Revision History
- Avoiding a zero sized array in cDevice::GetDevice() (thanks to Marko Mäkelä). - Avoiding a zero sized array in cDevice::GetDevice() (thanks to Marko Mäkelä).
- Now checking the video directory after setting the user id. - Now checking the video directory after setting the user id.
2022-12-24: 2022-12-26:
- Updated the Italian OSD texts (thanks to Diego Pierotto). - Updated the Italian OSD texts (thanks to Diego Pierotto).
- Fixed restoring the volume at program start (thanks to Matthias Senzel). - Fixed restoring the volume at program start (thanks to Matthias Senzel).
- Fixed symmetry of Begin/EndSegmentTransfer() calls in cEIT::cEIT() (thanks to - Fixed symmetry of Begin/EndSegmentTransfer() calls in cEIT::cEIT() (thanks to
Jörg Wendel). Jörg Wendel).
- Added a note to epg.h about not messing with event ids (suggested by Winfried Köhler). - Added a note to epg.h about not messing with event ids (suggested by Winfried Köhler).
- Added a note to vdr.5 about event ids possibly changing when an event moves from
one table to another.

6
vdr.5
View File

@ -8,7 +8,7 @@
.\" License as specified in the file COPYING that comes with the .\" License as specified in the file COPYING that comes with the
.\" vdr distribution. .\" vdr distribution.
.\" .\"
.\" $Id: vdr.5 5.7 2022/11/14 16:25:58 kls Exp $ .\" $Id: vdr.5 5.8 2022/12/26 13:24:09 kls Exp $
.\" .\"
.TH vdr 5 "27 Dec 2021" "2.6" "Video Disk Recorder Files" .TH vdr 5 "27 Dec 2021" "2.6" "Video Disk Recorder Files"
.SH NAME .SH NAME
@ -917,7 +917,7 @@ tab (@);
l l. l l.
<channel id> @is the "channel ID", made up from the parameters defined in 'channels.conf' <channel id> @is the "channel ID", made up from the parameters defined in 'channels.conf'
<channel name> @is the "name" as in 'channels.conf' (for information only, may be left out) <channel name> @is the "name" as in 'channels.conf' (for information only, may be left out)
<event id> @is a 32 bit unsigned int, uniquely identifying this event <event id> @is a 32 bit unsigned int, uniquely identifying this event (see note)
<start time> @is the time (as a time_t integer) in UTC when this event starts <start time> @is the time (as a time_t integer) in UTC when this event starts
<duration> @is the time (in seconds) that this event will take <duration> @is the time (in seconds) that this event will take
<table id> @is a hex number that indicates the table this event is contained in (if this is left empty it will be set to 0x00; and value less than 0x4E it will be treated as if it were 0x4E) <table id> @is a hex number that indicates the table this event is contained in (if this is left empty it will be set to 0x00; and value less than 0x4E it will be treated as if it were 0x4E)
@ -942,6 +942,8 @@ Note that the \fBevent id\fR that comes from the DVB data stream is actually
just 16 bit wide. The internal representation in VDR allows for 32 bit to just 16 bit wide. The internal representation in VDR allows for 32 bit to
be used, so that external tools can generate EPG data that is guaranteed be used, so that external tools can generate EPG data that is guaranteed
not to collide with the ids of existing data. not to collide with the ids of existing data.
Also note that some broadcasters change the \fBevent id\fR when an event is moved
from one table to another.
The \fBauxiliary data\fR can be used for plugin specific purposes and has no meaning The \fBauxiliary data\fR can be used for plugin specific purposes and has no meaning
whatsoever to VDR itself. It will \fBnot\fR be written into the \fIinfo\fR file of whatsoever to VDR itself. It will \fBnot\fR be written into the \fIinfo\fR file of