Modules for use with VCV Rack 2.0, with an emphasis on generative and self-regulating structure. Exploring the region between random and static.

• BASICally: A simple, likely familiar procedural programming language within the context of VCV Rack.
• Drifter: Creates sequences of values that can slowly (or quickly) vary, like a series of points doing random walks connected into a series.
• Fuse: Block, allow, or attenuate a signal passing through, based on the number of triggers observed in a different signal.

A simple, likely familiar procedural programming language within the context of VCV Rack. Can act like:

• a very flexible sequencer
• VCO or LFO
• a wavefolder
• a control voltage utility
• sample and hold
• all of the above and more, simultaneously

Useful for:

• quickly trying out an idea
• simple transformations that would otherwise involve many small utility modules
• non-standard approaches to otherwise straightforward ideas

Note that STYLE is set to "Start on trigger, don't loop".

The examples above are all in this patch. A patch with some simple/strange/silly ideas for other things BASICally can do are in this patch.

While there are other modules with a similar emphasis on "writing code within VCV", BASICally has some interesting differences:

• It intentionally bears a visual resemblance to the BASIC language (albeit a quite limited version of BASIC). BASIC is a language that many people know, once knew, or can pick up by looking at examples.
• The right side of the module is a resize bar; pull it to the right or left, and the code window changes size. Handy for reading those long comments without line breaks and for shrinking the module down to a small size when you don't wish to edit the code. Also, the text window scrolls vertically as you move through it.
• Four different run "STYLES" (see Controls below), giving it the ability to act on a RUN trigger, or to run the most recent working version continuously as you type, or only run while a button or trigger is pressed.
• Edits in the text window become part of the VCV Rack Undo/Redo system.
• You can pick from a (small) number of screen color schemes in the menu.
• Scientific pitch notation is supported (e.g., c4, Db2, d#8). They are turned into V/OCT values.

Always in the form:

variable name = mathematical expression

Set values of the OUT1, OUT2, OUT3, OUT4, OUT5, and OUT6 ports for other modules to read via connected cables. Assignment is also used for setting variables for use elsewhere by your program.

Examples:

' Creates a variable called 'foo' and sets it to 3.0. All values
' in BASICally are floating point numbers.
foo = 3
' Uses the value of the 'foo' variable.
bar = 5 * in1 + foo
' Sets the value of the OUT1 port.
out1 = bar * -0.01
' Sets out2 equal to -1.9. Operator precedence is the same as most other languages.
out2 = 0.1 + 2 * -1
' Set out2 to emit the V/OCT value for middle C.
out2 = C4

• All variables start with the value 0.0 when first read.
• Variables stay available in the environment of a module until the patch is restarted. This is true even if the code that created the variable has been removed from the program.
• OUT1-6 are by default clamped to the range -10v <--> 10v. You can make individual OUT ports unclamped in the module menu. Input values and internal values are not clamped.
• Scientific pitch notation is supported (e.g., c4, Db2, d#8), turning them into V/OCT values. So you can use out1 = c4, send OUT1 to a VCO in the default position, and the VCO will output a tone at middle C.

The following are operators and functions you can use in mathematical expressions:

• "+", "-", "*", "/" -- add, subtract, multiply, divide. Note that dividing any number by zero, while undefined in mathematics, is defined by BASICally to be 0.0.
• "<", "<=", ">" , ">=", "==", "!=" -- comparison operators. Most commonly used in IF-THEN[-ELSE] statements.
• "and", "or", "not" -- Boolean logic operators. For purposes of these, a zero value is treated as FALSE, and any non-zero value is treated as TRUE.

Note on time() and time_millis(): The resolution of these clocks appears to be system-dependent. On my Windows system, for one, the minimum non-zero interval between calls to time_millis() is about 16 milliseconds. This makes them unsuitable for making, say, consistent 40Hz signals.

Always in the form:

WAIT mathematical expression

Specifies a number of milliseconds for the program to make no changes. The OUTn ports maintain their voltages at the values they were at when the WAIT started.

Examples:

' Waits a full second.'
wait 1000
' Wait half of one thousandth of a second.
WAIT 0.5
' wait [in2] tenths of a second.
wait in2 * 100
' The shortest possible WAIT. Exactly one sample.
WAIT 0
' Negative values are treated as if the were zero.
WAIT -3

If you find that your BASICally module is using a lot of CPU, even a short WAIT will help make the module use less CPU.

A single quote (') followed by a space indicates that the rest of the line will be treated as a comment only to be read by the user. Comments have no effect on the execution of other statements.

Examples:

out2 = 3.250 ' A C4 note.
out2 = c4 ' Also a C4 note.
WAIT 200 ' Pause for 1/5 of a second.
' The next line can be turned on just by removing the initial tick (').
' out1 = 2.3 * in1  ' Look, I'm live-coding!

Simple one-dimensional, 0-indexed arrays are available. The index will have floor() act on it internally. Using an index less than zero will be ignored.

a[3.3] = 2.2  ' Same as a[3] = 2.2
a[-1] = 6     ' Ignored, will have no effect.

You can set a series of values in a array quickly by specifying just the initial index, and enclosing the series of values with curly braces '{}' For example, this will assign value to b[1], b[2], and b[3]. Note that these values do not need to be constants, as some other languages require.

b[1] = { -5, sin(in3), 2.2 }

Reading from an array works the same; The index will have floor() act on it internally. Using an index less than zero will return a value of 0.0. Accessing any index within the array that hasn't been set will also return a value of 0.0.

out1 = b[1]

Unlike BASIC and many other languages, there is no need to set the size of the array before using it (i.e, there is no DIM() statement.)

There are four kinds of IF statements:

IF conditional expression THEN

...Statements for True...

END IF

or

IF conditional expression THEN

...statements for True...

ELSE

...Statements for False...

END IF

or

IF conditional expression 1 THEN

...Statements for expression 1 is True...

ELSEIF conditional expression 2 THEN

...Statements for expression 2 is True...

ELSEIF conditional expression 3 THEN

...Statements for expression 3 is True... (You can have multiple ELSEIF clauses.)

END IF

or

IF conditional expression 1 THEN

...Statements for expression 1 is True...

ELSEIF conditional expression 2 THEN

...Statements for expression 2 is True...

ELSEIF conditional expression 3 THEN

...Statements for expression 3 is True... (You can have multiple ELSEIF clauses.)

ELSE

...Statements for expression 3 is False...

END IF

The conditional expression evaluates to False if it equals zero; it evaluates to True otherwise.

Examples:

if in1 > 3.7 then
  out1 = in2 * 0.01
  out2 = sin(in2)
end if

if in1 > 3.7 or foo == -1 then
  out1 = in2 * 0.01
  out2 = sin(in2)
else
  out1 = 0
  out2 = 0.5
end if

if a == 5 then
  out1 = in2 + 1
elseif a == 4 then
  out1 = in2
elseif a == 3 then
  out1 = in2 - 1
else
  out1 = in3
end if

Useful for repeating statements for some limited number of times. There are two kinds of FOR loops:

FOR variable = expression TO expression ...Statements... NEXT

(variable goes up by one every loop)

or

FOR variable = expression TO expression STEP expression ...Statements... NEXT

(variable goes up by the STEP expression every loop, or down if it's negative)

Examples:

for i = -5 to 5
  out1 = i
  wait 100
next
' out1 will be: -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5 and then leave the loop

for i = 0 to 5
  for j = 0.4 to 0 step -0.1
    out1 = i + j
    wait 10
  next
  wait 100
next
' out1 will be: 0.4, 0.3, 0.2, 0.1, 0, 1.4, 1.3, 1.2, ...

Note that the TO and STEP expressions are only computed when entering the loop.

dest = 10
leap = 2
FOR j = 0 TO dest STEP leap
  dest = .1  ' Has no effect on loop.
  leap = .1  ' Also no effect.
  out1 = j
  wait 10
next
' out1 will be: 0, 2, 4, 6, 8, 10 and then leave the loop.

While in a FOR loop, there may be circumstances when you want to change what statements to run. There are two special ways to do this.

CONTINUE FOR moves execution back to the beginning of the loop, changing the variable value as it normally would.

EXIT FOR, in contrast, moves to the statement after the NEXT, quitting the loop entirely.

Examples:

for i = 0 to 5
  if i == 2 then CONTINUE FOR end if  ' Skips rest of loop when i == 2.
  out1 = i
  wait 100
next
' out1 will be 0, 1, 3, 4, 5, and then leave this loop.

for i = 0 to 5
  if i == 2 then EXIT FOR end if   ' Leaves loop when i == 2.
  out1 = i
  wait 100
next
' out1 will be 0, 1, and then leave this loop.

Similarly, you can use CONTINUE ALL to move execution to the top of the program (or ALSO block).

For the two STYLES that support halting the program, which are:

• Start on trigger, loop
• Start on trigger, don't loop

encountering an EXIT ALL will actually halt the program/block. A trigger to the RUN input or pushing the RUN button will start it again.

"CLEAR ALL" resets all variables to 0, and resets all arrays to empty.

Whenever a "RESET" is executed, it immediately stops processing this sample, and on the next sample each block (see Multithreading, below) will start from scratch. It does NOT change any variable values. This is very similar to the state when you've just typed a character into the editing window and the code compiles correctly, with one exception; recompiling the code makes start() become true, but RESET does NOT make start() become true.

Note that RESET's effect is immediate. For example:

...
IF trigger(in7) OR foo > 20 THEN
  RESET
  out2 = 0
END IF
...

the "out2 = 0" will NEVER be executed.

Note: This section has kind of advanced topics, or at least they have the potential to make BASICally more confusing, especially if you are new to programming in general. You don't need to know this part to make BASICally do useful things for you, so feel free to skip this section the first time you learn about BASICally. But come back later; this may be useful to you soon.

The code style above (one big loop of code that gets repeated) doesn't allow for certain kinds of programs to be easily written, and can be less efficient than required. For example:

• Any initialization code will get executed every time. One can minimize this to an extent by setting and checking an "init" variable being non-zero, but this concept could be better integrated into the language.
• Running two loops with WAITs in them would be diabolically difficult to write.
• Checking for a trigger at an IN port is difficult, and impossible during a WAIT.

To allow BASICally to do these things, version 2.0.6 introduced "multithreading" and "blocks".

There are two kinds of Blocks of code.

ALSO blocks each run continuously, exactly the way the (un-blocked) code examples elsewhere in this manual do. For example:

FOR OUT1 = -5 TO 5 STEP 0.1
  WAIT 100
NEXT

Causes OUT1 to emit a stepped saw wave with a period of 10 seconds.

However, if you wanted the same program to also run this downward saw on OUT2:

FOR OUT2 = 5 TO -1 STEP -0.2
  WAIT 75
NEXT

that would be very difficult. But with ALSO blocks, it's easy.

FOR OUT1 = -5 TO 5 STEP 0.1
  WAIT 100
NEXT

ALSO
FOR OUT2 = 5 TO -1 STEP -0.2
  WAIT 75
NEXT
END ALSO

Now both loops will run at the same time!

The ALSO ... END ALSO is the new part here. Each ALSO block runs simultaneously with all of the other blocks. The ALSO blocks are run in the order that they appear in the program. So in this example:

' Block1
IF IN1 == 0 THEN
  foo = random(0, 1)
END IF

' Block2
ALSO
out1 = foo * 10
END ALSO

Then the foo variable that Block2 uses will be changed when Block1 changes it. They share the same "variable space".

As we see in these examples, if there is code at the top of the program that isn't otherwise in a block, BASICally treats it like an ALSO block. Note that these all work the same:

(some code)

ALSO
(more code)
END ALSO

ALSO
(some code)
END ALSO

ALSO
(more code)
END ALSO

But the following won't compile:

ALSO
(some code)
END ALSO

(more code)

WHEN Blocks are of the form:

WHEN (condition)
(some code)
END WHEN

For example:

WHEN foo > 3
FOR OUT1 = -5 TO 5 STEP 0.1
  WAIT 100
NEXT
END WHEN

BASICally will wait for the condition (in this case, "foo > 3") to be true, and then will start running the FOR-NEXT loop. Once the FOR-NEXT loop has completed, the block will stop running until the condition is true again. All of this is independent of the ALSO blocks; they will continue running simultaneously.

WHEN Blocks are useful when used with the start() or trigger() methods, especially for running the "initialization" code mentioned above:

' A trigger to IN9 resets the speed the notes are played.
FOR n = 0 TO 3
  out1 = note[n]
  WAIT pause_length
NEXT

WHEN start() OR trigger(in9)
IF start() THEN
  note[0] = { c3, g3, c4, c4 }  ' The notes in my score.
END IF
pause_length = random(100, 2000)  '  How fast we play the notes.
END WHEN

Some notes about how this all works under the hood.

Every sample, BASICally does the following:

• Walk through the list of WHEN Blocks, in the order they appear in the code.
• • If a WHEN block is not already running, then the (condition) is evaluated, and if it is true, then the Block is started.
• • If a WHEN block was already running (or was just started in the step above), then it is run for one sample's worth of time.
• Walk through the ALSO Blocks, in the order they appear in the code.
• • Each ALSO Block is run for one sample's worth of time.

BASICally is intended for the very casual user, with the hope that examples alone will suffice to suggest how programs can be written. Because of the UI limitations, detailed error reporting is difficult to provide. But if you hover your mouse over the little red area to the left that says "Fix", it will attempt to point out the first place that BASICally couldn't understand the code.

Programs are typically short. For that reason, this language doesn't need the features that are useful for writing long programs but increase the amount of boilerplate code. Here are a few surprising differences from more robust languages:

• BASICally is case-insensitive. "OUT1", "oUt1", and "out1" all refer to the same variable. "WAIT" and "wait" are identical in meaning. DB3, Db3, and db3 are the same note. I would certainly suggest you capitalize consistently within in your programs to make them easier to read, but BASICally won't insist on it.
• Newlines do not matter, except that comments always end at the newline. The following are identical in meaning:

out1 = sin(in2) * 0.3 + mod(in1, 4)

 out1 =
 sin(in2)
   * 0.3
      + mod(
  in1, 4)

If lines are wrapping around in a way that makes it hard to read, remember that you can resize the code window by dragging the right-side edge of the module.

• Indentation does not matter. That said, even short programs can become more readable to you by using the indentation demonstrated in the examples.

In the case of

wait in2 * 100

the length of time might get shorter or longer if in2 changes while the WAIT has started. For example, if in2 is 10.0 when the WAIT starts, then it will start to wait for 1000 millis. However, if, say, 100 milliseconds later the value of in2 changes to 0.5, then the WAIT is now for 50 milliseconds. What should happen?

What BASICally does is frequently recompute the wait time and then see if the WAIT has already exceeded the new value; if it does, the WAIT ends and the next statement runs. Doing this makes BASICally more responsive to changes from the user.

If this is not what you want, just assign the value to a variable:

pause_ms = in2 * 100
wait pause_ms

Then (in the scenario above) the length of the WAIT will be 1000 millis, and no change to in2 during the WAIT can change that.

Note that this differs from the way FOR-NEXT loops work, where the TO and STEP values are computed only upon entering the loop.

Under the hood, WAIT statements are how BASICally knows to stop running its code and pass control back to the other modules in VCV Rack. If it never WAITed, VCV Rack would hang and eventually the program will crash. Therefore, there are a number of hardwired WAIT 0 lines inserted. For example, consider this program:

OUT3 = 0
WAIT 100
FOR level = 0 To 5 STEP 0.01
  OUT3 = level
NEXT
OUT1 = sin(in2 * in2)

Under the hood, it is turned into:

OUT3 = 0
WAIT 100
FOR level = 0 To 5 STEP 0.01
  OUT3 = level
  WAIT 0   ' There is a hidden WAIT 0 inserted just before every NEXT in a FOR-NEXT loop.
NEXT
OUT1 = sin(in2 * in2)
WAIT 0  ' There is a hidden WAIT 0 inserted at the bottom of the program.

The lit word in the upper left corner indicates whether or not BASICally has figured out how to turn your code into instructions. If it looks like:

then BASICally can run your code. However if it looks like:

Then it cannot run the code as it stands. You can see that the line where it gets confused is highlighted in red.

If you roll the mouse pointer over the "Fix", then BASICally will attempt to describe the first error it found. As you can see here, it can only vaguely tell you where it got confused and why. Note that if the editing window is scrolled away from the line where the error occurs, you won't be able to see the highlight line until you scroll up (or down) to it.

If the red and green colors are hard to tell apart, there is a menu option to change it to blue and orange.

There are four options to determine when the code will run. Three of them rely on the RUN Button and trigger/gate, which are described below.

• Always run -- Will always try to run the latest code in the window that compiled. This is the best state for making changes on the fly and seeing them applied immediately. Also nice for when you are first determining what your code for this module should be. Note that when the code changes, BASICally restart the code from the start of the code.

• Start on trigger, loop -- If not already running, then it waits for the RUN button to be pressed or a trigger to be seen by the RUN input. When the signal to run happens, it will run and "loop", meaning it will when it gets to the last line, it will do a "WAIT 0", and then start again from the top.

• Start on trigger, don't loop -- If not already running, then it waits for the RUN button to be pressed or a trigger to be seen by the RUN input. When the signal to run happens, it will run and then stop when the last line is reached. This is useful for making Sample & Hold behavior; the RUN input becomes the trigger for the Hold.

• Run when gate is open -- While the RUN button is pressed or the RUN input is high, then BASICALLY will run. If the button is released or the input falls low, then the program will stop. As long as the program isn't changed, when the next button press/input high occurs, exection will pick up from where it left off. For example, suppose a five second WAIT starts, and then after 3.5 seconds the button is released. When the button is later pressed, the WAIT will continue for another 1.5 seconds before moving on to the next statement.

You can specify a short title that will appear above the INn ports. This may make it easier to identify what each BASICally module is doing, especially when you've minimized the size.

A small number of choices about text colors.

By default, if BASICally can't understand your code in its entirety, then it will attempt to highlight the line where it stopped understanding your code. It's not terribly accurate, but gives you a sense of where to change your code. If the red highlight is distracting, you can turn it off here.

By default, BASICally uses green and red for the Good/Fix light. In hopes of making the distinction clearer to more people, this option turns those colors to blue and orange, and makes the error line highlighting orange as well.

Normally OUTn values are not allowed to go below -10V or go above 10V; the bulk of VCV Rack modules do not have meaningful uses for values outside of that range. However, values within BASICally can be any floating point number, and it can be useful (especially for debugging a script) to see the true value of a variable in an OUTn. You can clamp/unclamp each of the OUTn ports individually in this menu.

Two modules that can usefully display the unclamped values are ML Modules' Volt Meter and NYSTHI's MultiVoltimetro.

Just in case you're in the middle of coding and you don't want to look up this documentation, there's some hints about the syntax of BASICally, as well as the complete list of math functions. You can click on a particular statement and it will be inserted into your code.

When the module is bypassed, all OUTn ports are set to zero volts.

• Frank Buss's Formula.
• docB's Formula One, which, compared to Formula and BASICally, seems to be very CPU efficient.

Creates sequences of values that can slowly (or quickly) vary, like a series of points doing random walks connected into a series.

• Set this up, and you'll just hear a single tone.
• Now try tapping the DRIFT button a few times, and you'll hear the frequency change.
• The IN signal is the value coming out of the Saw wave, and is shown in the display as a short line moving from left to right along the bottom.
• The OUT signal is the height (Y position) of the line in the display that jumps whenever you press DRIFT at the X position of IN.
• Set the TOTAL DRIFT value to something larger, like 5.0.
• Now press DRIFT; the line moves a lot more now!
• Play with the STYLE knob, which changes the shape of the line in the display and hear how that changes the OUT values.
• There are many more knobs and controls, and they are described below. They long to be twiddled!

More examples can be found in this patch. You can hear the results.

Creating or modifying a series of values you wish was gradually (or drastically) changing - melodies, volume levels, waveforms, CV levels. Note that the use of a Saw wave as the input in the sample rack is just to better illustrate the idea of it being a transformation function; you can put whatever you like into IN. Sine wave, oscillator output, random,... Drifter alters signals, basically.

Here's a video from Pazi K. showing two Drifters being used to simultaneously create the timbre of two sounds and create matching visuals in Etchasketchoscope.

(Someday I'll make a video or two that demonstrates these other notions better.)

The maximum distance, in V, that each point can move along the X-axis (i.e., left-to-right) in one DRIFT event. Setting it to zero locks the points horizontally in place. Higher values allow larger changes each DRIFT. Hint: start small.

Sets the range of the expected inputs and outputs from 0V - 10V or -5V - +5V.

The maximum distance, in V, that each point can move in the 2-dimensional space in one DRIFT event. Setting it to zero locks the points in place. Higher values allow larger changes each time. Hint: start small.

Selects one of two options: Left and right end points stay locked at value zero OR end points drift up and down when DRIFT events occur.

A trigger to the Input or a Button press will cause all of the points defining the output curve to move once, within the limits set by X DRIFT, TOTAL DRIFT, and ENDS.

The number of segments in the steps/line/curve, from 1 (just connecting the end points) to 32. Takes effect at the next RESET.

A trigger to the Input or a Button press resets the line to its starting position, which is all zeroes. This also applies any change to COUNT.

Selects one of three different line types, Steps/Lines/Curves. Changes are applied instantly.

Selects the horizontal position of the point on the line to be selected. Shown on the display as a short line at the bottom of the display.

The vertical position of the line at the position determined by IN.

• If checked - when the rack is saved, the current position of the line will be saved with the rack, and that position will be loaded along with the rack.
• If not checked - when the rack is loaded, the line will always start at all zeros.

If this module is bypassed, then OUT will equal IN.

Block, allow, or attenuate a signal passing through, based on the number of triggers observed in a different signal.

Here the LIMIT is set to 7, and Fuse basically acts like a clock divider, sending out a trigger every seven input triggers and then resetting the count.

Set this up and let it run, and you'll see that each setting of STYLE has a different effect on the relationship between IN and OUT, especially as the count of TRIGGER events gets closer to LIMIT. See the STYLE Knob description for details.

More examples can be found in this patch. You can hear the results.

• Paired with other modules, can simulate modules that "wear out" or "break" with repeated use.
• Allow generative patches to self-conduct behavioral changes over time.
• Periodically reset other accumulated state in a patch (e.g., in Drifter).
• Create fade-ins or fade-outs of signals that take hours to complete.

Note that hovering the cursor over the colored fuse progress bar displays the current count of TRIGGER events seen and the percentage of the LIMIT has been reached

Selects from one of four styles of behavior:

• BLOW CLOSED (IN -> 0.0) ** While count is less than LIMIT, OUT equals IN. Once count >= LIMIT, OUT is set to 0.0V.
• BLOW OPEN (0.0 -> IN) ** While count is less than LIMIT, OUT equals 0.0V. Once count >= LIMIT, OUT equals IN.
• NARROW (IN * (1 - count/LIMIT) -> 0.0) ** Initially, OUT equals IN. As the count increases, OUT becomes an increasingly attenuated version of IN, until it eventually becomes 0.0V.
• WIDEN (IN * (count/LIMIT) -> IN) ** Initially, OUT is 0.0V. As the count increases, OUT becomes an increasingly larger version of IN, until it eventually equals IN.

Specify the number of TRIGGER events (from 1 to 1000) that need to be received for the Fuse to blow.

Hint: To count more than 1000 TRIGGER events, connect the BLOWN signal of a first Fuse (with LIMIT X) to the TRIGGER of a second (with LIMIT Y) and to the RESET of the first; then the second Fuse will blow after X*Y TRIGGER events.

A trigger to the Input or a Button press adds one to the count of accumulated TRIGGER events. If that count now equals LIMIT, then BLOWN will emit a short trigger.

A trigger to the Input or a Button press resets the count of accumulated TRIGGER events to zero.

In math terms, OUT = X * IN. X is a value from 0.0 - 1.0 that is determined by the STYLE, LIMIT and current count of TRIGGER events.

Note that this knob controls the slew on X, not the slew on OUT. At the default SLEW value (0.0), changes to X happen instantaneously; this might cause clicks in OUT, especially when OUT is an audio signal (e.g., a Sine wave) using the NARROW or WIDEN style. Values of 0.1 will generally prevent this click.

The value of SLEW is the minimum number of seconds it takes for X to change from 0.0 -> 1.0 or from 1.0 -> 0.0. This means it will also affect how quickly RESET takes effect. For example, a SLEW value of 2.3 means that a RESET to a blown BLOW CLOSED Fuse will take 2.3 seconds to move from OUT = 0.0 -> OUT = IN. The change will be linear (i.e., a straight line).

Outputs a single trigger once count == LIMIT.

The signal being altered by Fuse.

The altered version of IN. See STYLE Knob for how it will be altered.

A convenience only used when IN has no cable running into it. The option (-10V, -5V, -1V, 1V, 5V, 10V) that is selected (if any) is then assumed to be the constant value entering IN. This constant value is then affected by the STYLE, LIMIT, and count of TRIGGERS when computing OUT, as per the usual case.

If this module is bypassed, then OUT will equal IN. If IN has no cable running into it, then OUT will be 0.0V, even if the "Unplugged value of IN" menu option is set to something else.

Thanks to all of the helpful people on the VCV Rack Community board for their willingness to help and advise me as I've been learning this new domain.

Many thanks to Marc Weidenbaum for his encouragement and enthusiasm for my module-making efforts.

And my deepest gratitude is to Diane LeVan, for letting me ignore her and/or the world for periods of time just to craft these things. I apologize for waking up with new ideas at 5AM, and for having a retirement hobby that is nearly impossible to even start describing to anyone.