another x 1000
https://learnrubythehardway.org/book/intro.html has this and other pieces of good advice that really helped me jump into learning TT.
but it for sure took me some time to settle into the right mindset. I jumped on any musical output I got and didn’t press on past basics for a while. eventually it clicked and lately, I’ve actually gone into sessions as “building”-focused vs “music”-focused, where I don’t patch a single cable and I just focus on the flow of data.
what do I want to happen, what control do I want to have (or not)? how do I want the exchange of action + reaction to play out?
idk if this helps, but sometimes I’ll write ideas in a notebook for TT that flow like:
- r beny’s sequences aren’t straightforward; fuzzy clock?
- how do I add accent notes/shamble to my sequences?
- basically need an occasional note between notes…
- replay last-played note right before next note…between metronome clicks
- delay replaying the last note by a half metronome click
Which leads to this:
CV 1 N PN.NEXT 0 —> plays next note in the pattern on a trigger
DEL / M 2: CV 1 N PN.HERE 0 —> replays that note a half metronome click later
I did the thing I wanted to do!
Now I listen to that, realize it needs more variety, so maybe I make the metronome divisor a random number (which prompts me to look up RAND). Maybe I need the replay 40% of the time, so I try to throw a PROB 40: in front of that and see what happens. If it doesn’t work, I can sort out why not and how it could. It’s small steps.
Working toward concrete goals (either an event or module replication) really helps structure the learning and more importantly, gets you asking questions.