Benutzer-Werkzeuge

Webseiten-Werkzeuge


liquidsoap:scheduler:config

Configuration

configuration sections

Setup your stations and basic setup at scheduler/scheduler/config.cfg.

stations

Each <station> section defines its primary source stream URL url1 and optionally a fallback stream URL url2 which is played in case of outage of the primary source URL. You can define multiple aliases for the station which can be used to address the station in the schedule. This can prevent playout errors caused by typos. You can define a default station which is played if no other stream is scheduled. The station title will be displayed in log and web GUI output.

status_dir should be readable and writeable for scheduler and apache users.

Put the the input file schedule.csv into status_dir. This can be done by Google calendar synchronization by cron or manually. Scheduler will check periodically if the file was updated.

web

This defines the path to the web application and the timezone. You do not need to change anything here.

scheduler

This sections contains file paths to the synchronization and the web GUI. Additionally there are some date and timing parameters. You might setup your time zone.

liquidsoap

This defines the host and the port of the liquidsoap instance. You do not need to change anything here.

example

scheduler/scheduler/config.cfg

<config>
	<stations>
		# put one of the comma separated aliases into google calendar event title (e.g. dolebrai)
		<station>
			alias	dolebrai,dolebraï
			title	Dolebraï - rastageek's station
			url1	http://dolebrai.net:8000/dolebrai.ogg
			url2	
		</station>

		<station>
			alias	default
			title	default (88vier)
			url1	http://ice.rosebud-media.de:8000/88vier
			url2	
		</station>
	</stations>

	<web>
		#web application directory
		webapp_dir	/home/radio/scheduler/web/

		#language used for date output format
		language	German

		#link to scheduled result stream, for link in GUI header only...
		result_stream	http://localhost:8000/radio
	</web>

	<scheduler>
		#contains input file schedule.csv and other shared files for scheduler, synchronization and web user
		status_dir	/home/radio/scheduler/status/

		#command to trigger synchronization with Google Calendar
		sync_command	/home/radio/scheduler/calcms/sync.sh

		#output log
		log		/var/log/liquidsoap/scheduler.log

		#how long scheduler should sleep between checks (in seconds)
		sleep		30

		#pre-switching offset in seconds (e.g. switch 8 seconds before scheduled time)
		switch_offset	8

		#local schedule reload period (in seconds)
		reload		10
	
		#set log/debug level
		debug		1
	</scheduler>

	<liquidsoap>
		#liquidsoap telnet server
		host		localhost
		port		8001
	</liquidsoap>

</config>

start/stop scheduler

if directly started from command line, depending on debug level there will be output at the console.

scheduler/scheduler.sh 

If you use the upstart job you can run the scheduler as a service

  • start the scheduler by

sudo start scheduler

  • stop the scheduler by

sudo stop scheduler

log

Log will be written to configured path. You can use the log to find the root cause in case of errors. Additionally current scheduler and liquidsoap status will be written into a status file, which can be used by the web GUI to see the current status online. Make sure that the log directory exists and the user has permissions to read from and write into it.

2011-05-29 17:05:46	INIT
2011-05-29 17:05:46	RELOAD	schedule	/home/radio/scheduler/status/schedule.csv
2011-05-29 17:05:47	current	'frapó' since	2011-05-29 10:00:00
2011-05-29 17:05:47	PLAY	frapó
2011-05-29 17:05:47	liquidsoap station1 plays:	http://frrapo.de:8000/radio
2011-05-29 17:05:47	liquidsoap station2.stop
2011-05-29 17:05:47	liquidsoap station2 plays:	http://warning/invalid_url
2011-05-29 17:05:47	next in	1 hours 24 min 5 secs	dolebrai at 2011-05-29 18:30:00

manually edit schedule

status/schedule.csv is a plain CSV file. Each line contains the starting time of a broadcast (RFC3339) and either the source stream URL or the name of a station alias. The file can be created manually or generated by the Google Calendar synchronization job.

Examples:

  • play a audio stream
    2011-05-01 15:00; http:/localhost:8000/audio-stream
  • play a audio stream, in case of outage play a second stream as fallback
    2011-05-01 16:00; http:/localhost:8000/audio-stream; http:/localhost:8000/fallback-stream
  • play a station given by name. A station predefines a set of stream URL and fallback stream
    2011-05-01 14:00; dolebrai

Calendar Synchronization

You need to setup this only, if you want to use the Google Calendar integration to frequently update the CSV file by current content of your Google Calendar.

configure source calendar

Login to Google Calendar, create a broadcast switch calendar and go to calendar settings. Copy the private calendar URL into calcms/sync_cms/config/source/schedule.cfg. Replace „/basic“ by „/full“

If you want to use the public calendar URL instead of the private one you need to set user and password at the <access> section additionally

calcms/sync_cms/config/source/schedule.cfg

