wxman;506472 Wrote:
> Thanks for the explanation. What does locally stored mean in this
> context? If it means on the radio itself, then why cant it remember my
> custom settings in the same manner as the tune itself? Also, I must be
> missing A LOT given the problems and hurdles trying to stabilize the
> alarm. Why not have ALL static content saved on the radio, a connection
> should only be attempted if live content is sought, if a connection
> cannot be achieved, it should default back to the local content, with
> all saved settings. Wouldn't that solve most if not all issues?
Actually there is nothing local on the Radio (except this one mp3 used
as fallback alarm). Everything else (time of alarm, sound to play, the
actual audio streams (also the tunes are 'streams') all comes from the
server.
The whole sqeezebox world is built around having a 24/7 server.
In most cases (98% of users having a proper setup) this will be true -
and for the rest of cornercases (i.e. server off when something is
broke) we should have the easiest possible solution (and as you can see
this is still complicated, given that 3 developers are discussing the
whole subject for over a month).
By having your server hibernate by intention you brake the main
assumption of your box ('I will always have a server') and thus will
need to fiddle that the server is always on, when the box expects it.
The new WOL event 10min before alarm will help you with that - but you'd
still have to make sure the server doesn't fall asleep again before the
alarm starts.
This is all very advanced stuff. I started with it myself but in the
end it wasn't worth all the trouble and unexpected behaviours (and I
couldn't stand waiting for my server to wake up just to play some
music).
In the end I went the route to buy a SheevaPlug with a (spinning down)
USB-drive. The time I needed to set it up was not higher than the time I
had to spend with proper hibernation - and now I have a 24/7 server with
lower energy consumption as before - and much less problems :)
>
> I don't think the problem is completely due to set up. My SB Radio has
> always played the alarm for a second or two at full volume before then
> immediately beginning the alarm with the volume fade-in as it should.
>
> If this bug is not already out there then it needs to be filed. The
> entire point of fade-in alarm volume is to avoid a rude jolt to the
> system first thing in the morning, something that my SB Radio currently
> cannot do.
So far the energy was put into making sure the alarm will sound
'whatever' happens.
Your problem was mentioned already but I'm not aware it has been filed
as bug already. It couldn't be reproduced reliably so far.
So if you can provide instructions
- local server vs. MySB.com
- what alarm tune
- where was the alarm configured (radio vs. web)
- was the server on at alarm time
...
to reliable reproduce the problem you would help very much !
--
bluegaspode
1x SB-Controller+Receiver (Duet), 1xSB-Boom. 1xSB-Radio
Server (7.4.1) running on SheevaPlug (Ubuntu) with attached Western
Digital MyBook Essential.
Secondary 7.4 Server on Debianized Buffalo Linkstation LS-CHL.
------------------------------------------------------------------------
bluegaspode's Profile: http://forums.slimdevices.com/member.php?userid=31651
View this thread: http://forums.slimdevices.com/showthread.php?t=74007
_______________________________________________
Radio mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/radio
