TimeSide
scalable audio processing framework and server written in Python
Install / Use
/learn @Parisson/TimeSideREADME
TimeSide : scalable audio processing framework and server written in Python
TimeSide is a Python framework enabling low and high level audio analysis, imaging, transcoding, streaming and labelling. Its high-level API is designed to enable complex processing on very large datasets of any audio or video assets with a plug-in architecture and a secured scalable backend.
Introduction
As the number of online audio applications and datasets increase, it becomes crucial for researchers and engineers to be able to prototype and test their own algorithms as fast as possible on various platforms and usecases like computational musicology and streaming services. On the other side, content providers and producers need to enhance user experiences on their platforms with more metadata based on cultural history but also audio feature analyses. Growing those metadata synchronously with the music published on the internet implies that the analysis and storage systems can be easily updated, scaled and deployed.
TimeSide has been developed in this sense to propose an online audio processing service. It provides:
- a core module for Python to work from a shell or any other Python based program
- a web server for the Web with a RESTful API built on top of the core module so that web developers can then easily embed the remote processing service into their own applications.
- a SDK for Javascript and based on OpenAPI to easily develop a third party application consuming the server API.
Use cases
- Asynchronous audio processing (filtering, feature analysis, machine learning, etc)
- Scaled and secured data provisioning, processing and accessing
- Audio plugin prototyping
- Audio visualization
- On-demand transcoding and streaming over the Web
- Enhanced shared audio player
- Automatic segmentation and manual labelling synchronized with audio events
Features
- Do asynchronous and fast audio processing with Python,
- Decode audio frames from any audio or video media format into numpy arrays,
- Analyze audio content with some state-of-the-art audio feature extraction libraries like Aubio, Yaafe and VAMP as well as some pure python processors
- Visualize sounds with various fancy waveforms, spectrograms and other cool graphers,
- Transcode audio data in various media formats and stream them through web apps,
- Serialize feature analysis data through various portable formats,
- Provide audio sources from plateform like YouTube or Deezer
- Deliver analysis and transcode on provided or uploaded tracks over the web through a REST API
- Playback and interact on demand through a smart high-level HTML5 extensible player,
- Index, tag and annotate audio archives with semantic metadata (see
Telemeta <http://telemeta.org>__ which embed TimeSide). - Deploy and scale your own audio processing engine through any infrastructure
Funding and support
To fund the project and continue our fast development process, we need your explicit support. So if you use TimeSide in production or even in a development or experimental setup, please let us know by:
- staring or forking the project on
GitHub <https://github.com/Ircam-WAM/TimeSide>_ - droping us an email at wam@ircam.fr
Thanks for your help and support!
News
1.1
-
Core:
- Use the libav based aubio decoder by default (fastest audio to numpy array converter on the planet!)
- Add a VAMP based analyzer and a few plugins like VampFlatness, VampCrest, VampTempo, VampTuning, VampSpectralCentroid, VampSpectralKurtosis and VampSpectralSlope
-
Server:
- Fix a lot of asynchronous processing issues: now do every pre-processing, processing and post-processing tasks through the worker including source stream fetching from youtube
- Add a process monitor based on websocket
- Waveform automatically processed on Item.save()
- Make UUID really unique
- Reordering models
- Improve unit tests
1.0
-
Server refactoring:
- audio process run on items (REST API track's model)
- several tools, views, models and serializers
- REST API's schema on OpenAPI 3 specification and automatic Redoc generation
-
Move core and server from Python 2.7 to 3.7
-
Upgrade Django to 2.2, Django REST Framework to 3.11, Celery to 4.4
-
Add an
Aubio <https://github.com/aubio/aubio>_ based decoder -
Add core and server processors' versioning and server process' run time
-
Regroup all dependencies on pip requirements removing conda use
-
Add Provider class as a core API component and as a REST API model
-
Add provider plugins deezer-preview, deezer-complete and youtube
-
Improve server unit testing
-
Add JWT authentication on REST API
-
Various bug fixes
-
Add core, server and workers logging
0.9
- Upgrade all python dependencies
- Add Vamp, Essentia, Yaafe, librosa, PyTorch, Tensorflow libs and wrappers
- Add a few analyzing plugins (Essentia Dissonance, Vamp Constant Q, Vamp Tempo, Vamp general wrapper, Yaafe general wrapper)
- Add processor parameter management
- Add processor inheritance
- Improve HTML5 player with clever data streaming
- Improve REST API and various serialzers
- Improve unit testing
- Various bug fixes
0.8
- Add Docker support for instant installation. This allows to run TimeSide now on any OS platform!
- Add
Jupyter Notebook <http://jupyter.org/>_ support for easy prototyping, experimenting and sharing (see the examples in the doc). - Add an experimental web server and REST API based on Django REST Framework, Redis and Celery. This now provides a real web audio processing server with high scaling capabilities thanks to Docker (clustering) and Celery (multiprocessing).
- Start the development of a new player interface thanks to Angular and WavesJS.
- Huge cleanup of JS files. Please now use bower to get all JS dependencies as
listed in settings <https://github.com/Ircam-WAM/TimeSide/blob/dev/app/sandbox/settings.py#L199>_. - Add metadata export to Elan annotation files.
- Fix and improve some data structures in analyzer result containers.
- Many various bugfixes.
0.7.1
- fix django version to 1.6.10 (sync with Telemeta 1.5)
0.7
-
Code refactoring:
- Create a new module
timeside.pluginsand move processors therein: timeside.plugins.decoder,analyzer, timeside.plugins.encoder, timeside.plugins.fx - WARNING: to properly manage the namespace packages structure, the TimeSide main module is now
timeside.coreand code should now be initialized withimport timeside.core timeside.pluginsis now anamespace package <https://pythonhosted.org/setuptools/setuptools.html#namespace-packages>_ enabling external plugins to be automatically plugged into TimeSide (see for exampletimeside-diadems <https://github.com/ANR-DIADEMS/timeside-diadems>_). This now makes TimeSide a real plugin host, yeah!- A dummy timeside plugin will soon be provided for easy development start.
- Create a new module
-
Move all analyzers developped by the partners of the Diadems project to a new repository:
timeside-diadems <https://github.com/ANR-DIADEMS/timeside-diadems>_ -
Many fixes for a better processing by
Travis-CI <https://travis-ci.org/Ircam-WAM/TimeSide>_ -
Add a dox file to test the docker building continously on
various distributions <https://github.com/Parisson/Docker>_
For older news, please visit: https://github.com/Ircam-WAM/TimeSide/blob/master/NEWS.rst
Documentation
-
Full documentation: https://timeside.ircam.fr/docs/
-
Server REST API: https://timeside.ircam.fr/api/docs/
-
Slides: https://ircam-wam.github.io/timeside-slides/#1
-
Core tutorials: https://timeside.ircam.fr/docs/tutorials/
-
Some notebooks: https://github.com/Ircam-WAM/TimeSide/tree/master/docs/ipynb
-
Some older notebooks: http://mybinder.org/repo/thomasfillon/Timeside-demos
-
Publications:
- https://github.com/Parisson/Telemeta-doc
- https://github.com/Ircam-WAM/timeside-papers
-
Player UI v2: https://github.com/Ircam-WAM/timeside-player
-
Player UI v1 guide: https://github.com/Ircam-WAM/TimeSide/wiki/Ui-Guide
-
Player UI v1 example: http://archives.crem-cnrs.fr/archives/items/CNRSMH_E_2004_017_001_01/
Install
Thanks to Docker, Timeside is now fully available as a docker composition ready to work. The docker based composition bundles some powerful applications and modern frameworks out-of-the-box like: Python, Numpy, Jupyter, Gstreamer, Django, Celery, PostgreSQL, Redis, uWSGI, Nginx and more.
First, install Docker <https://docs.docker.com/get-docker/>_ and docker compose <https://docs.docker.com/compose/install/>_
Then clone TimeSide and start it up::
git clone --recursive https://github.com/Ircam-WAM/TimeSide.git
cd TimeSide
docker compose up -d
That's it! Now please go to the :ref:User Interfaces section to see how to use it.
.. note:: To get technical support, please reach the development team. If you need to use TimeSide outside a docker image please refer to the rules of the Dockerfile which is based on a Debian stable system. We will NOT provide any kind of free support in this paticular usecase outside the original docker container.
Sponsors and Partners
IRCAM <https://www.ircam.fr>_ (Paris, France)Parisson <http://parisson.com>_ (Paris, France)CNRS <http://www.cnrs.fr>_: National Center of Science Research (France)Huma-Num <http://www.huma-num.fr/>_: big data equipment for digital humanities (CNRS, France)CREM <http://www.crem-cnrs.fr>_: French National Center of Ethomusicology Research (France)Université Pierre et Marie Curie <http://www.upmc.fr>_ (UPMC Paris, France)ANR <http://www.agence-nationale-recherche.fr/>_: Agence Nationale de la Recherche (France)MNHN <http://www.mnhn.fr>_ : Museum National d'Histoire Naturelle (Paris, F
Related Skills
node-connect
343.3kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
claude-opus-4-5-migration
92.1kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
92.1kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
model-usage
343.3kUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
