#61

i think i get what M! is all about from the 2.0 beta thread, do you want me to take a stab at adding it in?

#62

Go for it.

Both M and M! are get and set. The ā€˜getā€™ does the same thing for both, return the current metronome time in ms (no matter what it is). But the ā€˜setā€™ is different. M only allows you to set it to 25ms or above. Whereas M! allows 2ms and above, with the caveat that it is unsupported and may crash your Teletype (or other devices on the II bus if you send a message to them).

1 Like
#63

@sam added a pull request for the M ops.

I tested making the .pdf/.html locally and ran into a problem w/ the ā€œmakeā€ command which I believe to be related to adding the M! op (as I removed the M! op and it worked fine).

the error from terminal was

pytoml.core.TomlError: (6, 1): msg
make: *** [teletype.pdf] Error 1

Let me know if this works ok on your end

1 Like
#64

I canā€™t try it till tomorrow. But I had a quick look at the PR. You probably need to surround the M! with quotes like so: ["M!"]

1 Like
#65

gotttcha. yep, that did the trick.

thanks!

1 Like
#66

Merged your pull request. Thanks again!

I made some slight tweaks to the formatting in the metronome.md file. Mainly just adding backticks around the code bits. Hope thatā€™s okay.

https://github.com/samdoshi/teletype/blob/docs/docs/ops/metronome.md

2 Likes
#67

I can work on another this wknd, patterns?

1 Like
#68

That would be great. Patterns is one of the longer ones thoughā€¦ take as long as you need. Iā€™m going to busy next week, so I might not be able to merge till next weekend.

There are now PN versions of all the P ops. The first argument they take is the pattern number.

Again youā€™ve got the original docs to crib from: http://monome.org/docs/modular/teletype/

Also, Iā€™ve tried to avoid using ā€˜tracker modeā€™, Iā€™m not sure how others feel, but Iā€™ve referred to it as ā€˜pattern modeā€™.

  • P.N
  • P
  • PN
  • P.L
  • PN.L
  • P.WRAP
  • PN.WRAP
  • P.START
  • PN.START
  • P.END
  • PN.END
  • P.I
  • PN.I
  • P.HERE
  • PN.HERE
  • P.NEXT
  • PN.NEXT
  • P.PREV
  • PN.PREV
  • P.INS
  • PN.INS
  • P.RM
  • PN.RM
  • P.PUSH
  • PN.PUSH
  • P.POP
  • PN.POP
1 Like
#69

I can take another section too.

1 Like
#70

Any preference?

Queue, stack and delay, are all quite short, but would need some introduction to the concepts.

Hardware is all the CV and trigger stuff.

Ansible has a lot of OPs, but theyā€™re all quite straightforward.

Let me know and Iā€™ll post a list.

I donā€™t have much time to do any of this for the next week or so, I may not have time to merge anything either. So if you wanted to take dibs on more than one you could.

#71

Iā€™ll take stack & delay as an opportunity to learn a little more about them along the way!

1 Like
#72

Stack:

  • S
  • S.ALL
  • S.POP
  • S.CLR
  • S.L

Delay:

  • DEL
  • DEL.CLR

None of them have ā€˜setā€™. S and DEL are both mods. Just fill the details in like ops, Iā€™ll worry about how to change the presentation (if needed).

The existing docs are a good place to start: http://monome.org/docs/modular/teletype/

Thank you!

#73

Remaining opsā€¦

Hardware:

  • CV
  • CV.OFF
  • CV.SLEW
  • IN
  • PARAM (alias PRM
  • TR
  • TR.POL
  • TR.TIME
  • TR.TOG
  • TR.PULSE (alias TR.P)
  • CV.SET
  • MUTE
  • STATE

Ansible:

  • KR.PRE
  • KR.PAT
  • KR.SCALE
  • KR.PERIOD
  • KR.POS
  • KR.L.ST
  • KR.L.LEN
  • KR.RES
  • ME.PRESET
  • ME.RESET
  • ME.STOP
  • ME.SCALE
  • ME.PERIOD
  • LV.PRE
  • LV.RES
  • LV.POS
  • LV.L.ST
  • LV.L.LEN
  • LV.L.DIR
  • LV.CV
  • CY.PRE
  • CY.RES
  • CY.POS
  • CY.REV
  • CY.CV
  • MID.SHIFT
  • MID.SLEW
  • ARP.STY
  • ARP.HLD
  • ARP.RPT
  • ARP.GT
  • ARP.DIV
  • ARP.RES
  • ARP.SHIFT
  • ARP.SLEW
  • ARP.FIL
  • ARP.ROT
  • ARP.ER

If the Ansible ops and the Just Friends ones donā€™t get done, that probably doesnā€™t matter for releasing 2.0.

Also, looking at the Ansible ones, the names arenā€™t as consistent as they could be. Not sure what to do about that yet. (If you do attempt to do the Ansible ones, donā€™t worry if the script that builds the documentation complains about unknown OPs.)

#74

if nobody else gets on these remaining ops by tuesday morning iā€™ll get them done, but would hugely appreciate assistance so i can focus on firmware fixes. thanks!

#75

Stack and Delay done (not yet pushed). PIcking up Q.

1 Like
#76

The current docs (1.3) for Q.N are wrong. At some point it might be handy to have a command to read within the queue.

1 Like
#77

Thanks again for the PR :thumbsup:

I made a few small tweaks:

There was an errant backtick causing some issues in the rendering in queue.toml. I also dropped the space before a : as they arenā€™t needed anymore.

I will do any OPs that donā€™t have docs next week. (Not enough free time this week)

#78

Thanks. I wondered about use of ā€œcommandā€ vs ā€œcommandsā€ for the PREs, given the addition of the ā€˜;ā€™ separator. I presume we can edit for things like that, and consistency once all of the pieces are in place?

I might have time for some of the hardware ops on my commute home this evening.

1 Like
#79

Yep, Iā€™m planning on doing a once (or twice) through and sorting out the little things like that once the majority of the content in.

Excellent!

#80

Pull request for hardware. Either TR.POL isnā€™t working in b9, or my understanding of it is incorrect. Either way that piece needs editing!

1 Like