https://github.com/monome/teletype/releases/tag/v2.2.0 Features in 2.2:
NEW: new bitwise ops: &, |, ^, ~, BSET, BCLR, BGET
NEW: new ops PARAM.SCALE min max and IN.SCALE min max to add static scaling to inputs
NEW: blanking screensaver after 90 minutes of keyboard inactivity, any key to wake
NEW: new op: CHAOS chaotic sequence generator. Control with CHAOS.ALG and CHAOS.R
NEW: new op family: INIT to clear state
NEW: new ops: R, R.MIN, and R.MAX
IMP: optional profiling (enable at build time)
IMP: screen now redraws only lines that have changed
FIX: multiply now saturates at limits, previous behaviour returned 0 at overflow
FIX: entered values now saturate at int16 limits
FIX: reduced flash memory consumption by not storing TEMP script Features threads:
Features in discussion:
Bugfixes since 2.1:
MUL now saturates at limits
Screen redraws lines selectively
Removed TEMP script allocation from flash
Entered values now saturate at numeric limits
I now carries across delayed commands
Teletype 2.2 Discussion Thread
This thread is for discussing the addition of features to 2.2, including feature requests. If you have questions or comments about an existing feature proposal, please visit the relevant thread.
A new OP now deserving its own thread:
State Clearing Operators.
RESET clears the scene state to power-up status, including:
October 24, 2017, 6:21pm
PN.INIT to clear patterns
INIT.VARS reset vars, stacks, etc (everything not
KILL or pattern related)
KILL pre-exisitng OP (but maybe give it a new name)
INIT.ALL do everything, i.e. reset to power on state
RESET seems like it would be more useful in the context of sequencers (and is already used in various
i2c related OPs). Might be best to keep the name reserved for that.
Where was it ‘approved’?
Config Menu thread, in the context of vetoing the entire slate of config menu selections.
October 24, 2017, 6:46pm
What are your thoughts about changing the name from
RESET to something else?
Clearly this feature merits some discussion.
State Clearing Operators
A loose end from implementing
IN.SCALE: the operator names!
@bpcmusic had suggested
MAP as an alternative, as scale has a musical meaning.
The pull request
is ready, so discussion on the feature can continue on github for those with an account.
Added to the feature list:
Added a bugfix to cause entered numeric values to saturate at the appropriate limits. (PR #
Alpha 2 Release
teletype.zip (120.4 KB) Changelog
FIX: live mode redraw fixup
Why this release was removed temporarily:
Short answer: compiler bug. Vexed me for a while.
Split this topic
October 29, 2017, 3:52pm
8 posts were merged into an existing topic:
October 29, 2017, 3:54pm
@Leverkusen at @sliderule’s request I moved the
CHAOS discussion to the
i noticed that the shortcut for help screen is listed as
Alt-?. it’s a bit confusing since the actual shortcut is
Alt-Shift-/. perhaps we should allow both
Alt-Shift-/ to avoid confusion? (and it can stay as
Alt-? in the docs).
Alpha 3 Release
teletype-2.2.0-alpha.3.zip (120.5 KB) Changelog
PARAM.SCALE is great.
One question though, is it normal that PARAM.SCALE 1 16 results in a maximum of 15 ?
PARAM.SCALE, does your
PARAM go all the way to 16383?
is a bug in Alpha 3 it seems, as I’m scaling to 1638 4 not 1638 3, but that won’t make a difference if your
PARAM value doesn’t go all the way.
PARAM.CAL.MIN are on the way and will solve this problem, I’ll make bugfix at that time.
Great. Mine goes up to 16340 only.
Yeah, I am seeing slight inconsistencies with PARAM.SCALE as well.
PARAM.SCALE 0 24
yields values between 0 and 23