aboutsummaryrefslogtreecommitdiff
path: root/guile/starlet/playback.scm
AgeCommit message (Collapse)Author
2021-04-04Actually fade attribute values (when appropriate)Thomas White
2021-03-31print-playback: Return unspecifiedThomas White
2021-03-31Remove unnecessary exportsThomas White
2021-03-31Replace playback implementationThomas 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-28WIP on playbacksThomas White
2021-03-28Add some error checkingThomas White
2021-03-21Fix incorrect results when running cues out of orderThomas White
2021-03-13Store the real states in a cue list, not the functionsThomas 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-08Remove home state and abolish fixture-attribute use in statesThomas 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-07Make playback register themselvesThomas White
2021-03-05FormattingThomas White
2021-03-05Add "auto move while dark"Thomas White
2021-01-31Replace return-unspecified with *unspecified*Thomas White
2020-12-30Make 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-23Add separate fade time for non-intensity attributesThomas White
2020-11-22cut-to-cue-number: Copy the hash tableThomas 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-22Factorise vector-refThomas White
2020-11-18Improve syntax for cue partsThomas White
2020-10-25Add set-playback-cue-list! and get-playback-cue-numberThomas White
These support re-loading a cue list for live coding
2020-10-24Match cue-part attributes by name as wellThomas White
2020-10-24Implement cue parts with different fade timesThomas White
2020-10-23fade-up -> up-time, fade-down -> down-timeThomas White
This makes everything consistent: {up,down}-{time,delay}
2020-10-23Plumbing for cue partsThomas White
2020-10-16with-fade-times macroThomas White
2020-10-15New record type for fade timesThomas White
2020-10-15s/fade-params/fade-record/Thomas White
2020-10-13New way of doing cross-fadesThomas White
2020-09-13Add intensity?Thomas White
2020-09-10Add trackingThomas White
2020-09-07Un-export track-state, export qnumThomas White
2020-09-06Make cue 0 implicitThomas White
2020-09-06Add utils moduleThomas White
2020-09-06Rearrange for trackingThomas White
2020-09-05Store cue list as a vector instead of a listThomas White
Because we're about to do a lot of backwards/forwards tricks.
2020-09-05Move some things aroundThomas White
2020-09-04Move cue list stuff to playback moduleThomas White
Also, sketch out new way of doing cue lists
2020-09-03Return unspecified from 'go!' and 'cut-to-cue-number!'Thomas White
2020-08-23FormattingThomas White
2020-08-22Minimise exportsThomas White
2020-08-21Get rid of 'expand-state'Thomas White
From now on, states will always be real states (not functions evaluating to states). Cues, however, contain functions evaluating to states.
2020-08-17Implement 'go'Thomas White
2020-08-16Split playbacks into separate moduleThomas White
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-26 16:26:02 +0000