[mythtv] scheduling, starttime accuracy

Nigel Pearson nigel at ind.tansu.com.au
Thu Feb 12 22:06:15 UTC 2009

On Thu, Feb 12, 2009 at 04:27:26PM +1100, Nigel Pearson wrote:
> Haven't looked yet, but suspect its just the way the code works.
> e.g. Recording 1 ends at 8:30. Recording 2 starts at 8:30 on
> the same card, The scheduler and file IO takes 3sec to create
> a new recording file, update the database, et c., but the start
> time is recorded as the scheduled time of 8:30.

On 13/02/2009, at 3:51 AM, David Engel wrote:
> That would be me several years ago.  I used (and still do) a 5 second
> pre-roll and hated seeing all of my recordings displayed as starting
> at xx:29 and xx:59 and having filenames with *2957 and *5957.  I
> changed the scheduler to round the starttime to the nearest minute.


In hindsite, 'twould have been much better
to round on display in playbackbox?
(but having non-messy filenames is
  advantageous, so I will forgive you :-)

> 4) Could you use the ctime of the recording file?

Brilliant workaround! Won't break anything,
and much more reliable than what I was planning
(looking for timestamp in backend log:
2009-02-12 12:00:03.246 Started recording: blah)

Nigel Pearson, nigel at ind.tansu.com.au|"Gentlemen!              |
Telstra Net. Eng., Sydney, Australia | You can't fight in here-|
Office: 9202 3900    Fax:  9212 6348 |   this is the war room!"|
Mobile: 0408 664435  Home: 9792 6998 |     Dr Strangelove      |

More information about the mythtv-dev mailing list