<source>
	type			google_calendar
	<date>
		time_zone	Europe/Berlin
	</date>
	<access>
		url		http://www.google.com/calendar/feeds/123123123%40group.calendar.google.com/private-345345345345/full
	</access>
	read_blocks		0
</source>

configure output CSV file

Set the output path to schedule file schedule.csv at calcms/sync_cms/config/target/schedule.cfg . The directory should be the same as status_dir at scheduler configuration.

calcms/sync_cms/config/target/schedule.cfg

<target>
	type 				liquidsoap_scheduler
	<access>
		file			/home/radio/scheduler/status/schedule.csv
	</access>
	<date>
		time_zone		Europe/Berlin
		default_entry		default
	</date>
	<system>
		debug			1
	</system>
</target>

Use Google Calendar to create new events

Login to Google Calendar Create a new event in your broadcast calendar, put one of the station aliases into the event title (e.g. dolebrai). Save the event. After synchronization the station will be played out at the time defined in the event. If you want to play a stream which is not configured in your stations, you can just put the stream URL into the title field. If you want to use an additional fallback URL, you can put after the first URL separated with a colon „;“

trigger synchronizing

To synchronize the CSV file with the Google Calendar content,

  • you can still execute calcms/sync.sh
  • you can create a cronjob (e.g. hourly:
    0 * * * * /home/radio/scheduler/calcms/sync.sh >> /var/log/liquidsoap/sync.log
  • you can click at web GUI to synchronize the calendar.
  • you can touch a file named update at scheduler's status_dir. The scheduler will then execute the synchronization. This is used by the web GUI.

You can use multiple source and target files by configuring them in scheduler/calcms/sync_cms/config/source/ or scheduler/calcms/sync_cms/config/target/. For this you will need to adopt sync.sh.

see log

INFO:	last update: 2011-06-05 19:50:37
INFO:	read  events from google calendar: 'http://www.google.com/calendar/feeds/123...321/full'
INFO:	found 7 events
[1]     2011-06-02  18:00                     :                             - pi radio
[1]     2011-06-06  18:00                     :                             - frrapo
[1]     2011-06-07  02:00                     :                             - ansage
[2]     2011-06-07  18:00                     :                             - ansage
[1]     2011-06-08  18:00                     :                             - pi radio
[1]     2011-06-09  18:00                     :                             - pi radio
INFO:	clean up old database entries...
save to '/home/radio/scheduler/status/schedule.csv
INFO:	set last-update time: 2011-06-05 19:52:53

Web GUI

For restricted access change access permissions at scheduler/web/.htaccess and scheduler/.htpasswd. Default access is test/test

Configure <web> section at scheduler/config.cfg

Check http://localhost/scheduler/

Liquidsoap

This should work from scratch, so this section is only to show you how it works. Please see here for liquidsoap installation and see liquidsoap website to learn liquidsoap scripting language and get an overview on additional configuration.

There is a example liquidsoap file to get all running: play.liq.

To play out the currently scheduled stream execute

liquidsoap play.liq

The scheduler uses two http input streams station1 and station2 and telnet server for communication with liquidsoap. You may change anything else in the liq script to fit your needs.

This is the basic liquidsoap script. Put a mp3 to /home/radio/sound/net_outage.mp3 or change the path to an existing mp3 in the script below to define the fallback. Otherwise you can use the built-in drone-noise fallback.

#!/usr/bin/liquidsoap

#enable STDOUT logging for upstart support
set("log.stdout", true)

#enable telnet server
set("server.telnet", true)
set("server.telnet.port",8001)
set("server.telnet.bind_addr","127.0.0.1")

#define two stations, station2 is fallback stream for station1
station1	= input.http(id="station1", "http://init/liquidsoap")
station2	= input.http(id="station2", "http://init/liquidsoap")

#define net outage channel
announce	= mksafe(single(id="announce",   "say:unstable network!"));
#defined a noised sine signal as net outage 
net_outage 	= mksafe(amplify(0.1,add([sine(),noise()])));
#play a file instead of sine signal
#net_outage 	= mksafe(single(id="net_outage", "/home/radio/sound/net_outage.ogg")) 

#in case of net outage announce it every minute
net_outage      = smooth_add(
	normal=net_outage,
	special=switch([
		( { 0s }, announce )
	])
)

#set station2 as fallback for station1 and net_outage as fallback for station2
radio = fallback(
	id="http_input fallback",
	track_sensitive=false,
	[
		station1,
		station2,
		net_outage
	]
)

radio=mksafe(radio)

#audio out to soundcard
out(radio)

#output stream - http://localhost:8000/radio
output.harbor(
	protocol="http", port=8000, mount="/radio",
	format="audio/ogg",	
	%vorbis.cbr(samplerate=44100, channels=2, bitrate=160), 
	radio 
)

#avoid buffer overruns
output.dummy(fallible=true, station1);
output.dummy(fallible=true, station2);
liquidsoap/scheduler/config.txt · Zuletzt geändert: 02.01.2017 00:43 von milan

Seiten-Werkzeuge