OK, I thought that might be the problem. Once per minute is OK-ish, I suppose, but the user can continue to see details of the previous track for a long time.
What would be better, and would also reduce the load on the servers even more, would be to synchronise the refresh within (say) 5 secs of the start of each track. That way the user isn't confused, and you've reduced the server load probably by a half (given a two minute track length on average).
Is that a possibility?