Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-07-03 | Add option to store cue list in a file, and reload it | Thomas White | |
2021-05-28 | Add "cut!" (cut forwards) | Thomas White | |
2021-05-28 | Apply preset for running cue when the playback reverts to ready state | Thomas White | |
2021-05-27 | Set the preset state when cutting between cues | Thomas White | |
2021-05-27 | Calculate presets for all cues when cue list is created | Thomas White | |
2021-05-27 | Calculate tracking when cue list is created | Thomas White | |
2021-05-25 | Set default attribute fade time to zero | Thomas White | |
Rationale: get the lights in position for the current cue. If you want to see them move, set the time yourself. | |||
2021-05-24 | Factorise set-playback-state | Thomas White | |
2021-05-24 | Move preset from fade-times to cue properties | Thomas White | |
2021-05-24 | Add hook for state changes on a playback | Thomas White | |
2021-05-22 | Indicate playback paused via LEDs | Thomas White | |
2021-05-22 | Add 'stop!' and 'back!' | Thomas White | |
2021-05-22 | Add home-fixture!/blackout! | Thomas White | |
2021-05-16 | Remove newly redundant with-fade-times macro | Thomas White | |
2021-05-16 | Fix copy/paste error | Thomas White | |
2021-05-16 | Get rid of time parameter and use clock objects for cross-fades | Thomas White | |
Because we can stop a clock object, but not "gettimeofday". | |||
2021-05-10 | Run cues as single atomic operations | Thomas White | |
This avoids a potential situation where one parameter of a fixture is reconfigured before another, which could (in theory) lead to flickering of lights. | |||
2021-05-10 | Split 'base' module up into 'fixture', 'state' and 'scanout' | Thomas White | |
2021-05-06 | Add GPL boilerplate everywhere | Thomas White | |
2021-04-08 | Neater abstraction for fade types | Thomas White | |
2021-04-07 | Fade colours nicely | Thomas White | |
2021-04-06 | Initial abstraction layer for colours | Thomas White | |
2021-04-04 | Actually fade attribute values (when appropriate) | Thomas White | |
2021-03-31 | print-playback: Return unspecified | Thomas White | |
2021-03-31 | Remove unnecessary exports | Thomas White | |
2021-03-31 | Replace playback implementation | Thomas White | |
The old version was getting too complex. As it turns out, it can be done without duplicating information in the fade-record structure. This way also allows much more flexiblity and is a more clear abstraction. | |||
2021-03-28 | WIP on playbacks | Thomas White | |
2021-03-28 | Add some error checking | Thomas White | |
2021-03-21 | Fix incorrect results when running cues out of order | Thomas White | |
2021-03-13 | Store the real states in a cue list, not the functions | Thomas White | |
This shouldn't be a big memory burden, even lots of large states. It also makes for a more consistent language by allow lighting-state to be used in cue lists, rather than cue-state. | |||
2021-03-08 | Remove home state and abolish fixture-attribute use in states | Thomas White | |
The "home state" has no reason to exist. The home values are already stored perfectly well in the attribute lists of the fixtures. Any time we need to look up a home value, we already have the fixture itself available. This also gets rid of any use of <fixture-attribute> in states. This was confusing me. Better to just pass symbols around and only get the real attribute objects when needed (which isn't very often). | |||
2021-03-07 | Make playback register themselves | Thomas White | |
2021-03-05 | Formatting | Thomas White | |
2021-03-05 | Add "auto move while dark" | Thomas White | |
2021-01-31 | Replace return-unspecified with *unspecified* | Thomas White | |
2020-12-30 | Make set-in-state! private, export set-attr! | Thomas White | |
Two very similar procedures set-attr is more useful since it can handle both attribute names and objects. | |||
2020-12-23 | Add separate fade time for non-intensity attributes | Thomas White | |
2020-11-22 | cut-to-cue-number: Copy the hash table | Thomas White | |
This hash table will become the one which contains the cross-fade functions. Therefore, when we "emphatically" set it like this, it must not be the same table as in the cue state itself. | |||
2020-11-22 | Factorise vector-ref | Thomas White | |
2020-11-18 | Improve syntax for cue parts | Thomas White | |
2020-10-25 | Add set-playback-cue-list! and get-playback-cue-number | Thomas White | |
These support re-loading a cue list for live coding | |||
2020-10-24 | Match cue-part attributes by name as well | Thomas White | |
2020-10-24 | Implement cue parts with different fade times | Thomas White | |
2020-10-23 | fade-up -> up-time, fade-down -> down-time | Thomas White | |
This makes everything consistent: {up,down}-{time,delay} | |||
2020-10-23 | Plumbing for cue parts | Thomas White | |
2020-10-16 | with-fade-times macro | Thomas White | |
2020-10-15 | New record type for fade times | Thomas White | |
2020-10-15 | s/fade-params/fade-record/ | Thomas White | |
2020-10-13 | New way of doing cross-fades | Thomas White | |
2020-09-13 | Add intensity? | Thomas White | |