andr-ew
commented
3 years ago - _grid.pattern {}:public { sequin = ‘seq’, run = ‘run’, step=’step’ }
- total rewrite of pattern_time
- seq is a blank public table or sequin(<—!?!!)
- incrementation happens in an internal function w/clock which can be set to false for external usage (e.g. running on crow)
- this all relies on public allowing nested tables — if not we gotta go in a different direction (probably just using a custom pattern recorder)
- ok actually the above is probably maybe(not) a better idea - I’m relying a little too much on nest_ to cover crazy ideas
- basically the possible limitation of non-nested tables in public is encouragement to share data with crow in musical terms rather than interface terms - i.e. scale degrees rather than x,y positions, and unique sequences for time & notes which has interesting possibilities
- instead, make public_time !
- keyed targets linked to unique sequins + separation of time
- grid.pattern { target = { cv = , gate = _ } } :public { value = { cv=‘cv_seq’, gate=‘gate_seq’, }, time = { cv=‘cv_time’, gate=‘gate_time’ }, run = ‘run’ }
- this keeps all the useful separation of data points!
- currently cv is the only nested public table which is fine musically (degree+octave) but might not be allowed in public
- solution1: use a 1d value & add the wrap property
- solution2: allow binding a single table value to two public variables
- _grid.value {} :public { ‘deg’, ‘oct’ }
- grid.pattern { target = { cv = , gate = _ } } :public { value = { cv={ ‘deg_seq’, ‘oct_seq’ }, gate=‘gate_seq’, }, time = { cv={ ‘deg_time, ‘oct_time’ }, gate=‘gate_time’ }, run = ‘run’ }
- this opens up nice possibilities with independent messery of scale degrees & octaves
- (( 6 independent sequences ! ))
- public-bound patterns do not change the value of the targets, that’s intended to happen in a crow clock