#90

Yes, you got it! …remove the ‘s’ to get the TT to read.

2 Likes
#91

Submitted a pull request for the documentation for the TELEX modules (TXo and TXi). All have short descriptions; selected complex, new operators have long descriptions.

Used a node parser to validate the TOML as I don’t have all of the prerequisites figured out on my mac to compile it locally.

Hopefully I did things properly. :slight_smile:

Looking forward to moving my documentation here. Right now I’m maintaining in 4 places total. Ug!

Thanks again, @sam!

4 Likes
#92

@sam I opened a pull request for the pattern docs. I’m wondering in hindsight if these got a little wordy, so let me know if you want me to trim them or feel free to hack them up.

One thing I ran into double checking the ops, if you define the pattern length to be 6. The pattern should include indexes 0-5. If you use P.I for any number between 0-5 it will move the index to this location. For all values greater than 5 it moves the pattern index to 6. This seemed a little odd as it is technically out of the range of the pattern, so I just wanted to check if this was the correct intention.

I tested this with both P and PN ops on Beta 9.

2 Likes
#93

Guys im just learning the teletype and really im just faffing about with the 8 scripts that come with the TT - Im wondering - i havent dived into programming the TT because i dont know where to start. Should i wait for the TTv2 to settle for the final release (which i know is very near) then go nuts, or start going through it all which im finding super difficult at present because i dont know whats being changed from V1 to V2…

IM happy to wait and for there to be proper documentation…this is far away from my niormal musical world and will be a challenge but i know its worth it - just looking for some honest advise :slight_smile:

Im on the version of the firmware that shipped with the TT

1 Like
#94

don’t worry about the v2 changes for now. they won’t affect your general usage, particularly if you haven’t gotten into writing your own scripts.

this is what you want: http://monome.org/docs/modular/teletype/studies-1/

it’s probably the best documentation i’ve ever done, and should be pretty fun to work through.

2 Likes
#95

I’ve merged the following PRs

@tambouri and @GoneCaving thank you so much. I was wondering if there were any particular things either of you would like me to do to the Teletype firmware? Say if there was a particular OP you wanted implemented. Nothing too complicated please!

I know @tambouri you’ve mentioned keyboard controls for pattern editing.

No promises as to when it will be done (I’d like to get 2.0 released very soon), and we’ve got a new baby incoming. But I’ll try my hardest to get it done soon.

#96

@bpcmusic just been going through your PR:

This is absolutely my fault for not explaining it properly but…

A bunch of the ops only have prototype_set defined. Every op must have prototype defined, and only if needed prototype_set can also be defined too. (Yep the names I’ve chosen are awful, it’s to do with get and get/set ops in the source code.)

“set” ops are the ops that behave a bit like variables, (e.g. TR.TIME), you can both set the value and retrieve the current value.

To the best of my knowledge, none of the TX ops work like that, right? I can’t retrieve the current value for TO.TR.TIME. In which case everything should be using prototype.

I can make the change if you want me to?

#97

Yeah, I think you’re right, it should be set to 5 rather than 6.

I’m not a big user of P.I / P.L / P.NEXT / P.PREV.

Anyone else care to confirm? If I don’t hear otherwise I’ll make the change.

3 Likes
#98

Thanks. No, nothing right now. Let me know if you want another set of eyes once all the changes have been landed.

#99

I’ll probably take you up on that offer.

If you don think of something later on, send me a PM.

#100

That fix makes sense to me.

1 Like
#101

I’ve made the fix:

Will be in the next release

1 Like
#102

I’ll get to this in the next 24 hours. Apologies - I was pretty confused by the naming convention. :wink:

You are right, 100% of the TXo ops are push the value only ops. The TXi has the ops that retrieve values - and a few that set values with no retrieval.

I’ve a new TXo release that adds some juicy new operators; I’ll submit a separate pull request for that as well.

Finally - a quick question. Is adding an alias for “IF” possible in your current alias architecture? It is a MOD type - which uses a different macro/template from the traditional OP type. I was thinking about doing an alias for a question mark. I kept trying to do it now that we have the new, awesome math ops. :slight_smile: :slight_smile:

3 Likes
#103

Whaaat, confusing… it makes perfect sense to me :stuck_out_tongue_winking_eye:

Anyway tl;dr: Just use prototype for everything.

:+1:

It would be easy enough to do, I probably wouldn’t do it with a macro though. However…

? will always be the ternary operator to me, and that would actually be a really useful addition to the Teletype, it’s something that’s been on my mind for a while.

Thus,

TER x y z

If x is great than 0 return y, else return z. Basically an inline if statement…

So:

IF MOD T 2: CV 1 N 12
ELSE: CV 1 N 24

Can be rewritten without a PRE:

CV 1 N TER MOD T 2 12 24

Or using ? as an alias for TER, plus using % for MOD.

CV 1 N ? % T 2 12 24

That would be powerful because it can be placed in a delay or a stack as it isn’t using a PRE.

Just need to get 2.0 out the door and then I can spend my time on fun things like that. (That and the unified array/arp/quantisation ops that I’ve been waiting to do for ages now.)

8 Likes
(Teletype) Pre-2.1 Operators and Features
#104

Love the idea of a real ternary OP. Sounds yummy!! I’ll leave the question mark alone!

–

I pushed the documentation fixes and an additional pull request with a bunch of new operators for the latest TXo firmware.

Let me know if I need to do anything else to assist!

Thanks again…

1 Like
#105

Ansible docs cut & pasted. I’ll try to get the control flow ops done tomorrow before I cut the “rc1” release.

@scanner_darkly I’m missing docs for LV.CV and CY.CV.

How does this sound…

LV.CV x: get the current CV value for channel x

CY.CV x: get the current CV value for channel x

@bpcmusic I’m missing docs for TO.KILL, do you want to tell me what you want for the short entry and I’ll paste it in.

@Galapagoose do you want the Just Friends / Just Type ops documented? Or is it too beta still?

1 Like
#106

LV.CV and CY.CV look good!

1 Like
#107

I’m out walking the dog. Just saw this. I will send you a copy when I’m back. Thanks!

1 Like
#108

[“TO.KILL”]
prototype = “TO.KILL d”
short = “cancels all TR pulses and CV slews for device number d (1-8)”

Thanks!

1 Like
#109

Control flow done. I’ve also added the missing TO.KILL, CY.CV, and LV.CV.

Only Orca and JF left, they can be done whenever.

I will try to write up a “advanced coding guide” with details on sub commands and aliases once rc1 is out.

5 Likes