Airtime 2.5.1 broadcasted silence when the clocks changed this past weekend (BST -> GMT)
  • On Saturday night/Sunday morning, our Airtime production server (v2.5.1, Ubuntu 12.04.5 LTS) broadcast 1 hour of silence during the extra hour created when the clocks went back, even though we had scheduled content for that time. See the attached screenshot for the details of the show from 00:00 (BST) to 01:00 (GMT) - 2 hours.

    ls_script.log contains the following lines:
    2014/10/26 01:00:34 [s0:3] Finished with "/var/tmp/airtime/pypo/cache/scheduler/4653.mp3".
    2014/10/26 01:00:34 [amplify_5470:3] End of the current overriding.
    2014/10/26 01:00:34 [cross_5473:3] No next track ready yet.
    2014/10/26 01:00:34 [schedule_noise_switch:3] Switch to map_metadata_5601 with forgetful transition.
    2014/10/26 01:00:34 [lang:3] transition called...
    2014/10/26 01:00:34 [dummy(dot)3:3] Source failed (no more tracks) stopping output...
    2014/10/26 01:00:34 [dummy(dot)2:3] Source failed (no more tracks) stopping output...

    Is anyone aware of this bug/know of a fix?

    many thanks

    James