v0.2.1

Tempo Out follows the music faster, and stops sending nothing (#5). This follows the first report from a real rig.

• A change of music now reaches Resolume in about 4 s, as one message. v0.2.0 read the tempo every second, but only sent once several readings from a six-second window agreed. A change took 5–8 s (about 11 s on a crossfade), and small changes went out as two to four messages, with the values in between. Now, once a tempo is locked, a shorter 3-second reading also runs. A clear change is accepted as soon as two of those readings agree. Halving, doubling and other related-tempo jumps still take the careful path.

• Steadier. The tempo sent is the average of up to eight agreeing readings, so steady music no longer nudges Resolume back and forth.

• It no longer sends nothing for reasons it can fix:

  • an instance with nothing to send gives up the job to one that has a tempo;
  • a reading from before a silence no longer comes back afterwards;
  • when the new track isn't one it's confident about, the status row says HOLD instead of the old tempo with OK;
  • OVERRIDDEN shows when something else changed Resolume's tempo.

  Music it never gets confident about still leaves Resolume where it was. To see why, set Tempo Source to Detected and read the plugin's log.

What is verified

• Offline, with rendered grooves against a fake Resolume:
  • a hard cut goes from 6 s to 4 s (median and worst), one message per change;
  • wrong sends after a change go from 5 to 0, and noise still sends nothing in 72 runs;
  • steady re-sends across 150 grooves go from 29 to 1.
  • Each new check fails under the v0.2.0 rule it replaces.
• On Windows, the Arena gate on Resolume Arena 7.27.1 passed 9 of 9: all 28 controls match and 8 move the picture.
• Not verified: nothing has run in Resolume with real audio.

Full Changelog: v0.2.0...v0.2.1