Not sure where the best place to report this is, but figured I'd post here anyhow.
When you view the Current Rotational Queue with any songs queued up to play, it shows you the ETA of when they will play. However, the times are all wrong. Instead of basing the ETA on each individual song length going down the stack, it appears to use the length of the CURRENT playing song for all the ETAs in the calculations.
Just a minor thing, but something I spotted.
Spotted bug on Slay Radio
Spotted bug on Slay Radio
Lie with passion and be forever damned...
Re: Spotted bug on Slay Radio
Thanks for the report!
We'll look into that!
We'll look into that!
Re: Spotted bug on Slay Radio
No worries
Just to give an example, if it wasn't completely clear. Say you have four songs queued, lasting 3, 4, 5, and 6 minutes long respectively. The first song plays at 12:00 for example, and the ETAs update.
It will say song 2 will start at 12:03, which is correct. However, it will also say that song 3 will start at 12:06 (instead of 12:07), and song 4 will start at 12:09 (instead of 12:12).
When song 2 actually gets going, it will say that song 3 will start at 12:07, which is now correct. But it will say song 4 will start at 12:11, instead of 12:12.
Just to give an example, if it wasn't completely clear. Say you have four songs queued, lasting 3, 4, 5, and 6 minutes long respectively. The first song plays at 12:00 for example, and the ETAs update.
It will say song 2 will start at 12:03, which is correct. However, it will also say that song 3 will start at 12:06 (instead of 12:07), and song 4 will start at 12:09 (instead of 12:12).
When song 2 actually gets going, it will say that song 3 will start at 12:07, which is now correct. But it will say song 4 will start at 12:11, instead of 12:12.
Lie with passion and be forever damned...
Re: Spotted bug on Slay Radio
Yup. I think we have sorted it now. It was pulling the duration of the song from the wrong source and in the wrong manner.
Re: Spotted bug on Slay Radio
Just noticed that the ETA is still bugged but in a different way! Okay, let's try to explain here.
Imagine song A has just started, beginning at time J and lasts length K. Song B is scheduled after it and lasts length L. Song C is scheduled third and lasts length M.
On the left it will show Song A playing, with the time until song B starts counting down correctly. In the upcoming queue, it will list Song B as next. Except the ETA shown for song B is not J+K, it's actually J+L. Song C is then listed with an ETA of J+L+M, not J+K+L.
So if song A starts playing at 12:00 and lasts 4 minutes, and song B lasts 8 minutes, the ETA shown for song B is not 12:04, but 12:08 instead.
Hopefully that now makes sense :p
Imagine song A has just started, beginning at time J and lasts length K. Song B is scheduled after it and lasts length L. Song C is scheduled third and lasts length M.
On the left it will show Song A playing, with the time until song B starts counting down correctly. In the upcoming queue, it will list Song B as next. Except the ETA shown for song B is not J+K, it's actually J+L. Song C is then listed with an ETA of J+L+M, not J+K+L.
So if song A starts playing at 12:00 and lasts 4 minutes, and song B lasts 8 minutes, the ETA shown for song B is not 12:04, but 12:08 instead.
Hopefully that now makes sense :p
Lie with passion and be forever damned...