BlinkenArea - GitList
Repositories
Blog
Wiki
Blinker
Code
Commits
Branches
Tags
Search
Tree:
d0a5991
Branches
Tags
master
Blinker
doc
index.html
document pong module
Stefan Schuermans
commited
d0a5991
at 2019-06-16 18:17:06
index.html
Blame
History
Raw
<html> <head> <title>Blinker</title> </head> <body> <h1>Blinker</h1> <p> Blinker is a server for LED projects and Blinken-houses that are driven by Blinkenlights network streams. </p> <h2>Overview</h2> <p> Blinker is based on different modules, which can be connected via streams. Several types of modules are available, for example a movie player, a network stream sender, modules to mix and separate streams. </p> <h2>Getting Started</h2> <p> As Blinker uses BlinkenLib to perform the low-level operations on Blinken movies and Blinken streams, BlinkenLib has to be installed first. </p> <p> Go to the <code>src</code> directory and type <code>make</code>. This should compile Blinker and produce a binary <code>Blinker</code> in this directory. </p> <p> Start Blinker using the example configuration directory using <code>./Blinker ../example_cfg</code>. You should see a small test movie appearing on standard output (printed there by a printer module). Other movies are sent as MCUF streams over UDPv4, one stream is sent to <code>127.0.0.1:2323</code>. </p> <h2>Streams</h2> <p> Every stream is identified by a name and works like a TV program. A source creates the content and uses the stream to distribute it to its receivers. A single stream can have any number of receivers, they all receive the same content. Usually, there should be only one provider of content for a single stream. If multiple parties send video frames to the stream, the frames are mixed, which is most likely not what you want. </p> <h2>Operator Connections</h2> <p> Some modules can react to events and/or send events to other modules. Suche events are delivered over so-called operator connections. A module can caonnect to another module listen for incoming operator connections. If this connection is accepted, both modules can exchange events over the connection until one of the modules choses to close the connection. <br> In the context of controlling Blinkenlights style displays over a phone connections, events can be keys pressed on the phone or requests to play a certain sound. </p> <h2>Configuration Directory</h2> <p> The configuration of blinker is not stored in a single file, but in a directory structure, reflecting the inner structure of Blinker's modules. This way, every module has got its own configuration directory containing single files each containing one simple setting. It the module has some internel structure, those config setting files are organized in a directory structure underneath the module's configuration directory. </p> <p> The main config directory contains a directory for each module class, e.g. <code>players</code> for movie player modules. Inside, there is an arbitrary number of subdirectories, one for each instantance of the player module. E.g. the <code>players/stereoscope</code> directory in the example configuration (<code>example_cfg</code> directory in the top level) contains the configuration of the movie player for Blinkenlights stereoscope movies. </p> <p> Reconfiguration can happen at runtime by just changing the configuration directory. Blinker will detect those changes and adapt its operation to the new configuration without restart. <br> Sometimes, especially after an invalid configuration has been seen by Blinker, changes are not automatically detected by Blinker. In this case, it is neccessary to <code>touch</code> the parent directory containing the setting file to make Blinker aware of the reconfiguration. (Solving this issue is planned.) </p> <h2>Modules</h2> <p> The following module types are available for instantiation: <ul> <li><a href="canvas.html">Canvas</a></li> <li><a href="etherpix.html">EtherPix</a></li> <li><a href="filter.html">Filter</a></li> <li><a href="loveletter.html">Loveletter</a></li> <li><a href="opprinter.html">Operator Connection Printer</a></li> <li><a href="opsplitter.html">Operator Connection Splitter</a></li> <li><a href="output.html">Output</a></li> <li><a href="player.html">Player</a></li> <li><a href="pong.html">Pong</a></li> <li><a href="printer.html">Printer</a></li> <li><a href="priority.html">Priority</a></li> <li><a href="ratelimiter.html">Rate Limiter</a></li> <li><a href="resizer.html">Resizer</a></li> <li><a href="scaler.html">Scaler</a></li> <li><a href="syncnamesplitter.html">Synchronization Name Splitter</a></li> <li><a href="syncprinter.html">Synchronization Printer</a></li> <li><a href="transformer.html">Transformer</a></li> <li><a href="udp4phone.html">UDP4 Phone Connector</a></li> <li><a href="udp4receiver.html">UDP4 Receiver</a></li> <li><a href="udp4sender.html">UDP4 Sender</a></li> <li><a href="udp4syncreceiver.html">UDP4 Synchronization Receiver</a></li> <li><a href="udp6phone.html">UDP6 Phone Connector</a></li> <li><a href="udp6receiver.html">UDP6 Receiver</a></li> <li><a href="udp6sender.html">UDP6 Sender</a></li> <li><a href="udp6syncreceiver.html">UDP6 Synchronization Receiver</a></li> </ul> </p> <h2>Copyright / Copyleft</h2> <p> Blinker<br> Copyright 2011-2019 Stefan Schuermans <stefan@blinkenarea.org><br> Copyleft GNU public license - http://www.gnu.org/copyleft/gpl.html<br> a blinkenarea.org project </p> <h2>Links</h2> <ul> <li> <a href="https://git.blinkenarea.org/?p=Blinker"> Blinker GIT repository </a> </li> <li> <a href="https://git.blinkenarea.org/?p=BlinkenLib"> BlinkenLib GIT repository </a> </li> <li> <a href="https://wiki.blinkenarea.org/index.php/Protocols"> Information about Blinken protocols </a> </li> <li> <a href="https://wiki.blinkenarea.org/index.php/DateiformateEnglish"> Information about Blinken movie file formats </a> </li> <li> <a href="https://www.blinkenarea.org/"> BlinkenArea is a group of people building and operating Blinken stuff </a> </li> <li> <a href="http://www.blinkenlights.de/"> Project BlinkenLights kicked off the whole Blinken story </a> </li> </ul> </body> </html>
