#102

why not:

SCRIPT INIT
SCRIPT MT

?

#103

INIT is an operator already.

9 and 10 make the most sense IMO. The keyboard executes M with F9 and INIT with F10 so it will be coherent.

If the aversion is only for the second script bank, why not just make an operator for the alt scripts to mask their actual number, e.g.:

SCRIPT ALT 1

To run the ā€œalternativeā€ script 1, or maybe a different operator entirely, e.g.:

ASCRIPT 1

Just my 2c.

4 Likes
#104

Seconded with 20ish characters

#105

Makes sense.

I like the ALT script idea.

With all the Telex units, and JF and now ER-301 extending the family of modules that can be scripted from TT having another layer of the 8 scripts is really worth considering. If accessing the second set/layer of scripts was set up in a way where one would be using the ALT key, then having them called ALT SCRIPTs becomes very coherent and intuitive.

1 Like
#106

I like where this is going!

#107

The best thing any of you could do to help this see the light of day is to help write documentation for 2.2.

AFAIK, I have left:

  • Undocumented features
  • Undocumented operators
  • Un-adjusted documentation for changes

The changelog is accurate, but not all of the changes are reflected in the documentation files.

A prospective contributor would only have to:

  1. Scan the changelog for changes that should be reflected in documentation
  2. Investigate if the documentation exists
  3. Update the documentation
    a. Relevant docs/*/*.toml files
    b. module/help_mode.c summaries for built-in help
  4. Submit a pull request

Once 2.2 is released, it will be easier for anyone to submit and test a simple change like this (SCRIPT 9 calling M, etc).

2 Likes
#108

When I type TR.TOG C the third trigger out illuminates as it should.

I enter INIT and all scripts are cleared, but the trigger light remains on until I either enter TR.TOG C or INIT.TR.ALL

My expectation was that INIT would reset everything.

1 Like
#109

It should. If itā€™s missing clearing the trigger states, thatā€™s a bug!

#110

While I can scan for changes and help with documentation there will be parts I wonā€™t be able to do like update the *.c file but at least I can get the documentation ready for someone else to integrate it.

@sliderule if you could point me to your repository?

1 Like
#111

My repository has been merged to monome/master, so you can work from there!

If you note which things are missing from the .c files, thatā€™s half the work done!

Thanks a lot for considering this contribution. :heart:

Edit: OOPS! The documentation files are TOML files. Still easy enough to work with.

2 Likes
#112

Unexpected behavior using Mute:

I would expect the script to fully mute, instead it depends on where the trigger is in the cycle. If the trigger is off the gate I have it triggering goes silent, but if itā€™s open then it locks the trigger open and the gate continues to allow sound through.

Unexpected behavior running a script with a hotkey:

If while a script is muted I caught the trigger in the off mode and I go to run a script the trigger will cycle open, opening the corresponding gate, but the script itself wonā€™t run until I un-mute the script. If I manually run a script that was muted, I would expect for it to either remain muted or that my action will run the script and simultaneously un-mute the script.

#113

Documentation note:

Alt + ? is listed in the Global Key Bindings as the hotkey combo for bringing up Help

In the code it shows the hotkey combo to be Shift + Alt + ? which is what brings it up

#114

mute is for muting input edge-triggered script executions. there is no ā€œstateā€

mute does not (should not, i mean) apply to hotkeys

let me know if iā€™m misunderstanding your report

#115

So it wonā€™t mute a script if the trigger is going high-to-low (positive)? Is this a negative side of the trigger execution?

Didnā€™t mean to imply a connection between mute and hotkeys, the second issue I referred to is when Iā€™m using one of the key bindings to run a script that had been muted and that the trigger opens again but the script doesnā€™t start executing until after I un-mute the script. Itā€™s like it half runs/un-mutes when using the hotkey.

I was under the impression that mute would simply fully mute the entire script and stop the trigger from toggled in an open state (which is what I think the manual refers to as the positive edge or when low-to-high).

#117

My understanding is that mute is only for the trigger inputs. Any other means of running a script, either by calling it explicitly

SCRIPT 2

or using the hotkey, will still run the script as normal.

#118

My suggestion would be to think of Teletype a bit like the ER-301 in terms of it being in constant development. There is a lot of information out, but it it evolving, and sometimes difficult to figure out what is what.
That said: the studies and extensive manual all apply and are useful in learning. I would say going through the series of studies is a good path. Only after that it would make sense to explore new additions to code.

1 Like
#119

This is nearly exactly how I see things and am working through it all. The user manual and the studies are my constant companion, though I wish I could edit the studies for things that need updating or greater clarification for those who come after me. Just as Iā€™m signing up for a soldering class, Iā€™m starting to think Iā€™ll have to explore some C coding skills at some point too.

#120

I have the script references on my desk at all times. Mainly for when I need to confirm my ideas, but also regularly finding and introducing new concepts.

I have been using teletype since day one, and still find it useful to be able to reference the docs, especially since new ideas are being introduced to the environment. But again, just like re-301, you can accomplish a lot, even with the awareness that you are actively utilizing only a fraction of the potential. Which is truly vast (in both instances)

2 Likes
#121

I only recently acquired Teletype and I am still learning it; Iā€™ve been having a blast so far. To me one of the most convenient thing about it was the integrated help pages as they allow to check the reference really quickly. Having a short explanation of every operator and their parameters is really useful ā€” sometimes I wish it was a bit more detailed regarding the parameters. I donā€™t know whatā€™s done or planned for 2.2 (Iā€™m not even running it yet, got to hunt that weird A to A USB cable), but detailed help pages for grid ops would be extremely useful as those seem to have a lot of parameters.

Edit: my unit was ordered from TechnoSynth (small MontrƩal based distributor) in December 2017 and shipped with Teletype 1.1 installed

1 Like
#122

Your teletype should have shipped with the A to A cableā€¦