(Teletype) 2.2 Release

teletype
pinned #2
0 Likes

#3

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

#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

#5

In the Config Menu thread, in the context of vetoing the entire slate of config menu selections.

0 Likes

#6

What are your thoughts about changing the name from RESET to something else?

1 Like

#7

Clearly this feature merits some discussion.

New thread: State Clearing Operators

0 Likes

#8

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.

0 Likes

#9

Added to the feature list: bitwise operators!

1 Like

#10

Added a bugfix to cause entered numeric values to saturate at the appropriate limits. (PR #128)

0 Likes

#11

Alpha 1 Release

Status: Superseded by Alpha 2

Changelog:

  • 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
  • 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
3 Likes

#12

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

(Teletype) Monitoring Live Variables (Done)
split this topic #13

8 posts were merged into an existing topic: (Teletype) CHAOS

0 Likes

#14

@Leverkusen at @sliderule’s request I moved the CHAOS discussion to the CHAOS thread.

0 Likes

#15

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

CHAOS Operators
#16

Alpha 3 Release

teletype-2.2.0-alpha.3.zip (120.5 KB)

Changelog

  • CHAOS bug fixes
2 Likes

CHAOS Operators
#17

PARAM.SCALE is great.
One question though, is it normal that PARAM.SCALE 1 16 results in a maximum of 15 ?

1 Like

CHAOS Operators
#18

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.

0 Likes

#19

Great. Mine goes up to 16340 only.

0 Likes

#20

Yeah, I am seeing slight inconsistencies with PARAM.SCALE as well.
For example

PARAM.SCALE 0 24

yields values between 0 and 23

0 Likes

#21

Same comment as above. If your naked PARAM at fully-clockwise does not reach 16384, then the maximum value yielded by a scaled PARAM will be off-by-one.

0 Likes