#81

Thanks!

I won’t be able to look at TR.POL till next week now. I’ll merge the changes then too.

#82

just checked TR.POL and it seems to be working.

basically TR.POL is the polarity of TR.PULSE (TR.P)

when TR.POL = 1, the pulse is 0 to 1 then back to zero

when TR.POL = 0, the inverse is true. 1 to 0 to 1

this parameter is per TR output

2 Likes
#83

D’oh. Ok, that makes sense.

1 Like
#84

can someone point me to instructions on usb scene saving/loading?

Thanks

#85

If you are running beta…

Just insert a usb stick. TT will auto write the Scenes to the stick, root level.

The tricky thing is if you reinsert it and want the TT to READ those scenes, you need to mount the USB stick on your computer and manually remove the ‘s’ from the name that it auto-assigns to each preset file…or else the files will be overwritten next time you insert (behavior which is fine, if your sole intention is to just back-up your files; but I use it to move the files around between different TT’s, so I have to be cautious!).

Sam mentioned he wants to tweak this read/write behavior.

If you aren’t running beta, I believe you have to power down, insert USB, then power up while holding down the program key. Then it will do the above.

#86

just power up with inserted. do not hold program key, which enters firmware bootloader.

#87

oy, right. sorry about the misinformation…

#88

oh not at all-- thanks for helping out!

#89

Thanks,

I am running beta.

Just to clarify then if I want to flash to the newest beta, first I save the scenes to a stick. Then I flash TT to the newest beta but I can’t just insert the stick and get the scenes back, I have to mount the stick and remove all the ‘s’ letters assigned to each scene, correct?

#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