I don't know what build this started happening, but the behavior I'm getting with the X10 MP3 remote's "play" button is not the same as using MC's play button or "Ctrl-P." I'm relatively sure that this was not the case until fairly recently.
Normally, as long as nothing is currently playing or on pause (i.e. MC is in a "stopped" state), hitting "play" (or Ctrl-P) will immediately start playing the song that's currently highlighted. When using the remote, however, the behavior is not the same (I typically use Theater View when using the remote.) When doing the same procedure with the remote, I get a short burst of music from the beginning of the new track, then it stops and I have to hit "play" again for the track to play. In other words, it cues the track up, plays a burst, and stops, waiting for a second "play" command. Once the track is playing the button works normally, toggling between play and pause, but once I hit "stop" it once again requires two hits to get the highlighted track to play.
This behavior is distinctly different from the actual mouse controlled "play" button in MC (or Ctrl-P), which always starts to play the track immediately on the first hit. This is totally repeatable on my system -- the "play" button and "Ctrl-P" have a different effect compared to using the remote's "play" button. The result is a confusing playback procedure when using the remote since the behavior is suddenely different.
Thanks for any help with this,
Larry
Author
Topic: Odd remote control "play" button behavior. (Read 1150 times)