No Description

boyska 23b04a58bc remove useless js things 1 year ago
contrib bd8850b6a2 deploy contrib/ 6 years ago
server 23b04a58bc remove useless js things 1 year ago
.gitignore 5a40d24798 pyinstaller funzionante 1 year ago
12factors.md 4d6324e328 12factors.md format fixed 6 years ago
LICENSE e58997a1cf AGPL license and better readme 6 years ago
MANIFEST.in 0c254dabe2 FIX packaging to include static files 1 year ago
README.md 0bad389a9e readme: py3 support 1 year ago
RELEASE.md 1350dad450 More information about release 6 years ago
publish-release d8c8520950 publish release script 1 year ago
setup.py b956076fc5 black reformatting 1 year ago
techrec.spec 5a40d24798 pyinstaller funzionante 1 year ago

README.md

TechRec

A Python2/Python3 web application that assist radio speakers in recording their shows. Meant to be simple to install and to maintain.

It basically takes a directory with the continuous recording and create new files "cutting/pasting" with ffmpeg.

Features

  • little system dependencies: python and ffmpeg
  • The interface is extremely simple to use
  • Supports nested recording (ie: to record an interview inside of a whole show)
  • There is no user system: any user opening the website will see the complete status of the applications. There is, also, nothing stored in cookie or similar mechanisms. This means that recording a session does not require a browser to remain open, or any kind of persistence client-side: server-side does it all. It also means that authorization must be done on another layer (for example, your webserver could add a Basic Auth)

How does it work

We suppose that you have a continous recording of your radio broadcasting. What techrec does is taking files from this directory and "cutting/pasting" parts of them. This can boil down to something like

ffmpeg -i concat:2014-20-01-00-00.mp3|2014-20-01-00-01.mp3 -acodec copy -ss 160 -t 1840 foo.mp3

Implementation details

It is based on bottle, to get a minimal framework. Simple APIs are offered through it, and the static site uses them.

Jobs are not dispatched using stuff like celery, but with a thin wrapper over multiprocessing.Pool; this is just to keep the installation as simple as possible.

The encoding part is delegated to ffmpeg, but the code is really modular so changing this is a breeze. To be quicker and avoid the quality issues related to reencoding, the codec "copy" is used: this means that input and output must have the same format.

testing

unit tests can be run with python setup.py test

screenshots

See screenshots at https://boyska.degenerazione.xyz/proj/techrec/