Adding more images
|
@ -1,4 +1,4 @@
|
|||
# Navigation
|
||||
# Navigation for Docs page (guides.md)
|
||||
djguides:
|
||||
- page: Broadcasting Live
|
||||
url: live-broadcast
|
||||
|
@ -11,7 +11,7 @@ djguides:
|
|||
|
||||
managerguides:
|
||||
- page: Playout History & Auditing
|
||||
url: playout-history
|
||||
url: analytics
|
||||
- page: Rights and Royalties
|
||||
url: rights-royalties
|
||||
- page: User Management
|
||||
|
|
|
@ -13,6 +13,8 @@ Search results can be copied to the clipboard using the **Copy** button, exporte
|
|||
|
||||
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.
|
||||
|
||||

|
||||
|
||||
In the **Log Sheet** tab, the playout history is sorted by **Start Time** and **End Time** by default.
|
||||
|
||||
The number of times each file was played and the length of the files are shown in the **File Summary** tab. To make optimal use of this feature for royalty reporting purposes, music files must be tagged with **Composer** and **Copyright** metadata. The artist performing a piece of music may not be the original composer of the work, or the copyright holder of the sound recording.
|
||||
|
@ -27,8 +29,12 @@ Log entries can also be manually deleted, using the button with the trashcan ico
|
|||
|
||||
## History Templates
|
||||
|
||||

|
||||
|
||||
The **History Templates** page on the History menu enables you to prepare reports with the exact content required by regulatory agencies in the territories that you are broadcasting to. You can begin creating a custom template by clicking the button **New Log Sheet Template** or the button **New File Summary Template**.
|
||||
|
||||

|
||||
|
||||
Either of these actions opens a page in which you can name the new template, and add or remove elements from the list on the left. To add a new element from the list on the right, click the plus icon for the item you require. If the element you require is not listed, you can use the **Add New Field** box at the lower end of the right side column. Select *string*, *boolean*, *integer*, or *float*, depending on the type of data that you wish to log, and then click the **+ Add** button.
|
||||
|
||||
When the template is in the format you require, click the **Save** button, and **Set Default Template** if you wish. The new template will now be listed on the History Templates page. If you have set a new default template, any changes will be visible on the tabs of the Playout History page.
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: LibreTime API Usage
|
||||
git: api.md
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Contributing to LibreTime
|
||||
|
||||
git: contribute.md
|
||||
---
|
||||
|
||||
> LibreTime is a fork of AirTime due to stalled development of the FLOSS version. For background on this,
|
||||
|
@ -27,7 +27,9 @@ supported? Follow [this guide](interface-localization) to add your language to L
|
|||
## Help write documentation for LibreTime
|
||||
|
||||
Our site is now run by Jekyll. After cloning our repo locally, enter the `/docs` directory and run
|
||||
|
||||
```
|
||||
bundle install
|
||||
jekyll serve
|
||||
```
|
||||
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: HD Audio Modules
|
||||
git: hd-audio-modules.md
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Icecast and Shoutcast Stream Configuration
|
||||
git: icecast-shoutcast.md
|
||||
---
|
||||
|
||||
## Background
|
||||
|
|
After Width: | Height: | Size: 31 KiB |
After Width: | Height: | Size: 102 KiB |
After Width: | Height: | Size: 116 KiB |
After Width: | Height: | Size: 48 KiB |
After Width: | Height: | Size: 88 KiB |
After Width: | Height: | Size: 32 KiB |
After Width: | Height: | Size: 42 KiB |
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Built-in Microsite
|
||||
git: microsite
|
||||
---
|
||||
|
||||

|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Preparing Media for LibreTime
|
||||
|
||||
git: preparing-media.md
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Rights and Royalties
|
||||
git: rights-royalties.md
|
||||
---
|
||||
|
||||
If you're new to broadcasting, or have not streamed your station online before,
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Settings
|
||||
git: settings.md
|
||||
---
|
||||
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Upgrading LibreTime
|
||||
|
||||
git: upgrading.md
|
||||
---
|
||||
|
||||
## LibreTime versioning
|
||||
|
|
|
@ -8,7 +8,7 @@ git: users.md
|
|||
it is recommended that you create a second administrator account with a secure password and then
|
||||
delete the `admin` account, for best security practice.
|
||||
|
||||
## Adding user accounts
|
||||
## User Account Types
|
||||
|
||||
To add further user accounts to the system, one for each of your station staff that need access to Airtime, click the **New User** button with the plus icon. Enter a user name, password and contact details, and then select the **User Type** from the drop down menu, which can be *Admin*, *Program Manager*, *DJ*, or *Guest*. The difference between these user types is:
|
||||
|
||||
|
@ -37,11 +37,15 @@ To add further user accounts to the system, one for each of your station staff t
|
|||
|
||||
## Editing or deleting user accounts
|
||||
|
||||

|
||||
|
||||
New user accounts that you add will be shown in the table on the left side of the **Users** page. If you have a
|
||||
large number of users on the system, you can use the search tool above the table (which has a magnifying glass icon)
|
||||
to identify specific user accounts. Click the white chevrons in the table headings to sort the search results
|
||||
by **Username**, **First Name**, **Last Name** or **User Type**.
|
||||
|
||||

|
||||
|
||||
To edit a user account, click on that user's row in the table, change the user's details in the box on the
|
||||
right side, and then click the **Save** button. To remove a user account, click the small **x** icon to the right
|
||||
side of its row in the table. You cannot delete your own user account, and usernames cannot be changed once created.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: default
|
||||
title: Using Vagrant and Virtualbox for developing LibreTime
|
||||
|
||||
git: vagrant.md
|
||||
---
|
||||
|
||||
> Prerequisites: git, [Vagrant](https://vagrantup.com), libvirt or VirtualBox
|
||||
|
|