Feature suggestion - scheduling

coderholic / pyradio

Curses based internet radio player

www.coderholic.com/pyradio

MIT License

961 stars 129 forks source link

Feature suggestion - scheduling #162

Open wturrell opened 2 years ago

wturrell commented 2 years ago

This is maybe a bit niche, but I often find myself trying to remember to switch over to a different station at a specific time, e.g. for a news bulletin or live event.

I think the way it might work is you browse to the desired station, press a keyboard shortcut and enter a time, and that time would be displayed maybe right aligned in the station list as an indication the 'alarm' was set. As soon as the time is reached, whichever station you were on before would stop playing and the new one would start.

s-n-g commented 2 years ago

Hi again @wturrell

Yes, this is a nice feature! But I do have to think about it... The thing is that in the meantime, we can load a different playlist, or use radiobrowser, and then thing get... well... complicated... :smile:

amano-kenji commented 6 months ago

Isn't it better implemented as remote control server commands? Remote commands can be scheduled externally.

amano-kenji commented 6 months ago

Cron jobs can send remote commands.

amano-kenji commented 6 months ago

I'm not sure that a radio program should have a proper scheduler UI. Perhaps, you can develop an external scheduler UI that sends remote commands to pyradio?

s-n-g commented 6 months ago

Hm, that is an interesting idea! But that would make it nesessary to always have the remote control server on... I will think about it!

amano-kenji commented 6 months ago

Instead of listening on a port, you can listen on a stream unix domain socket.
If schedule UI is well designed, then it can be a part of pyradio. I don't know whether it's better to implement schedule UI in pyradio or outside pyradio. A schedule screen can exist if pyradio has built-in scheduler.

s-n-g commented 6 months ago

I've been in the process of testing several solutions for some time... I have put it in the back burner for now, until the 0.9.3.x transition settles down and all bugs and such are discovered ans taken care of :wink: