Currently there is a single example config file which serves as a great starting point, but it would be nice to have a few pre-built configs for people to drop in and go.

Some examples:

• One designed entirely around Docker and monitoring container metrics.
• Another designed to look pretty and having an overview of system metrics.

Gracias por su trabajo en este proyecto -

In /examples/index.html

the path to soundfont-player.js is relative to root vs /examples

<script src="/dist/soundfont-player.js"></script>

should be

<script src="../dist/soundfont-player.js"></script>

With that in place, /examples/index.html w

It would be great to be able to build this project, and/or https://github.com/langolierz/c_o_n_j_u_r/ and/or https://github.com/langolierz/ofxVideoArtTools/ outside of the ARM architecture.

The big problem, at least with conjur/the ofx addon, seems to be the OMX dependency.

Being able to build in an emulator, or VM, or docker, or something would be helpful for development times. Has anybody

In the list of dependencies the following libraries are not mentioned:
-lFLAC, -logg, -lvorbis and -lvorbisenc.

If they are mandatory they should be added to the docs. However, it would probably be better to have those codecs as options in cmake.

• structure and format
• compression - gzip w/ brotli or zopfli?
• buffers
  • markdown
  • ChucK code See #7
  • Faust diagrams See #11
• pattern data
  • notes
  • envelopes
  • per-note
  • per-channel
  • per-pattern
  • per-document

salut tout le monde,
j'adore ce projet et je suis en train de bosser sur ma premiere contribution sur github !
Je trouve qu'il serait cool qu'on ait la possibilité de définir des trajectoire pour les clouds de façon à automatiser des dynamiques dans la production du son.
J'ai un peu travaillé dessus déjà, je vais essayer de le mettre sur github .

J'ai ajouté une classe abstraite trajectory d

Currently, NOTE_OFF and NOTE_ON messages ignores the channel. Ideally each channel should have its own state. 16 voices per channel?