Teletype 2.0 documentation

sam · 2017-06-02T17:49:54.161Z

tambouri:

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’ve made the fix:

github.com/samdoshi/teletype

set P.I and PN.I to less than pattern length if too long

by samdoshi on 05:48PM - 02 Jun 17 UTC

changed 2 files with 4 additions and 3 deletions.

Will be in the next release

bpcmusic · 2017-06-02T20:36:09.029Z

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

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.

sam · 2017-06-02T20:57:15.504Z

bpcmusic:

I was pretty confused by the naming convention.

Whaaat, confusing… it makes perfect sense to me

Anyway tl;dr: Just use prototype for everything.

bpcmusic:

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

bpcmusic:

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.

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.)

bpcmusic · 2017-06-03T04:43:28.242Z

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…

sam · 2017-06-04T19:44:29.358Z

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?

scanner_darkly · 2017-06-04T22:13:47.827Z

LV.CV and CY.CV look good!

bpcmusic · 2017-06-04T22:27:12.102Z

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

bpcmusic · 2017-06-05T00:01:41.560Z

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

Thanks!

sam · 2017-06-05T12:33:53.911Z

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.

scanner_darkly · 2017-07-12T02:14:00.250Z

getting an error trying to build docs:

    print(f" - WARNING: {name} - no prototype entry")
_______________________________________________^
SyntaxError: invalid syntax```

i might be doing something wrong - i'm running `make teletype.pdf` from docs folder in bash for windows 10. do i need to install anything else?

sam · 2017-07-12T06:06:52.448Z

Yeah there are a few bits and pieces to install, I’ve written instructions for OSX, but never quite got round to the Linux instructions. I’ll try to find some time today or tomorrow.

(Thanks for the Orca docs, just in time too, I’ve just been updating the builtin help docs, which is the only thing I’ve got left to do before we can release 2.0)

sam · 2017-07-12T10:24:40.886Z

Can you tell me the output from python3 --version please?

tehn · 2017-07-12T12:54:56.655Z

i am now back and (finally) able to prioritize helping to get 2.0 released with finished docs. is there anything you’d like to specifically task me with?

scanner_darkly · 2017-07-12T14:37:02.801Z

for some reason i have different versions on my laptop vs desktop… 3.5.2 on laptop and 3.4.3 on desktop. i get the same error on both when trying to build docs.

sam · 2017-07-13T10:53:49.466Z

Orca ops merged in (thanks @scanner_darkly)

github.com/samdoshi/teletype

docs for orca ops

by scanner-darkly on 11:52PM - 11 Jul 17 UTC

1 commits changed 2 files with 87 additions and 0 deletions.

(I’ll come back to the python stuff later on today)

sam · 2017-07-13T12:29:02.113Z

tehn:

i am now back and (finally) able to prioritize helping to get 2.0 released with finished docs. is there anything you’d like to specifically task me with?

If you could help out with this, that would be grand:

Teletype 2.0 beta (release candidate 2 released 13th July 2017) Monome

Hello all. I’ve got a new version to upload but I can’t seem to edit the first post anymore… A bit of Googling points me towards: https://meta.discourse.org/t/free-to-edit-post-at-any-time/35516 @tehn, any chance for an increase on the time limit so that I can make one (last) edit for rc2.

Once I’ve got rc2 uploaded I’ll discuss plans for getting the final version out the door (hopefully this weekend).

scanner_darkly:

for some reason i have different versions on my laptop vs desktop… 3.5.2 on laptop and 3.4.3 on desktop. i get the same error on both when trying to build docs.

Okay, we need python 3.6 or greater, luckily it is possible to have multiple versions of python installed, but it is a bit more complex making sure that the right version is used.

Can you give me some info about the version of Ubuntu you’ve got installed in WSL? Run the following:

lsb_release -a

scanner_darkly · 2017-07-13T14:53:50.466Z

on desktop:

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty```

on laptop:

```No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.2 LTS
Release:        16.04
Codename:       xenial```

not sure why they're different - i probably need to update it on my desktop...

sam · 2017-07-13T15:19:30.913Z

Thanks for that. Unfortunately Python 3.6 is not directly available from the Ubuntu 16.04 repos.

You’ve got 2 choices…

Either wait a bit for more Linux options to become available for WSL (see here and here, WSL apparently supports multiple installed distros now).

Or, we can install Python 3.6 onto 16.04 with either a PPA or using pyenv.

The PPA route will teach you more about Ubuntu (as they are specific to it), whereas pyenv is a much more generic Unix solution that will teach you more about Python infrastructure.

scanner_darkly · 2017-07-13T19:14:27.921Z

thanks @sam! i’m a bit reluctant to use either option to be completely honest was more curious about generating docs, not likely something i’ll do often, and for ops i’m able to execute op_enums.py from windows without any issues.

so i thought i’d check if i could get docs to work with python for windows, managed to download all the required packages and latex for windows, and was able to build the html version! for pdf ran into another issue, i don’t have helvetica and menlo fonts, updated latex_preamble.md to use different fonts and i can generate pdf file too now.

sam · 2017-07-13T19:19:03.514Z

scanner_darkly:

i don’t have helvetica and menlo fonts, updated latex_preamble.md to use different fonts and i can generate pdf file too now.

If you pull in the latest code for RC2 it has the Roboto TTF files included to stop that issue.

I’m glad you’ve got it working on Windows with a workflow that you’re comfortable with.