Upcoming overlays duration

You have a question or need an advice about how to do something? Ask it here!
Post Reply
User avatar
hdradio
Posts: 625
Joined: 10 Apr 2012 17:36
Location: Crete, Hellas
Upcoming overlays duration

Post by hdradio »

Is there any explanation why every time I click the Upcoming overlays ribbon it shows different results in duration ? My clicks had a 4-5 secs difference.
Look at "Time is" overlay:

Here is shows at 17:30 00:02 and 18:00 00:02
2014-12-12_172001.png
2014-12-12_172001.png (8.7 KiB) Viewed 4655 times
Here it shows at 17:30 00:02 and 18:00 00:00
2014-12-12_172002.png
2014-12-12_172002.png (14.78 KiB) Viewed 4655 times
Here it shows at 17:30 00:00 and at 18:00 00:02
2014-12-12_172003.png
2014-12-12_172003.png (8.7 KiB) Viewed 4655 times
User avatar
radio42
Site Admin
Posts: 8926
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Upcoming overlays duration

Post by radio42 »

Maybe random selection of multiple advert tracks?
That's what I tried to explain when you requested the feature - that it is for advert slots not always possible to determine the exact tracks, if the slots are either overbooked or a campaign might contain multiple tracks (which are randomly) picked or if there are dynamic fillers used or other elements are dynamic/random...
User avatar
hdradio
Posts: 625
Joined: 10 Apr 2012 17:36
Location: Crete, Hellas
Re: Upcoming overlays duration

Post by hdradio »

But why when I click test overlay everything shows as it should ?
User avatar
radio42
Site Admin
Posts: 8926
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Upcoming overlays duration

Post by radio42 »

Now I see what you mean. And yes, its a slight bug when calculating the duration, but only in case the list of upcoming overlays contained exactly the same script to be executed.
That will be corrected with the next version.
User avatar
radio42
Site Admin
Posts: 8926
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Upcoming overlays duration

Post by radio42 »

Fixed in v3.0.14.28

Post Reply