Inaccurate time problem SOLVED (was RE: [slim] Slimbox-Newbie with questions)
Hi again and sorry to reply to myself ... The problems that I had, i. e. - strange behaviour of the "next letter" timeout in searches via remote - displayed stuff on the squeezebox vanishing too quickly - wildly fluctuationg time with the daylight screensaver were all caused by a glitch in the server's time source. A 'watch -n 1 -d ntptime', while crude, showed the same skewed results. Apparently most reasonably modern CPU have TSC capability, which basically means using the CPU's clock generator as an accurate time source. I had 'AMD 76x native power management' in my .config, which seems to change frequency on the fly without notifying the timers -> go figure. The same could happen with any other kind of non-cpufreq throttling - if you don't want to disable it, disabling TSC altogether (kernel option + notsc boot option) works, but is not recommended. C. ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
RE: [slim] Slimbox-Newbie with questions
While I don't know that I am much help with the rest of your post, the on thing that I would point out is that the version you are running (6.0a) is considered alpha at best. Not that it doesn't work well, but it is not ready for "production" release. You may consider dropping back to the current production release and see if this fixes your usability problems I'd prefer to be able to use the stable version, but with no unicode support on the server and no "browse music folder" option on the box I wouldn't be able to listen to my Japanese tracks at all. FWIW, I tried 5.4.0 and it's exactly the same. My very limited perl reading skills showed that the timer that jumps to the next letter is basically an alarm that triggers at a certain absolute time, not some predefined "seconds from now". Considering that the clock display on the device is off by 3 seconds at times the other issues don't surprise me. According to the code it should be impossible to get a "=>" in the middle of a Input.Text string... I get them anyway. Will test some more tomorrow. Anyway, thanks for the welcome! C. ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
RE: [slim] Slimbox-Newbie with questions
> I just received my Squeezebox yesterday, and so far I love it! Glad to hear it. Welcome to the community... > > First of all a bit about my configuration: > > SlimServer 6.0a 2005-02-25, generic tarball > server machine: Dual 1.6 GHz Athlon MP, 1 GB RAM > The Squeezebox is bridged into my WLAN via an AirPort Express :) > While I don't know that I am much help with the rest of your post, the on thing that I would point out is that the version you are running (6.0a) is considered alpha at best. Not that it doesn't work well, but it is not ready for "production" release. You may consider dropping back to the current production release and see if this fixes your usability problems then you can decide if you want to stay with the solid (but less feature rich) version or jump back to the bleeding edge (and prone to some problems) version. What ever you decide, you will get great support from the community. ~c ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
[slim] Slimbox-Newbie with questions
Hi all! I just received my Squeezebox yesterday, and so far I love it! First of all a bit about my configuration: SlimServer 6.0a 2005-02-25, generic tarball server machine: Dual 1.6 GHz Athlon MP, 1 GB RAM The Squeezebox is bridged into my WLAN via an AirPort Express :) Music playback works flawlessly and the quality is well above my expectations even over analog, however I've run into a few useability glitches: 1) The daytime screensaver does not work all that well. The seconds get updated in irregular intervals of 2-4 seconds only, sometimes it goes a second backwards even. 2a) The way the text input for the search (via remote) works seems a little strange to me. Sometimes I press (example) the ABC key once, and before I can press it a second time the A gets accepted, it moves to the next char and my second press (which should have made the A into a B) spawns a B or two after the A. I tried changing the Text Entry Timing - it did not affect that problem. Essentially the system behaves as if the timeout was zero in these cases. Tends to happen from third letter onwards - maybe the timeout counts total entry time instead of entry time for current letter by mistake? 2b) When the jump-to-next-letter timeout kicks in the cursor will move one position to the right and display "=>'. If I now press the same letter key on the remote again it is overwritten, as it should be. (i. e. M - timeout - O - timeout - N gives [MON]) When the key I press is not identical to the one pressed before the timeout the arrow stays intact and the letter will be put after it. (M - timeout - A gives [M=>D], thus putting an arrow in the middle of the search string. Pressing M - A works of course if there is no timeout, but the SlimServer seems to throw these in at random. These two issues combined make sure I can't type 5 letters without doubling back, much less "blind". I use this kind of text input a lot on my cell - would be great if it worked. 3) When I press and hold one of the volume keys on the remote the display will flicker back and forth between the volume bar and whatever was there before (e. g. now playing) Seems to me some kind of timing is royally screwed up here. Just for testing I tried the Windows server on my workstation - no problems in 6.x or 5.4. Then I downgraded to 5.4 on linux - problems persist. So it's either something on the linux machine (too fast, too slow, bug in my perl version) or in the linux version of SlimServer. 4) On an unrelated note: I have a lot of Japanese tracks tagged in Japanese. (in whatever flavour of unicode foobar2000 uses for ID3v2) The tags display on the 6.0 server (nice!) but not on the Squeezebox, which was to be expected. Are there any Japanese font hacks? Failing that any hack that would allow the Squeezebox to use something in the vein of ALBUM_TRANSCRIBED, TITLE_TRANSCRIBED if the original tags can't be rendered? I need the romanized version anyway, for generating file and folder names. Sorry this post got so long, I hope you're still with me. I'll go poke the source for a bit now, but I don't know much perl :) Any comments, tips and pointers appreciated. C. ___ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
