[vdr] [feature request] recording length computation and storage

Steffen Barszus steffenbpunkt at googlemail.com
Fri Aug 19 15:30:07 CEST 2011


On Fri, 19 Aug 2011 14:48:46 +0200
Klaus Schmidinger <Klaus.Schmidinger at tvdr.de> wrote:

> On 19.08.2011 14:39, Steffen Barszus wrote:
> > On Fri, 19 Aug 2011 12:21:24 +0200
> > Klaus Schmidinger<Klaus.Schmidinger at tvdr.de>  wrote:
> >
> >> On 08/19/11 11:46, Steffen Barszus wrote:
> >>> Hi !
> >>>
> >>> After having seen that there are several plug-ins computing the
> >>> recording length on their own and that being a very expensive task
> >>> (in respect of io and cpu) and also the same implementation needs
> >>> to be copied over and over again, i would like to request, that
> >>> vdr is storing the length of a recording and make it accessible
> >>> to the plug-ins. I would imagine, that some logic to store it in
> >>> the info file after/while generating/writing the index would be a
> >>> good way.
> >>>
> >>
> >> How about cIndexFile::GetLength()?
> >> This was newly added in version 1.7.20.
> >
> > Not yet - its returning the number of frames - to have one
> > calculation, length in seconds would be required (Ok, its available
> > as well).
> >
> > Also it reads the index directly (if i'm not mistaken, i can barely
> > read C), which would then be read x-times , where x is the number of
> > plugins using it ( + vdr ? I'm not sure of it ).
> >
> > I would think that in recording.h as public member of class
> > cRecordingInfo would make sense. In my understanding the recordings
> > information are held in memory after reading it with
> > ScanVideoDir, this should be part of that information in
> > memory (not reading file from disk for this separately).
> 
> I don't want to make this part of the 'info' file.
> Besides, it's only the directory entry that gets read, not
> the file itself.

Where it gets stored is not my point, that it can be served from in
meory data read by ScanVideoDir is my point. 

- read&compute by the core
- dont access harddisk for known recordings
- dont do it multiple times, if more then one part of vdr wants to know
  it. 

If its only in memory and read by the scanner its fine with me. 

for medium to large recording base we speak about minutes not
milliseconds for reading that data. 






More information about the vdr mailing list