Clojars release 0.1.3

Although not that much has changed in the core project, the ability to convert QLC+ fixture definitions will be helpful enough to new users that it is worth making a release.

Changes:

• Separated OLA communication into its own project, ola-clojure.
• Added ability to translate fixture definitions from the format used by QLC+ to help people get started on defining fixtures.

Clojars release 0.1.2

This release primarily improves integration with more environments and configuration flexibility.

Changes:

• Allow configuration of an alternate host for the OLA daemon (primarily for Windows users, since there is not yet a Windows port of OLA).
• Flesh out the command-line arguments when running as an executable jar.
• Allow a list of files to be loaded at startup when running as an executable jar, in order to configure fixtures, shows, effects, and cues.
• Support syncing to Traktor’s beat grid with the help of a new custom controller mapping.
• MIDI sync sources are now always watched for, and can be offered to the user without pausing first.

Clojars Release 0.1.1

This release went in a different direction than anticipated, and primarily supports the development and release of afterglow-max.

Changes:

• Forked the Protobuf related libraries to make them build Java 6 compatible classes, so afterglow-max can run inside the Java environment provided by Cycling ‘74’s Max.
• Added the ability to register for notifications about changes in cue status and show variable values.
• Fixed crashes in the Ableton Push interface when trying to adjust the value of a cue variable which had not yet been set to anything.
• Made the meaning of the :start attribute of cue variables simpler and more consistent.
• Cue variables which respond to aftertouch now also respond to initial velocity, and the related configuration attributes have been renamed to :velocity to reflect this increased generality.
• Creating a show can optionally register it with the web interface by passing a description with :description.
• Now cleans up thread-local bindings stored by the web REPL when sessions time out.
• Improved the detection of project name and version number so they work for afterglow-max builds too.

Initial public release

Although far from finished, and development is still moving quickly, Afterglow is ready for the world to start exploring. I would like to find out what parts are interesting, what directions other people would like to see it grow, and what parts of the documentation most need reinforcement and clarification.

The next areas I plan to work on are the show visualizer, so that people who don’t yet have actual lighting hardware (or who don’t have convenient access to it, which often describes myself) can still design and test effects and shows, and compound cues and cue lists, to round out the basic features that other, non-algorithmic light show software offers, to help people come up to speed quickly when they are considering moving to Afterglow.

Beyond that, hopefully other people will have opinions to share! The wiki is a great place to start doing that.