# Time remaining is incorrect when adding new tracks

**URL:** <https://discourse.libretime.org/t/time-remaining-is-incorrect-when-adding-new-tracks/802>\
**Category:** Dev Talk\
**Created:** [February 16, 2021, 11:42pm UTC](https://discourse.libretime.org/t/time-remaining-is-incorrect-when-adding-new-tracks/802 "2021-02-16T23:42:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bobjonkmandj](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/bobjonkmandj/32/340_2.png) [@bobjonkmandj](https://discourse.libretime.org/u/bobjonkmandj)\
**Post date:** [February 16, 2021, 11:42pm UTC](https://discourse.libretime.org/t/time-remaining-is-incorrect-when-adding-new-tracks/802/1 "2021-02-16T23:42:37Z")

</div>

One of our DJs reported an interesting bug: When he adds tracks to his show the Time Remaining at the bottom of the track list displays correctly. When he re-orders the tracks he’s selected, the track list displays incorrect values, even though the sum of the track lengths hasn’t changed. He’s created a YouTube video to illustrate the problem: [Libretime Scheduling Issue - YouTube](https://www.youtube.com/watch?v=n1CZ9X5aPBs)

We’re running LibreTime version 6ac31f3a1, but won’t be updating until we’ve got a dev server running (We have the hardware, but the SysAdmin has been too busy to set it up)

I suspect the Time Remaining calculation and display is done with Javascript in the browser. I haven’t tried to duplicate the problem (yet), but I suspect that once the track list is saved then  
the Time Remaining will display correctly in the Dashboard.

–Bob the Busy SysAdmin

---

<div class="post-metadata">

**Author:** ![robbt](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/robbt/32/15_2.png) [@robbt](https://discourse.libretime.org/u/robbt)\
**Post date:** [February 17, 2021, 1:20pm UTC](https://discourse.libretime.org/t/time-remaining-is-incorrect-when-adding-new-tracks/802/2 "2021-02-17T13:20:27Z")

</div>

Interesting, that certainly does look like a bug in the javascript. It would probably be a good idea to open an issue on github once it has been replicated.