ffplayout/README.md

135 lines
4.8 KiB
Markdown
Raw Normal View History

2019-03-30 15:17:32 -04:00
**ffplayout-engine**
2018-01-07 07:58:45 -05:00
================
2019-03-14 10:25:13 -04:00
[![made-with-python](https://img.shields.io/badge/Made%20with-Python-1f425f.svg)](https://www.python.org/)
[![License: GPL v3](https://img.shields.io/badge/License-GPLv3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
2018-01-07 07:58:45 -05:00
2019-06-05 05:23:52 -04:00
This is a playout application based on python and ffmpeg.
2018-01-07 07:58:45 -05:00
2019-06-05 05:23:52 -04:00
The purpose with ffplayout is to provide a 24/7 broadcasting solution that plays a *json* playlist for every day, while keeping the current playlist editable.
2018-01-07 07:58:45 -05:00
2019-03-30 15:12:28 -04:00
#### Check [ffplayout-gui](https://github.com/ffplayout/ffplayout-gui): web-based GUI for ffplayout.
2018-01-07 07:58:45 -05:00
2019-06-06 12:30:51 -04:00
Features
2018-01-07 07:58:45 -05:00
-----
- have all values in a separate config file
- dynamic playlist
2019-03-30 16:28:25 -04:00
- replace missing playlist or clip with a dummy clip
2019-06-06 12:30:51 -04:00
- playing clips from watched folder
2018-01-07 07:58:45 -05:00
- send emails with error message
- overlay a logo
2019-03-30 16:28:25 -04:00
- trim and fade the last clip, to get full 24 hours, if the duration is less then 6 seconds add a dummy clip
2018-01-07 07:58:45 -05:00
- set custom day start, so you can have playlist for example: from 6am to 6am, instate of 0am to 12pm
2019-03-30 16:28:25 -04:00
- copy mode, for more info's take a look in the [Wiki](https://github.com/ffplayout/ffplayout-engine/wiki/Copy-Mode)
2018-01-07 11:22:24 -05:00
- normal system requirements and no special tools
2019-06-06 12:30:51 -04:00
- no GPU power is needed
- stream to server or play on desktop
2018-01-07 07:58:45 -05:00
2019-06-04 06:31:59 -04:00
#### Why not more features?
2019-06-04 09:18:05 -04:00
- ffplayout follows the principle: stability over features!
2019-06-04 06:31:59 -04:00
- ffplayout must be able to run in containers and VMs without problems, so it should be resource-efficient and not use GPU features
- if you have a great feature that needs to be integrated and can be done with ffmpeg - feel free to submit code
- besides that, you can also check the [TODO](https://github.com/ffplayout/ffplayout-engine/projects/1) to see if more is planned
2019-06-06 12:30:51 -04:00
Requirements
-----
- python version 3.5+
- python module **watchdog**
- **ffmpeg** and **ffprobe** (**ffplay** if you want to play on desktop)
- RAM and CPU depends on video resolution, minimum 4 threads and 3GB RAM for 720p are recommend
JSON Playlist Example
2018-01-07 07:58:45 -05:00
-----
```json
{
"channel": "Test 1",
"date": "2019-03-05",
"begin": "06:00:00.000",
"length": "24:00:00.000",
"program": [{
"in": 0,
"out": 647.68,
"duration": 647.68,
2019-03-12 16:13:58 -04:00
"source": "/Media/clip1.mp4",
}, {
"in": 0,
"out": 149,
"duration": 149,
2019-03-12 16:13:58 -04:00
"source": "/Media/clip2.mp4",
}, {
"in": 0,
"out": 114.72,
"duration": 114.72,
2019-03-12 16:13:58 -04:00
"source": "/Media/clip3.mp4",
"category": "advertisement"
}, {
"in": 0,
"out": 2531.36,
2019-03-06 09:29:37 -05:00
"duration": 2531.36,
2019-03-12 16:13:58 -04:00
"source": "/Media/clip4.mp4",
"category": ""
}
]
}
2018-01-07 07:58:45 -05:00
```
`"begin"` and `"length"` are optional, when you leave **begin** blank, length check will be ignored and the playlist starts from the begin, without time awareness. If you leave **length** blank, the validation will not check if the real length of the playlist will match the length value.
#### Warning:
2019-03-30 16:28:25 -04:00
(Endless) streaming over multiple days will only work when the playlist have **both** keys and the **length** of the playlist is **24 hours**. If you need only some hours for every day, use a *cron* job, or something similar.
2019-03-06 09:25:14 -05:00
Source from URL / Live Stream
-----
You can use sources from url or live stream in that way:
```json
...
{
"in": 0,
"out": 149,
"duration": 149,
2019-03-13 09:59:05 -04:00
"source": "https://example.org/big_buck_bunny.webm"
2019-03-06 09:25:14 -05:00
},
...
{
"in": 0,
"out": 2531.36,
"duration": 0,
2019-03-06 09:29:37 -05:00
"source": "rtmp://example.org/live/stream"
2019-03-06 09:25:14 -05:00
}
...
```
But be careful with it, better test it multiple times!
2019-03-30 15:12:28 -04:00
More informations in [Wiki](https://github.com/ffplayout/ffplayout-engine/wiki/URL---Live-Source)
2019-03-06 09:25:14 -05:00
2018-01-07 11:22:24 -05:00
Installation
-----
2019-05-27 10:30:49 -04:00
- install ffmpeg, ffprobe (and ffplay if you need the preview mode)
2019-06-04 09:18:05 -04:00
- copy ffplayout.py to **/usr/local/bin/**
- copy ffplayout.conf to **/etc/ffplayout/**
2019-03-30 16:28:25 -04:00
- create folder with correct permissions for logging (check config)
2018-01-07 11:22:24 -05:00
- copy ffplayout.service to **/etc/systemd/system/**
2019-06-04 09:18:05 -04:00
- change user in **/etc/systemd/system/ffplayout.service**
2018-01-07 11:22:24 -05:00
- create playlists folder, in that format: **/playlists/year/month**
- set variables in config file to your needs
2019-05-27 10:32:27 -04:00
- use **get_playlist_from_subfolders.sh /path/to/mp4s/** as a starting point for your playlists (path in script needs to change)
2018-01-07 11:22:24 -05:00
- activate service and start it: **sudo systemctl enable ffplayout && sudo systemctl start ffplayout**
2019-03-18 16:31:10 -04:00
2019-04-01 16:05:46 -04:00
Start with Arguments
2019-03-18 16:31:10 -04:00
-----
ffplayout also allows the passing of parameters:
- `-l, --log` for user-defined log file
- `-f, --file` for playlist file
The entire command could look like this:
```
python3 ffplayout.py -l ~/ffplayout.log -f ~/playlist.json
```
2019-03-31 14:54:22 -04:00
2019-05-27 10:30:49 -04:00
Preview Mode on Desktop
2019-04-01 16:05:46 -04:00
-----
2019-03-31 14:54:22 -04:00
For playing on desktop set `preview = True` in config under `[OUT]`.