Author: Burkhard Ritter
Revision Date: 2013-08-26 07:35:04 UTC

More signals. Code cleanup.

* More signals for communication between Jack thread and GUI thread: transport
  start/stop and tempo changes are now handled via signals.
* Renamed queues to "engineQueue" (signals to the Jack thread) and "guiQueue"
  (signals to the GUI).
* Renamed global "jack" object to "engine". The idea is that we can have
  different engines (Jack, Alsa) with the same interface, making it easier to
  use different engines / Midi backends.
* Removed global "tempo".
* TODO: Tempo does not seem to get saved to the file. Quite generally, I have
  to figure out how my Jack implementation / engine works best together with
  loading data from a file and saving data to a file.

Author: Burkhard Ritter
Revision Date: 2013-08-19 06:27:28 UTC

Control sequencer support in Jack midi.

* Control sequencers now work with Jack midi.
* Only flat slope style is supported for now. Linear slope is probably best
  implemented in the controller class itself.
* Fixed a number of issues with note-on and note-off scheduling.
* Notably, the play-once functionality is still missing from Jack midi playback
  support. Otherwise we are slowly getting there (for the playback part).

Author: Burkhard Ritter
Revision Date: 2013-08-08 03:26:09 UTC

Added more OSC methods.

* two new OSC methods
* with that the experimental extended OSC interface seems to work quite well
  with a custom TouchOSC layout (and a python script "translating" from
  TouchOSC to harmonyseq and back)