You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/server_api/introduction.rst
+17-6Lines changed: 17 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ In addition to be usable as a library, TimeSide has furthermore been built into
10
10
- collect tags and indices on tracks to build annotated audio corpora for further machine learning purpose.
11
11
12
12
Models and Serializers
13
-
-----------------------
13
+
======================
14
14
15
15
The models of the backend are defined as usual Django models and are all stored with a UUID. Here is a list of the main ones:
16
16
@@ -21,12 +21,23 @@ The models of the backend are defined as usual Django models and are all stored
21
21
- Experience: a list of Presets
22
22
- Task: a list of Selection linked to an Experience to run
23
23
24
-
This modelization allows to define some specific precessing \textit{Experiences} that can be re-processed on any new \textit{Selection} which is espacially convenient for analysis on growing datasets. All model instances and related data are accesible through a REST API with authentication. This ensures that a client can consume TimeSide as a dedicated and autonomous web service.
24
+
This modelization allows to define some specific precessing *Experiences* that can be re-processed on any new *Selection* which is espacially convenient for analysis on growing datasets. All model instances and related data are accesible through a REST API with authentication. This ensures that a client can consume TimeSide as a dedicated and autonomous web service.
25
25
26
-
The API full documentation is there: https://timeside.ircam.fr/timeside/api/docs/
26
+
Results and Formats
27
+
====================
27
28
29
+
All processing results are accesible in a \verb|AnalyzerResult| python object containing a structured and documented data dictionary which can be serialized, stored and restored in HDF5, JSON, YAML or XML formats. The file contains all the preset parameters and data structure so that, if a process is requested for the same media file, same processors type and same version, the data will be automatically retrieve from the databasen and eventualluy re-processed in another child processor or serializer. The TimeSide server also embeds a full relational database to store any lighter data that has be be linked to models.
28
30
29
-
Results and Formats
30
-
--------------------
31
31
32
-
All processing results are accesible in a \verb|AnalyzerResult| python object containing a structured and documented data dictionary which can be serialized, stored and restored in HDF5, JSON, YAML or XML formats. The file contains all the preset parameters and data structure so that, if a process is requested for the same media file, same processors type and same version, the data will be automatically retrieve from the databasen and eventualluy re-processed in another child processor or serializer. The TimeSide server also embeds a full relational database to store any lighter data that has be be linked to models.
32
+
API documentation
33
+
==================
34
+
35
+
The `API full documentation is available online <https://timeside.ircam.fr/timeside/api/docs/>`_
36
+
37
+
38
+
Javascript SDK
39
+
===============
40
+
41
+
In order to build frontends on top of this web API, a `Software Development Kit (SDK) is available <https://github.com/Ircam-WAM/timeside-sdk-js>`_ for the Javascript and Typescript languages. It has been created from the routes of the OpenAPI schema automatically exported from the backend thanks to the OpenAPI Generator. The SDK proposes some examples for clients to reach the server and request some processing.
42
+
43
+
As an example, an augmented HTML5 player is presented in the "User Interfaces" section.
0 commit comments