Bugzilla – Bug 3426
Slimserver auto-refresh causes inaccuracies in UI song reporting
Last modified: 2008-09-15 14:39:24 UTC
(reference TMID 3203) User is seeing errors in the song listed at top-right in Slimserver UI. (user's short description) I am using three SQB3 and Slimserver 6.2.2. I open Slimserver, the correct SQB3 player is shown in the Windows drop-down window (called through the web interface and IP number). The other two SQB2 are ianctive/closed. I enter/play a/n album/playlist, the title of the first song is coorectly shown in the "Now playing" grey area. I skip it. The Correct title of the following song is shown in the "Now playing" grey area .... until the next automatic refreshing which brings back the former title in the same area and "bolds" the correct titrel in the playlist. I delete this info with the right-hand button, (on the light-grey panel), the correct song title is shown.... until the next automatic refreshing. Which brings back the former song's title. etc etc. etc. (user's long description) I have reset the web settings and stopped SlimServer (SS) I am using Internet Explorer V. 6.0.2800.1106 SP1 The exact sequence: Start SS Squeezebox (SQB) "Office" shown The playlists of the 3 Squeezeboxes are "empty". Back to SQB "Office" Dark Grey Area (DGA): Stop Power Off Volume 6 Repeat Off Shuffle Off Light Grey Area (LGA): Stopped Bowse Albums Album A inserted in the playlist Song 1 starts LGA: Now Playing : Title of song 1 DGA: Play Power On Volume 6 Repeat Off Shuffle Off sfsg (so far so good) First automatic refresh Music continues DGA: Stop Power Off LGA: Stopped No song title shown I try to SKIP to the next song No change Skip does not work the page trembles but no change except an old songtitle from the same or previous album shown under LGA Now Playing (sometimes the text starts at the left margin) DGA Play Power On Volume 6 Repeat Off Shuffle Off until the first automatic refresh Music continues DGA: Stop Power Off LGA Stopped No song title shown I refresh with the IE refresh button Music continues DGA Play Power On Volume 6 Repeat Off Shuffle Off LGA: Now Playing showing the correct songtitle (the text starts about half an inch more to the right) until the first automatic refresh DGA: Stop Power Off LGA Stopped No song title shown automatic change to the next song Music continues OK DGA Stop Power Off etc no change LGA Stpopped no song title In the playlist the active/correct songtitle is bolded Now I cannot Clear the playlist I try Remote: FWD works Next/correct songtitle bolded in the playlist but no change in DGA nor LGA Clear the playlist still does not work I hope this detailed account will facilitate communication.
I wonder if this is related to bug 3404. Would be great if he could test with a 6.3 nightly.
(In reply to comment #1) > I wonder if this is related to bug 3404. Would be great if he could test with > a 6.3 nightly. I have tried a 6.3 nightly, no change as far as bug 3426 is concerned.
chris to reproduce and see if it's related to multiple players.
(In reply to comment #3) > chris to reproduce and see if it's related to multiple players. I have tested my 3 SQB. No difference. A question/hint: Once the info under "Now playing" and the bolded songtitle in the playlist are not the same (especially after an auto-refresh bringing back an "old" songtitle) the problem starts.
I cannot reproduce this. Can you try the most recent nightly and see if you can still reproduce it? My steps: 2 SB's, playlists cleared, powered off. Selected SB #1. Found an album to play, hit the "play" icon, SB powered on and album started to play. Playlist frame displayed normally. After auto-refresh, no change to selected player, playlist, or any of the orange text settings in the dark gray area. This continues for as long as I let it play. I think the key thing in your list of steps is that after an auto-refresh, the power status had changed back to Off. Was the same player still selected or had it auto-selected a different player that was in fact turned off?
I can't reproduce this bug with 6.2.2 or 6.3. What are your shuffle and repeat settings? Is your content or playlists from some other application, like iTunes? Is there anything unusual about your setup that I should take note of in trying to reproduce this?
(In reply to comment #6) > I can't reproduce this bug with 6.2.2 or 6.3. > What are your shuffle and repeat settings? Is your content or playlists from > some other application, like iTunes? Is there anything unusual about your > setup that I should take note of in trying to reproduce this? OK. I am using iTunes only to import CDs and organise the music database. During the whole exercise, Power is ON, Shuffle and Repeat are OFF. The same SQB3 is playing and its name shown in the dropdown window. I start the sequence with the right-hand panel being clean. I select and play an album, any album. The music starts, Play is ON, Now Playing shows the first songtitle until the first auto-refresh. Play becomes Stop, Now Playing becomes Stopped, no songtitle is shown, the music continues unchanged. Clear does not function. I stop here. If you could reproduce until this point, that would be great. My PC is an ordinary Sony, 3 years old, windows home edition SP1, pentium 4 IE 6. I am using Slimserver 6.3. and 2 SQB2s (ethernet) and 1 SQB3 (WiFi). The 3 boxes work fine independently or synchronized with their remotes. Good luck.
Roger, after the auto-refresh, is a different player listed in the upper-right player select box?
(In reply to comment #8) > Roger, after the auto-refresh, is a different player listed in the upper-right > player select box? No, the same player is shown all the time in the select box. This player uses WiFi and is selected at the start of Slimserver through the appropriate command line. The other players use ethernet through electricity network called CPL in french. The CPL network works fine.
Is this perhaps not the Default skin? Default2 perhaps? I'm just guessing, since I haven't tried to reproduce When this problem occurs: 1) what is the mac addy for the player in the selection list 2) what is the url addy for a link in the DGA or LGA (pick a few if you want to be thorough and view properties from right click) 3) what is the url for the "clear" link, again right click and view properties for the link. 4) check the javascript console if you have access (firefox/safari). not much I can think of in specifics, as it's a longshot at this point.
(In reply to comment #10) > Is this perhaps not the Default skin? Default2 perhaps? I'm just guessing, > since I haven't tried to reproduce > When this problem occurs: > 1) what is the mac addy for the player in the selection list > 2) what is the url addy for a link in the DGA or LGA (pick a few if you want to > be thorough and view properties from right click) > 3) what is the url for the "clear" link, again right click and view properties > for the link. > 4) check the javascript console if you have access (firefox/safari). not much > I can think of in specifics, as it's a longshot at this point. I am using the default skin that comes with 6.3.0. version of slimserver. I suppose Mac addy means Mac Address of the active SQB3: 00:04:20:06:64:3D As for the rest of your questions, I am afraid they reach beyond my computer horizon. I am quite willing to provide the answers e.g. for Direct Graphics Access Leadless Grid Array etc but you have to help me to find the answers on my PC. Maybe a question from me: Can you reproduce the problem on your computer?
DGA = Dark Grey Area LGA = Light Grey Area as referred in the initial report. for getting link properties, right click on the link instead of left click. choose properties from the pulldown. copy and paste the url given. This will allow us to verify the consistency of the player identification in the links.
oh, and no. I've not been able to see this. but I am also ONLY every running 6.3, 6.5 and a couple local experimental versions, and they are all on a linux machine. I have a small setup at work on win2k, but use only softsqueeze. One player, I suspect, will never cause this problem. Another option: in the Default skin, the url's for the links should show up in the status bar at the bottom of the browser window. You can look at those when you move the mouse pointer over the "PLAY" link, and the "CLEAR" link. My guess is that those links won't match the selected player MAC when you are seeing the problem. That would at least confirm what has happened. As to how, I am at a loss for suspects at the moment, but we'll see. After the refresh that shows bad info, check the bottom of the browser window. See if there is anything that says something like "Done: with errors". I think, in IE, you can double-click on that and it will report the recent errors. if anything is there, that might help us locate the problem as well.
(In reply to comment #13) > oh, and no. I've not been able to see this. but I am also ONLY every running > 6.3, 6.5 and a couple local experimental versions, and they are all on a linux > machine. I have a small setup at work on win2k, but use only softsqueeze. One > player, I suspect, will never cause this problem. > Another option: in the Default skin, the url's for the links should show up in > the status bar at the bottom of the browser window. You can look at those when > you move the mouse pointer over the "PLAY" link, and the "CLEAR" link. My > guess is that those links won't match the selected player MAC when you are > seeing the problem. That would at least confirm what has happened. As to how, > I am at a loss for suspects at the moment, but we'll see. > After the refresh that shows bad info, check the bottom of the browser window. > See if there is anything that says something like "Done: with errors". I > think, in IE, you can double-click on that and it will report the recent > errors. if anything is there, that might help us locate the problem as well. I have connected the SQB WiFi or Ethernet : no change. NB: Using the IE refresh button puts everything in the right order and place ... until the next auto-refresh I hope this info will help you in your research: Before the sequence: http://localhost:9000/index.html?player=192.168.0.5 Player in window=correctplyer settings url's http://localhost:9000/setup.html?page=server&player=00%3A04%3A20%3A06%3A64%3A3d http://localhost:9000/setup.html?page=player&player=00%3A04%3A20%3A06%3A64%3A3d&playerid=00%3A04%3A20%3A06%3A64%3A3d http://localhost:9000/setup.html?page=player&player=00%3A04%3A20%3A06%3A64%3A3d&playerid=00%3A04%3A20%3A05%3Ab7%3Abe http://localhost:9000/setup.html?page=player&player=00%3A04%3A20%3A06%3A64%3A3d&playerid=00%3A04%3A20%3A05%3Aa9%3Aa3 Black area: DGA: http--localhost9000-status_header.htmlp0=playlist&p1=jump&p2=+1&player=00042006643d http--localhost9000-status_header.htmlp0=play&player=00042006643d http--localhost9000-status_header.htmlp0=pause&player=00042006643d stop=orange Repeat: http--localhost9000-status_header.htmlp0=playlist&p1=repeat&p2=0&player=00042006643d&start= http--localhost9000-status_header.htmlp0=playlist&p1=repeat&p2=1&player=00042006643d&start= http--localhost9000-status_header.htmlp0=playlist&p1=repeat&p2=2&player=00042006643d&start= Shuffle: Off=orange http--localhost9000-status_header.htmlp0=playlist&p1=shuffle&p2=1&player=00042006643d&start= http--localhost9000-status_header.htmlp0=playlist&p1=shuffle&p2=2&player=00042006643d&start= LGA Stopped clear colour area: http://localhost:9000/html/images/nav_download.gif http://localhost:9000/html/images/nav_clear.gif Album played: DGA http--localhost9000-status_header.htmlp0=playlist&p1=jump&p2=+1&player=00042006643d http--localhost9000-html-images-nav_play_sel.gif http--localhost9000-status_header.htmlp0=pause&player=00042006643d http--localhost9000-status_header.htmlp0=stop&player=00042006643d After auto-refresh: DGA: stop=orange skip url unchanged play url unchanged pause url unchanged repeat: ALL=orange http--localhost9000-status_header.htmlp0=playlist&p1=repeat&p2=0&player=00042006643d&start= http--localhost9000-status_header.htmlp0=playlist&p1=repeat&p2=1&player=00042006643d&start= http--localhost9000-status_header.htmlp0=playlist&p1=repeat&p2=2&player=00042006643d&start= LGA Stopped or showing sometimes prebious songtitle sometimes "old, old" songtitle I am at your disposal for further research on my side.
192.168.0.5, are you using a software player like winamp or windows media player?
(In reply to comment #15) > 192.168.0.5, are you using a software player like winamp or windows media > player? I use iTunes to rip my CDs and to organise the Music Base. I have Winamp and Windows Media Player on my PC but don't normally use them.
so 192.168.0.5 is the IP of one of your hardware players? I'm just curious becuase the player change handling does detect IP and MAC, but I'd have to double check that it works properly if an IP is used for a hardware player. The server normally expects the MAC address to be used for player=<> when a squeezebox or softsqueeze is connected.
(In reply to comment #17) > so 192.168.0.5 is the IP of one of your hardware players? I'm just curious > becuase the player change handling does detect IP and MAC, but I'd have to > double check that it works properly if an IP is used for a hardware player. > The server normally expects the MAC address to be used for player=<> when a > squeezebox or softsqueeze is connected. Your references to IP and Mac made me check my entire CPL network: IP numbers and MAC references. I had to make some adjustments in my modem. Could it be that a "muddle" of Mac addresses could cause Slimserver to "muddle" its display? Indeed, some problems seem to have been "solved" (at auto-refresh, the change from "play" to "stop" and "stopped" or the change under repeat from "off" to "all"?). But one issue remains: the display under "Now Playing": why do previous and old songtitles pop up under "Now Playing" at auto-refresh and why, using the IE refresh button, is the correct information displayed? To answer your question my hardware players have both IP and MAC addresses, hence my question above?
Everything with a MAC address will be assigned an IP address. However, on dynamic networks, the IP address is not always the same for a given MAC address. For this reason, Slimserver uses the MAC address to identify the player. If these were confused on the network, that could explain why slimserver was also confused. As for song title being incorrect, that sounds more like a case of bug 2510, which should be improved in more recent nightly builds of 6.3
(In reply to comment #19) > Everything with a MAC address will be assigned an IP address. However, on > dynamic networks, the IP address is not always the same for a given MAC > address. For this reason, Slimserver uses the MAC address to identify the > player. If these were confused on the network, that could explain why > slimserver was also confused. > As for song title being incorrect, that sounds more like a case of bug 2510, > which should be improved in more recent nightly builds of 6.3 Well, hm hm, the news is that this morning, after the first auto-refresh, on the Web interface, "PLAY" switches to "STOP" and "NOW PLAYING" to "STOPPED" with the songtitle disappearing. The display on the SQB3 continues correct (and the music also). The IE refresh button puts the display on the web interfcae back in place including the correct songtitle again until the next auto-refresh. I'm afraid, our exchanges will continue, more from you to me as I am at a loss about what to tell you to help. I will obviously provide you with any anwers you may need and I can provide. Concerning bug 2510, I hesitate to switch Slimserver version before noting progress on this issue, unless you can provide me with an argument about possible links between the two bugs.
Only one more from me, I'm out of ideas. I would suggest not using the IP addresses in the url for "player=", just let index.html load the default player and you can then select from the player list. A cookie will take care of remembering which one you last chose, so that eash restart will go to that player. Other than the missing url coding in the "player=" section of the urls you provided (which, I'm assuming is something wrong in pasting, since "/" becomes "-" as well), nothing seems to indicate that the player is wrong. The Active players' MAC address you gave in comment 11, and the urls seem to match it. If the urls really do look like that, then there is something else going on at a lower level, and I wouldn't have the first clue what to suggest for dealing with that, except for experimenting with a different browser just to see if it makes any difference at all.
(In reply to comment #21) > Only one more from me, I'm out of ideas. I would suggest not using the IP > addresses in the url for "player=", just let index.html load the default player > and you can then select from the player list. A cookie will take care of > remembering which one you last chose, so that eash restart will go to that > player. > Other than the missing url coding in the "player=" section of the urls you > provided (which, I'm assuming is something wrong in pasting, since "/" becomes > "-" as well), nothing seems to indicate that the player is wrong. The Active > players' MAC address you gave in comment 11, and the urls seem to match it. If > the urls really do look like that, then there is something else going on at a > lower level, and I wouldn't have the first clue what to suggest for dealing > with that, except for experimenting with a different browser just to see if it > makes any difference at all. If I understood you well there are two separate issues: 1. how to identify the default player in the url in the slimserver web interface. Ok, this is not really a problem. 2. more importantly: I understand you are refering to the "loose ends" such as "start=" of the urls in your software, urls such as REPEAT or SHUFFLE. I do not quite understand your reference to "lower level". I am surprised that there is no beginning of an explanation. But there is another point 3: why does the auto-refresh change "Now Playing" into "Stopped" and why does it bring back "previous" or "old" songtitles? and why is the IE refresh button displaying the correct songntitle? Does this mean that there may be no solution to some bugs? Following your suggestion and reference to bug 2510 I tried 6.5b 20th June nightly. Unfortunately, it did not run on my machine: only part of the web interface was displayed on my screen and the music lasted only approx. 5 minutes before being interrupted. I am wodering whether this is a RAM size issue? I noticed that the file of 6.5b is about double the size of a previous version. Could that mean that in the future 1028 RAM is needed? Do not misunderstand me! I am only trying to understand the pro and cons of Slimserver and the SQBs at this stage of development of my PC. I very much appreciate your efforts to assist me.
Answering some of your questions: 2. the urls are used to send parameters to teh server. why I asked for them is for the "player=00%3A04%3A20%3A06%3A64%3A3d". Some of your urls appear as "player=00042006643d" which is incorrect. I am assuming that this must be a copy past error, as other errors in the url would most likely result in a "not found" response from the server. If they are not a past error, then something else "lower level", meaning underneath the user interface level of IE, in the code, is interfering with the urls. Given that nothing so far has really shown the exact cause of the problem, I am digging much deeper to guess at that cause. You have no explanation, because it is getting very hard to understand WHY you are seeing what you are seeing. This is NOT happening for the majority of users, and has yet to be reproduced by myself or apparently anyone working at Slim Devices. why does the auto-refresh change "Now Playing") We don't know why in your case. We are guessing that somehow the server is getting one player confused with another. That the refresh is showing you the status of another player that is currently stoppped. This would explain why "now playing" changes to "Stopped" and why Play changes to Stop. However, this is not something that normally happens, so we are trying to figure out why. That is very hard when we are unable to reproduce locally and be able to look for more details. This does not happen for me at all. I have tried. "and why is the IE refresh button displaying the correct songtitle?") Clicking the refresh button loads the entire page as a fresh start. Just as if you had typed in a new url in the address bar. The refresh is using internal information to redraw a section of the page. They are two different processes, and so it is possible to have different results. "Does this mean that there may be no solution to some bugs?") No, not at all. There is always some solution somewhere. The problem is now that we don't really have a 'bug' to fix. Seomthing is happening, but we don't know exactly why it is happening in your case. It might be a bug, caused by what I described above, or it might be something we haven't throught of yet. I'd recommend staying away from 6.5 right now, given the current issues. bug 2510 really only applies in response to your comment 18, suggesting some of the issues were solved. Since this turned out to not be the case, bug 2510 isn't really of any use here. Ram size is unlikely to be the issue. I recommend that you re-contact support@slimdevices.com and get some one-to-one time on this. I fear that there just isn't enough information turning up here to figure out where the problem has originated. I'm only a volunteer developer, so if there is an isolated code problem, I can fix that. I'm afraid that I'm stumped right now based on the current information. Sorry that I cannot offer you much more to work on. I can assure you that Slim Devices will try their best to narrow down and solve the issue.
(In reply to comment #23) > Answering some of your questions: > 2. the urls are used to send parameters to teh server. why I asked for them is > for the "player=00%3A04%3A20%3A06%3A64%3A3d". Some of your urls appear as > "player=00042006643d" > which is incorrect. I am assuming that this must be a copy past error, as > other errors in the url would most likely result in a "not found" response from > the server. If they are not a past error, then something else "lower level", > meaning underneath the user interface level of IE, in the code, is interfering > with the urls. Given that nothing so far has really shown the exact cause of > the problem, I am digging much deeper to guess at that cause. You have no > explanation, because it is getting very hard to understand WHY you are seeing > what you are seeing. This is NOT happening for the majority of users, and has > yet to be reproduced by myself or apparently anyone working at Slim Devices. > why does the auto-refresh change "Now Playing") > We don't know why in your case. We are guessing that somehow the server is > getting one player confused with another. That the refresh is showing you the > status of another player that is currently stoppped. This would explain why > "now playing" changes to "Stopped" and why Play changes to Stop. However, this > is not something that normally happens, so we are trying to figure out why. > That is very hard when we are unable to reproduce locally and be able to look > for more details. This does not happen for me at all. I have tried. > "and why is the IE refresh button displaying the correct songtitle?") > Clicking the refresh button loads the entire page as a fresh start. Just as if > you had typed in a new url in the address bar. The refresh is using internal > information to redraw a section of the page. They are two different processes, > and so it is possible to have different results. > "Does this mean that there may be no solution to some bugs?") > No, not at all. There is always some solution somewhere. The problem is now > that we don't really have a 'bug' to fix. Seomthing is happening, but we don't > know exactly why it is happening in your case. It might be a bug, caused by > what I described above, or it might be something we haven't throught of yet. > I'd recommend staying away from 6.5 right now, given the current issues. bug > 2510 really only applies in response to your comment 18, suggesting some of the > issues were solved. Since this turned out to not be the case, bug 2510 isn't > really of any use here. Ram size is unlikely to be the issue. > I recommend that you re-contact support@slimdevices.com and get some one-to-one > time on this. I fear that there just isn't enough information turning up here > to figure out where the problem has originated. I'm only a volunteer > developer, so if there is an isolated code problem, I can fix that. I'm afraid > that I'm stumped right now based on the current information. Sorry that I > cannot offer you much more to work on. I can assure you that Slim Devices will > try their best to narrow down and solve the issue. A quick reaction on two of your points and one question: 1. The way urls show in my email is the way they show up on the status line of my PC 2. If some of this is related to IP/MAC confusion the question arises whether some of the network equipment is problematic at least for Slimserver My question is therefore: I am using a DG834 modem-router and XE104 CPL adaptors and a WG602 from the same company. Do the XE104 adaptors need to be identified in the DG834 as for instance the WG602 with IP and MAC?
1. If that is really the urls that you are seeing, then I'm surprised you are getting anything at all to work. I simply cannot even guess at how they would get mangled so badly, especially by IE. With that formatting, I'm not surprised they do not work. do you perhaps have any high security settings on your system? zonealarm or some type of netnanny or browser security program that could be getting in the way? 2. I'm no network analyst, so I cannot answer that one.
(In reply to comment #25) > 1. If that is really the urls that you are seeing, then I'm surprised you are > getting anything at all to work. I simply cannot even guess at how they would > get mangled so badly, especially by IE. With that formatting, I'm not surprised > they do not work. do you perhaps have any high security settings on your > system? zonealarm or some type of netnanny or browser security program that > could be getting in the way? > 2. I'm no network analyst, so I cannot answer that one. (In reply to comment #25) > 1. If that is really the urls that you are seeing, then I'm surprised you are > getting anything at all to work. I simply cannot even guess at how they would > get mangled so badly, especially by IE. With that formatting, I'm not surprised > they do not work. do you perhaps have any high security settings on your > system? zonealarm or some type of netnanny or browser security program that > could be getting in the way? > 2. I'm no network analyst, so I cannot answer that one. Many thanks for comment. Do I understand that you folks don't sleep at all? I am using Norton Internet Security with, what I always thought, a medium level securtiy. But, even if, would NIS be selective because only the urls on that line (repeat and shuffle) get that kind of treatment, not the urls related to e.g. Stop or Skip etc. On the second/network point: would you have a network specialist in the area or should I refer that point to SlimDevices? Thanks a lot Roger
I doubt norton has done anything, but you could try disabling it and restart...as a test. nothing really makes sense for causing urls to look like that, but at least it's a detail to watch for. I'll leave the rest for Chris et al.
(In reply to comment #27) > I doubt norton has done anything, but you could try disabling it and > restart...as a test. > nothing really makes sense for causing urls to look like that, but at least > it's a detail to watch for. > I'll leave the rest for Chris et al. I have de-activated Norton, stopped Slimserver and re-started Slimserver: no change
I've asked the support team to contact you, Roger. I don't want to hold up the Slimserver 6.3 release, but I don't want to close this bug as 'WORKS FOR ME' either, yet, so I've moved the target to 6.5.
(In reply to comment #29) > I've asked the support team to contact you, Roger. I don't want to hold up the > Slimserver 6.3 release, but I don't want to close this bug as 'WORKS FOR ME' > either, yet, so I've moved the target to 6.5. Thanks. I suppose we will hear from each other!
(In reply to comment #30) > (In reply to comment #29) > > I've asked the support team to contact you, Roger. I don't want to hold up the > > Slimserver 6.3 release, but I don't want to close this bug as 'WORKS FOR ME' > > either, yet, so I've moved the target to 6.5. > > Thanks. > I suppose we will hear from each other! > Following a suggestion from Daniel, I have tried Firefox: It works well that is no problems anymore with the display nor with "Now playing" and the songtitles etc after auto-refresh. Obviously a bug with IE. I will continue with Firefox. I am however surprised that other IE users apparently do not have this bug. Secondly: the status bar in Firefox shows the urls all the urls the same way with no "%" anywhere and no info behind "start=". But, by Jove, it's a pleasure to see Slimserver 6.2.2 work fine! I will eventually move up to 6.3 etc, but let me enjoy a well-working 6.2.2 under Firefox for some time. I will be back to you in the future. Thanks to all for the co-operation.
Well then, I'll go ahead and mark it 'works for me' for now, then, but I'll be keeping an eye out for similar problems in the future. And by all means re-open the bug if there's new information or some new facet to the problem.