software:relive

channel
channel nameChaos-West TV
statustested
playout slug (CDN)cwtv2
managed_byChaos-West TV
gema_schedule1x DJ-Set, Zeitpunkt unbekannt
contactsthunfisch
ingest_typertmp-push
recording_typemanual
releasing_typehttp-tracker
releasing_youtubeja: Kanal mediacccde
schedule_roomChaos-West TV
commentIngest via direct upload
studio
nameChaos-West TV
locationEnnepetal
live
preproductionnein
remote_speakersJa
contactsthunfisch
mailthunfisch@chaoswest.tv
full_remote_operationja
plz58256
geo
engelsystem_usernamesthunfisch
possible_production_times12:00-22:00 CET

This is an old revision of the document!


HLS Relive

Documentation for the relive system is contained within its git repo git@c3voc.de:hls-relive mirrored at https://github.com/voc/hls-relive → README.md

It's currently deployed at live.alb:/home/relive/git/

Login to server

ssh relive@live.alb.c3voc.de
cd git 
screen -dR
  1. Create an appropriate config for your event in `live.alb:/home/relive/git/configs`
    1. either by using `./gen_event_config.py <conference slug>`, or
    2. manually: copy `cfg.example`, look at other files in that directory, or in the `old/` subdirectory for inspiration. The filename will be used as the conference name from here on.
  2. After a minute, a cronjob will run and download the schedule, etc. (If you are impatient, you can run `/home/relive/git/scripts/foreach-project.sh /home/relive/git/scripts/get-fahrplan.sh` manually)
  3. Start the scheduler (run as user relive, inside of a screen/tmux session): `./launcher.sh <conference slug>`
  4. In the streaming-website configuration, set RELIVE_JSON to point to http://live.alb.c3voc.de/relive/<conference slug>/index.json

Note that the index.json file is also only regenerated periodically, so it might be a minute or two before that URL actually works.

When an event in voctoweb has no recordings, voctoweb will try to find the corresponding relive recording. This only works if the conference acronym matches the acronym used in the relive system.

To use this feature, first create the conference in voctoweb and in c3tracker. In theory there are multiple variants, but this one is the one we currently use:

  • create-event-by-ticket.py is able to create an event in voctoweb, based on the CRS Ticket ID.
  • This script can be called during any state transition, we currently use `scheduled` → `recording`
  • To enable this for you conference, enable the “releasing.c3voc.de-relive” worker group which is handled by a modified version of CRS worker `script-A` living in a screen (user voc). TODO: Create systemd timer for this.
  • If you need re-create the session, run following commands:

``` ssh voc@releasing.c3voc.de screen -x cd /opt/crs/tools/tracker3.0 source tracker-profile-relive.sh export LOCALFILE=tracker-profile-relive.sh ./bin/crs_run script-A-recording+relive-scheduler.pl ```

Please read the README in the repository, it is being kept up to date with regard to the general behavior of the relive system.

  • software/relive.1602539331.txt.gz
  • Last modified: 2020/10/12 23:48
  • by andi