Just finished reading through this and looking forward to trying it out, but Iâm a bit confused by the description for trigger input 1.
It reads:
Ramp up CV 4 (level) and assign CV 2 to the current value of CV 1. This is basically a sample and hold.
with the corresponding script
CV D V 10 CV B C
Should that second line actually be CV B A or am I missing something? I donât see where C is assigned a valueâŚ
i have one question regarding âworkingâ pattern. Itâs general and not script-specific, right ?
So what happens if two scripts are triggered at the same time accessing to 2 different patterns ?
yes indeed, typo here. it should be
CV 4 V 10
CV 2 CV 1
if you want to work with two patterns, youâll need to set P.N before doing a âworking patternâ specific command, to make sure youâre using the correct pattern.
So if you had a fast triggering script that was using pattern commands running at the same time as a slow triggering, slow running (long delays in the script) script â you would have to possibly refresh the P.N command in the slow running script each time it set a pattern specific value to make sure it wasnât taking the commands from the faster running script?
If thatâs true, to get around that you could use the PN commands, but is there somthing like that for P.NEXT etc?
"Attributes
SHIFT-L set LENGTH of current pattern to position"
So, we donât need to use INIT scripts to define pattern lengths on scene load, necessarily? Will the pattern data from tracker mode be read at this time also?
This could save some valuable linesâŚ
the âworking patternâ is global, so yes, if P.N is changed with a script and then another script uses P.NEXT, itâll be according to whatever P.N is currently set to. but each pattern keeps track of its own playhead/etc so if youâre trying to do multi-P.N stuff, just be sure to set P.N prior to P.NEXT/etc. you can use PN instead but you lose functionality of the working-pattern ops.
yes there are various ways to set length, and length is stored with the pattern. so yes, saved space. i was being explicit in the script.
Not sure if the Studies will be updated at some point, but I found that if youâve not been into the manual yet and you start with the Studies, by the time you get to Part 5 and are about to learn about Patterns you get that you are editing patterns and so near the end of the page when the Tracker is first mentioned it feels like itâs supposed to be another interface.
The manual makes it clear that the Tracker is the Pattern editor so there is thatâŚfor those who read manuals first 
Iâm new to Teletype and have also been doing the studies. It seems to me that itâs intentional that the tracker is not revealed immediately. Brian is trying to have the reader conceptualize the numbers first, setting up that moment when you âconnect the dotsâ between patterns and the tracker.
The tracker is a different interface in a way⌠the visualization of the list (as a data structure) of numbers that we have been working with. Thinking about the live mode/scripts/tracker, I see all of them as different interfaces we use to manipulate the data floating around in the memory of the Teletype. With that being said, I think the only thing that might need to be updated is that tab (instead of tilde) key is how you now navigate to the tracker?
After doing that study, Iâve found that the most useful thing for me was the 4track scene (tt03 of the default scenes). It was helpful to get me going on the patterns and tracker, as you can start using it right away, triggering the 4 patterns.
Lots to explore!
the community decided on the rename, and the studies need updating-- in fact, if you have a github account, itâd be very helpful to file issues there as forum reports tend to get lost: https://github.com/monome/docs/issues
also, iâd generally suggest people start with the studies. they are designed as a sequential building of knowledge-- the manual is more of a reference.