Closed KingaJanicka closed 5 months ago
The basic sequencer will consist of isobar iso.Psequence()
that will hold values 1 for gate on and 0 for gate off. This will be advanced by the tick_callback()
and will send a prebaked osc messages for both on and off events.
This sequencer needs to be connected directly to the pad state.
I want to use different sequencers for gate/pitch/accent/mute information and then assemble them later into one message myself so I can have all of those be different lengths.
It looks like we might have issues with baking the sequence index into the sequence itself but I think it's not an issue as the sequences will really only advance forwards. so simple counters should suffice - could also use PCurrentTime()
for this in patterns or add_event_callback()
in timeline/track.py
made clock faster, we could use this to get the underlying 480ppqm clock - along with previously mentioned PCurrentTime()
and/or add_event_callback()
this would be used to sync sequences
added a basic trigger sequencer in commit ade7b80
closing
started in 71730e4, the code for warpseq that has been added should work but we're focusing on visual feedback for now