Scheduled recordings start too early leading to :59:59 times

[smarquard]

If you schedule a recording to start on the hour, e.g.:

galicaster 2016-07-20 14:30:33,823 INFO scheduler/scheduler Create timer for MP 56458750, it starts at 2016-07-20T15:00:00

Then Galicaster can start recording slightly early:

galicaster 2016-07-20 14:59:59,790 INFO scheduler/scheduler Start record 56458750, duration 3000000 ms

and you get a start time in the manifest like *:59:59:

gc_hahn2_20160713T16h34m23_3/manifest.xml:
<mediapackage duration="3000043" id="56458750" start="2016-07-20T12:59:59" xmlns="http://mediapackage.opencastproject.org">

which is a bit annoying.

[smarquard]

Also elapsed time will typically show as 49:59 in the recording UI for a 50:00 (50 minutes) recording, but 50:00 in the media manager.

[hcaloto]

@dpeite, take a look at this issue and let's check if there is a simple solution

[silviabf]

This continues happening

[smarquard]

Would be nice to get this fixed...

[smarquard]

We're seeing ":59" times in the Galicaster Media manager, and also in the final published recording in the Opencast player, e.g.:

March 16 2017, 8:59:59 am

[Alfro]

I need to take a look at this, but at a first glance, it seems it can be related to #470

[smarquard]

I think it's because Galicaster starts recording slightly before the scheduled time, e.g.:

galicaster 2017-03-17 07:59:59,277 INFO scheduler/scheduler Timeout to start record 492634213855766528, duration 3300000 ms

and then writes the actual start time into the mediapackage that's ingested.