Different volume levels for different alarms?

[L0O]

Would you really want to change the snooze time and the alarm timeout on a per alarm basis?

Quick illustration only.
But well - why not? If such option is possible maybe someone would find it useful?
Personally I never used snooze feature, but different timeout for different alarms or as someone named it 'radio play scheduler' - yes.
People sometimes differ from each other

[slartibartfast]

Quick illustration only.
But well - why not? If such option is possible maybe someone would find it useful?
Personally I never used snooze feature, but different timeout for different alarms or as someone named it 'radio play scheduler' - yes.
People sometimes differ from each other

Good point about scheduling. Is the timeout adjustable on players at the the moment or only in LMS?

Sent from my Pixel 3a using Tapatalk

[Jaca]

+1 for scheduler.. I did suggest in other thread to tweak alarm timeout time so it's possible to set it at 0 in which case there is no snooze and alarm works as scheduler.
I would find it very useful. Seems like relatively small job as existing alarm settings page could already serve it.

Individual volume levels would be good too

[L0O]

I did suggest in other thread to tweak alarm timeout time so it's possible to set it at 0 in which case there is no snooze and alarm works as scheduler.

It is already done, as I've seen on LMS/Player/Alarm clock page (I am on LMS 8.2.0 - 1610887865 + newest Radio firmware):

Alarm Timeout (in minutes)
This setting allows you to choose how long alarms will play for before they stop automatically. If set to 0, alarms will continue playing until they are stopped manually.

[bpa]

Yup! That's good point against.
But as I wrote above - it could be as an option for those who like to use it only (default, for less advanced - as it is now). Also - maybe it could be visible only on web frontend, not on devices etc. Don't know if it is possible. Thinking loud only.

Everything is possible but somebody has to write the code and more importantly takes responsibility to own, test and maintain it.

This is the path that was gone down before and probably why a plugin was suggested in the code. It devolves ownership to those who want the feature and doesn't overload the core.

[Jaca]

It is already done, as I've seen on LMS/Player/Alarm clock page (I am on LMS 8.2.0 - 1610887865 + newest Radio firmware):

Alarm Timeout (in minutes)
This setting allows you to choose how long alarms will play for before they stop automatically. If set to 0, alarms will continue playing until they are stopped manually.

I think I meant to set snooze time to 0 not timeout. Sorry. I believe if timeout is 0 then it will play forever but still display alarm "overlay" with snooze and turn off alarm options..

Im guessing really as haven't updated community firmware yet

[gordonb3]

Hmmm.... I'd rather be able to change the default alarm (on connection loss with LMS) as this happens to be extremely annoying and extremely loud.

[slartibartfast]

Hmmm.... I'd rather be able to change the default alarm (on connection loss with LMS) as this happens to be extremely annoying and extremely loud.

I am pretty sure it is possible to replace the default file. There must be threads about this from years ago.

Sent from my Pixel 3a using Tapatalk

[gordonb3]

I am pretty sure it is possible to replace the default file. There must be threads about this from years ago.

Somewhat puzzled there. Searching back I found a 10 year old post that referenced a fixed volume, but when I open the corresponding file the current software shows something of a fade-in that doesn't appear to work as expected. That is, from zero to max (43) is in my experience almost instant whereas the code appears to imply that this level should only be reached after 8.6 seconds.

So what is LUA timer() supposed to refer to? Is that milliseconds (obviously not), microseconds, nanoseconds, clock ticks?

[slartibartfast]

Somewhat puzzled there. Searching back I found a 10 year old post that referenced a fixed volume, but when I open the corresponding file the current software shows something of a fade-in that doesn't appear to work as expected. That is, from zero to max (43) is in my experience almost instant whereas the code appears to imply that this level should only be reached after 8.6 seconds.

So what is LUA timer() supposed to refer to? Is that milliseconds (obviously not), microseconds, nanoseconds, clock ticks?

I have never noticed any fade in for the fallback alarm.

Sent from my Pixel 3a using Tapatalk