Since we elected to remove the "transport" showBriefly controls, a user has to wait more than 1.5 seconds to have any visual feedback that the song that they are playing is coming up. On ip3k players, when you hit fwd, for next, for instance, on a local track, the visual feedback is almost instant showing you the name of the next track (and the track generally starts just as quick).

On SP, on baby and jive, in particular, the next track details don't appear until the playerstatus comes back, which can takes 1.5 seconds minimum, usually.

I was doing testing with my family and they would frequently overshoot when moving forward or backward track by track, and when I compared with ip3k, there wasn't nearly the same problem.

Visual feedback of remote streams actually responds quicker in this regard than local music, because we feed the showBriefly message into the NP title area for remote streams.

There is a showBriefly messages that come back from SC much sooner that the playerstatus message that contain the name of the next track to play, but we are completely suppressing this message, since we didn't want as many popup messages to appear.

To remedy this, I have, for local streams, done the same showBriefly transformation (push it's text into the NP title area) that we do for remote streams.  I will check this code in after posting this bug.

I'd like feedback on the new behavior after you try it out. 

To test, after getting the updated fw, on the NP Screen, try doing fwd or back, or play a preset or new track. You'll see the name of track to be played appear quickly (with "Now playing" in the artist/album line, since this is what SC sends when a track is played). When the playerstatus message comes back, the "Now playing" message will switch to the artist/album name. From this you can see how long you would have had to have waited to get any feedback about the "to be played" track.