That was helpful. One thing that page does that isn’t helpful to a newcomer is that it puts stuff at the top which they don’t need to know-- update features, version history, etc. While that’s all useful information at some point, if what you are trying to find out is, “what does it do NOW” it takes far to long to get started on that to the point that many times I ended up on that page in frustration thinking I was looking at release notes and not a comprehensive manual. I’d put all that stuff on a separate release-notes page and just have a link to it, up top at this page maybe, but not lead off with big bunches of irrelevance to the newcomer, who doesn’t care what version 2.2 did or didn’t do.

Well, as you probably realized, I didn’t write the manual :slight_smile:

1 Like

LOL! I tend to read manuals sporadically, just to look up specific information I want to know. Don’t think I’ve ever read a manual cover to cover…

But here’s a question maybe you know the answer to-- the Pattern buffer cells are 16 bits, right? Please say their 16 bits. Please, please, please say they’re 16 bits. If they’re only 8 bits I’m in big trouble with my Markov modeler…

They are 16 bits! Greater than 15 bits wraps to negative numbers…

NB: I never read the manual through myself, I use “search” for stuff when I need it…

1 Like

You need spaces after the semicolons. And I think the line limit is 31 characters, so
A + X * 12 Y; X % A 64; Y / A 64
might still be a no-go.

It may be possible to use the Grid OPs (without a Grid present) as a 8x16 pattern space, if that helps. You can initialize virtual faders onto each single cell, I believe, and store a 16-bit value in them (though it defaults to 15-bit range).

Another possibility is hacking the firmware to extend the pattern dimensions to meet your needs. Or, more broadly helpful / less hacky, a new OP for addressing all 4 patterns sequentially could be a useful addition to the firmware.

Updating the Teletype:

-Will a USB-C to USB-A cable work?

-Any chance to use anything other than a USB-A <-> USB-A cable?

Thanks!

USB C negotiates down to the highest common spec (fully backwards compatible). It would probably work fine.

1 Like

Pro tip: if you need 2 more characters on a line, edit the script on a computer and upload it to the TT.

1 Like

20 characters of why does that work?!?

My guess is the editor does not account for the script number and space at the beginning of the line. I have made scripts with maximum characters via a computer then could not edit them on the TT and retain all characters.

We’re in “Unethical Life Pro Tip” territory :sweat_smile:

Teletype is a live coding platform, so anything which breaks that paradigm is more like a bug than a feature.

1 Like

Isn’t that reflected on the TT in that you can actually “type a bit off the screen to the right” and still press enter and have the line be both accepted and displayed?

1 Like

I’ve noticed that myself. The limit is 31 characters though, right?

So you can type the last couple of characters blind and it’ll work? Wondered about that…

Hey there! Before I guess at a command and create a headache for myself, I wanted to ask about a similar issue. My PARAM readings go from 0 - 16320. So I set the knob to full CCW and entered PARAM.CAL.MIN but the max value is still 16320. would turning the knob full CW and entering PARAM.CAL.MAX clear that up?

Ended up not working… will try and eliminate other factors.

Sorry if asking something obvious but it was a data cable and not just a charging cable, right?

1 Like

Keeping it obvious is the way to go with tech and me :slight_smile:

Got a USB A to A cable, it worked, but had a very scary moment:

turning off my rack with the cable still attached between TT and computer - the rest of my rack started blinking, as if powered by the USB cable. Any ideas why this could be, anyone?

1 Like

One area that I don’t really understand fully is what is going on with the DEL delay command. I gather the basic use:

DEL 10: J IN

Will delay 10ms before it performs the J IN, then after it does that it’ll process the next line. And it looks like some of the other options, such as:

DEL.X 3 10: J IN
CV 1 J
TP.P 1

Will delay 10ms before the J IN, then another 10ms delay before the CV and another 10 before the TP.P, and then run any subsequent commands without a delay first? (I’m assuming the count includes the J IN).

And DEL.R has a similar syntax as DEL.X but it won’t delay on the J IN, only the subsequent two lines.

But what’s with the “Delay buffer” and DEL.CLR?

Also, I don’t quite understand S and the stack. I noted that the factory Metronome script uses an S.ALL. I gather that’s so you can push some commands on the stack that the Metronome will then call? Is the stack persistent, or does doing this cause the Metronome to clear the command you might push when it executes it? How many commands can you put on the stack? How would this interact with a DEL.X or DEL.R? And will DEL.X transfer across to a script? Example: Could I do:

DEL.R 6 10: SCRIPT 7

And would it then delay for each individual line in script 7? Or only delay once it returns from the script?

DEL will only delay commands on the same line (so lines after that will execute with no delay)

DEL.X will execute more than once.

The delay buffer can hold 16 commands, so if the buffer holds 16 commands already and try to put another command into the delay buffer, the additional command will not be added to the buffer.

Hope that helps…