Bugzilla – Bug 12045
Audio playback switches back and jumps
Last modified: 2009-10-05 14:36:00 UTC
While I was listening to XM, I went back and played an MP3 album from my library. Suddenly, with no action on my part, Controller switched back to doing XM Then, while listening to mp3 from my library, Controller jumped to the next track before finishing the one it was playing from my Library. This is with today's update (5/13)
Were you connected to Squeezenetwork or Squeezecenter when this happened? Can you also verify that the MAC address of your controller is correct? I.E. check the Lable in the battery compartment with the reported MAC address in firmware Settings > Advanced > About
SqueezeCenter. I never use SqueezeNetwork, which I find awkward, and can never figure out how to exit.
What add-on were you using to listen to XM?
The new XM beat version from ndpotter, which works perfectly on Squeezebox and softsqueeze
New firmware will be needed to fix this issue, code merge needed.
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the single original product.
QA to verify on 7.4
James: if you are feeling particularly adventuresome...you can install 7.4 to see if this issue has been addressed or if it's still an issue for you. So far I have not experienced the described behavior with 7.4
I'm going to mark this bug as fixed as I can not reproduce this with 7.4. Please verify then reopen the bug if you can still see it with that version.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.