Project

General

Profile

Forums » General »

entry.start_real does not contain the real start time

Added by Ken Fox over 7 years ago

Hi there,

I'm using the json api "/api/dvr/entry/grid" to retrieve information about available recordings. The returned information contains two fields about the recording start time:

- start
- start_real

According to the documentation (/api/dvr/entry/class), "start" is the start time as noted in the EPG, whereas "start_real" is the actual start time of the recording. However, I found in the resulting json document, that "start_real" ALWAYS contains the "start" time minus 30 seconds. If I record a already running show, I would expect "start_real" to be the time, when I hit the record-button.

Is this a bug? Or does start_real have a different meaning?

Btw.: I'm using tvheadend V4.0.8 on debian.

Regards
Ken


Replies (1)

RE: entry.start_real does not contain the real start time - Added by Joe User over 7 years ago

I am using 4.1 and the help for the recording profile says:

Pre-recording padding : Start recording earlier than the defined start time by x minutes: for example, if a program is to start at 13:00 and you set a padding of 5 minutes it will start recording at 12:54:30 (including a warm-up time of 30 seconds). If this isn't specified, any pre-recording padding as set in the channel or DVR entry will be used.

So, maybe it is the time Tvheadend "should" start the recording including that "warm-up time of 30 seconds"?? If you change the padding in the recording profile, do the numbers reflect the change?

If you look in "finished recordings" you will see the "scheduled start time" is always the EPG scheduled start time and not the actual time the recording started. (And scheduled stop time is also the EPG stop time and not when the recording was actually stopped.)

If you need the real time the recording started, maybe you can use something like the "stat" command on the file.

    (1-1/1)