RELEASED: 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.
8 Likes
A new OP now deserving its own thread: RESET
(approved). State Clearing Operators .
RESET
clears the scene state to power-up status, including:
Variables
Queue
Stack
Delays
CVs
Slews
Script Mutes
1 Like
sam
October 24, 2017, 6:21pm
4
Alt.
P.INIT
/ 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’?
3 Likes
In the Config Menu thread , in the context of vetoing the entire slate of config menu selections.
sam
October 24, 2017, 6:46pm
6
What are your thoughts about changing the name from RESET
to something else?
1 Like
Clearly this feature merits some discussion.
New thread: State Clearing Operators
A loose end from implementing PARAM.SCALE
and 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: bitwise operators !
1 Like
Added a bugfix to cause entered numeric values to saturate at the appropriate limits. (PR #128 )
Alpha 2 Release
teletype.zip (120.4 KB)
Changelog
FIX : missing CHAOS.ALG
entries
FIX : live mode redraw fixup
Why this release was removed temporarily:
Short answer: compiler bug. Vexed me for a while.
1 Like
cmcavoy
Split this topic
October 29, 2017, 3:52pm
13
8 posts were merged into an existing topic: (Teletype) CHAOS
cmcavoy
October 29, 2017, 3:54pm
14
@Leverkusen at @sliderule ’s request I moved the CHAOS
discussion to the CHAOS
thread .
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-/
and Alt-Shift-/
to avoid confusion? (and it can stay as Alt-?
in the docs).
2 Likes
Alpha 3 Release
teletype-2.2.0-alpha.3.zip (120.5 KB)
Changelog
2 Likes
PARAM.SCALE is great.
One question though, is it normal that PARAM.SCALE 1 16 results in a maximum of 15 ?
1 Like
Before executing PARAM.SCALE
, does your PARAM
go all the way to 16383?
There is a bug in Alpha 3 it seems, as I’m scaling to 16384 not 16383 , but that won’t make a difference if your PARAM
value doesn’t go all the way.
PARAM.CAL.MAX
and 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.
For example
PARAM.SCALE 0 24
yields values between 0 and 23