Internet radio browser GUI for music/video streams from various directory services.

⌈⌋ ⎇ branch:  streamtuner2


Diff

Differences From Artifact [d6f1dbf4e2]:

To Artifact [85a02da8f4]:


20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<div class="body">
<div class="hgroup"><h1 class="title"><span class="title">Timer</span></h1></div>
<div class="region">
<div class="contents"></div>
<div id="intro" class="sect"><div class="inner">
<div class="hgroup"></div>
<div class="region"><div class="contents">
<p class="p">You can programm play/recording events with the timer plugin. Simply select a station
	and choose <span class="guiseq"><span class="gui">Station</span> ▸ <span class="gui">Add timer...</span></span>.
	A small popup will ask for a data/time string. If you press <span class="key"><kbd>OK</kbd></span> the station
	and the programmed time will be stored in the bookmarks channel in the "timer" category.
	<span class="em">Please take note of the required text format</span>.</p>
<p class="p"><span class="media"><span class="media media-image"><img src="img/timer.png" class="media media-inline" alt="Timer"></span></span></p>
<div class="note note-tip" title="Tip"><div class="inner"><div class="region"><div class="contents"><p class="p">Note that streamtuner2 must be running for the programmed timer events to work.
	(In a future version there might be the option to have it handled by the system cron
	daemon.)</p></div></div></div></div>
</div></div>
</div></div>
<div id="timestring" class="sect"><div class="inner">
<div class="hgroup"><h2 class="title"><span class="title">Time specification strings</span></h2></div>
<div class="region"><div class="contents">
<p class="p">The time and date specificators follow a simple scheme. It's always one or more day names
	followed by a clock range, and finally the action.</p>
<p class="p">For example "<span class="code">Mon,Tue,Wed</span>" will make the event occour on the first
	three days of each week, while just "Fri" would limit it to Fridays.</p>
<p class="p">A clock range of "<span class="code">18:00-20:00</span>"
	would start the event at 18 o'clock and last it two hours. Note that for "play" events, the end
	time is irrelevant, since streamtuner2 can't kill your audio player anyway.</p>
<p class="p">The end time is only important if you replace "play" with the word "<span class="code">record</span>"
        in the timer event string. This runs streamripper instead and limits the recording time.</p>
</div></div>







|

|













|







20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<div class="body">
<div class="hgroup"><h1 class="title"><span class="title">Timer</span></h1></div>
<div class="region">
<div class="contents"></div>
<div id="intro" class="sect"><div class="inner">
<div class="hgroup"></div>
<div class="region"><div class="contents">
<p class="p">You can program play/recording events with the timer plugin. Simply select a station
	and choose <span class="guiseq"><span class="gui">Station</span> ▸ <span class="gui">Add timer...</span></span>.
	A small popup will ask for a date/time string. If you press <span class="key"><kbd>OK</kbd></span> the station
	and the programmed time will be stored in the bookmarks channel in the "timer" category.
	<span class="em">Please take note of the required text format</span>.</p>
<p class="p"><span class="media"><span class="media media-image"><img src="img/timer.png" class="media media-inline" alt="Timer"></span></span></p>
<div class="note note-tip" title="Tip"><div class="inner"><div class="region"><div class="contents"><p class="p">Note that streamtuner2 must be running for the programmed timer events to work.
	(In a future version there might be the option to have it handled by the system cron
	daemon.)</p></div></div></div></div>
</div></div>
</div></div>
<div id="timestring" class="sect"><div class="inner">
<div class="hgroup"><h2 class="title"><span class="title">Time specification strings</span></h2></div>
<div class="region"><div class="contents">
<p class="p">The time and date specificators follow a simple scheme. It's always one or more day names
	followed by a clock range, and finally the action.</p>
<p class="p">For example "<span class="code">Mon,Tue,Wed</span>" will make the event occur on the first
	three days of each week, while just "Fri" would limit it to Fridays.</p>
<p class="p">A clock range of "<span class="code">18:00-20:00</span>"
	would start the event at 18 o'clock and last it two hours. Note that for "play" events, the end
	time is irrelevant, since streamtuner2 can't kill your audio player anyway.</p>
<p class="p">The end time is only important if you replace "play" with the word "<span class="code">record</span>"
        in the timer event string. This runs streamripper instead and limits the recording time.</p>
</div></div>