Topic: 32-step sequencing without meta pattern
Hello,
just like to share and get some feedback for optimizing/expanding my first scene created for kira. Im a bloody beginner in teletype programming so Im sure there is plenty of space for improvement
.
First I would like to refer to my feature request in another thread. After all I decided to create a workaround with tt.
The scene can simply chain track 1 and 2 to a “32-step track” and you can manually switch on the grid between track 1 and 2 as usual for editing first 1-16 and second 17-32 steps without automatic switching between patterns, which I often prefer while composing, compared with the workflow with metapatterns - which of course also does a great job in a lot of live usages. CV of all notes will be redirected to tt`s CV1. Beside this you also have the ability to adjust the clock speed (even to zero for stopping) with the param knob. (Triggers from Ansible could be also summarized and outputted from TR 1 of tt in $ 1)
As it`s only a simple workaround with some disadvantages I like to read your ideas:
- Longer or continious data (like glide) can
t be emitted of tts CV1 as it is only a momentary rec. of ansibles CV1+2. Is there a possibility to continiously forward those data or am I forced to solve this outside the monome ecosystem?
- There could be done some other improvements like simple adjusting the complete length of track 1 and 2 via scripts. (Of course you would have to change the lengths manually for kira as well.)
- You are welcome for other thoughts.
It`s perhaps not worth at all, but it was fun and interessting to me that I could realize this behavior by myself…
KIRA: START+STOP 32 LENGTH
#1
SC.CV 1 ADD KR.CV 1 KR.CV 2
CV 1 ADD KR.CV 1 KR.CV 2
#2
#3
#4
#5
#6
#7
#8
#M
M SUB 1000 RSH PARAM 4
IF > PRM 50: TR.P D P.NEXT
IF P.HERE: KR.MUTE 2 1; $ 1
ELSE: KR.MUTE 2 0; $ 1
IF P.HERE: KR.MUTE 1 0
ELSE: KR.MUTE 1 1
#I
TR.TIME D 5
KR.POS 0 0 0
P.I 0
P.L 32
#P
32 0 0 0
1 1 1 1
0 0 0 0
63 63 63 63
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
1 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
#G
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0000000000000000
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
tt30s.txt (1.2 KB)