-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Spaces and Nodes for media data controls and organisation
The Span project is a kind of CMS (Content Management Software) for media instruments.
It works with the notion of a "project" which could be highly customized, run local patches and/or use distant existing namespace (in localhost or with a network).
It has a powerfull mapping engine and is natively (OSC) Open Sound Control.
It could be used with a lot of protocols such as OSC, MIDI, DMX, ARTNET, SERIAL, VISCA, PJLINK, MINUIT, COPERLAN and more…
A SPAN project file is a JSON that has multiple indexes and dictionaries. This format has been chosen for its speed and simplicity. However, a special syntax is needed, and we could use this online viewer to read it or another JSON viewer. A lot of little utilities should be easily found over the web.
All the requests are done in a single place.
| Open-Sound-Control communication | Project-manager | Multi-mapping | Events manager | Namespace Manager |
|---|---|---|---|---|
| Multicast - Unicast - Broadcast | files and folder handling | One-to-Many mapping | Polyphonic cues player | Description files loading |
| tags and custom taxonomy | Multi-modes mapping |
The span-requests is your interlocutor when working with a span database. This object allows you to speak with span. You can do get or set all the values inside.
When span is loading, it adds some default preferences and create the span database. This action is done by span.load.json file.
When span loads a project, it adds all the keys found in the file to the root of span database, and add a copy of all its file structure with keys and sub-keys but without values. It will be used to know what to save in each project.