Merge branch 'master' into docs-stream-settings-update
This commit is contained in:
Robb
GitHub
commit
5220501f9b
207 changed files with 10837 additions and 6651 deletions
|
|
@ -1,6 +1,6 @@
|
|||
If you do not have direct access to the Airtime server, you can add files to the Airtime library using the **Add Media** page of the administration interface. (The **Add Media** page is not visible to *Guest* users). This page includes an upload queue for media files, which supports drag and drop from your computer's file manager if you are using a recent web browser, such as *Mozilla Firefox 16* or later.
|
||||
If you do not have direct access to the Libretime server, you can add files to the Libretime library using the **Add Media** page of the administration interface. (The **Add Media** page is not visible to *Guest* users). This page includes an upload queue for media files, which supports drag and drop from your computer's file manager if you are using a recent web browser, such as *Mozilla Firefox 16* or later.
|
||||
|
||||
Some web browsers may set an upload limit for a single file, between 200MB and 2GB. If you need to upload files larger than 200MB to the Airtime server on a regular basis, you may find it more convenient to perform the upload using SFTP, rather than through the browser. See the chapter *Automated file import* for more details.
|
||||
Some web browsers may set an upload limit for a single file, between 200MB and 2GB. If you need to upload files larger than 200MB to the Libretime server on a regular basis, you may find it more convenient to perform the upload using SFTP, rather than through the browser. See the chapter *Automated file import* for more details.
|
||||
|
||||
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ After you have added all the files that you require to the upload queue, click t
|
|||
|
||||
|
||||
|
||||
The row of the file currently being uploaded is highlighted in pale green. At the bottom of the upload queue, a progress bar and percentage indicates how much of the upload has taken place so far. The upload speed will depend on the network connection between your computer and the Airtime server.
|
||||
The row of the file currently being uploaded is highlighted in pale green. At the bottom of the upload queue, a progress bar and percentage indicates how much of the upload has taken place so far. The upload speed will depend on the network connection between your computer and the Libretime server.
|
||||
|
||||
|
||||
|
||||
|
|
@ -20,4 +20,4 @@ Once it has been uploaded successfully, each file row displays a white check mar
|
|||
|
||||
|
||||
|
||||
Your files are now imported into the Airtime library, ready to be included in your broadcast playlists, smart blocks and shows.
|
||||
Your files are now imported into the Libretime library, ready to be included in your broadcast playlists, smart blocks and shows.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
The Airtime API enables many types of information about the broadcast schedule and configuration to be retrieved from the Airtime server. Other than the live-info and week-info data fetched by website widgets (see the chapter *Exporting the schedule*), all API requests must be authenticated using the secret API key stored in the file */etc/airtime/api\_client.cfg* on the Airtime server. This key is autogenerated during Airtime installation and should be unique for each server.
|
||||
The Libretime API enables many types of information about the broadcast schedule and configuration to be retrieved from the Libretime server. Other than the live-info and week-info data fetched by website widgets (see the chapter *Exporting the schedule*), all API requests must be authenticated using the secret API key stored in the file */etc/airtime/api\_client.cfg* on the Libretime server. This key is autogenerated during Libretime installation and should be unique for each server.
|
||||
|
||||
If you intend to use the Airtime API across a public network, for security reasons it is highly recommended that all API requests are sent over encrypted https: and that the web server is configured to accept requests to the api/ directory from specific host names or IP addresses only.
|
||||
If you intend to use the Libretime API across a public network, for security reasons it is highly recommended that all API requests are sent over encrypted https: and that the web server is configured to accept requests to the api/ directory from specific host names or IP addresses only.
|
||||
|
||||
The format of API requests is:
|
||||
|
||||
https://airtime.example.com/api/api-action/format/json/api_key/XXXXXX
|
||||
https://libretime.example.com/api/api-action/format/json/api_key/XXXXXX
|
||||
|
||||
where api-action is the type of request and XXXXXX is the secret API key. Available actions include:
|
||||
|
||||
- on-air-light - return true if the station is on air
|
||||
- status - get the status of Airtime components and resource usage
|
||||
- version - returns the version of Airtime installed
|
||||
- status - get the status of Libretime components and resource usage
|
||||
- version - returns the version of Libretime installed
|
||||
- get-files-without-silan-value - list files for which silence detection has not yet been performed
|
||||
- get-stream-setting - gets the settings of Airtime output streams
|
||||
- get-stream-parameters - gets the parameters of Airtime output streams
|
||||
- get-stream-setting - gets the settings of Libretime output streams
|
||||
- get-stream-parameters - gets the parameters of Libretime output streams
|
||||
|
||||
For example, using the action *get-stream-setting* returns the following output for the first configured stream:
|
||||
|
||||
|
|
@ -41,9 +41,9 @@ Some API requests require the directory ID number to be specified as *dir\_id* i
|
|||
|
||||
For example, using a request such as:
|
||||
|
||||
http://airtime.example.com/api/list-all-files/format/json/api_key/XXXXXX/dir_id/1/
|
||||
http://libretime.example.com/api/list-all-files/format/json/api_key/XXXXXX/dir_id/1/
|
||||
|
||||
returns the full path to each media file in the Airtime storage directory:
|
||||
returns the full path to each media file in the Libretime storage directory:
|
||||
|
||||
{"files":[
|
||||
"imported\/1\/Mark Ronson feat. Saigon\/Here Comes the Fuzz\/7-Diduntdidunt-unknown.flac",
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
|
|
@ -1,6 +1,6 @@
|
|||
The *airtime-import* script can be combined with the standard *SFTP* (secure FTP) program and *cron* daemon on a GNU/Linux server to enable automated file import from multiple remote computers. This could save time for your station staff when using distributed production methods, or content syndication.
|
||||
|
||||
Traditional FTP servers use plain text passwords (without encryption) and are therefore not recommended for upload accounts on Airtime servers accessible from the public Internet. SFTP is a cross-platform protocol which works with many desktop programs including **gFTP** for GNU/Linux (<http://www.gftp.org/>). This program can be installed on Debian or Ubuntu desktop computers with the command:
|
||||
Traditional FTP servers use plain text passwords (without encryption) and are therefore not recommended for upload accounts on Libretime servers accessible from the public Internet. SFTP is a cross-platform protocol which works with many desktop programs including **gFTP** for GNU/Linux (<http://www.gftp.org/>). This program can be installed on Debian or Ubuntu desktop computers with the command:
|
||||
|
||||
sudo apt-get install gftp
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ To enable SFTP uploads, first invoke the **adduser** command to create the *uplo
|
|||
|
||||
sudo adduser --home /srv/airtime/uploads --shell /usr/lib/sftp-server uploads
|
||||
|
||||
The server will then invite you to type in the password for the new *uploads* user, and once again for confirmation. The security of your Airtime server depends on the strength of the password that you set, so be sure to use a long and complex password with upper case, lower case and numerical characters. It is not necessary to set a full name or other details for this account.
|
||||
The server will then invite you to type in the password for the new *uploads* user, and once again for confirmation. The security of your Libretime server depends on the strength of the password that you set, so be sure to use a long and complex password with upper case, lower case and numerical characters. It is not necessary to set a full name or other details for this account.
|
||||
|
||||
Adding user `uploads' ...
|
||||
Adding new group `uploads' (1003) ...
|
||||
|
|
@ -37,7 +37,7 @@ Then create a script to run once per hour:
|
|||
|
||||
sudo nano /etc/cron.hourly/airtime-upload
|
||||
|
||||
The script should import the newly uploaded files from the incoming folder specified, using the *copy* option, and then remove the original uploaded files. This step, rather than simply using the *watch* option on the */srv/airtime/uploads/incoming/* folder, ensures that the *uploads* SFTP account does not have direct write access to the Airtime storage archive. That could be a security risk if the password was compromised.
|
||||
The script should import the newly uploaded files from the incoming folder specified, using the *copy* option, and then remove the original uploaded files. This step, rather than simply using the *watch* option on the */srv/airtime/uploads/incoming/* folder, ensures that the *uploads* SFTP account does not have direct write access to the Libretime storage archive. That could be a security risk if the password was compromised.
|
||||
|
||||
#!/bin/sh
|
||||
|
||||
|
|
@ -55,9 +55,9 @@ Finally, the script should be made executable so that the cron daemon can run it
|
|||
|
||||
By default, Debian and Ubuntu GNU/Linux run *cron.hourly* tasks at 17 minutes past each hour. This value can be adjusted in the file */etc/crontab* on the server, if required.
|
||||
|
||||
Remote users should connect to the Airtime server using their client software of choice, making sure that they specify an SFTP rather than FTP connection. The remote directory for the clients to use would be */srv/airtime/uploads/incoming/* as configured above.*
|
||||
Remote users should connect to the Libretime server using their client software of choice, making sure that they specify an SFTP rather than FTP connection. The remote directory for the clients to use would be */srv/airtime/uploads/incoming/* as configured above.*
|
||||
*
|
||||
|
||||
|
||||
|
||||
For additional security, you could configure your Airtime server to use an encryption key pair for the *uploads* account, instead of a password. See <https://help.ubuntu.com/community/SSH/OpenSSH/Keys> for details of how to do this on an Ubuntu server.
|
||||
For additional security, you could configure your Libretime server to use an encryption key pair for the *uploads* account, instead of a password. See <https://help.ubuntu.com/community/SSH/OpenSSH/Keys> for details of how to do this on an Ubuntu server.
|
||||
|
|
|
|||
|
|
@ -1,31 +1,71 @@
|
|||
The following shell commands can be used for database backup and restore on a running *PostgreSQL* server in an Airtime system.
|
||||
The following shell commands can be used for database backup and restore on a
|
||||
running *PostgreSQL* server in an Libretime system.
|
||||
|
||||
You can dump the entire database to a zipped file with the combination of the **pg\_dumpall** command and **gzip**. The **pg\_dumpall** command is executed as the user *postgres*, by using the **sudo** command and the **-u** switch. It is separated from the **gzip** command with the pipe symbol.
|
||||
You can dump the entire database to a zipped file with the combination of the
|
||||
**pg\_dumpall** command and **gzip**. The **pg\_dumpall** command is executed
|
||||
as the user *postgres*, by using the **sudo** command and the **-u** switch. It
|
||||
is separated from the **gzip** command with the pipe symbol.
|
||||
|
||||
sudo -u postgres pg_dumpall | gzip -c > airtime-backup.gz
|
||||
```bash
|
||||
sudo -u postgres pg_dumpall | gzip -c > libretime-backup.gz
|
||||
```
|
||||
|
||||
This command can be automated to run on a regular basis using the standard **cron** tool on your server.
|
||||
This command can be automated to run on a regular basis using the standard
|
||||
**cron** tool on your server.
|
||||
|
||||
When restoring a production database on a cleanly installed Airtime system, it may be necessary to drop the empty database that was created during the new installation, by using the **dropdb** command. Again, this command is executed with **sudo** as the user *postgres*:
|
||||
When restoring a production database on a cleanly installed Libretime system, it
|
||||
may be necessary to drop the empty database that was created during the new
|
||||
installation, by using the **dropdb** command. Again, this command is executed
|
||||
with **sudo** as the user *postgres*:
|
||||
|
||||
sudo -u postgres dropdb airtime
|
||||
```bash
|
||||
sudo -u postgres dropdb airtime
|
||||
```
|
||||
|
||||
This **dropdb** command above is necessary to avoid 'already exists' errors on table creation when overwriting an empty Airtime database in the next step. These errors might prevent some data from being restored, such as user account data.
|
||||
This **dropdb** command above is necessary to avoid 'already exists' errors on
|
||||
table creation when overwriting an empty Libretime database in the next step.
|
||||
These errors might prevent some data from being restored, such as user account
|
||||
data.
|
||||
|
||||
To restore, first unzip the backup file with **gunzip**, then use the **psql** command as the *postgres* user:
|
||||
To restore, first unzip the backup file with **gunzip**, then use the **psql**
|
||||
command as the *postgres* user:
|
||||
|
||||
gunzip airtime-backup.gz
|
||||
sudo -u postgres psql -f airtime-backup
|
||||
```bash
|
||||
gunzip libretime-backup.gz
|
||||
sudo -u postgres psql -f libretime-backup
|
||||
```
|
||||
|
||||
You should now be able to log in to the Airtime web interface in the usual way.
|
||||
You should now be able to log in to the Libretime web interface in the usual way.
|
||||
|
||||
For safety reasons, your regular database backups should be kept in a directory which is backed up by your storage backup tool of choice; for example, the */srv/airtime/database\_backups* directory. This should ensure that a storage restore can be made along with a matching and complete version of the Airtime database from the day that the storage backup was made.
|
||||
For safety reasons, your regular database backups should be kept in a directory
|
||||
which is backed up by your storage backup tool of choice; for example, the
|
||||
*/srv/airtime/database\_backups* directory. This should ensure that a storage
|
||||
restore can be made along with a matching and complete version of the Libretime
|
||||
database from the day that the storage backup was made.
|
||||
|
||||
Storage backup
|
||||
--------------
|
||||
|
||||
Backing up the Airtime database with **pg\_dumpall** will not back up the Airtime media storage server, which is likely to need a great deal more backup space. Creating a compressed file from hundreds of gigabytes of storage server contents is likely to take a very long time, and may have little benefit for the amount of CPU power used, if the media files are already stored in a highly compressed format. It is also impractical to copy very large backup files across the network on a daily basis.
|
||||
Backing up the Libretime database with **pg\_dumpall** will not back up the
|
||||
Libretime media storage server, which is likely to need a great deal more backup
|
||||
space. Creating a compressed file from hundreds of gigabytes of storage server
|
||||
contents is likely to take a very long time, and may have little benefit for the
|
||||
amount of CPU power used, if the media files are already stored in a highly
|
||||
compressed format. It is also impractical to copy very large backup files across
|
||||
the network on a daily basis.
|
||||
|
||||
Instead, it is preferable to use an incremental backup technique to synchronize the production Airtime server storage with a backup server each day or night. If the backup server also contains an Airtime installation, it should be possible to switch playout to this second machine relatively quickly, in case of a hardware failure or other emergency on the production server.
|
||||
Instead, it is preferable to use an incremental backup technique to synchronize
|
||||
the production Libretime server storage with a backup server each day or night. If
|
||||
the backup server also contains an Libretime installation, it should be possible
|
||||
to switch playout to this second machine relatively quickly, in case of a
|
||||
hardware failure or other emergency on the production server.
|
||||
|
||||
A standard incremental backup tool on GNU/Linux servers is *rsync* [(http://rsync.samba.org/)](http://rsync.samba.org/)) which can be installed using the package manager of your GNU/Linux distribution. However, incremental backup alone cannot help in the scenario where a file which later proves to be important has been deleted by an administrator. For backups that can be rolled back to restore from an earlier date than the current backup, the tool *rdiff-backup* [(http://www.nongnu.org/rdiff-backup/](http://www.nongnu.org/rdiff-backup/)) can be deployed.
|
||||
A standard incremental backup tool on GNU/Linux servers is *rsync*
|
||||
[(http://rsync.samba.org/)](http://rsync.samba.org/)) which can be installed
|
||||
using the package manager of your GNU/Linux distribution. However, incremental
|
||||
backup alone cannot help in the scenario where a file which later proves to be
|
||||
important has been deleted by an administrator. For backups that can be rolled
|
||||
back to restore from an earlier date than the current backup, the tool
|
||||
*rdiff-backup*
|
||||
[(http://www.nongnu.org/rdiff-backup/](http://www.nongnu.org/rdiff-backup/)) can
|
||||
be deployed.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ In the top left corner of the page, you can go back or forward through the **Cal
|
|||
Adding a show
|
||||
-------------
|
||||
|
||||
Only *Admins* and *Program Managers* can use this feature. To add a new show to the Calendar, click the **+ New Show** button in the top left corner of the page, or click on any future row or box in the Calendar which is empty. Either of these actions opens the **Add this show** box, which has seven sections, arranged vertically: **What**, **Automatic Playlist**, **When**, **Live Stream Input**, **Record & Rebroadcast**, **Who**, and **Style**. Click the small orange triangle to the left of the section name if you wish to minimize or maximize it.
|
||||
Only *Admins* and *Program Managers* can use this feature. To add a new show to the Calendar, click the **+ New Show** button in the top left corner of the page, or click on any future row or box in the Calendar which is empty. Either of these actions opens the **Add this show** box, which has seven sections, arranged vertically: **What**, **Autoloading Playlist**, **When**, **Live Stream Input**, **Record & Rebroadcast**, **Who**, and **Style**. Click the small orange triangle to the left of the section name if you wish to minimize or maximize it.
|
||||
|
||||
What
|
||||
----
|
||||
|
|
@ -18,7 +18,7 @@ In the **What** box, enter the **Name**, public website **URL**, **Genre** and *
|
|||
|
||||
|
||||
|
||||
Automatic Playlist
|
||||
Autoloading Playlist
|
||||
------------------
|
||||
|
||||
In this section, you can select a playlist that will be used for this show. The playlist must already be defined in your library. **Auto Schedule Playlist** needs to be checked for **Select Playlist** and **Repeat AutoPlaylist Until Show is Full** to be visible.
|
||||
|
|
@ -64,15 +64,7 @@ A reminder of the connection **Host**, **Port** and **Mount** for the live input
|
|||
Record & Rebroadcast
|
||||
--------------------
|
||||
|
||||
In the **Record & Rebroadcast** section, checking the **Record from Line In?** box enables automatic recording of the soundcard line input, if your LibreTime server has one, at the time of the show. Shows set for line-in recording should not also contain files or playlists. The default audio format for live recordings is 256kbps Ogg Vorbis, and the files are saved in the *recorded* folder, under the **Import Folder** path set in the **Media Folders** page on the **System** menu. See the chapter *Host configuration* for details of recorder settings.
|
||||
|
||||
If you wish the recording to be played out at a later time, check the **Rebroadcast?** box, and then select up to ten date and time slots in the **Choose Days** box.
|
||||
|
||||
|
||||
|
||||
Shows set for rebroadcast have a white loop icon in the calendar.
|
||||
|
||||
|
||||
The **Record & Rebroadcast** section is currently not working, and so has been removed from the web interface. If this feature is important to you, please search for relevant issues in the [LibreTime github repository](https://github.com/LibreTime/libretime/search?q=record&type=Issues) and help us make it happen!
|
||||
|
||||
Who
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
Airtime has a feature which enables your station's show and schedule information to be displayed on remote websites. This feature is included in Airtime because you would not usually invite the general public to access your Airtime server directly. If you had very large numbers of people requesting data from the Airtime server at once, the burst of network traffic might overload the server, potentially disrupting your broadcasts. If carried out maliciously, this network overload is known as a *denial of service attack*.
|
||||
Libretime has a feature which enables your station's show and schedule information to be displayed on remote websites. This feature is included in Libretime because you would not usually invite the general public to access your Libretime server directly. If you had very large numbers of people requesting data from the Libretime server at once, the burst of network traffic might overload the server, potentially disrupting your broadcasts. If carried out maliciously, this network overload is known as a *denial of service attack*.
|
||||
|
||||
Instead, your public-facing web server can retrieve the schedule information from the Airtime API. This information can then be displayed on your broadcast station or affiliate websites by a content management system, such as Sourcefabric's **Newscoop** (<http://newscoop.sourcefabric.org/>). It can be presented using Javascript widgets and styled with CSS, in any format that you require. The **Broadcaster** theme for Newscoop (<https://github.com/newscoop/theme-Broadcaster>) integrates these widgets with ready-to-use styles.
|
||||
Instead, your public-facing web server can retrieve the schedule information from the Libretime API. This information can then be displayed on your broadcast station or affiliate websites by a content management system, such as Sourcefabric's **Newscoop** (<http://newscoop.sourcefabric.org/>). It can be presented using Javascript widgets and styled with CSS, in any format that you require. The **Broadcaster** theme for Newscoop (<https://github.com/newscoop/theme-Broadcaster>) integrates these widgets with ready-to-use styles.
|
||||
|
||||
There are two kinds of information that can be retrieved remotely from the Airtime API without authentication; the metadata for the current show plus the following show (live-info), or the schedule for the current week and the week ahead (week-info). The week-info metadata includes show names, times, and individual show URLs on your public website. That way, the audience for your station can click through from the schedule information to find out more about a particular show, or download a previous show recording that you might have made available.
|
||||
There are two kinds of information that can be retrieved remotely from the Libretime API without authentication; the metadata for the current show plus the following show (live-info), or the schedule for the current week and the week ahead (week-info). The week-info metadata includes show names, times, and individual show URLs on your public website. That way, the audience for your station can click through from the schedule information to find out more about a particular show, or download a previous show recording that you might have made available.
|
||||
|
||||
If your Airtime server was accessible at https://airtime.example.com the live show information could be retrieved by your web server using this URL:
|
||||
If your Libretime server was accessible at https://libretime.example.com the live show information could be retrieved by your web server using this URL:
|
||||
|
||||
https://airtime.example.com/api/live-info/?callback
|
||||
https://libretime.example.com/api/live-info/?callback
|
||||
|
||||
The comma-separated text metadata returned to your web server might be something like this:
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ The comma-separated text metadata returned to your web server might be something
|
|||
|
||||
The information for the current week's schedule could be retrieved using the URL:
|
||||
|
||||
https://airtime.example.com/api/week-info/?callback
|
||||
https://libretime.example.com/api/week-info/?callback
|
||||
|
||||
In this case, the metadata returned would be in a different format from the above example, something like the following. To keep the example short, this particular schedule export only contains four shows on a Monday. A full weekly schedule export would contain a great deal more text.
|
||||
|
||||
|
|
@ -126,32 +126,32 @@ In this case, the metadata returned would be in a different format from the abov
|
|||
"sunday":[],
|
||||
"AIRTIME_API_VERSION":"1.1"})
|
||||
|
||||
If you see the message *You are not allowed to access this resource* when attempting to display schedule information in your web browser, log in to the Airtime administration interface, click *System* in the main menu, then *Preferences*. Set **Allow Remote Websites To Access "Schedule" Info?** to **Enabled**, click the **Save** button, then refresh the browser window opened on the schedule export URL. If you do not wish to make schedule information available to the public, set this option to **Disabled** instead.
|
||||
If you see the message *You are not allowed to access this resource* when attempting to display schedule information in your web browser, log in to the Libretime administration interface, click *System* in the main menu, then *Preferences*. Set **Allow Remote Websites To Access "Schedule" Info?** to **Enabled**, click the **Save** button, then refresh the browser window opened on the schedule export URL. If you do not wish to make schedule information available to the public, set this option to **Disabled** instead.
|
||||
|
||||
|
||||
|
||||
Caching schedule information
|
||||
----------------------------
|
||||
|
||||
If the Airtime server is behind a firewall, or you want to protect the Airtime server from large numbers of schedule requests, you may wish to cache the schedule information on a public-facing or intermediate server. You can then create a firewall rule that only allows the schedule server to connect to the Airtime server, in addition to any remote users of the Airtime web interface.
|
||||
If the Libretime server is behind a firewall, or you want to protect the Libretime server from large numbers of schedule requests, you may wish to cache the schedule information on a public-facing or intermediate server. You can then create a firewall rule that only allows the schedule server to connect to the Libretime server, in addition to any remote users of the Libretime web interface.
|
||||
|
||||
Your system administrator can set up schedule caching on a standard Apache and PHP enabled web server with the *curl* program installed, using the following steps:
|
||||
|
||||
1. Create a shell script on the schedule server (schedule.example.com) that polls the remote Airtime server (airtime.example.com), and writes the metadata returned into a pair of local temporary files:
|
||||
1. Create a shell script on the schedule server (schedule.example.com) that polls the remote Libretime server (libretime.example.com), and writes the metadata returned into a pair of local temporary files:
|
||||
|
||||
sudo nano /usr/local/bin/airtime-schedule.sh
|
||||
sudo nano /usr/local/bin/libretime-schedule.sh
|
||||
|
||||
The content of this file should be like the following script, replacing airtime.example.com with the name of your Airtime server:
|
||||
The content of this file should be like the following script, replacing libretime.example.com with the name of your Libretime server:
|
||||
|
||||
#!/bin/sh
|
||||
|
||||
curl -s "https://airtime.example.com/api/live-info/?callback=***" > /tmp/live-info
|
||||
curl -s "https://libretime.example.com/api/live-info/?callback=***" > /tmp/live-info
|
||||
|
||||
curl -s "https://airtime.example.com/api/week-info/?callback=***" > /tmp/week-info
|
||||
curl -s "https://libretime.example.com/api/week-info/?callback=***" > /tmp/week-info
|
||||
|
||||
2. Make the script executable:
|
||||
|
||||
sudo chmod +x /usr/local/bin/airtime-schedule.sh
|
||||
sudo chmod +x /usr/local/bin/libretime-schedule.sh
|
||||
|
||||
3. Create an Apache VirtualHost configuration for the schedule server:
|
||||
|
||||
|
|
@ -214,18 +214,18 @@ containing the following code:
|
|||
|
||||
8. Create a cron job to run the shell script each minute:
|
||||
|
||||
sudo nano /etc/cron.d/airtime-schedule
|
||||
sudo nano /etc/cron.d/libretime-schedule
|
||||
|
||||
containing the line:
|
||||
|
||||
* * * * * www-data /usr/local/bin/airtime-schedule.sh
|
||||
* * * * * www-data /usr/local/bin/libretime-schedule.sh
|
||||
|
||||
The schedule server will now be serving the same show information as the Airtime server, with a cache lifetime of one minute. You can adjust the cache lifetime by altering the frequency of the cron job that polls the Airtime server.
|
||||
The schedule server will now be serving the same show information as the Libretime server, with a cache lifetime of one minute. You can adjust the cache lifetime by altering the frequency of the cron job that polls the Libretime server.
|
||||
|
||||
Pushing schedule information via FTP or SSH
|
||||
-------------------------------------------
|
||||
|
||||
If there is no inbound access to the Airtime server at all, an FTP script can be used to push cached schedule data from Airtime to an external web server. The standard ftp command should be available on the Airtime server and the external web server should have a suitably restricted FTP account set up. After following steps 1 and 2 above to export schedule data to a pair of temporary files on the Airtime server, create a new script on the Airtime server to automatically make the upload:
|
||||
If there is no inbound access to the Libretime server at all, an FTP script can be used to push cached schedule data from Libretime to an external web server. The standard ftp command should be available on the Libretime server and the external web server should have a suitably restricted FTP account set up. After following steps 1 and 2 above to export schedule data to a pair of temporary files on the Libretime server, create a new script on the Libretime server to automatically make the upload:
|
||||
|
||||
sudo nano /usr/local/bin/upload-schedule-data.sh
|
||||
|
||||
|
|
@ -247,129 +247,4 @@ Replace host, user and password values with appropriate values for your external
|
|||
|
||||
Then make the new script executable and create a cron job to launch it every minute, as in step 8 above. Steps 3 to 7 above should be carried out on the external web server so that it can convert the two temporary files uploaded via FTP into public schedule data.
|
||||
|
||||
If you have secure shell access (SSH) to the remote web server, you could write a script to use the secure copy command (scp) instead of ftp.
|
||||
|
||||
Website widgets
|
||||
---------------
|
||||
|
||||
Example HTML, Javascript and CSS code for your public website are provided in the *widgets* folder of the Airtime installation tarball, or on GitHub: <https://github.com/sourcefabric/Airtime/tree/master/widgets>
|
||||
|
||||
If you have performed an automated installation on Debian or Ubuntu, the widgets can be found in the */usr/share/doc/airtime/examples/* directory.
|
||||
|
||||
For the widgets to work on a typical web server, links to the Javascript and CSS code have to be included in the HTML page <head> element, like the following example:
|
||||
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<title>Airtime widgets</title>
|
||||
<script src="js/jquery-1.6.1.min.js" type="text/javascript">
|
||||
</script>
|
||||
<script src="js/jquery-ui-1.8.10.custom.min.js" type="text/javascript">
|
||||
</script>
|
||||
<script src="js/jquery.showinfo.js" type="text/javascript">
|
||||
</script>
|
||||
<link href="css/airtime-widgets.css" rel="stylesheet" type="text/css" />
|
||||
</head>
|
||||
|
||||
A full example is shown in the *widgets/sample\_page.html* file in the Airtime installation tarball, on GitHub, or in the */usr/share/doc/airtime/examples/* directory if you have installed the Debian/Ubuntu package of Airtime.
|
||||
|
||||
The following code is for a small *airtimeLiveInfo* widget that displays information about the current show (show time elapsed, and show time remaining), as well as some information about the next show (start time and end time). In this example, the label text for *onAirNow* is translated into French for local language support:
|
||||
|
||||
<script>
|
||||
$(document).ready(function() {
|
||||
$("#headerLiveHolder").airtimeLiveInfo({
|
||||
sourceDomain: "https://schedule.example.com/",
|
||||
text: {onAirNow:"Sur Les Antennes", offline:"Offline", current:"Current", next:"Next"},
|
||||
updatePeriod: 20 //seconds
|
||||
});
|
||||
});
|
||||
</script>
|
||||
|
||||
The <script> element above would typically be added to the page's <head> element. You would then add a <div> element to the <body> element of the page to hold the widget, such as:
|
||||
|
||||
<div id="headerLiveHolder" style="border: 1px solid #999999; padding: 10px;"></div>
|
||||
|
||||
On the public website, this widget can be made to look like the following screenshot:
|
||||
|
||||
|
||||
|
||||
The CSS properties *color:* and *text-transform:uppercase* have been used to style the *onAirNow* label. There is a full example CSS file *widgets/css/airtime-widgets.css* in the Airtime installation tarball, GitHub repository, or */usr/share/doc/airtime/examples/* directory on Debian/Ubuntu.
|
||||
|
||||
A variation on this widget displays the item being played out, rather than the show names:
|
||||
|
||||
<script>
|
||||
$(document).ready(function() {
|
||||
$("#headerLiveTrackHolder").airtimeLiveTrackInfo({
|
||||
sourceDomain: "https://schedule.example.com/",
|
||||
text: {onAirNow:"On Air Now", offline:"Offline", current:"Current", next:"Next"},
|
||||
updatePeriod: 20 //seconds
|
||||
});
|
||||
});
|
||||
</script>
|
||||
|
||||
The id of the <div> element in the page body would have to be updated to match:
|
||||
|
||||
<div id="headerLiveTrackHolder" style="border: 1px solid #999999; padding: 10px;"></div>
|
||||
|
||||
The next widget *airtimeShowSchedule* is medium sized, and displays the upcoming show schedule for that day.
|
||||
|
||||
<script>
|
||||
$(document).ready(function() {
|
||||
$("#onAirToday").airtimeShowSchedule({
|
||||
sourceDomain: "https://schedule.example.com/",
|
||||
text: {onAirToday:"On air today"},
|
||||
updatePeriod: 60 //seconds
|
||||
});
|
||||
});
|
||||
</script>
|
||||
|
||||
Again, the id of the <div> element has to match the script for the widget to appear:
|
||||
|
||||
<div id="onAirToday"></div>
|
||||
|
||||
The output from the widget script above can be styled to look like this screen shot:
|
||||
|
||||
|
||||
|
||||
Finally, the following code creates a large widget *airtimeWeekSchedule* that enables site visitors to browse through the show schedule for that week. In this example, all widget labels have been translated into French:
|
||||
|
||||
<script>
|
||||
$(document).ready(function() {
|
||||
|
||||
$("#scheduleTabs").airtimeWeekSchedule({
|
||||
sourceDomain:"https://schedule.example.com/",
|
||||
dowText:{monday:"Lundi", tuesday:"Mardi", wednesday:"Mercredi", thursday:"Jeudi", friday:"Vendredi", saturday:"Samedi", sunday:"Dimanche"},
|
||||
miscText:{time:"Temps", programName:"Nom du Programme", details:"Détails", readMore:"Lire La Suite"},
|
||||
updatePeriod: 600 //seconds
|
||||
});
|
||||
|
||||
var d = new Date().getDay();
|
||||
$('#scheduleTabs').tabs({selected: d === 0 ? 6 : d-1, fx: { opacity: 'toggle' }});
|
||||
|
||||
});
|
||||
</script>
|
||||
|
||||
The <div> element for this widget would be:
|
||||
|
||||
<div id="scheduleTabs"></div>
|
||||
|
||||
Using the code above and the CSS and image files provided with Airtime, the weekly schedule can be styled to look like this:
|
||||
|
||||
|
||||
|
||||
Optionally, you can display the schedule for the week ahead, as well as the current week. This requires the Javascript file *jquery.showinfo.js* supplied with Airtime 2.5.0 or later, where the value of the variable *dow* (for days of the week) includes fourteen rather than seven days:
|
||||
|
||||
var dow = ["monday", "tuesday", "wednesday", "thursday", "friday",
|
||||
"saturday", "sunday", "nextmonday", "nexttuesday",
|
||||
"nextwednesday","nextthursday", "nextfriday",
|
||||
"nextsaturday", "nextsunday"];
|
||||
|
||||
In that case, the labels for the days of the week could be configured as follows:
|
||||
|
||||
dowText: {monday:"Monday", tuesday:"Tuesday", wednesday:"Wednesday",
|
||||
thursday:"Thursday", friday:"Friday", saturday:"Saturday",
|
||||
sunday:"Sunday", nextmonday:"Next Monday",
|
||||
nexttuesday:"Next Tuesday", nextwednesday:"Next Wednesday",
|
||||
nextthursday:"Next Thursday",nextfriday:"Next Friday",
|
||||
nextsaturday:"Next Saturday", nextsunday:"Next Sunday"},
|
||||
|
||||
The value of **sourceDomain** in the code examples above should match the URL that you wish to serve schedule information to the public from. If you have used the *Caching schedule information* method detailed above, this would be the URL of your schedule server, not the Airtime server directly.
|
||||
If you have secure shell access (SSH) to the remote web server, you could write a script to use the secure copy command (scp) instead of ftp.
|
||||
|
|
@ -1,16 +1,17 @@
|
|||
If the server is only being used for Airtime and has a web browser installed, you can access the administration interface directly on that server by opening the address:
|
||||
If the server is only being used for LibreTime and has a web browser installed, you can access the administration interface directly on that server by opening the address:
|
||||
|
||||
http://localhost/
|
||||
|
||||
If you have set up Airtime so that it can be accessed from other computers, you would use a domain name instead. For example:
|
||||
If you have set up LibreTime so that it can be accessed from other computers, you would use a domain name instead. For example:
|
||||
|
||||
https://airtime.example.com/
|
||||
https://libretime.example.com/
|
||||
|
||||
You can log in for the first time with the user name *admin* and the password set during installation. Your browser should automatically focus on the **Username** field.
|
||||
|
||||
|
||||
|
||||
|
||||
If you enter the password incorrectly three times, you will be presented with a reCAPTCHA challenge to prove that you are a human, and not a password-guessing robot. This feature helps protect your Airtime installation against brute force attacks.
|
||||
If you enter the password incorrectly three times, you will be presented with a reCAPTCHA challenge to prove that you are a human, and not a password-guessing robot. This feature helps protect your LibreTime installation against brute force
|
||||
attacks.
|
||||
|
||||
|
||||
|
||||
|
|
@ -22,50 +23,48 @@ The **E-mail** address you enter must match the address stored in the database f
|
|||
|
||||
|
||||
|
||||
Register Airtime
|
||||
----------------
|
||||
|
||||
After you have logged in as *admin* for the first time, a pop-up window will ask if you wish to send technical support data about your server to Sourcefabric.
|
||||
|
||||
|
||||
|
||||
These details can be viewed by clicking on the **Show me what I am sending** link, which expands a scrolling window. The data helps Sourcefabric engineers resolve any problems with your Airtime installation, as well as count the number of installations worldwide.
|
||||
|
||||
<img src="static/Screenshot546-Remind_me_never_250.png" width="535" height="275" />
|
||||
|
||||
Sourcefabric has a privacy policy regarding data collection, which you can read by clicking the link to <http://www.sourcefabric.org/en/about/policy/> further down. After checking the **Send support feedback** and **privacy policy** boxes, you can submit the data by clicking the **Yes, help Airtime** button.
|
||||
|
||||
This window also offers the opportunity to **Promote my station on Sourcefabric.org** (on the page <http://www.sourcefabric.org/en/airtime/whosusing/>) by checking the box. Fill in the form which will appear with some details about your station. The contact details are only requested for verification purposes, and will not be made available to the public. Click the **Browse** button to select a **Station Logo** image from the file manager on your computer.
|
||||
|
||||
|
||||
|
||||
The Master Panel
|
||||
----------------
|
||||
|
||||
After the pop-up window is closed, you should now see the **Master Panel**, which is present at the top of every page of the Airtime interface. On the left hand side, the Master Panel displays the details of the **Previous** file played out, the current file playing (with an orange progress bar and time elapsed/time remaining), and the details of the **Next** file due to play. It also displays the name and scheduled time of the current show, with a blue progress bar.
|
||||
The **Master Panel** is present at the top of every page of the LibreTime interface. On the left hand side, the Master Panel displays the details of the **Previous** file played out,
|
||||
the current file playing (with an orange progress bar and time elapsed/time remaining), and the details of the **Next**
|
||||
file due to play. It also displays the name and scheduled time of the current show, with a blue progress bar.
|
||||
|
||||
Beneath this side of the Master Panel is the main navigation menu, with sub-menus labelled **Now Playing**, **Add Media**, **Library**, **Calendar**, **System**, **History** and **Help**. We'll be looking at the contents of these menus in the following chapters of this book.
|
||||
|
||||
|
||||
<img src="static/Screenshot542-Main_menus_250.png" width="595" height="145" />
|
||||
Beneath this side of the Master Panel is the main navigation menu. We'll be looking at the contents of these menus in the
|
||||
following chapters of this book.
|
||||
|
||||
On the right hand side of the Master Panel are the switches for the **Source Streams**, which enable you to switch from scheduled play to remote live sources, and back. (See the chapter *Stream settings* for details of this feature). The **On Air** indicator turns from dark grey to red whenever audio is being played out. Underneath this indicator is a **Listen** button, which opens a pop-up player that can be used to audition the available playout streams.
|
||||
|
||||
|
||||
There is also a clock indicating the **Station time** and time zone. Beneath the clock and just to the left, the name of the user currently logged in is displayed, and there is the link for you to **Logout**.
|
||||
On the right hand side of the Master Panel are the switches for the **Source Streams**, which enable you to switch from
|
||||
scheduled play to remote live sources, and back. (See the chapter *Stream settings* for details of this feature). The
|
||||
**On Air** indicator turns from dark grey to red whenever audio is being played out. Underneath this indicator is a
|
||||
**Listen** button, which opens a pop-up player that can be used to audition the available playout streams.
|
||||
|
||||
There is also a clock indicating the **Station time** and time zone. Beneath the clock and just to the left, the name of
|
||||
the user currently logged in is displayed, and there is the link for you to **Logout**.
|
||||
|
||||
|
||||
|
||||
Clicking the username link opens a page in which you can update your Airtime password, contact details, language and time zone preferences. Click the **Save** button once you have made the changes that you require.
|
||||
Clicking the username link opens a page in which you can update your LibreTime password, contact details, language and time
|
||||
zone preferences. Click the **Save** button once you have made the changes that you require.
|
||||
|
||||
|
||||
|
||||
On the right of the Logout link, clicking the green check mark opens a pop-up window with information about the version of Airtime installed. If your Airtime installation is not the latest version available, the green check mark changes to a green upgrade arrow. Should your Airtime installation get too far out of date, this arrow will change to a red exclamation mark.
|
||||
On the right of the Logout link, clicking the green check mark opens a pop-up window with information about the version of
|
||||
LibreTime installed. If your LibreTime installation is not the latest version available, the green check mark changes to a
|
||||
green upgrade arrow. Should your LibreTime installation get too far out of date, this arrow will change to a red exclamation
|
||||
mark.
|
||||
|
||||
<img src="static/Screenshot543-Running_latest_version_250.png" width="595" height="230" />
|
||||
|
||||
Checking an Icecast server
|
||||
--------------------------
|
||||
|
||||
If you have installed an Icecast streaming media server, you can check that Icecast is running by opening its default server port of 8000 in your web browser. For example, on the server itself, you can use:
|
||||
If you have installed an Icecast streaming media server, you can check that Icecast is running by opening its default server
|
||||
port of 8000 in your web browser. For example, on the server itself, you can use:
|
||||
|
||||
http://localhost:8000
|
||||
|
||||
|
|
@ -73,6 +72,7 @@ or from another machine, using the domain name of the Icecast server:
|
|||
|
||||
http://streaming.example.com:8000
|
||||
|
||||
You should see the Icecast status page, with details of any connections that your Airtime server has made to this Icecast server. If you have only just installed Airtime, there may not be any media playing out yet.
|
||||
You should see the Icecast status page, with details of any connections that your LibreTime server has made to this Icecast
|
||||
server. If you have only just installed LibreTime, there may not be any media playing out yet.
|
||||
|
||||
|
||||
|
|
|
|||
BIN
docs/manual/getting-started/static/Screenshot-Login.png
Normal file
BIN
docs/manual/getting-started/static/Screenshot-Login.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
docs/manual/getting-started/static/Screenshot-MainMenu.png
Normal file
BIN
docs/manual/getting-started/static/Screenshot-MainMenu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
BIN
docs/manual/getting-started/static/Screenshot-MasterPanel.png
Normal file
BIN
docs/manual/getting-started/static/Screenshot-MasterPanel.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 20 KiB |
|
|
@ -1,4 +1,4 @@
|
|||
This listing is provided to help ensure that the correct model parameter is passed to the ALSA kernel module for an Intel HDA soundcard, if one is fitted to your Airtime server. See the chapter *Preparing the server* in this book for more details.
|
||||
This listing is provided to help ensure that the correct model parameter is passed to the ALSA kernel module for an Intel HDA soundcard, if one is fitted to your Libretime server. See the chapter *Preparing the server* in this book for more details.
|
||||
|
||||
Model name Description
|
||||
---------- -----------
|
||||
|
|
|
|||
|
|
@ -1,24 +1,30 @@
|
|||
The first entry on Airtime's **Help** menu offers a **Getting Started** guide for new users. Further down, there is also a link to the online version of this **User Manual** and an **About** page, which displays version and licensing information.
|
||||
The first entry on Libretime's **Help** menu offers a **Getting Started** guide
|
||||
for new users. Further down, there is also a link to the online version of this
|
||||
**User Manual**.
|
||||
|
||||
|
||||
|
||||
You can visit the Airtime online support forum, and sign up for the mailing list, at <http://forum.sourcefabric.org/categories/airtime-support>
|
||||
You can visit the Libretime online support forum at
|
||||
<https://discourse.libretime.org/c/get-help> to ask for help from the community
|
||||
regarding your LibreTime setup.
|
||||
|
||||
This forum is mirrored by the mailing list, so posts on the forum appear on the mailing list and vice versa. You can therefore also post a message there by emailing <airtime-support@lists.sourcefabric.org>
|
||||
|
||||
To subscribe to forum updates via email, please register or login to the forum by clicking the appropriate link. Then visit your profile page at <http://forum.sourcefabric.org/profile/> and click the link **My Email Subscriptions** on the left side menu. In the pop-up window that opens, check the boxes for the mailing lists you wish to subscribe to, then click the **Save** button.
|
||||
|
||||
Bug reporting
|
||||
-------------
|
||||
|
||||
Airtime needs your input to improve. If you think you've found a bug, please visit <http://dev.sourcefabric.org/> and sign in, using the same login and password that you registered for the Airtime forum. Create a bug report by selecting **Create Issue**, then **Airtime**, and then **Bug**. That way, the Airtime team can keep track of your problem and notify you when it has been fixed. You can also suggest improvements and new features for Airtime on that site.
|
||||
Libretime needs your input to improve. If you think you've found a bug, please
|
||||
visit <https://github.com/LibreTime/libretime>. Create a bug report by selecting
|
||||
**Issues**, then **New Issue**. That way, the Libretime team can keep track of
|
||||
your problem and notify you when it has been fixed. You can also suggest
|
||||
improvements and new features for Libretime on that site.
|
||||
|
||||
Contact
|
||||
-------
|
||||
|
||||
Finally, when all other avenues have been exhausted, email us directly at <contact@sourcefabric.org> and we'll try to help!
|
||||
|
||||
Other help
|
||||
----------
|
||||
|
||||
The UNESCO publication [*Community Radio - A user's guide to the technology*](static/CommunityRadioUserGuide.pdf) features a very comprehensive guide to setting up a community radio station. This guide is aimed at people thinking about setting up a radio station in India, but includes lots of practical advice that would be useful in any country.
|
||||
The UNESCO publication [*Community Radio - A user's guide to the technology*](static/CommunityRadioUserGuide.pdf)
|
||||
features a very comprehensive guide to setting up a community radio station.
|
||||
This guide is aimed at people thinking about setting up a radio station in
|
||||
India, but includes lots of practical advice that would be useful in any
|
||||
country.
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 67 KiB |
|
|
@ -3,7 +3,7 @@ History
|
|||
|
||||
On the History menu, the **Playout History** page enables you to view a list of files played within a specific date and time range. This page is designed to help your station prepare reports for music royalty collection societies and regulatory agencies.
|
||||
|
||||
Search results can be copied to the clipboard using the **Copy** button, exported as data in **CSV** format (comma separated values), exported as a document in **PDF** format, or displayed in a printer-friendly format using the **Print** button. (Your web browser must have an Adobe Flash plugin installed for these buttons to appear). Press the **Esc** key to return to the Airtime interface once the print job is complete.
|
||||
Search results can be copied to the clipboard using the **Copy** button, exported as data in **CSV** format (comma separated values), exported as a document in **PDF** format, or displayed in a printer-friendly format using the **Print** button. (Your web browser must have an Adobe Flash plugin installed for these buttons to appear). Press the **Esc** key to return to the Libretime interface once the print job is complete.
|
||||
|
||||
This page has three tabs: **Log Sheet**, **File Summary** and **Show Summary**. On any of these tabs, you can select a date and time range by clicking the calendar and clock icons in the upper left corner of the page. Then click the search button, which has a magnifying glass icon, to the right. A list of files played during that date and time range will appear further down the page.
|
||||
|
||||
|
|
@ -22,7 +22,7 @@ On the **Show Summary** tab, click the name of a show within the search range to
|
|||
Manual logging
|
||||
--------------
|
||||
|
||||
If your station features playout from analogue sources such as turntables or microphones, there is no automatic metadata for Airtime to collect from these inputs. To ensure that the playout history is complete, you can add log entries manually by clicking the **+ Create Entry** button. This action opens a pop-up window with default fields of Start Time, End Time, Title and Creator. Click the **Find** button to automatically fill the **Choose Show Instance** menu with the names of shows that took place within the specified time range. Then click the **Save** button to enter the new item into the playout history.
|
||||
If your station features playout from analogue sources such as turntables or microphones, there is no automatic metadata for Libretime to collect from these inputs. To ensure that the playout history is complete, you can add log entries manually by clicking the **+ Create Entry** button. This action opens a pop-up window with default fields of Start Time, End Time, Title and Creator. Click the **Find** button to automatically fill the **Choose Show Instance** menu with the names of shows that took place within the specified time range. Then click the **Save** button to enter the new item into the playout history.
|
||||
|
||||
<img src="static/Screenshot536-Manual_login_250.png" width="530" height="575" />
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
The streaming host configuration for Airtime is shown in the file */etc/airtime/liquidsoap.cfg* which is automatically generated by the **Streams** page, found on the **System** menu of the Airtime administration interface. For this reason, you would not normally edit the streaming configuration manually, as any changes are likely to be overwritten by the administration interface.
|
||||
The streaming host configuration for Libretime is shown in the file */etc/airtime/liquidsoap.cfg* which is automatically generated by the **Streams** page, found on the **System** menu of the Libretime administration interface. For this reason, you would not normally edit the streaming configuration manually, as any changes are likely to be overwritten by the administration interface.
|
||||
|
||||
Database and RabbitMQ hosts
|
||||
---------------------------
|
||||
|
|
@ -7,7 +7,7 @@ Optionally, you may wish to edit the file */etc/airtime/airtime.conf* to set the
|
|||
|
||||
sudo nano /etc/airtime/airtime.conf
|
||||
|
||||
You can also set options for RabbitMQ messaging, the Airtime server and SoundCloud uploads in this file, although you should not normally need to adjust the defaults unless you are running a large Airtime system distributed across multiple servers. To run the Airtime server in demo mode, which changes the greeting on the login page and prevents user accounts from being created or modified, set the value of *demo* to 1.
|
||||
You can also set options for RabbitMQ messaging, the Libretime server and SoundCloud uploads in this file, although you should not normally need to adjust the defaults unless you are running a large Libretime system distributed across multiple servers. To run the Libretime server in demo mode, which changes the greeting on the login page and prevents user accounts from being created or modified, set the value of *demo* to 1.
|
||||
|
||||
[database]
|
||||
host = localhost
|
||||
|
|
@ -26,7 +26,7 @@ You can also set options for RabbitMQ messaging, the Airtime server and SoundClo
|
|||
api_key = XXXXXXXXXXXXXXXXXXXXX
|
||||
web_server_user = www-data
|
||||
airtime_dir = /usr/share/airtime
|
||||
base_url = airtime.example.com
|
||||
base_url = libretime.example.com
|
||||
base_port = 80
|
||||
base_dir = /
|
||||
cache_ahead_hours = 1
|
||||
|
|
@ -46,13 +46,14 @@ Save and close the file with **Ctrl+O** and **Ctrl+X**. If you have changed the
|
|||
|
||||
sudo airtime-update-db-settings
|
||||
|
||||
to make sure all of Airtime's database configuration files are updated. This command should output the following text to the server console:
|
||||
to make sure all of Libretime's database configuration files are updated. This command should output the following text to the server console:
|
||||
|
||||
Airtime root folder found at /usr/share/airtime
|
||||
Libretime root folder found at /usr/share/airtime
|
||||
Updating /usr/share/airtime/application/configs/application.ini
|
||||
Updating /usr/share/airtime/build/build.properties
|
||||
Updating /usr/share/airtime/build/runtime-conf.xml
|
||||
Success!
|
||||
|
||||
|
||||
API client configuration
|
||||
------------------------
|
||||
|
|
@ -62,53 +63,15 @@ If you have changed the *base\_url*, *base\_port* or *base\_dir* setting in */et
|
|||
bin_dir = /usr/lib/airtime/api_clients
|
||||
api_key = 'XXXXXXXXXXXXXXXXXXXX'
|
||||
api_base = api
|
||||
host = airtime.example.com
|
||||
host = libretime.example.com
|
||||
base_port = 80
|
||||
base_dir = /
|
||||
|
||||
Media monitor settings
|
||||
----------------------
|
||||
|
||||
Airtime's media monitor has its own configuration file in */etc/airtime/media-monitor.cfg* which contains RabbitMQ settings and other preferences.
|
||||
|
||||
api_client = airtime
|
||||
|
||||
# where the binary files live
|
||||
bin_dir = /usr/lib/airtime/media-monitor
|
||||
|
||||
# where the logging files live
|
||||
log_dir = /var/log/airtime/media-monitor
|
||||
|
||||
############################################
|
||||
# RabbitMQ settings #
|
||||
############################################
|
||||
rabbitmq_host = localhost
|
||||
rabbitmq_user = airtime
|
||||
rabbitmq_password = XXXXXXXXXXXXXXXXXXXX
|
||||
rabbitmq_vhost = /airtime
|
||||
|
||||
############################################
|
||||
# Media-Monitor preferences #
|
||||
############################################
|
||||
|
||||
#how long to queue up events performed on the files themselves.
|
||||
check_filesystem_events = 5
|
||||
|
||||
#how long to queue metadata input from airtime.
|
||||
check_airtime_events = 30
|
||||
|
||||
# MM2 only:
|
||||
touch_interval = 5
|
||||
chunking_number = 450
|
||||
request_max_wait = 3.0
|
||||
rmq_event_wait = 0.1
|
||||
logpath = /var/log/airtime/media-monitor/media-monitor.log
|
||||
index_path = /var/tmp/airtime/media-monitor/last_index
|
||||
|
||||
Playout and recorder settings
|
||||
-----------------------------
|
||||
|
||||
Settings for pypo, the playout and recording engine used by Airtime, are found in the file */etc/airtime/pypo.cfg*. After making changes to this file, you will have to issue the command:
|
||||
Settings for pypo, the playout and recording engine used by Libretime, are found in the file */etc/airtime/airtime.conf*. After making changes to this file, you will have to issue the command:
|
||||
|
||||
sudo /etc/init.d/airtime-playout restart
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
Airtime supports direct connection to two popular streaming media servers, the open source **Icecast** (<http://www.icecast.org>) and the proprietary **SHOUTcast** (<http://www.shoutcast.com>). Apart from the software license, the main difference between these two servers is that Icecast supports simultaneous MP3, AAC, Ogg Vorbis or Ogg Opus streaming from Airtime, whereas SHOUTcast supports MP3 and AAC streams but not Ogg Vorbis or Opus. The royalty-free Ogg Vorbis format has the advantage of better sound quality than MP3 at lower bitrates, which has a direct impact on the amount of bandwidth that your station will require to serve the same number of listeners. Ogg Opus also benefits from good sound quality at low bitrates, with the added advantage of lower latency than other streaming formats. Opus is now an IETF standard (<http://tools.ietf.org/html/rfc6716>) and requires Icecast 2.4 or later to be installed on the streaming server.
|
||||
Libretime supports direct connection to two popular streaming media servers, the open source **Icecast** (<http://www.icecast.org>) and the proprietary **SHOUTcast** (<http://www.shoutcast.com>). Apart from the software license, the main difference between these two servers is that Icecast supports simultaneous MP3, AAC, Ogg Vorbis or Ogg Opus streaming from Libretime, whereas SHOUTcast supports MP3 and AAC streams but not Ogg Vorbis or Opus. The royalty-free Ogg Vorbis format has the advantage of better sound quality than MP3 at lower bitrates, which has a direct impact on the amount of bandwidth that your station will require to serve the same number of listeners. Ogg Opus also benefits from good sound quality at low bitrates, with the added advantage of lower latency than other streaming formats. Opus is now an IETF standard (<http://tools.ietf.org/html/rfc6716>) and requires Icecast 2.4 or later to be installed on the streaming server.
|
||||
|
||||
Ogg Vorbis playback is supported in **Mozilla Firefox**, **Google Chrome** and **Opera** browsers, via **jPlayer** (<http://jplayer.org/>), and is also supported in several popular media players, including VideoLAN Client, also known as VLC (<http://www.videolan.org/vlc/>). (See the chapter *Stream player for your website* on how to deliver **jPlayer** to your audience). Ogg Opus is relatively new and is supported natively in the very latest browsers, such as Mozilla Firefox 25.0, and media players including VLC 2.0.4 or later.
|
||||
|
||||
Streaming MP3 below a bitrate of 128kbps is not recommended for music, because of a perceptible loss of high audio frequencies in the broadcast playout. A 96kbps or 64kbps MP3 stream may be acceptable for voice broadcasts if there is a requirement for compatibility with legacy hardware playback devices which do not support Ogg Vorbis or Opus streams.
|
||||
|
||||
Because Airtime supports simultaneous streaming in multiple formats, it is possible to offer one or more streams via your website, and another independent stream for direct connection from hardware players. You can test whether Ogg streams sound better at low bitrates for yourself, by using the **LISTEN** button in Airtime's **Master Panel** to switch between streaming formats.
|
||||
Because Libretime supports simultaneous streaming in multiple formats, it is possible to offer one or more streams via your website, and another independent stream for direct connection from hardware players. You can test whether Ogg streams sound better at low bitrates for yourself, by using the **LISTEN** button in Libretime's **Master Panel** to switch between streaming formats.
|
||||
|
||||
Conversely, you may have a music station which wants to stream at 160kbps or 192kbps to offer a quality advantage over stations streaming at 128kbps or less. Since Ogg, AAC and MP3 formats use lossy compression, listeners will only hear the benefit of higher streaming bitrates if the media files in the Airtime storage server are encoded at an equivalent bitrate, or higher.
|
||||
Conversely, you may have a music station which wants to stream at 160kbps or 192kbps to offer a quality advantage over stations streaming at 128kbps or less. Since Ogg, AAC and MP3 formats use lossy compression, listeners will only hear the benefit of higher streaming bitrates if the media files in the Libretime storage server are encoded at an equivalent bitrate, or higher.
|
||||
|
||||
UTF-8 metadata in Icecast MP3 streams
|
||||
-------------------------------------
|
||||
|
|
@ -15,10 +15,10 @@ When sending metadata about your stream to an Icecast server in non-Latin alphab
|
|||
|
||||
|
||||
|
||||
The solution is to specify that the metadata for the MP3 mount point you are using should be interpreted using UTF-8 encoding. You can do this by adding the following stanza to the */etc/icecast2/icecast.xml* file, where *airtime.mp3* is the name of your mount point:
|
||||
The solution is to specify that the metadata for the MP3 mount point you are using should be interpreted using UTF-8 encoding. You can do this by adding the following stanza to the */etc/icecast2/icecast.xml* file, where *libretime.mp3* is the name of your mount point:
|
||||
|
||||
<mount>
|
||||
<mount-name>/airtime.mp3</mount-name>
|
||||
<mount-name>/libretime.mp3</mount-name>
|
||||
<charset>UTF-8</charset>
|
||||
</mount>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
In a typical radio station configuration, the live output from the broadcast studio and the scheduled output from Airtime are mixed together before being sent further along the broadcast chain, to a transmitter or streaming media server on the Internet. (This may not be the case if your Airtime server is remote from the studio, and you are using the **Show Source Mount Point** or **Master Source Mount Point** to mix live and scheduled content. See the *Stream Settings* chapter for details).
|
||||
In a typical radio station configuration, the live output from the broadcast studio and the scheduled output from Libretime are mixed together before being sent further along the broadcast chain, to a transmitter or streaming media server on the Internet. (This may not be the case if your Libretime server is remote from the studio, and you are using the **Show Source Mount Point** or **Master Source Mount Point** to mix live and scheduled content. See the *Stream Settings* chapter for details).
|
||||
|
||||
If your **Icecast** server is hosted in a remote data centre, you may not have the option to handover the streaming media source manually, because you have no physical access to connect a broadcast mixer to the server. Disconnecting the stream and beginning another is less than ideal, because the audience's media players will also be disconnected when that happens.
|
||||
|
||||
The **Icecast** server has a *fallback-mount* feature which can be used to move clients (media players used by listeners or viewers) from one source to another, as new sources become available. This makes it possible to handover from Airtime output to a show from another source, and handover to Airtime again once the other show has ended.
|
||||
The **Icecast** server has a *fallback-mount* feature which can be used to move clients (media players used by listeners or viewers) from one source to another, as new sources become available. This makes it possible to handover from Libretime output to a show from another source, and handover to Libretime again once the other show has ended.
|
||||
|
||||
To enable fallback mounts, edit the main Icecast configuration file to define the mount points you will use, and the relationship between them.
|
||||
|
||||
sudo nano /etc/icecast2/icecast.xml
|
||||
|
||||
The example *<mount>* section provided in the *icecast.xml* file is commented out by default. Before or after the commented section, add three mount point definitions. The default mount point used by Airtime is */airtime\_128* which is shown in the */etc/airtime/liquidsoap.cfg* file. You must also define a mount point for the live source (called */live.ogg* in this example) and a mount point for the public to connect to (called */stream.ogg* in this example).
|
||||
The example *<mount>* section provided in the *icecast.xml* file is commented out by default. Before or after the commented section, add three mount point definitions. The default mount point used by Libretime is */airtime\_128* which is shown in the */etc/airtime/liquidsoap.cfg* file. You must also define a mount point for the live source (called */live.ogg* in this example) and a mount point for the public to connect to (called */stream.ogg* in this example).
|
||||
|
||||
<mount>
|
||||
<mount-name>/airtime_128</mount-name>
|
||||
|
|
@ -29,9 +29,9 @@ The example *<mount>* section provided in the *icecast.xml* file is commen
|
|||
<hidden>0</hidden>
|
||||
</mount>
|
||||
|
||||
These mount point definitions mean that a client connecting to a URL such as *http://icecast.example.com:8000/stream.ogg* will first fall back to the */live.ogg* mount point if it is available. If not, the client will fall back in turn to the */airtime\_128* mount point for Airtime playout.
|
||||
These mount point definitions mean that a client connecting to a URL such as *http://icecast.example.com:8000/stream.ogg* will first fall back to the */live.ogg* mount point if it is available. If not, the client will fall back in turn to the */airtime\_128* mount point for Libretime playout.
|
||||
|
||||
Setting the value of *<fallback-override>* to 1 (enabled) means that when the */live.ogg* mount point becomes available again, the client will be re-connected to it. If you wish to hide the */airtime\_128* and */live.ogg* mount points from the public Icecast web interface, set the value of *<hidden>* in each of these definitions to 1.
|
||||
Setting the value of *<fallback-override>* to 1 (enabled) means that when the */live.ogg* mount point becomes available again, the client will be re-connected to it. If you wish to hide the */airtime\_128* and */live.ogg* mount points from the public Icecast web interface, set the value of *<hidden>* in each of these definitions to 1.
|
||||
|
||||
Source configuration
|
||||
--------------------
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Piwik (<http://piwik.org/>) is an open source web analytics platform which supports Icecast's log format, in Piwik version 2.0 or later. For your convenience, packages of Piwik for Debian and Ubuntu are provided in the <http://apt.sourcefabric.org> repository. If you have already configured your Airtime server for this repository, you can install the **piwik** package and its dependencies with the command:
|
||||
Piwik (<http://piwik.org/>) is an open source web analytics platform which supports Icecast's log format, in Piwik version 2.0 or later. For your convenience, packages of Piwik for Debian and Ubuntu are provided in the <http://apt.sourcefabric.org> repository. If you have already configured your Libretime server for this repository, you can install the **piwik** package and its dependencies with the command:
|
||||
|
||||
sudo apt-get install piwik php5-geoip php5-cli mysql-server
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
The Airtime administration interface, as a web application, is fully customizable using the same methods that you might use to modify a website. For instance, you may wish to increase certain font sizes or change the colours in the Airtime interface to better suit staff users with impaired vision. To do this, open one of the CSS files in the */public/css/* directory under the Airtime *DocumentRoot* directory in an editor such as **nano**:
|
||||
The Libretime administration interface, as a web application, is fully customizable using the same methods that you might use to modify a website. For instance, you may wish to increase certain font sizes or change the colours in the Libretime interface to better suit staff users with impaired vision. To do this, open one of the CSS files in the */public/css/* directory under the Libretime *DocumentRoot* directory in an editor such as **nano**:
|
||||
|
||||
sudo nano /usr/share/airtime/public/css/styles.css
|
||||
|
||||
|
|
@ -14,7 +14,7 @@ To change the background colour of the administration interface from dark gray t
|
|||
|
||||
Save the file with **Ctrl+O**, then refresh your browser to see the change to the interface background colour.
|
||||
|
||||
Any custom changes that you make to the administration interface should be backed up before upgrading Airtime to a newer version, otherwise they could be overwritten. If you have made improvements that you think might be useful to other Airtime users, please contact Sourcefabric and tell us about them.
|
||||
Any custom changes that you make to the administration interface should be backed up before upgrading Libretime to a newer version, otherwise they could be overwritten. If you have made improvements that you think might be useful to other Libretime users, please contact Libretime and tell us about them.
|
||||
|
||||
Modifying the Icecast interface
|
||||
-------------------------------
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
The Airtime administration interface can be localized using the standard GNU **gettext** method. Using GitHub for this task means you don't have to tackle the whole of a localization yourself; just as much as you can manage.
|
||||
The Libretime administration interface can be localized using the standard GNU **gettext** method. Using GitHub for this task means you don't have to tackle the whole of a localization yourself; just as much as you can manage.
|
||||
|
||||
|
||||
|
||||
First, you should check if a localization is already under way for your locale of choice. The best way to do this is to take a look at the 'master' branch in the GitHub repository for Airtime at <https://github.com/sourcefabric/Airtime/tree/master>. You can also ask in the Airtime development forum at <http://forum.sourcefabric.org/categories/airtime-development>, where you might find community members who can help you with the translation.
|
||||
First, you should check if a localization is already under way for your locale of choice. The best way to do this is to take a look at the 'master' branch in the GitHub repository for Libretime at <https://github.com/LibreTime/libretime>. You can also ask in the Libretime development forum at <https://discourse.libretime.org/>, where you might find community members who can help you with the translation.
|
||||
|
||||
GNU **gettext** means using a .po file for each language or dialect, a specially formatted plain text file with groups of three or more lines, like this example from Airtime's Korean localization:
|
||||
GNU **gettext** means using a .po file for each language or dialect, a specially formatted plain text file with groups of three or more lines, like this example from Libretime's Korean localization:
|
||||
|
||||
#: airtime_mvc/application/configs/navigation.php:57
|
||||
msgid "Media Folders"
|
||||
|
|
@ -16,11 +16,11 @@ If you use the cross-platform program **Poedit** (<http://www.poedit.net/>) to e
|
|||
|
||||
Before manually translating strings in Poedit from scratch, you should take a look at the online translation services available, such as Lingohub (<https://lingohub.com>) or Google's Translator Toolkit (<http://translate.google.com/toolkit/>), which both support gettext .po files. If using automatic translation, you can then use Poedit to fine-tune the localization and fix any formatting errors.
|
||||
|
||||
If you don't already have a GitHub account, you can sign up at <https://github.com/signup/free>. Once you have a GitHub account, you can fork a copy (<https://help.github.com/articles/fork-a-repo>) of the Airtime project. Work for the next major version of the software is done in the **master** branch of each project, so that's the branch to **checkout** after you have made the initial **git clone**.
|
||||
If you don't already have a GitHub account, you can sign up at <https://github.com/signup/free>. Once you have a GitHub account, you can fork a copy (<https://help.github.com/articles/fork-a-repo>) of the Libretime project. Work for the next major version of the software is done in the **master** branch of each project, so that's the branch to **checkout** after you have made the initial **git clone**.
|
||||
|
||||
In the locale code *de\_CH*, for example, *de* represents the German language and the suffix *\_CH* indicates the dialect spoken in Switzerland. Some languages have a wide variety of dialect localizations, which can be differentiated with a suffix in this way. You should update the header information in the .po file, which includes the language code and a country code, using one of the existing .po files as a guide.
|
||||
|
||||
After forking the Airtime git repository, make sure you're in the **master** branch:
|
||||
After forking the Libretime git repository, make sure you're in the **master** branch:
|
||||
|
||||
git branch
|
||||
devel
|
||||
|
|
@ -40,18 +40,18 @@ and update the header information in the new copy of the *airtime.po* file using
|
|||
|
||||
For the example of Swiss German, the header of the file should now look like this:
|
||||
|
||||
# SWISS GERMAN (de_CH) translation for Airtime.
|
||||
# SWISS GERMAN (de_CH) translation for Libretime.
|
||||
# Copyright (C) 2013 Sourcefabric
|
||||
# This file is distributed under the same license as the Airtime package.
|
||||
# This file is distributed under the same license as the Libretime package.
|
||||
# Sourcefabric <contact@sourcefabric.org>, 2013.
|
||||
#
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Airtime 2.5\n"
|
||||
"Report-Msgid-Bugs-To: http://forum.sourcefabric.org/\n"
|
||||
"Project-Id-Version: Libretime 3.0-Alpha\n"
|
||||
"Report-Msgid-Bugs-To: https://discourse.libretime.org/\n"
|
||||
|
||||
After using an online translation tool to begin a new localization, you can load the exported .po file into Poedit and complete your translation there. Enter the localization team's contact information and language into Poedit's **Edit -> Preferences** and **Catalog -> Settings** dialogs, which will be added to the .po file. When you save a .po file in Poedit, the corresponding binary .mo file will be compiled automatically.
|
||||
|
||||
Finally, **git add**, **git commit** and **git push** these new .mo and .po files to your GitHub fork of the project, and send a git pull request (<https://help.github.com/articles/using-pull-requests>) to the Airtime developers. The localization can then be added to a forthcoming Airtime release.
|
||||
Finally, **git add**, **git commit** and **git push** these new .mo and .po files to your GitHub fork of the project, and send a git pull request (<https://help.github.com/articles/using-pull-requests>) to the Libretime developers. The localization can then be added to a forthcoming Libretime release.
|
||||
|
||||
If you don't want to work with git, that's no problem - download a copy of the .po template file, edit the header, run it through an automatic translator and check it with Poedit. Then email your contribution to the Airtime team as an attachment - it will be very welcome! However, learning to use git is a good idea, because it means you can work directly on the current source code, share the localization work with the Airtime community, and avoid duplicated effort.
|
||||
If you don't want to work with git, that's no problem - download a copy of the .po template file, edit the header, run it through an automatic translator and check it with Poedit. Then email your contribution to the Libretime team as an attachment - it will be very welcome! However, learning to use git is a good idea, because it means you can work directly on the current source code, share the localization work with the Libretime community, and avoid duplicated effort.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This page of the Airtime interface enables you to search the media library, sort and display the search results by the criteria that you choose, audition library items, and drag and drop those items into a playlist. You can also adjust fade and cue points, create smart blocks (automatically generated playlists), or add incoming web streams to the library. The **Library** page is not visible to *Guest* users.
|
||||
This page of the Libretime interface enables you to search the media library, sort and display the search results by the criteria that you choose, audition library items, and drag and drop those items into a playlist. You can also adjust fade and cue points, create smart blocks (automatically generated playlists), or add incoming web streams to the library. The **Library** page is not visible to *Guest* users.
|
||||
|
||||
Searching the library
|
||||
---------------------
|
||||
|
|
@ -35,7 +35,7 @@ With a playlist open, click on an item in the search results and then click **Ad
|
|||
|
||||
|
||||
|
||||
You can also select or deselect a whole page of search results using the **Select** button, just below the simple search field. Alternatively, use the checkboxes in the first column of the search results table to select individual items, then click the **Add to current playlist** button. Items that you own which you no longer require can be deleted from Airtime's library using the **Trashcan** button.
|
||||
You can also select or deselect a whole page of search results using the **Select** button, just below the simple search field. Alternatively, use the checkboxes in the first column of the search results table to select individual items, then click the **Add to current playlist** button. Items that you own which you no longer require can be deleted from Libretime's library using the **Trashcan** button.
|
||||
|
||||
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ After adding files to the playlist, the total playlist time is displayed in the
|
|||
|
||||
To audition a playlist file in your web browser, click the white triangle**** button on the left side of its row. (If the format of the file is not supported by your browser, the triangle in this button will be greyed out). If audition of the file format is supported, a pop-up window will open, with the playlist starting at the file you clicked.
|
||||
|
||||
Click the small white **x** icon on the right hand side of each row to remove a file from the playlist. You can also drag and drop files to re-order them, or click the **Shuffle** button to re-order files automatically. Click the **Clear** button to remove all content from the playlist, or click the **Delete** button to remove the playlist from the Airtime library altogether.
|
||||
Click the small white **x** icon on the right hand side of each row to remove a file from the playlist. You can also drag and drop files to re-order them, or click the **Shuffle** button to re-order files automatically. Click the **Clear** button to remove all content from the playlist, or click the **Delete** button to remove the playlist from the Libretime library altogether.
|
||||
|
||||
|
||||
|
||||
|
|
@ -69,7 +69,7 @@ If a **Fade In** and **Cue In** are set on the same item in the playlist, the fa
|
|||
|
||||
|
||||
|
||||
When your playlist is complete, click the **New** button in the top left corner to create another playlist, click the close icon (a white cross in a black circle) in the top right corner, or browse to another page of the Airtime interface.
|
||||
When your playlist is complete, click the **New** button in the top left corner to create another playlist, click the close icon (a white cross in a black circle) in the top right corner, or browse to another page of the Libretime interface.
|
||||
|
||||
If you want to edit the playlist content or metadata later, you can find it by **Title**, **Creator**, **Last Modified** date, **Length**, **Owner** or **Year** using one of the search tools on the Library page. Click the playlist in the search results list, and then click **Edit** from the pop-up menu. You can also **Preview** the entire playlist in a pop-up audition window, **Duplicate** or **Delete** one of your playlists from this menu.
|
||||
|
||||
|
|
@ -78,13 +78,13 @@ If you want to edit the playlist content or metadata later, you can find it by *
|
|||
Creating a smart block
|
||||
----------------------
|
||||
|
||||
Smart blocks are automatically filled with media files from the Airtime library, according to the criteria that you specify. This feature is intended to save staff time, compared to selecting items for a playlist manually.
|
||||
Smart blocks are automatically filled with media files from the Libretime library, according to the criteria that you specify. This feature is intended to save staff time, compared to selecting items for a playlist manually.
|
||||
|
||||
To create a smart block, click the **New** button on the right side of the Library page, and select **New Smart Block** from the pop-up menu. Like a playlist, smart blocks can have a title and **Description**, which you can edit. This helps you find relevant smart blocks in searches.
|
||||
|
||||
|
||||
|
||||
Click the link **Smart Block Options** to display the criteria and modifiers for the smart block. The criteria can be any one of Airtime's metadata categories, such as **Title**, **Creator** or **Genre**. The modifier depends on whether the metadata in question contains letters or numbers. For example, **Title** has modifiers including *contains* and *starts with*, whereas the modifiers for **BPM** include *is greater than* and *is in the range*.
|
||||
Click the link **Smart Block Options** to display the criteria and modifiers for the smart block. The criteria can be any one of Libretime's metadata categories, such as **Title**, **Creator** or **Genre**. The modifier depends on whether the metadata in question contains letters or numbers. For example, **Title** has modifiers including *contains* and *starts with*, whereas the modifiers for **BPM** include *is greater than* and *is in the range*.
|
||||
|
||||
You can also set the **smart block type**. A **Static** smart block will save the criteria and generate the block content immediately. This enables you to edit the contents of the block in the **Library** page before adding it to a show. A **Dynamic** smart block will only save the criteria, and the specific content will be generated at the time the block is added to a show. After that, the content of the show can be changed or re-ordered in the **Now Playing** page.
|
||||
|
||||
|
|
@ -102,7 +102,11 @@ To add an AND criteria, such as **Creator** containing *jimi* AND BPM in the ran
|
|||
|
||||
By default, a smart block will not contain repeated items, which will limit the duration of the block if you do not have sufficient items meeting the specified criteria in your **Library**. To override the default behaviour, check the **Allow Repeat Tracks** box. The **Sort tracks by** menu offers the options of **random**, **newest** or **oldest** items first.
|
||||
|
||||
<img src="static/Screenshot582-Smart_block_repeat_tracks.png" alt="Smart block repeat tracks" width="595" height="255" />
|
||||
|
||||
|
||||
In addition Smart Blocks by default will never overflow the Time Limit. For instance if you set a time limit of 1 hour. It will add tracks to the schedule until it can't add any more tracks without exceeding the hour. This is to prevent tracks from being cut-off because they exceed the time limit of a show.
|
||||
|
||||
If you want a smartblock to schedule tracks until it is longer than the Time Limit you can check "Allow last track to exceed time limit". This will make LibreTime add tracks that meet the criteria until it equals or is longer than the time limit. The was the default behaviour with the Libretime software.
|
||||
|
||||
If you have a large number of files which meet the criteria that you specify, you may wish to limit the duration of the smart block using the **Limit to** field, so that it fits within the show you have in mind. Select **hours**, **minutes** or **items** from the drop-down menu, and click the **Generate** button again, if it is a static smart block. Then click the **Save** button.
|
||||
|
||||
|
|
@ -115,7 +119,7 @@ Once created, smart blocks can be found in Library searches and refined at any t
|
|||
Adding a web stream
|
||||
-------------------
|
||||
|
||||
A web stream URL and metadata can be added to the Airtime library, so that a remote stream can be searched for and scheduled to be *pulled* into a show. For example, at the top of the hour your station may pull a news report from journalists working in another studio. This is a different concept from **Master Source** and **Show Source** remote streams which are *pushed* into the Airtime playout schedule.
|
||||
A web stream URL and metadata can be added to the Libretime library, so that a remote stream can be searched for and scheduled to be *pulled* into a show. For example, at the top of the hour your station may pull a news report from journalists working in another studio. This is a different concept from **Master Source** and **Show Source** remote streams which are *pushed* into the Libretime playout schedule.
|
||||
|
||||
To add a web stream, click the **New** button on the right side of the Library page, and select **New Webstream** from the pop-up menu. Like a playlist, web streams in the Library can have a title and **Description**, which may help you find them in searches later.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ This button opens a pop-up **Live stream** window, which enables you to monitor
|
|||
|
||||
|
||||
|
||||
Beneath the drop-down menu for stream selection is an orange volume control bar. This volume control only adjusts the output level of the pop-up **Live Stream** window, not the output level of the Airtime server itself. To adjust output level between muted and maximum, click on the corresponding place in the orange bar, with maximum level on the right side. Click on the left side speaker icon to mute the output.
|
||||
Beneath the drop-down menu for stream selection is an orange volume control bar. This volume control only adjusts the output level of the pop-up **Live Stream** window, not the output level of the Libretime server itself. To adjust output level between muted and maximum, click on the corresponding place in the orange bar, with maximum level on the right side. Click on the left side speaker icon to mute the output.
|
||||
|
||||
|
||||
|
||||
|
|
@ -14,4 +14,4 @@ To display the URL of the stream you are monitoring, so that you can copy and pa
|
|||
|
||||
|
||||
|
||||
When you have finished monitoring the streams, you can close the pop-up window in the normal way, depending on the browser you are using. In Firefox, you can close the window by clicking the **X** button in the top right corner. This action will not shut down the output from the Airtime server, only the stream monitoring on your desktop computer or laptop.
|
||||
When you have finished monitoring the streams, you can close the pop-up window in the normal way, depending on the browser you are using. In Firefox, you can close the window by clicking the **X** button in the top right corner. This action will not shut down the output from the Libretime server, only the stream monitoring on your desktop computer or laptop.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ The Listener Stats page on the Analytics menu shows graphs of listener connectio
|
|||
|
||||
|
||||
|
||||
If the status indicator is red, check that the **Admin User** and **Admin Password** settings are correct under **Additional Options** for the named mount point, such as *airtime\_128*, on the **Streams** page of the **Settings** menu.
|
||||
If the status indicator is red, check that the **Admin User** and **Admin Password** settings are correct under **Additional Options** for the named mount point, such as *libretime\_128*, on the **Streams** page of the **Settings** menu.
|
||||
|
||||
By default, statistics for the last 24 hours of streaming are shown. To change this date and time range, click the calendar and clock icons in the lower left corner of the page, then click the magnifying glass icon.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
Mixxx is a cross-platform Open Source application for DJs, available from <http://www.mixxx.org/>
|
||||
|
||||
Installed on a desktop or laptop computer, Mixxx complements your Airtime server to provide a complete system for both live and scheduled broadcasting. Although Mixxx has many features designed for dance music DJs that require beat matching and pitch independent time stretching, the program can be used for any kind of manually triggered broadcast playout, including live speech shows such as news or current affairs.
|
||||
Installed on a desktop or laptop computer, Mixxx complements your Libretime server to provide a complete system for both live and scheduled broadcasting. Although Mixxx has many features designed for dance music DJs that require beat matching and pitch independent time stretching, the program can be used for any kind of manually triggered broadcast playout, including live speech shows such as news or current affairs.
|
||||
|
||||
Mixxx supports a wide variety of popular hardware control surfaces, which can be connected to your computer using a USB cable. A control surface might replace or augment an analogue mixer in your studio, depending on your live mixing and playout requirements.
|
||||
|
||||
Sound cards
|
||||
-----------
|
||||
|
||||
If you wish to use Airtime and Mixxx on the same machine, you will need two or more sound cards, as each program requires exclusive access to the sound hardware. Otherwise, you may see an error message that Mixxx cannot access the sound device.
|
||||
If you wish to use Libretime and Mixxx on the same machine, you will need two or more sound cards, as each program requires exclusive access to the sound hardware. Otherwise, you may see an error message that Mixxx cannot access the sound device.
|
||||
|
||||
|
||||
|
||||
|
|
@ -18,45 +18,27 @@ The solution is to configure Mixxx to use additional sound cards by clicking **O
|
|||
Sharing storage
|
||||
---------------
|
||||
|
||||
If you make the Airtime server's storage directory */srv/airtime/stor/* accessible to a desktop machine as a read-only location, Mixxx will accept that location as its default music library when starting up for the first time. (This location can also be configured after installation by clicking **Options**, **Preferences**, then **Library** in the main Mixxx menu).
|
||||
If you make the Libretime server's storage directory */srv/airtime/stor/* accessible to a desktop machine as a read-only location, Mixxx will accept that location as its default music library when starting up for the first time. (This location can also be configured after installation by clicking **Options**, **Preferences**, then **Library** in the main Mixxx menu).
|
||||
|
||||
|
||||
|
||||
You may need to adjust file and directory permissions so that the storage directory has read access from the desktop user account. Enabling write access directly to the storage server is not recommended, as this would allow desktop users to delete files which might be needed for playout later.
|
||||
|
||||
If the filesystem path has been configured correctly, the metadata for the files in the Airtime storage server will be displayed in the main window of the Mixxx interface. Individual files from the Airtime storage server can then be added to either of Mixxx's live players with a right-click on the filename, or by using the appropriate hardware buttons on a control surface. Therefore it is possible to manage the station's storage archive remotely and collaboratively through Airtime, while using Mixxx as the live playout client in multiple, remote studios.
|
||||
If the filesystem path has been configured correctly, the metadata for the files in the Libretime storage server will be displayed in the main window of the Mixxx interface. Individual files from the Libretime storage server can then be added to either of Mixxx's live players with a right-click on the filename, or by using the appropriate hardware buttons on a control surface. Therefore it is possible to manage the station's storage archive remotely and collaboratively through Libretime, while using Mixxx as the live playout client in multiple, remote studios.
|
||||
|
||||
|
||||
|
||||
The Airtime storage archive can be exported like any other file server share. The method that you implement would depend on the operating system of your desktop client machines, and whether they were on the same local network as the Airtime server, or remote.
|
||||
The Libretime storage archive can be exported like any other file server share. The method that you implement would depend on the operating system of your desktop client machines, and whether they were on the same local network as the Libretime server, or remote.
|
||||
|
||||
For performance and redundancy reasons it is advisable to cache files required for a particular show on the client machine where Mixxx is installed. For example, for a GNU/Linux client machine, a nightly **rsync** download of new media in the archive would guard against network problems at playout time potentially disrupting a broadcast at a remote studio.
|
||||
|
||||
Mixxx users can also record a show, and then upload it through the Airtime web interface on a local or remote server for collaborative or user-generated broadcasts.
|
||||
Mixxx users can also record a show, and then upload it through the Libretime web interface on a local or remote server for collaborative or user-generated broadcasts.
|
||||
|
||||
Streaming from Mixxx into Airtime
|
||||
Streaming from Mixxx into Libretime
|
||||
---------------------------------
|
||||
|
||||
Mixxx 1.9.0 or later includes a live streaming client which, like Airtime, is compatible with the **Icecast** and **SHOUTcast** media servers. This feature can also be used to stream from Mixxx directly into Airtime, using either the **Show Source** or **Master Source**.
|
||||
Mixxx 1.9.0 or later includes a live streaming client which, like Libretime, is compatible with the **Icecast** and **SHOUTcast** media servers. This feature can also be used to stream from Mixxx directly into Libretime, using either the **Show Source** or **Master Source**.
|
||||
|
||||
|
||||
|
||||
To configure **Mixxx** for streaming into Airtime, click **Options**, **Preferences**, then **Live Broadcasting** on the main Mixxx menu. For server **Type**, select the default of **Icecast 2**. For **Host**, **Mount**, **Port**, **Login** and **Password**, use the **Input Stream Settings** configured in the Airtime **Streams** page, on Airtime's **System** menu. See the chapter *Stream settings* for remote input connection details.
|
||||
|
||||
Airtime skins for Mixxx
|
||||
-----------------------
|
||||
|
||||
Airtime-themed skins for Mixxx, designed with broadcast users in mind, are available for download from <https://github.com/Airtime/MixxxSkins>
|
||||
|
||||
These skins provide a simplified interface for live broadcasting which do away with EQ, flange effect, looping and other features required by dance music DJs. Instead, the emphasis is on a clear and uncluttered interface which does not require large mouse movements to operate the most important controls. There are versions available both with and without pitch/tempo controls for beat matching.
|
||||
|
||||
|
||||
|
||||
After downloading one of the skins, extract the zip file and copy it to the *skins* directory on the computer where Mixxx is installed. For example, on Debian or Ubuntu:
|
||||
|
||||
unzip Airtime1280x1024_skin_for_Mixxx.zip
|
||||
sudo cp -r Airtime1280x1024 /usr/share/mixxx/skins/
|
||||
|
||||
Then, start Mixxx and select the Airtime skin by clicking **Options**, **Preferences**, then **Interface** in the Mixxx main menu.
|
||||
|
||||
|
||||
To configure **Mixxx** for streaming into Libretime, click **Options**, **Preferences**, then **Live Broadcasting** on the main Mixxx menu. For server **Type**, select the default of **Icecast 2**. For **Host**, **Mount**, **Port**, **Login** and **Password**, use the **Input Stream Settings** configured in the Libretime **Streams** page, on Libretime's **System** menu. See the chapter *Stream settings* for remote input connection details.
|
||||
|
|
|
|||
|
|
@ -1,51 +1,4 @@
|
|||
Airtime's media library is inside the */srv/airtime/stor/* folder on your server, by default. In **Media folders** on the **System** menu, you can change this default location, or add extra folders to be watched by Airtime.
|
||||
Libretime's media library is inside the */srv/airtime/stor/* folder on your server, by default.
|
||||
|
||||
|
||||
Edits to your stored media files are noticed by Libretime. If you edit any file known to the database and change its duration, Libretime will automatically adjust the duration of playlists, smart blocks and shows that the file is included in. If you edit the metadata tags of a file, Libretime will automatically update the database with the new information. This may invalidate existing playlists or smart blocks that the file is part of. For example, if you use 'genre' as a search criteria to create a playlist or smart block and then edit the 'genre' tag for a file, that file may no longer match the original search criteria. A playlist or static smart block would still have an entry for the original file if either of these items was created before you modified the tag of the file in question.
|
||||
|
||||
If you specify a network drive as a media folder and that network becomes disconnected for any reason, Airtime's **media monitor** will flag the files as 'missing' in its database until the drive is reconnected. If those files are still missing at the time of the show, the broadcast output could be silenced.
|
||||
|
||||
For the same reason, if a removable drive (such as a USB memory stick or MP3 player) is specified as a watched folder, that drive has to be present and powered on until the corresponding show time, so that the Airtime playout engine can download the files needed for the show. If your station staff use removable drives to store media files, it is safer to use the **Add media** page of the Airtime administration interface or the **airtime-import copy** command to copy the files to the main storage server. See the chapters *Add media* and *Using the airtime-import script* for more details.
|
||||
|
||||
The metadata for new media files you add to the *organize* folder or a watched folder will be automatically imported into the Airtime database. The *organize* or watched folders can be exported to computers on the local network. This would enable dragging and dropping of media uploads using the file managers on the desktop computers at your studio.
|
||||
|
||||
|
||||
|
||||
A file dropped into the *organize* folder will appear to vanish as the metadata is read, and the file is moved to the correct location under the *imported* directory, according to its creator and title. This means you can find files for download and editing using a file browser connected to your server, as well as in the **Search** table in the **Library**. This location could be under a filesystem path such as */srv/airtime/stor/imported/Beck/Midnite Vultures/* in the screenshot below.
|
||||
|
||||
|
||||
|
||||
If a media file is corrupted and cannot be played by Liquidsoap, Airtime will move the file to the *problem\_files* folder in the storage archive, and its metadata will not be added to the database. This feature ensures that all files are tested for encoding errors or upload corruption before playout time.
|
||||
|
||||
Files in watched folders are not moved into the main Airtime storage folder. However, just like in the main storage, files deleted from a watched folder will be automatically flagged as missing in any show that they are part of.
|
||||
|
||||
Edits to your stored and watched media files are noticed by Airtime. If you edit any file known to the database and change its duration, Airtime will automatically adjust the duration of playlists, smart blocks and shows that the file is included in. If you edit the metadata tags of a file, Airtime will automatically update the database with the new information. This may invalidate existing playlists or smart blocks that the file is part of. For example, if you use 'genre' as a search criteria to create a playlist or smart block and then edit the 'genre' tag for a file, that file may no longer match the original search criteria. A playlist or static smart block would still have an entry for the original file if either of these items was created before you modified the tag of the file in question.
|
||||
|
||||
Changing the storage folder
|
||||
---------------------------
|
||||
|
||||
To change Airtime's storage folder, click the upper **choose folder** button. In the pop-up window that opens, double-click on the folder names to select the folder that you require. Then click the **Open** button to open that folder.
|
||||
|
||||
|
||||
|
||||
Back on the **Manage Media Folders** page, click the **Set** button to change the storage folder. Airtime will ask if you are sure about this action. Click the **OK** button to confirm your choice.
|
||||
|
||||
|
||||
|
||||
The **Manage Media Folders** page will now display the new storage location.
|
||||
|
||||
|
||||
|
||||
The storage folder cannot be changed while a file import is in progress. If you attempt to do this, an error message will be displayed.
|
||||
|
||||
|
||||
|
||||
Watching a folder
|
||||
-----------------
|
||||
|
||||
Under **Watched Folders**, click the lower **choose folder** button, open the folder you require, and then click the **Add** button. You can add as many watched folders as you require.
|
||||
|
||||
|
||||
|
||||
To remove a watched folder, click the small **x** on the right side of its row in the list. Again, you will be asked to confirm if you are sure about the action.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
The Now Playing page provides a view of the content your station will play out, or has already played out, which defaults to showing the 24 hours ahead. This page also enables you to make last-minute changes to running shows.
|
||||
|
||||
If you've only just installed Airtime, there might not be any content shown yet. Click the calendar and clock icons above the table to change the date and time range, then click the **Find Shows** button (with the magnifying glass icon) to the right.
|
||||
If you've only just installed Libretime, there might not be any content shown yet. Click the calendar and clock icons above the table to change the date and time range, then click the **Find Shows** button (with the magnifying glass icon) to the right.
|
||||
|
||||
|
||||
|
||||
|
|
@ -35,18 +35,18 @@ To cancel the current show completely, click the red button to the right again.
|
|||
|
||||
|
||||
|
||||
Items which are no longer available have an exclamation mark icon in the second column. This may happen for media files which were part of previous shows, and were removed from Airtime's library (main storage or watched folders) subsequently. Items which are included in forthcoming shows cannot be removed from the Library via the Airtime interface.
|
||||
Items which are no longer available have an exclamation mark icon in the second column. This may happen for media files which were part of previous shows, and were removed from Libretime's library (main storage or watched folders) subsequently. Items which are included in forthcoming shows cannot be removed from the Library via the Libretime interface.
|
||||
|
||||
|
||||
|
||||
Advanced and simple library searches
|
||||
------------------------------------
|
||||
|
||||
In the top left corner of the page is an **Add / Remove Content** button which enables you to open Airtime's library.
|
||||
In the top left corner of the page is an **Add / Remove Content** button which enables you to open Libretime's library.
|
||||
|
||||
|
||||
|
||||
In the library table which opens, the upper section is for the **Advanced Search Options**, which enable you to search within individual fields of the database such as **Title** or **Creator**. Like an Internet search engine, you do not have to type in the correct upper or lower case, press the **Enter** key, or even type the whole of the search term before matches from the Airtime library are displayed.
|
||||
In the library table which opens, the upper section is for the **Advanced Search Options**, which enable you to search within individual fields of the database such as **Title** or **Creator**. Like an Internet search engine, you do not have to type in the correct upper or lower case, press the **Enter** key, or even type the whole of the search term before matches from the Libretime library are displayed.
|
||||
|
||||
<img src="static/Screenshot574-Advanced_search.png" alt="Advanced search options" width="740" />
|
||||
|
||||
|
|
@ -68,13 +68,13 @@ Use the drop-down menu at the top of the search results to display **Files**, **
|
|||
|
||||
|
||||
|
||||
Click the Advanced Search Options link to collapse that area. Beneath the collapsed link is the **Simple Search** field, with a magnifying glass icon, which enables the selection of items based on any tag metadata stored in the Airtime database, whether that metadata column is currently displayed in the table or not. For example, to search for all items between four and five minutes duration, enter *00:04* into the simple search field (for 00 hours and 04 minutes).
|
||||
Click the Advanced Search Options link to collapse that area. Beneath the collapsed link is the **Simple Search** field, with a magnifying glass icon, which enables the selection of items based on any tag metadata stored in the Libretime database, whether that metadata column is currently displayed in the table or not. For example, to search for all items between four and five minutes duration, enter *00:04* into the simple search field (for 00 hours and 04 minutes).
|
||||
|
||||
|
||||
|
||||
If your jingles are tagged with *Jingle* in the **Genre** or other fields, you can very easily find them by entering *jingle* into the simple search field. The same technique can be used to find advertising and promotional files. (See the chapter *Preparing media for ingest* for tips on batch tagging files with metadata). Unlike advanced searches, simple searches use 'or' logic for multiple search terms, so a simple search for *jingle ident* will return items matching either keyword.
|
||||
|
||||
Clicking on an item in the library table opens a pop-up menu which enables you to audition the item, or remove it from the Airtime library. Media types which cannot be auditioned directly in a web browser, such as FLAC, have a lock icon instead of a loudspeaker icon, but these files can be downloaded to your local computer for audition instead. The **Delete** option should be used with caution, because this action cannot be undone. For media files, you can also **Edit Metadata** stored for the file using this menu.
|
||||
Clicking on an item in the library table opens a pop-up menu which enables you to audition the item, or remove it from the Libretime library. Media types which cannot be auditioned directly in a web browser, such as FLAC, have a lock icon instead of a loudspeaker icon, but these files can be downloaded to your local computer for audition instead. The **Delete** option should be used with caution, because this action cannot be undone. For media files, you can also **Edit Metadata** stored for the file using this menu.
|
||||
|
||||
|
||||
|
||||
|
|
@ -87,11 +87,11 @@ Adding content to a running show
|
|||
|
||||
After you have found the items that you want using the search tools, you can then drag and drop them from the library table on the left side of the page into the shows on the right side, including the current playing show.
|
||||
|
||||
If the current show has nothing playing out at the time, the new item will begin playing immediately. This manual triggering of playout can be used as a live assist technique, in which the Airtime server's soundcard output is mixed with other sources such as microphones or telephone hybrids on its way to a transmitter, or a separate stream encoder. For instance, a live show's host may not wish to cut off a studio discussion in order to play music at a fixed time.
|
||||
If the current show has nothing playing out at the time, the new item will begin playing immediately. This manual triggering of playout can be used as a live assist technique, in which the Libretime server's soundcard output is mixed with other sources such as microphones or telephone hybrids on its way to a transmitter, or a separate stream encoder. For instance, a live show's host may not wish to cut off a studio discussion in order to play music at a fixed time.
|
||||
|
||||
|
||||
|
||||
You can also select multiple items using the **Select** menu button, just beneath the simple search field, which has the options to **Select this page** of search results, **Deselect this page** and **Deselect all**. Alternatively, use the checkboxes on the left side of the library table to select specific items. Then drag one of the items into the show to add all of the selected items, or click the **Add to selected show** button, which has a plus icon. If you wish, you can also use the **Trashcan** button to permanently remove items from Airtime's library. Only *admin* users have permission to delete all items.
|
||||
You can also select multiple items using the **Select** menu button, just beneath the simple search field, which has the options to **Select this page** of search results, **Deselect this page** and **Deselect all**. Alternatively, use the checkboxes on the left side of the library table to select specific items. Then drag one of the items into the show to add all of the selected items, or click the **Add to selected show** button, which has a plus icon. If you wish, you can also use the **Trashcan** button to permanently remove items from Libretime's library. Only *admin* users have permission to delete all items.
|
||||
|
||||
To insert checkbox selected items at a specific time in the show schedule, click one of the grey and white triangle icons on the left side of the schedule table, which will change to red and white. A red horizontal line will be shown at the insertion point. Then click the **Add to selected show** button in the library table.
|
||||
|
||||
|
|
@ -105,6 +105,6 @@ Another way to create an insertion point is to click an item in the show table,
|
|||
|
||||
Multiple insertion points can be enabled, so that the same item is inserted into the schedule at different times. For example, you may wish to play a news report every hour, or a station ident after every five music files.
|
||||
|
||||
A live show set for recording from the Airtime server's sound card is displayed with a red dot icon in the first column. It would not contain any files or playlists, smart blocks or web streams.
|
||||
A live show set for recording from the Libretime server's sound card is displayed with a red dot icon in the first column. It would not contain any files or playlists, smart blocks or web streams.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,34 +1,13 @@
|
|||
On the <span style="font-weight: bold;">Settings</span> menu, click **General** to set your **Station Name**. This text is shown in your web browser's title bar when your station staff are logged into Airtime, and optionally in stream metadata. You can also set a **Station Description** and **Station Logo** here.
|
||||
You can enable live, read-only access to the Airtime schedule calendar for your station's public website with the **Allow Remote Websites to Access "Schedule" Info?** option, if you wish. (There is more about this feature in the *Exporting the schedule* chapter, in the *Advanced Configuration* section of this book).
|
||||
On the <span style="font-weight: bold;">Settings</span> menu, click **General** to set your **Station Name**. This text is shown in your web browser's title bar when your station staff are logged into Libretime, and optionally in stream metadata. You can also set a **Station Description** and **Station Logo** here.
|
||||
You can enable live, read-only access to the Libretime schedule calendar for your station's public website with the **Allow Remote Websites to Access "Schedule" Info?** option, if you wish. (There is more about this feature in the *Exporting the schedule* chapter, in the *Advanced Configuration* section of this book).
|
||||
|
||||
Initially, the **Default Fade In** and **Default Fade Out** times for automated fades are set to half a second, and the **Default Crossfade Duration** is set to zero seconds. Custom fade and crossfade times can be set for adjacent items in a playlist or static smart block. See the chapter *Library* for details.
|
||||
|
||||
The **Default Interface Language** drop-down menu sets the default localization for your Airtime instance, and the **Station Timezone** drop-down menu can be used to display local time at your station. Airtime stores show times internally in UTC format (similar to *Greenwich Mean Time*), but displays local time for the convenience of your station staff. You can also set the day of the week that you wish to start your station's weekly schedule on, which defaults to Sunday. Then click the **Save** button.
|
||||
The **Default Interface Language** drop-down menu sets the default localization for your Libretime instance, and the **Station Timezone** drop-down menu can be used to display local time at your station. Libretime stores show times internally in UTC format (similar to *Greenwich Mean Time*), but displays local time for the convenience of your station staff. You can also set the day of the week that you wish to start your station's weekly schedule on, which defaults to Sunday. Then click the **Save** button.
|
||||
|
||||
|
||||
|
||||
Individual Airtime users can choose another interface localization when they log in, or set personal preferences for localization and time zone by clicking their username on the right side of the menu bar.
|
||||
Individual Libretime users can choose another interface localization when they log in, or set personal preferences for localization and time zone by clicking their username on the right side of the menu bar.
|
||||
|
||||
|
||||
|
||||
Email / Mail Server Settings
|
||||
----------------------------
|
||||
|
||||
The **Enable System Emails (Password Reset)** box is not checked by default, because although enabling staff users to retrieve their lost password for themselves may be convenient, this option does have security implications. If the email account of the staff user is compromised, an attacker could very easily gain access to your Airtime server by clicking the **Reset Password** link on the login page.
|
||||
|
||||
If you wish to enable the password reset option, your Airtime server can have an SMTP mail program installed. (See the chapter *Preparing the server* for details). Alternatively, you can check the box **Configure Mail Server** and specify the details of an external SMTP server, which would usually require authentication if it is outside of your local network.
|
||||
|
||||
Whether SMTP runs on the same server as Airtime or on another server, you should enter a valid email address into the **Reset Password 'From' Email** field to help ensure emails are delivered correctly. Then click the **Save** button.
|
||||
|
||||
|
||||
|
||||
SoundCloud Settings
|
||||
-------------------
|
||||
|
||||
If your station has a SoundCloud account (on [http://soundcloud.com](http://soundcloud.com/ "SoundCloud")), you may wish to upload files and show recordings to this service, in order to broaden distribution and balance the bandwidth load with your own servers. Click the small black triangle next to **SoundCloud Settings** to show the options available. Check the **Enable Soundcloud Upload** box, then optionally check the **Automatically Upload Recorded Shows** box. You will also need to enter your SoundCloud login email address and password, and the tag metadata that SoundCloud will use to categorize your show recordings.
|
||||
|
||||
Check the box **Automatically Mark Files "Downloadable" on SoundCloud** if you wish to enable this option. **** You can also set a default genre, track type and copyright license here, including public domain, all rights reserved, or one of the *Creative Commons* licenses (see [http://creativecommons.org](http://creativecommons.org/ "Creative Commons")). Then click the **Save** button again.
|
||||
|
||||
|
||||
|
||||
Please note that like most online distribution services, SoundCloud terms of service require you to have copyright in, or permission for Internet distribution from the copyright holder of, any media that you upload. Commercially released music files uploaded to SoundCloud are likely to be automatically removed from your station's SoundCloud page.
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
Before uploading media to an Airtime server, there are a number of factors which should be considered. Getting your ingest workflow right will save you a lot of time later.
|
||||
Before uploading media to an Libretime server, there are a number of factors which should be considered. Getting your ingest workflow right will save you a lot of time later.
|
||||
|
||||
Metadata quality
|
||||
----------------
|
||||
|
||||
Airtime automatically imports any metadata that is in the files' ID3 tags. If these tags are incorrect or are missing information, you will have to either edit the metadata manually, or suffer the consequences. For example, if the files have creator or genre metadata missing, it will be impossible to search for, create playlists or generate smart blocks according to these criteria until you add it.
|
||||
Libretime automatically imports any metadata that is in the files' ID3 tags. If these tags are incorrect or are missing information, you will have to either edit the metadata manually, or suffer the consequences. For example, if the files have creator or genre metadata missing, it will be impossible to search for, create playlists or generate smart blocks according to these criteria until you add it.
|
||||
|
||||
There are a number of programs available which can be used to correct mistakes or incomplete information in ID3 tags. On GNU/Linux, the program **Ex Falso** ([http://code.google.com/p/quodlibet/](http://code.google.com/p/quodlibet/) "http://sourceforge.net/projects/dr14tmeter/")) can be useful for batch setting and editing ID3 tags before importing files into your Airtime server. On a Debian or Ubuntu desktop machine, you can install this program with the command:
|
||||
There are a number of programs available which can be used to correct mistakes or incomplete information in ID3 tags. On GNU/Linux, the program **Ex Falso** ([http://code.google.com/p/quodlibet/](http://code.google.com/p/quodlibet/) "http://sourceforge.net/projects/dr14tmeter/")) can be useful for batch setting and editing ID3 tags before importing files into your Libretime server. On a Debian or Ubuntu desktop machine, you can install this program with the command:
|
||||
|
||||
sudo apt-get install exfalso
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ or from the desktop menu. The *Tags From Path* feature of this program is a part
|
|||
Metadata in legacy character sets
|
||||
---------------------------------
|
||||
|
||||
Airtime expects file tag metadata to be stored in the international *UTF-8* character set. Programs such as **Ex Falso** (described above) encode metadata in UTF-8 by default. If you have an archive of files encoded with metadata in a legacy character set, such as the Cyrillic encoding *Windows-1251*, you should convert these files before import.
|
||||
Libretime expects file tag metadata to be stored in the international *UTF-8* character set. Programs such as **Ex Falso** (described above) encode metadata in UTF-8 by default. If you have an archive of files encoded with metadata in a legacy character set, such as the Cyrillic encoding *Windows-1251*, you should convert these files before import.
|
||||
|
||||
The program **mid3iconv** (part of the **python-mutagen** package in Debian and Ubuntu) can be used to batch convert the metadata character set of files on the command line. You can install **python-mutagen** with the command:
|
||||
|
||||
|
|
@ -55,15 +55,15 @@ CP1256: Arabic
|
|||
Audio loudness
|
||||
--------------
|
||||
|
||||
On file ingest, Airtime analyzes each Ogg Vorbis, MP3, AAC or FLAC file's loudness, and stores a *ReplayGain* value for that file in its database. At playout time, the ReplayGain value is provided to Liquidsoap so that gain can be automatically adjusted to provide an average output of -14 dBFS loudness (14 decibels below full scale). See <http://www.replaygain.org/> for more details of ReplayGain.
|
||||
On file ingest, Libretime analyzes each Ogg Vorbis, MP3, AAC or FLAC file's loudness, and stores a *ReplayGain* value for that file in its database. At playout time, the ReplayGain value is provided to Liquidsoap so that gain can be automatically adjusted to provide an average output of -14 dBFS loudness (14 decibels below full scale). See <http://www.replaygain.org/> for more details of ReplayGain.
|
||||
|
||||
Because of this automatic gain adjustment, any files with average loudness higher than -14 dBFS will not sound louder than quieter files at playout time, but the lower crest factor in the louder files (their relatively low peak-to-average ratio) may be apparent in the output, making those files sound less dynamic. This may be an issue for contemporary popular music, which can average at -9 dBFS or louder before ReplayGain adjustment. (See <http://www.soundonsound.com/sos/sep11/articles/loudness.htm> for a detailed analysis of the problem).
|
||||
|
||||
Your station's producers should therefore aim for 14dB between peak and average loudness to maintain the crest factor of their prepared material (also known as *DR14* on some dynamic range meters, such as the command-line DR14 T.meter available from <http://sourceforge.net/projects/dr14tmeter/>). If the producers are working to a different loudness standard, the ReplayGain modifier in Airtime's Stream Settings page can be adjusted to suit their material.
|
||||
Your station's producers should therefore aim for 14dB between peak and average loudness to maintain the crest factor of their prepared material (also known as *DR14* on some dynamic range meters, such as the command-line DR14 T.meter available from <http://sourceforge.net/projects/dr14tmeter/>). If the producers are working to a different loudness standard, the ReplayGain modifier in Libretime's Stream Settings page can be adjusted to suit their material.
|
||||
|
||||
Large transient peaks in otherwise quiet files should be avoided, to guard against the need for peak limiting when ReplayGain is applied to those quieter files.
|
||||
|
||||
The **vorbisgain** command-line tool, available in the **vorbisgain** package in Debian/Ubuntu, can be used to indicate the ReplayGain of an individual Ogg Vorbis file before ingest into Airtime. (A similar tool for MP3 files is available in the **mp3gain** package in Debian/Ubuntu).
|
||||
The **vorbisgain** command-line tool, available in the **vorbisgain** package in Debian/Ubuntu, can be used to indicate the ReplayGain of an individual Ogg Vorbis file before ingest into Libretime. (A similar tool for MP3 files is available in the **mp3gain** package in Debian/Ubuntu).
|
||||
|
||||
Here is an example of a very quiet file where the use of ReplayGain would make the output more than 17dB louder:
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ In the output from vorbisgain, *Peak* is the maximum sample value of the file be
|
|||
Silence in media files
|
||||
----------------------
|
||||
|
||||
Before importing media, it is good practice to check for any silent sections in the media files. While Airtime compensates for leading and trailing silence with the use of automatic cue-in and cue-out points****, it may be preferable to trim these files to the intended length before upload. This is because media in the Airtime library could potentially be re-used in many different systems. **Audacity** is a cross-platform editor suitable for the task of trimming audio files, available from [http://audacity.sourceforge.net/](http://audacity.sourceforge.net "http://sourceforge.net/projects/dr14tmeter/")
|
||||
Before importing media, it is good practice to check for any silent sections in the media files. While Libretime compensates for leading and trailing silence with the use of automatic cue-in and cue-out points****, it may be preferable to trim these files to the intended length before upload. This is because media in the Libretime library could potentially be re-used in many different systems. **Audacity** is a cross-platform editor suitable for the task of trimming audio files, available from [http://audacity.sourceforge.net/](http://audacity.sourceforge.net "http://sourceforge.net/projects/dr14tmeter/")
|
||||
|
||||
Very quiet introductions or over-long fades can also lead to apparent gaps in your broadcast playout. Some audio CDs feature a 'hidden track' at the end, which in fact uses a long period of silence within the final track, rather than an actual separate track on the disc. This means that CD encoding programs will often encode both the hidden material and the silence in the media file. For example, the track *Debra* from the CD *Midnite Vultures* by *Beck* includes hidden material preceded by seven minutes of silence, as shown in the screen shot from Audacity below.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ The recommended Libretime server platform is Ubuntu 16.04 LTS (Xenial Xerus).
|
|||
|
||||
The server should have at least a 1GHz processor and 1GB of RAM, preferably 2GB RAM or more. If you are using a desktop environment and web browser directly on the server you should install at least 2GB RAM, to avoid swapping to disk.
|
||||
|
||||
The LibreTime installation does not use much disk space, but you should allow plenty of storage capacity for the Airtime library. A hot-swap RAID array is recommended for media storage, in case of disk failure. You should also consider a UPS or other battery-powered system to offer some protection against short-term power failures.
|
||||
The LibreTime installation does not use much disk space, but you should allow plenty of storage capacity for the Libretime library. A hot-swap RAID array is recommended for media storage, in case of disk failure. You should also consider a UPS or other battery-powered system to offer some protection against short-term power failures.
|
||||
|
||||
LibreTime depends on infrastructure and services that need to be configured properly for it to run smoothly. This chapter will go through the individual parts of a LibreTime install and help you assess how you need to manage them.
|
||||
|
||||
|
|
@ -79,15 +79,15 @@ See these links for more information:
|
|||
|
||||
***Beware, Here be dragons!***
|
||||
|
||||
The following instructions have been taken verbatim from the Airtime docs and
|
||||
The following instructions have been taken verbatim from the Libretime docs and
|
||||
not been brought up to date.
|
||||
|
||||
Sound cards
|
||||
-----------
|
||||
|
||||
If your Airtime machine will only be used to stream directly to an **Icecast** or **SHOUTcast** streaming media server, you do not require a sound card to be installed on the Airtime server side. This option is suitable for Airtime installations at your ISP's data centre, remote from any transmitter. However, you will not be able to take advantage of Airtime's live show recording feature (yet).
|
||||
If your Libretime machine will only be used to stream directly to an **Icecast** or **SHOUTcast** streaming media server, you do not require a sound card to be installed on the Libretime server side. This option is suitable for Libretime installations at your ISP's data centre, remote from any transmitter. However, you will not be able to take advantage of Libretime's live show recording feature (yet).
|
||||
|
||||
If you intend that your Airtime server will have a direct audio output to a broadcast transmitter or a separate stream encoder, your server machine must have a sound card supported by an **ALSA** driver. Almost all standard sound cards have ALSA drivers built into the Linux kernel, which do not need to be installed separately. If in doubt about driver support for your sound card, check the ALSA support matrix at: <http://www.alsa-project.org/main/index.php/Matrix:Main>
|
||||
If you intend that your Libretime server will have a direct audio output to a broadcast transmitter or a separate stream encoder, your server machine must have a sound card supported by an **ALSA** driver. Almost all standard sound cards have ALSA drivers built into the Linux kernel, which do not need to be installed separately. If in doubt about driver support for your sound card, check the ALSA support matrix at: <http://www.alsa-project.org/main/index.php/Matrix:Main>
|
||||
|
||||
USB audio device index
|
||||
----------------------
|
||||
|
|
@ -113,7 +113,7 @@ Save the file with **Ctrl+O** and close **nano** with **Ctrl+X**. Then remove an
|
|||
Subdevices: 1/1
|
||||
Subdevice #0: subdevice #0
|
||||
|
||||
When using a USB sound card with ALSA, some how-to documents advocate setting the *nrpacks=1* option, but this is not recommended for Airtime because it can increase CPU load significantly.
|
||||
When using a USB sound card with ALSA, some how-to documents advocate setting the *nrpacks=1* option, but this is not recommended for Libretime because it can increase CPU load significantly.
|
||||
|
||||
Intel HDA mixer labels
|
||||
----------------------
|
||||
|
|
@ -147,7 +147,7 @@ Save the file with **Ctrl+O** and close **nano** with **Ctrl+X**. Then reboot th
|
|||
Disable desktop and other sounds
|
||||
--------------------------------
|
||||
|
||||
If you are installing Airtime on a desktop computer, make sure you disable or remove any programs that could send unintended audio to a sound card you are using for broadcast output. This includes alert sounds which play when the computer is ready for use, or when a user logs in. On Ubuntu, these sounds are configured using *System -> Preferences -> Sound* on the main desktop menu. (This configuration tool only works when the PulseAudio sound server is installed).
|
||||
If you are installing Libretime on a desktop computer, make sure you disable or remove any programs that could send unintended audio to a sound card you are using for broadcast output. This includes alert sounds which play when the computer is ready for use, or when a user logs in. On Ubuntu, these sounds are configured using *System -> Preferences -> Sound* on the main desktop menu. (This configuration tool only works when the PulseAudio sound server is installed).
|
||||
|
||||
You may prefer to remove all system sound files from the computer, in case they could be played unintentionally via the sound card. For example, on Ubuntu you may wish to remove the **ubuntu-sounds** package, with the following command:
|
||||
|
||||
|
|
@ -156,13 +156,13 @@ You may prefer to remove all system sound files from the computer, in case they
|
|||
PulseAudio
|
||||
----------
|
||||
|
||||
The PulseAudio sound server is not recommended for Airtime sound card output, but is installed by default on Ubuntu. To remove PulseAudio from an Ubuntu machine, type the following command:
|
||||
The PulseAudio sound server is not recommended for Libretime sound card output, but is installed by default on Ubuntu. To remove PulseAudio from an Ubuntu machine, type the following command:
|
||||
|
||||
sudo apt-get purge pulseaudio
|
||||
|
||||
Removing the **pulseaudio** package on a desktop Ubuntu machine may force the removal of the **ubuntu-desktop** metapackage. However, this metapackage is only installed on the system for managing upgrades; removing it does not remove the entire desktop.
|
||||
|
||||
After removing PulseAudio, if your Airtime machine has a desktop, you can install a mixer applet which can control the ALSA soundcard driver directly, such as **gnome-alsamixer**:
|
||||
After removing PulseAudio, if your Libretime machine has a desktop, you can install a mixer applet which can control the ALSA soundcard driver directly, such as **gnome-alsamixer**:
|
||||
|
||||
sudo apt-get install gnome-alsamixer
|
||||
|
||||
|
|
@ -177,13 +177,13 @@ This program should already be installed on an Ubuntu or Debian machine with a s
|
|||
The PHP cache
|
||||
-------------
|
||||
|
||||
This dependency, introduced in Airtime 2.5.0, can improve the responsiveness of the Airtime administration interface and reduce server load. Various PHP cache software is available, but the current cache software required by Airtime is **APC** (<http://pecl.php.net/package/APC>). You should uninstall or disable any other PHP cache that may be present on the server, such as **XCache**, before installing Airtime and APC. This is because having multiple caches enabled can cause problems for PHP.
|
||||
This dependency, introduced in Libretime 2.5.0, can improve the responsiveness of the Libretime administration interface and reduce server load. Various PHP cache software is available, but the current cache software required by Libretime is **APC** (<http://pecl.php.net/package/APC>). You should uninstall or disable any other PHP cache that may be present on the server, such as **XCache**, before installing Libretime and APC. This is because having multiple caches enabled can cause problems for PHP.
|
||||
|
||||
You can remove the XCache package **php5-xcache** from a Debian or Ubuntu server with the command:
|
||||
|
||||
sudo apt-get remove php5-xcache
|
||||
|
||||
APC is available in Debian or Ubuntu as the **php-apc** package. If you already have Apache installed on the server you are going to use for Airtime, you can install APC and get it working with the following commands:
|
||||
APC is available in Debian or Ubuntu as the **php-apc** package. If you already have Apache installed on the server you are going to use for Libretime, you can install APC and get it working with the following commands:
|
||||
|
||||
sudo apt-get install php-apc
|
||||
sudo invoke-rc.d apache2 restart
|
||||
|
|
@ -197,9 +197,9 @@ You should set an admin password for the *apc* user on line 42 of the file, such
|
|||
|
||||
defaults('ADMIN_PASSWORD','mynewpassword');
|
||||
|
||||
Save the *apc.php* file with **Ctrl+O** and close it with **Ctrl+X**. Then open a web browser at the *apc.php* page of your Airtime server, such as:
|
||||
Save the *apc.php* file with **Ctrl+O** and close it with **Ctrl+X**. Then open a web browser at the *apc.php* page of your Libretime server, such as:
|
||||
|
||||
http://airtime.example.com/apc.php
|
||||
http://libretime.example.com/apc.php
|
||||
|
||||
You will then be able to confirm that APC is working, and view some statistics for the cache.
|
||||
|
||||
|
|
@ -208,16 +208,16 @@ You will then be able to confirm that APC is working, and view some statistics f
|
|||
Remove webmin, if installed
|
||||
---------------------------
|
||||
|
||||
The **webmin** control panel (<http://www.webmin.com>) has been known to remove Apache and PHP packages on Debian and Ubuntu systems, which can cause the Airtime package to be removed in turn. This problem is easily reversed by re-installation of the affected packages, but it has the potential to disrupt your broadcast playout from Airtime. Webmin is not likely to be installed on your server unless your system administrator has installed it manually. This is because webmin was removed from official Debian and Ubuntu package repositories some years ago.
|
||||
The **webmin** control panel (<http://www.webmin.com>) has been known to remove Apache and PHP packages on Debian and Ubuntu systems, which can cause the Libretime package to be removed in turn. This problem is easily reversed by re-installation of the affected packages, but it has the potential to disrupt your broadcast playout from Libretime. Webmin is not likely to be installed on your server unless your system administrator has installed it manually. This is because webmin was removed from official Debian and Ubuntu package repositories some years ago.
|
||||
|
||||
RabbitMQ on Debian squeeze
|
||||
--------------------------
|
||||
|
||||
In Debian 6.0 'squeeze' the **rabbitmq-server** daemon does not start automatically after a reboot. This should be fixed before installing Airtime, to prevent problems at playout time. If the rabbitmq-server package was installed before the last reboot, you will need to run:
|
||||
In Debian 6.0 'squeeze' the **rabbitmq-server** daemon does not start automatically after a reboot. This should be fixed before installing Libretime, to prevent problems at playout time. If the rabbitmq-server package was installed before the last reboot, you will need to run:
|
||||
|
||||
invoke-rc.d rabbitmq-server start
|
||||
|
||||
as the root user before the installation of Airtime. If it is not already installed, run the following command as root:
|
||||
as the root user before the installation of Libretime. If it is not already installed, run the following command as root:
|
||||
|
||||
apt-get install rabbitmq-server
|
||||
|
||||
|
|
@ -234,12 +234,3 @@ and then run the command (as root):
|
|||
|
||||
This should make sure that **rabbitmq-server** starts after the next reboot.
|
||||
|
||||
libav on Debian squeeze and .m4a files
|
||||
--------------------------------------
|
||||
|
||||
The version of libav shipped with Debian 6.0 'squeeze' is known to cause problems when Airtime analyses .m4a files containing the AAC codec for silence, using Silan (see <https://github.com/x42/silan/issues/2>). It is recommended that Debian servers are upgraded to the current stable 'wheezy' 7.2 release. As a short-term measure, updated libav packages from the squeeze-backports repository can be used to work around this problem. This work-around is only required if you do not wish to upgrade to 'wheezy' yet, but have AAC codec .m4a files in your Airtime library.
|
||||
|
||||
Mail server
|
||||
-----------
|
||||
|
||||
If you wish Airtime to be able to send password reminder emails to your staff users, the server can have an SMTP program installed, such as the **postfix** package in Debian or Ubuntu. For configuration options, refer to the documentation for your mail server of choice. Alternatively, you can specify an external SMTP server in the **Preferences** page on Airtime's **System** menu.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
If you have an Icecast server, you can put a link to the Icecast status page (by default at port 8000) on your station's homepage, to provide an overview of available streams. See the chapter *Interface customization* for tips on theming the Icecast status page. You can also use Now Playing widgets (see the chapter *Exporting the schedule*) or HTML5 stream players (see the chapter *Stream player for your website*) to help grow your audience.
|
||||
|
||||
On an Icecast server, you can uncomment the *<directory>* section in the */etc/icecast2/icecast.xml* file to have your station automatically listed on the Icecast directory website <http://dir.xiph.org> which could help you pick up more listeners.
|
||||
On an Icecast server, you can uncomment the *<directory>* section in the */etc/icecast2/icecast.xml* file to have your station automatically listed on the Icecast directory website <http://dir.xiph.org> which could help you pick up more listeners.
|
||||
|
||||
<!-- Uncomment this if you want directory listings -->
|
||||
|
||||
|
|
@ -9,7 +9,7 @@ On an Icecast server, you can uncomment the *<directory>* section in the *
|
|||
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
|
||||
</directory>
|
||||
|
||||
The Indymedia stream directory at <http://radio.indymedia.org/en/yp> links to grassroots independent radio projects around the world. You can add your station to their list with an additional *<directory>* section, as follows:
|
||||
The Indymedia stream directory at <http://radio.indymedia.org/en/yp> links to grassroots independent radio projects around the world. You can add your station to their list with an additional *<directory>* section, as follows:
|
||||
|
||||
<directory>
|
||||
<yp-url-timeout>15</yp-url-timeout>
|
||||
|
|
@ -25,7 +25,7 @@ Another stream directory service is provided by the Liquidsoap Flows! site <http
|
|||
genre="Rock",
|
||||
user="",
|
||||
password="",
|
||||
streams=[("ogg/128k","http://streaming.example.com/airtime_128")],
|
||||
streams=[("ogg/128k","http://streaming.example.com/libretime_128")],
|
||||
ourstation)
|
||||
|
||||
For the time being, a stream can be registered on the Liquidsoap Flows! site with any username and password. Authenticated services may be offered in future.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
To increase the security of your server, you can enable encrypted access to the Airtime administration interface, and direct your users towards this more secure login page. The main advantage of using this encryption is that your remote users' login names and passwords are not sent in plain text across the public Internet or untrusted local networks, such as shared Wi-Fi access points.
|
||||
To increase the security of your server, you can enable encrypted access to the Libretime administration interface, and direct your users towards this more secure login page. The main advantage of using this encryption is that your remote users' login names and passwords are not sent in plain text across the public Internet or untrusted local networks, such as shared Wi-Fi access points.
|
||||
|
||||
The padlock icon in a web browser's address bar depends on the browser's recognition of an encryption certificate. Because the users of your Airtime server will often be known to you personally, it is feasible to use a self-signed certificate for this purpose. Alternatively, you can pay a Certificate Authority to sign the certificate for you. Airtime Pro servers are pre-configured with a certificate signed by a Certificate Authority which is automatically recognised by all popular browsers.
|
||||
The padlock icon in a web browser's address bar depends on the browser's recognition of an encryption certificate. Because the users of your Libretime server will often be known to you personally, it is feasible to use a self-signed certificate for this purpose. Alternatively, you can pay a Certificate Authority to sign the certificate for you. Libretime Pro servers are pre-configured with a certificate signed by a Certificate Authority which is automatically recognised by all popular browsers.
|
||||
|
||||
Deploying a self-signed certificate
|
||||
-----------------------------------
|
||||
|
|
@ -9,11 +9,11 @@ The Debian/Ubuntu package *ssl-cert* creates a *snakeoil* certificate and key ba
|
|||
|
||||
sudo apt-get install ssl-cert
|
||||
|
||||
If the hostname of your server does not match the domain name you intend to use with the Airtime virtual host, the user's browser will present an additional security warning. You can set the domain name of the certificate by editing the file */usr/share/ssl-cert/ssleay.cnf* to replace the *@HostName@* variable:
|
||||
If the hostname of your server does not match the domain name you intend to use with the Libretime virtual host, the user's browser will present an additional security warning. You can set the domain name of the certificate by editing the file */usr/share/ssl-cert/ssleay.cnf* to replace the *@HostName@* variable:
|
||||
|
||||
commonName = @HostName@
|
||||
|
||||
with the domain name used by Airtime:
|
||||
with the domain name used by Libretime:
|
||||
|
||||
commonName = airtime.example.com
|
||||
|
||||
|
|
@ -25,13 +25,13 @@ You should enable additional Apache modules for page redirections, custom header
|
|||
|
||||
sudo a2enmod alias headers ssl
|
||||
|
||||
Next, edit the virtual host configuration for your Airtime server to include a stanza for the https:// interface on port 443 and a redirect for logins from port 80:
|
||||
Next, edit the virtual host configuration for your Libretime server to include a stanza for the https:// interface on port 443 and a redirect for logins from port 80:
|
||||
|
||||
sudo nano /etc/apache2/sites-available/airtime-vhost.conf
|
||||
|
||||
Using the following configuration for Apache 2.2 as a guide, replace *airtime.example.com* with the name of your server and *admin@example.com* with your email address. The older SSLv2 and SSLv3 protocols and SSL compression should be disabled, as they are generally believed to be insecure. You may wish to create a *ServerAlias* for users to access the administration interface over https:// if required.
|
||||
|
||||
On port 80, Apache's *alias* module is used to set a *Redirect permanent* for the login page. Optionally, access could be denied to all sites except *localhost* and any other Airtime servers on your network, so that unencrypted communication between Airtime components can continue.
|
||||
On port 80, Apache's *alias* module is used to set a *Redirect permanent* for the login page. Optionally, access could be denied to all sites except *localhost* and any other Libretime servers on your network, so that unencrypted communication between Libretime components can continue.
|
||||
|
||||
<VirtualHost *:443>
|
||||
SSLEngine on
|
||||
|
|
@ -84,7 +84,7 @@ When attempting to log into your server via http:// in future, you should be red
|
|||
Importing a self-signed certificate into the browser
|
||||
----------------------------------------------------
|
||||
|
||||
The first time you access an Airtime server with a self-signed certificate over https:// your browser will block the login page and display a security warning. In **Mozilla Firefox**, you can click **Technical Details** to confirm that the warning is due to the certificate being self-signed before clicking the **Add Exception** button. In **Google Chrome**, the button to click on the security warning page is **Proceed Anyway**.
|
||||
The first time you access an Libretime server with a self-signed certificate over https:// your browser will block the login page and display a security warning. In **Mozilla Firefox**, you can click **Technical Details** to confirm that the warning is due to the certificate being self-signed before clicking the **Add Exception** button. In **Google Chrome**, the button to click on the security warning page is **Proceed Anyway**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ On the next page in Firefox, click the **Get Certificate** button to inspect the
|
|||
|
||||
|
||||
|
||||
If the users of your Airtime server wish to avoid going through these steps, or they do not trust the remote Airtime server to be what it claims to be, it is also possible to import a trusted local copy of a certificate file into the browser. For example, in Firefox version 30 preferences, you can go into the **Advanced** section, click the **Certificates** tab, then click the **View Certificates** button. On the **Servers** tab of the **Certificate Manager**, there is an **Import** button which enables you to load a certificate file from the local computer.
|
||||
If the users of your Libretime server wish to avoid going through these steps, or they do not trust the remote Libretime server to be what it claims to be, it is also possible to import a trusted local copy of a certificate file into the browser. For example, in Firefox version 30 preferences, you can go into the **Advanced** section, click the **Certificates** tab, then click the **View Certificates** button. On the **Servers** tab of the **Certificate Manager**, there is an **Import** button which enables you to load a certificate file from the local computer.
|
||||
|
||||
Mixed encrypted and unencrypted content
|
||||
---------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Accurate time keeping on your server is vital for Airtime performance. You can confirm that the date and time of your server are set correctly with the **date** command:
|
||||
Accurate time keeping on your server is vital for Libretime performance. You can confirm that the date and time of your server are set correctly with the **date** command:
|
||||
|
||||
date
|
||||
|
||||
|
|
@ -6,12 +6,12 @@ The server should respond with the date, time, time zone and year in a format si
|
|||
|
||||
Tue Jul 2 15:08:57 BST 2013
|
||||
|
||||
If the time on your server is wrong, it is recommended that you take Airtime off-air until the problem is fixed.
|
||||
If the time on your server is wrong, it is recommended that you take Libretime off-air until the problem is fixed.
|
||||
|
||||
Configuring NTP
|
||||
---------------
|
||||
|
||||
Although it is possible to set the date and time of the server manually, this is not recommended because the server clock can drift over time, compromising the accuracy of your broadcast schedule. If your Airtime server is permanently connected to the Internet, you can synchronize your server to a time server with the **ntp** ** program. If **ntp** is not yet installed, you can enter the following command on Debian or Ubuntu:
|
||||
Although it is possible to set the date and time of the server manually, this is not recommended because the server clock can drift over time, compromising the accuracy of your broadcast schedule. If your Libretime server is permanently connected to the Internet, you can synchronize your server to a time server with the **ntp** ** program. If **ntp** is not yet installed, you can enter the following command on Debian or Ubuntu:
|
||||
|
||||
sudo apt-get install ntp
|
||||
|
||||
|
|
@ -19,7 +19,7 @@ Optionally, open the **ntp** configuration file in the **nano** editor to add fu
|
|||
|
||||
sudo nano /etc/ntp.conf
|
||||
|
||||
On Ubuntu GNU/Linux, the default time server is *ntp.ubuntu.com*, but there are many other time servers available on the public Internet, including the group of servers listed at <http://www.pool.ntp.org/> for each country. Using a variety of NTP servers located closely to your Airtime server should produce the most accurate results. For example, for a server in the United Kingdom you could use the following list:
|
||||
On Ubuntu GNU/Linux, the default time server is *ntp.ubuntu.com*, but there are many other time servers available on the public Internet, including the group of servers listed at <http://www.pool.ntp.org/> for each country. Using a variety of NTP servers located closely to your Libretime server should produce the most accurate results. For example, for a server in the United Kingdom you could use the following list:
|
||||
|
||||
# You do need to talk to an NTP server or two (or three).
|
||||
server ntp.ubuntu.com
|
||||
|
|
@ -51,7 +51,7 @@ Then use the **ntpq -p** command to confirm that **ntp** is working. This comman
|
|||
Adjusting the server time zone
|
||||
------------------------------
|
||||
|
||||
The data centre which hosts your Airtime server could be located anywhere in the world. Some servers are set to *Coordinated Universal Time* or UTC (similar to *Greenwich Mean Time* or GMT), regardless of their location. Airtime uses UTC time in its database for scheduling purposes, independent of the server time zone.
|
||||
The data centre which hosts your Libretime server could be located anywhere in the world. Some servers are set to *Coordinated Universal Time* or UTC (similar to *Greenwich Mean Time* or GMT), regardless of their location. Libretime uses UTC time in its database for scheduling purposes, independent of the server time zone.
|
||||
|
||||
If the server time zone is not appropriate for integration with your station's other systems, on a Debian or Ubuntu server you can reconfigure the **tzdata** (time zone data) package with the command:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Using an ordinary smartphone and Airtime, you can upload your audio reports to the studio library or put them straight on the air. Here's how...
|
||||
Using an ordinary smartphone and Libretime, you can upload your audio reports to the studio library or put them straight on the air. Here's how...
|
||||
|
||||
The basic voice recorder app on your phone may not have all the features you need for journalism, but there are plenty of more suitable recording apps available for both iPhone and Android. For instance, searching for 'ogg recorder' in the *Play Store* on an Android phone yields plenty of alternatives. The following example uses *RecForge Lite* because of its configurable recording formats. This free app is limited to three minutes per recording in Ogg and MP3 formats, but there is an unrestricted version available at very modest cost.
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ Back in the main recording window of RecForge, create a directory such as '*reco
|
|||
|
||||
|
||||
|
||||
Open the web interface of your station's Airtime server in the phone's browser, log in with your username and password, and tap **Add Media** on Airtime's main menu. After tapping the **Add Files** button, the phone will offer a choice of file to upload. By tapping **Select music track** you can browse the */mnt/sdcard/media/audio/* directory on the SD card filesystem, without requiring the installation of a file manager app on the phone.
|
||||
Open the web interface of your station's Libretime server in the phone's browser, log in with your username and password, and tap **Add Media** on Libretime's main menu. After tapping the **Add Files** button, the phone will offer a choice of file to upload. By tapping **Select music track** you can browse the */mnt/sdcard/media/audio/* directory on the SD card filesystem, without requiring the installation of a file manager app on the phone.
|
||||
|
||||
|
||||
|
||||
|
|
@ -18,29 +18,27 @@ Tap one of the date-and-time-stamped files listed from the '*recordings*' direct
|
|||
|
||||
|
||||
|
||||
After tapping the **Start upload** button on the Add Media page, the files are now copied into the remote Airtime library.
|
||||
After tapping the **Start upload** button on the Add Media page, the files are now copied into the remote Libretime library.
|
||||
|
||||
|
||||
|
||||
If you prefer, you can upload audio files to the *organize* folder on the Airtime server using an SFTP client, skipping the web browser step. See the chapter *Manage media folders* for details. Suitable client applications include **AndFTP** for Android: <http://www.lysesoft.com/products/andftp/index.html>
|
||||
|
||||
You can now add the uploaded files directly to a forthcoming show, use them to create smart blocks or playlists in the **Library**, or edit their metadata to make them easier to find in searches later. One of the limitations of mobile recording is that it isn't always convenient to enter large amounts of text metadata when you're on the move. So a phone app that tagged audio recordings with creator, location and other relevant metadata would be very useful.
|
||||
|
||||
Going live
|
||||
----------
|
||||
|
||||
Mobile apps which enable you to stream directly into Airtime's live rebroadcast feature include **KoalaSan** for iOS: <http://koalasan.net/> and **BroadcastMySelf** for Android: <https://play.google.com/store/apps/details?id=sa.broadcastmyself> DemoIcesShout for Android also shows promise, although it can only stream a static file, rather than stream from a microphone: <http://droidtools.sourceforge.net/content/icecast-client-android>
|
||||
Mobile apps which enable you to stream directly into Libretime's live rebroadcast feature include **KoalaSan** for iOS: <http://koalasan.net/> and **BroadcastMySelf** for Android: <https://play.google.com/store/apps/details?id=sa.broadcastmyself> DemoIcesShout for Android also shows promise, although it can only stream a static file, rather than stream from a microphone: <http://droidtools.sourceforge.net/content/icecast-client-android>
|
||||
|
||||
A live workflow does of course depend on a steady network connection between the phone and Airtime server. Because streaming media on a regular basis can use a lot of bandwidth, it is advisable to use WiFi rather than mobile data (3G/4G) whenever possible, especially when roaming across networks.
|
||||
A live workflow does of course depend on a steady network connection between the phone and Libretime server. Because streaming media on a regular basis can use a lot of bandwidth, it is advisable to use WiFi rather than mobile data (3G/4G) whenever possible, especially when roaming across networks.
|
||||
|
||||
KoalaSan can stream input from either the built-in microphone or the external jack of the iOS device. An example configuration for the **Settings** tab might be:
|
||||
|
||||
Name: Airtime
|
||||
Server: airtime.example.com
|
||||
Name: Libretime
|
||||
Server: libretime.example.com
|
||||
Port: 8003
|
||||
Mountpoint: mastermount
|
||||
Stream name: Airtime
|
||||
Description: A live stream to Airtime
|
||||
Stream name: Libretime
|
||||
Description: A live stream to Libretime
|
||||
Genre: News
|
||||
Username: masterstreamer
|
||||
Password: masterpassword
|
||||
|
|
@ -57,7 +55,7 @@ You can start streaming from the iOS device by tapping the start button in Koala
|
|||
To configure BroadcastMySelf, tap the gears icon in the top left corner to enter the settings page, then tap **Output Settings**. This action opens the **Icecast Settings** page, where example settings could be:
|
||||
|
||||
Hostname
|
||||
airtime.example.com
|
||||
libretime.example.com
|
||||
|
||||
Port
|
||||
8003
|
||||
|
|
@ -84,6 +82,6 @@ You may also wish to configure the **Tracks Folder** setting, which enables you
|
|||
|
||||
/mnt/sdcard/media/audio/
|
||||
|
||||
To connect the Android device to the Airtime server, tap the square button in the lower middle of the main interface. The connection indicator on the button should turn blue, and the message *connected* should be shown. Push up the fader on the left to increase input level from the internal microphone, or push up the fader on the right and tap one of the named files in the upper right window to stream it. Tap either of the **LOCK** buttons to prevent the stream input level being changed accidentally.
|
||||
To connect the Android device to the Libretime server, tap the square button in the lower middle of the main interface. The connection indicator on the button should turn blue, and the message *connected* should be shown. Push up the fader on the left to increase input level from the internal microphone, or push up the fader on the right and tap one of the named files in the upper right window to stream it. Tap either of the **LOCK** buttons to prevent the stream input level being changed accidentally.
|
||||
|
||||
When the connection is made, Airtime output will fade from scheduled play to the stream from your mobile device. See the chapter *Stream settings* for more details of connection preferences.
|
||||
When the connection is made, Libretime output will fade from scheduled play to the stream from your mobile device. See the chapter *Stream settings* for more details of connection preferences.
|
||||
|
|
|
|||
|
|
@ -21,7 +21,8 @@ Click the **Save** button on the right side of the page to save any changes that
|
|||
Input stream settings
|
||||
---------------------
|
||||
|
||||
On the lower left side of the Stream Settings page you can configure remote live input streams from DJ programs such as **Mixxx** or **IDJC**, or smartphone applications used by broadcast journalists. Note that a [bug](https://sourceforge.net/p/butt/bugs/12/) has been reported with **Butt** versions 1.14 to 1.16 that causes streams not to connect to LibreTime. Butt version 1.13 does appear to be working. A fix has been introduced with **Butt** version 1.17 that allows it to be used by LibreTime.
|
||||
On the lower left side of the Stream Settings page you can configure remote live input streams from DJ programs such as **Mixxx** or **IDJC**, or smartphone applications used by broadcast journalists. A bug with **Butt** versions 1.14 to 1.16 causes streams not to connect to LibreTime. A fix has been introduced with **Butt** version 1.17 that allows it to be used by LibreTime.
|
||||
|
||||
|
||||
Airtime supports two types of live input stream; the **Show Source**, which enables a specific person to stream in during their own show, and the **Master Source**, which can override the Show Source if necessary. If neither type of live input is available, Airtime will fall back to **Scheduled Play** (playlists, smart blocks, remote streams and files scheduled in Airtime, in advance of or during a show).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +0,0 @@
|
|||
If you did not already register Airtime when you installed it, as shown in the *Getting Started* chapter, you can click **Support Feedback** on the <span style="font-weight: bold;">System</span> menu to display Airtime's automated feedback options. Check the **Send support feedback** box in order to post technical details about your Airtime installation to Sourcefabric, over the Internet. These details help Sourcefabric diagnose any problem that you might be having with your Airtime system.
|
||||
|
||||
You may also wish to send details of your station to Sourcefabric, so that your station has the opportunity to be promoted with other Airtime users on the [http://www.sourcefabric.org](http://www.sourcefabric.org/) website. This feature also helps Sourcefabric target its support services to the countries where they are needed most. Check the box **Promote my station on Sourcefabric.org** and fill in the details of your station. You can upload a station logo file (of up to 600 x 600 pixels) from your desktop computer by clicking the **Browse** button.
|
||||
|
||||
|
||||
|
||||
Click on the **Show me what I am sending** link to expand a box which displays the technical data being returned to Sourcefabric. The data is collected according to the Sourcefabric privacy policy (<http://www.sourcefabric.org/en/about/policy/>) which you are required to agree to before you can submit the information. If you have already checked the box to indicate your acceptance of the privacy policy, a link to the policy will be displayed instead.
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 28 KiB |
|
|
@ -1,5 +1,6 @@
|
|||
LibreTime 3.x versions support upgrading from Airtime 2.5.x versions. LibreTime
|
||||
follows the [Semantic Versioning (semver)](http://semver.org/spec/v2.0.0.html) standards.
|
||||
## LibreTime versioning
|
||||
|
||||
LibreTime 3.x versions support upgrading from Airtime 2.5.x versions. LibreTime follows the [Semantic Versioning (semver)](http://semver.org/spec/v2.0.0.html) standards.
|
||||
|
||||
In a nutshell, given a version number MAJOR.MINOR.PATCH we increment the:
|
||||
|
||||
|
|
@ -7,45 +8,17 @@ In a nutshell, given a version number MAJOR.MINOR.PATCH we increment the:
|
|||
2. MINOR version when we add functionality in a backwards-compatible manner, and
|
||||
3. PATCH version when we make backwards-compatible bug fixes.
|
||||
|
||||
Any pre-release versions of LibreTime are denoted by appending a hyphen and a series
|
||||
of dot separated identifiers immediately following the patch version. This pre-release
|
||||
indicates that the version is unstable in a sense that it might contain incomplete
|
||||
features or not satisfy the intended compatibility requirements as per semver.
|
||||
Any pre-release versions of LibreTime are denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. This pre-release indicates that the version is unstable in a sense that it might contain incomplete features or not satisfy the intended compatibility requirements as per semver.
|
||||
|
||||
Before upgrading a production LibreTime server, you should back up both the PostgreSQL
|
||||
database and the storage server used by LibreTime. This is especially important if you
|
||||
have not already set up a regular back up routine. This extra back up is a safety measure
|
||||
in case of accidental data loss during the upgrade, for example due to the wrong command
|
||||
being entered when moving files. See [Backing up the server](../backing-up-the-server/)
|
||||
in this manual for details of how to perform these back ups.
|
||||
## Upgrading
|
||||
|
||||
If you have deployed LibreTime using the method shown in [Automated installation](../automated-installation/),
|
||||
you can upgrade in the same way. A new LibreTime package available in
|
||||
the repository can be installed with:
|
||||
Before upgrading a production LibreTime server, you should back up both the PostgreSQL database and the storage server used by LibreTime. This is especially important if you have not already set up a regular back up routine. This extra back up is a safety measure in case of accidental data loss during the upgrade, for example due to the wrong command being entered when moving files. See [Backing up the server](../backing-up-the-server/) in this manual for details of how to perform these back ups.
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get upgrade
|
||||
The LibreTime [installation script](../install) will detect an existing LibreTime or Airtime deployment and back up any configuration files that it finds. We recommend taking your own manual backups of the configuration yourself nevertheless. The install script also tries to restart the needed services during an upgrade. In any case you should monitor if this happened and also take a quick look at the logs files to be sure everything is still fine. Now might be the time to reboot the system or virtual machine LibreTime is running on since regular reboots are part of a healthy system anyway.
|
||||
|
||||
If you have used the method shown in [Manual installation](../manual-installation/), you should
|
||||
repeat the installation steps of downloading and unpacking the tarball to an
|
||||
installation directory, or pulling from the git repository with `git pull`, and
|
||||
running the `./install` script. The installation script will detect an existing
|
||||
LibreTime deployment and back up any configuration files that it finds. We recommend
|
||||
taking your own manual backups of the configuration yourself nevertheless.
|
||||
After the upgrade has completed, you may need to clear your web browser's cache before logging into the new version of the LibreTime administration interface. If the playout engine starts up and detects that a show should be playing at the current time, it will skip to the correct point in the current item and start playing.
|
||||
|
||||
The install script tries to restart the needed services during an upgrade. In any case
|
||||
you should monitor if this happened and also take a quick look at the logs files to
|
||||
be sure everything is still fine. Now might be the time to reboot the system or
|
||||
virtual machine LibreTime is running on since regular reboots are part of a healthy
|
||||
system anyway.
|
||||
|
||||
After the upgrade has completed, you may need to clear your web browser's cache
|
||||
before logging into the new version of the LibreTime administration interface. If
|
||||
the playout engine starts up and detects that a show should be playing at the
|
||||
current time, it will skip to the correct point in the current item and start playing.
|
||||
|
||||
There will be tested ways to switch from a LibreTime pre-release to a packaged version
|
||||
of LibreTime.
|
||||
There will be tested ways to switch from a LibreTime pre-release to a packaged version of LibreTime.
|
||||
|
||||
Airtime 2.5.x versions support upgrading from version 2.3.0 and above. If you are
|
||||
running a production server with a version of Airtime prior to 2.3.0, you should
|
||||
|
|
|
|||
|
|
@ -1,76 +1,9 @@
|
|||
[Sourcefabric Manuals](http://sourcefabric.booktype.pro/)
|
||||
|
||||
- [Sign In / Create Account](http://sourcefabric.booktype.pro/accounts/signin/?redirect=/airtime-25-for-broadcasters/using-the-airtime-import-script/)
|
||||
|
||||
English | <a href="index.html#" class="langes">Español</a> | <a href="index.html#" class="langfr">Français</a> | <a href="index.html#" class="langit">Italiano</a> | <a href="index.html#" class="langpt">Português</a> | <a href="index.html#" class="langru">Русский</a> | <a href="index.html#" class="langsq">Shqip</a>
|
||||
|
||||
- [Books](http://sourcefabric.booktype.pro/list-books/)
|
||||
- [Groups](http://sourcefabric.booktype.pro/list-groups/)
|
||||
- [People](http://sourcefabric.booktype.pro/list-people/)
|
||||
|
||||
Airtime 2.5 for Broadcasters
|
||||
----------------------------
|
||||
|
||||
- **Introduction**
|
||||
- [What is Airtime?](../index.html)
|
||||
- [Rights and royalties](../rights-and-royalties/index.html)
|
||||
- **Using Airtime**
|
||||
- [On air in 60 seconds!](../on-air-in-60-seconds/index.html)
|
||||
- [Getting started](../getting-started/index.html)
|
||||
- [Smartphone journalism](../smartphone-journalism/index.html)
|
||||
- **The System menu**
|
||||
- [Preferences](../preferences/index.html)
|
||||
- [Users](../users/index.html)
|
||||
- [Media folders](../media-folders/index.html)
|
||||
- [Stream settings](../stream-settings/index.html)
|
||||
- [Support feedback](../support-feedback/index.html)
|
||||
- [Status](../status/index.html)
|
||||
- [Listener stats](../listener-stats/index.html)
|
||||
- **The main menus**
|
||||
- [Now playing](../now-playing/index.html)
|
||||
- [Add media](../add-media/index.html)
|
||||
- [Library](../library/index.html)
|
||||
- [Calendar](../calendar/index.html)
|
||||
- [History](../playout-history/index.html)
|
||||
- [Listen](../listen/index.html)
|
||||
- [Help](../help/index.html)
|
||||
- **Airtime in the studio**
|
||||
- [Recording shows](../recording-shows/index.html)
|
||||
- [Live shows with Mixxx](../live-shows-with-mixxx/index.html)
|
||||
- [Icecast and SHOUTcast](../icecast-and-shoutcast/index.html)
|
||||
- **Installation**
|
||||
- [Preparing the server](../preparing-the-server/index.html)
|
||||
- [Easy setup](../easy-setup/index.html)
|
||||
- [Automated installation](../automated-installation/index.html)
|
||||
- [Manual installation](../manual-installation/index.html)
|
||||
- [Setting the server time](../setting-the-server-time/index.html)
|
||||
- **Administration**
|
||||
- [Preparing media for ingest](../preparing-media-for-ingest/index.html)
|
||||
- [Using the airtime-import script](index.html)
|
||||
- [The airtime-log command](../the-airtime-log-command/index.html)
|
||||
- [Backing up the server](../backing-up-the-server/index.html)
|
||||
- [Upgrading](../upgrading/index.html)
|
||||
- [Troubleshooting](../troubleshooting/index.html)
|
||||
- [Using Monit](../using-monit/index.html)
|
||||
- **Advanced configuration**
|
||||
- [Automated file import](../automated-file-import/index.html)
|
||||
- [Icecast handover](../icecast-handover/index.html)
|
||||
- [Promoting your station](../promoting-your-station/index.html)
|
||||
- [Stream player for your website](../stream-player-for-your-website/index.html)
|
||||
- [Exporting the schedule](../exporting-the-schedule/index.html)
|
||||
- [Interface customization](../interface-customization/index.html)
|
||||
- [Interface localization and Git](../interface-localization/index.html)
|
||||
- [Host configuration](../host-configuration/index.html)
|
||||
- [Airtime API authentication](../airtime-api-authentication/index.html)
|
||||
- [Secure login with SSL or TLS](../secure-login-with-ssl/index.html)
|
||||
- [Icecast statistics with Piwik](../icecast-statistics-with-piwik/index.html)
|
||||
- **Appendix**
|
||||
- [HD Audio Models](../hd-audio-models/index.html)
|
||||
- [About this manual](../about-this-manual/index.html)
|
||||
|
||||
Using the import script
|
||||
=======================
|
||||
|
||||
###NOTE: This page has issues, as the import script is not currently functional
|
||||
|
||||
|
||||
If you have a large number of files in your media library, importing these files one at a time into a broadcast automation system would be time-consuming and tedious. That's why Airtime includes a script that can import an entire directory of files in one go.
|
||||
|
||||
Copying versus watching
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue