Codebox

The constant value used when converting from degrees to radians

degtorad

out1

halfpi

invpi

ln10

log10e

log2e

not supported in RNBO, will always return 1.

mc_channel

mc_channelcount

returns the maximum number value that the number system can represent

number_max

PI_OVER_2

PI_OVER_4

The constant value used when converting from radians to degrees

radtodeg

sqrt1_2

sqrt2

twopi

objects use a JavaScript-like scripting language to implement DSP and event code directly inside of RNBO. The syntax is similar to the

 in Gen, with some important differences.

Unline Gen, variables must be declared with 

 keyword. While this makes the RNBO codebox language 

 very similar to JavaScript, not all JavaScript features are supported. Overall, 

 object, rather than a replacement for the Max 

You can create and reference inlets and outlets using 

basic.png

bascic-dsp.png

 is sufficent to create a second inlet. When using

, any assignment to an outlet will cause an output on that outlet.

Screen Shot 2022-06-27 at 2.57.49 PM.png

This will print 4 and then 5 whenever the codebox receives input at its first inlet. The codebox will always have a first inlet. As is often the case in Max, only the leftmost inlet is "hot". Sending a value to the first inlet will trigger output, while sending a value to the other inlets will instead simply update the internal value of 

, all outlets are always signals, and will output a signal vector every audio frame.

list-basic.png

 identifiers to get accordingly typed inlets and outlets.

 to declare local variables. While you can re-assign the value of 

 variables, these updates will not persist between codebox calls—see 

 values in parameter declarations. This includes globally-defined 

Codebox supports a subset of RNBO objects. Very simple objects, the ones that just wrap a stateless function call, are exposed as built-in functions in codebox. So one can write:

 object in RNBO. Some built-in functions return a number:

operators.png

Others return multiple values as an array:

operators-multi-return.png

RNBO objects with some internal state, like a 

, are exposed as codebox-supported objects. These must be created with 

 method, which returns the object's output while advancing its internal state by one sample. So calling 

The cycle and phasor objects are very common:

phasor_cycle_02.png

 are not currently supported. Built-in functions and codebox-supported RNBO objects are listed on this page's lefthand sidebar as operators and stateful operators. 

Most of the control flow keywords from C++ and JavaScript are supported. The looping constructs 

However, language-specific paradigms like 

 are not currently supported. You can also use branching constructs like 

These keywords should follow the C++ and JavaScript specification, so refer to the documentation for those languages for a more thorough discussion of how to use these keywords.

Function declarations are supported using the 

function.png

A function can return multiple values by returning an array.

functions.png

The return type of a function is automatically deduced (it will be a list, if you use an array expression as a return type). Anonymous functions, like you might create with big-arrow notation in JavaScript or C++ lambdas, are not currently available.

There are currently three special functions:

Screenshot 2022-05-31 at 19.15.14.png

Sometimes you want a function to be called whenever data comes into one of the inlets that is not the first one. This can be achieved through an inlet function. In this example, the function is called whenever a list is received at the second inlet:

Screenshot 2022-05-31 at 19.28.30.png

 whenever the second inlet receives any input. This function will run in addition to setting the value of 

, so you can think of the function as a side effect of setting 

In order to re-use state after codebox has triggered some output, use the 

 decorator.  This will create state that persists across the lifetime of the codebox object.

state2.png

 keyword to declare variables that can be used during codebox execution, these are not reusable state variables. For example, something like this will not work:

Screen Shot 2022-06-27 at 3.50.57 PM.png

 decorator to introduce a state variable that can be set via a message:

Screen Shot 2022-06-28 at 2.05.51 PM.png

 decorator function is the only place in the codebox language that you can use a JavaScript-style object. The function takes as its one and only argument an object describing how the parameter should behave. It can take the keys 

 to define a range, or it can take the key 

, followed by a list of enumerated values. Enumerated parameters always start at index 0.

Following the decorator function, the parameter must be given a name and an initial value.

A codebox's state can also hold a reference to a buffer. This may be sized, unsized, named, or anonymous. For example, this creates a reference to a buffer "mybuf" defined outside of the codebox.

buffers.png

This will create an internal, anonymous buffer, that will always be twice the sample rate in size:

buffers2.png

 the only two supported operators in size expressions are 

 This will create a named buffer (which will also be available in Max) of size 44100:

buffers3.png

 to set and get sample values. Reading and writing in buffers does bound checking, so you cannot read or write out of bounds. As you can see, some built-in functions take a buffer as their argument. The list of operators in the left sidebar includes such functions.

It is possible to give a codebox variable an explicit type.

types.png

This is usually unnecessary, but sometimes necessary (for example) when strict typing requires that a number have an integer type.

Explicit types also allow you to declare a variable without setting it, if you want to. For example:

 is a number and will throw an error. Valid types include 

Finally, you may find that your codebox fails to compile sometimes in cases where you're using a custom function that returns a list. Sometimes the compiler can infer the return type of a function, and the explicit 

 type is unnecessary. However, you can always add the explicit return type to clear up the error if you're seeing a problem. 

 do not have a fixed size. Adding and removing elements from the list changes the size of the list. Sometimes it's convenient to work with fixed size arrays. These arrays are highly efficient, especially when it comes to setting and getting values from the array at a particular index. One thing that's particularly useful is that with fixed arrays, you can create multidimensional arrays that you can index along multiple dimensions. For example:

 that fills up an array with a sinusoid, 180 degrees out of phase in each channel.

The following types are supported for fixed size arrays:

Name ------------------ C Type --------------- Description
FixedInt8Array -------- int8_t --------------- Signed 8-bit integer
FixedUint8Array ------- uint8_t -------------- Unsigned 8-bit integer
FixedInt16Array ------- int16_t -------------- Signed 16-bit integer
FixedUint16Array ------ uint16_t ------------- Unsigned 16-bit integer
FixedInt32Array ------- int32_t -------------- Signed 32-bit integer
FixedUint32Array ------ uint32_t ------------- Unsigned 32-bit integer
FixedFloat32Array ----- float ---------------- 32-bit float
FixedFloat64Array ----- double --------------- 64-bit float
FixedBigInt64Array ---- int64_t -------------- Signed 64-bit integer
FixedBigUint64Array --- uint64_t ------------- Unsigned 64-bit integer
FixedSampleArray ------ float or double ------ The same type as an audio sample
FixedNumberArray ------ multiple ------------- Value may change depending on the 
                                               circumstances in which code is generated 
                                               and used. Use this if you don't need a 
                                               particular number type.
FixedIntArray --------- int ------------------ Signed integer, equivalent to C int
FixedFloatArray ------- float ---------------- Equivalent to C float
FixedDoubleArray ------ double --------------- Equivalent to C double

 object can also accept a number message at any of its inlets.

If only messages and no signals are connected to the inlet of a 

, then the inlet value (in1, in2, etc.) will only update once every signal vector. This is much more efficient, though it does mean that the value cannot change during the computation of an audio block.

List functions in RNBO fall into two categories: global list functions and methods on a list object.

Global list functions all have a RNBO object equivalent. For example, the object 

 is equivalent to the global codebox function 

. For all of these objects, the function inside codebox is simply the name of the RNBO object without the period after the word "list". 

The following is a list of methods on a list object. Some of these have a RNBO object equivalent, for example the 

 method is equivalent to the RNBO object 

. Many of the list functions that are currently supported are modeled after their JavaScript equivalent. Where possible, these are identical. For a full discussion of the behavior of each function, see the JavaScript documentation of that function.

codebox and codebox~ enable you to use rnboscript, a JavaScript-like scripting language, to implement DSP and event code directly inside of RNBO.

Codebox and Codebox~ Reference

C++ API

realIn

imagIn

out2

A sync signal that ramps from 0 to the number of points minus 1 over the period in which the IFFT output occurs. When the IFFT is not being output (in the case where the interval is larger than the number of points), the sync signal is 0.

out3

reset

ifftstream

The first argument specifies the number of points (samples) in the IFFT. It must be a power of two. The default number of points is 512.

fftsize

The second argument specifies the number of samples between successive IFFTs. This must be at least the number of points, and must also be a power of two. The default interval is 512.

framesize

The third argument specifies the offset into the interval where the IFFT will start. This must either be 0 or a multiple of the signal vector size. ifft~ will correct bad arguments, but if you change the signal vector size after creating an ifft~ and the offset is no longer a multiple of the vector size, the ifft~ will not operate when signal processing is turned on.

phase

A {rnbo_buffer~} object can be used as an alternative lookup table for the IFFT window if a custom windowing function is necessary.

win_bufname

Specify which windowing function for the FFT to use (none, the 'rectangular' window, is the default).

window

Performs the subtraction with the value currently stored.

The value in the right inlet is subtracted from this value and the result is sent out the outlet.

Compute the absolute difference between two inputs

absdiff

The absolute value of the difference between the two numbers received in the inlets.

acos

Input to the inverse hyperbolic cosine function.

acosh

The inverse hyperbolic cosine of the input.

Performs the operation with the value currently stored. If there is no argument, && initially holds `0`.

The value is compared to the value in the left inlet to determine output but only a value in the left inlet will trigger output.

If either the value in the left inlet or the value in the right inlet (or specified by the argument) is not `0`, then the output is `0`. Otherwise, the output is `1`.

The input number or list that will come before any appended values in the output list.

A number or list of numbers to append to the input.

append

Outputs a list composed of the input value(s) followed by the appended value(s).

asin

Input to the inverse hyperbolic sine function.

asinh

The inverse hyperbolic sine of the input.

arc tangent of the input (returns radians)

atan

atan2

The arc-tan of the divided input in radians.

Input to the inverse hyperbolic tan function.

atanh

atodb

The gain or attenuation from unity gain, expressed in decibels.

The number of beats (quarter notes) to be converted to the equivalent time in Hz using the tempo of the device transport.

beattime

convert beat time (quarter notes) to frequency (Hz)

beatstohz

The number of beats (quarter notes) to be converted to the equivalent time in milliseconds using the tempo of the device transport.

Convert beat time (quarter notes) to milliseconds.

beatstoms

The number of beats (quarter notes) to be converted to the equivalent time in samples using the tempo of the device transport and sample rate of the audio device.

Convert beat time (quarter notes) to samples.

beatstosamps

The number of beats (quarter notes) to be converted to the equivalent time in ticks.

Convert beat time (quarter notes) to ticks.

beatstoticks

offset

Report the current beat time at a specific sample offset.

beattimeatsample

The values to be windowed, bounded to the range 0. - 1.

blackman

The windowed output, bounded to the range 0. - 1.

boolnum

Outputs 1 for non-zero inputs and 0 if the input is zero

A float value sets the phase of the window.

A value between 0.0 and 1.0 sets the shape of the window between the boxcar and the triangle window functions. A value of 1.0 sets a triangle window.

Codebox Guides

ifftstream

Options

Aliases

Methods

next(realIn, imagIn): [out1, out2, out3]

Arguments

Returns

reset(): void

Name	Type	Default	Description
fftsize	enum	512	The first argument specifies the number of points (samples) in the IFFT. It must be a power of two. The default number of points is 512. Enum Values: `64 \| 128 \| 256 \| 512 \| 1024 \| 2048 \| 4096`
framesize	int	512	The second argument specifies the number of samples between successive IFFTs. This must be at least the number of points, and must also be a power of two. The default interval is 512.
phase	int		The third argument specifies the offset into the interval where the IFFT will start. This must either be 0 or a multiple of the signal vector size. ifft~ will correct bad arguments, but if you change the signal vector size after creating an ifft~ and the offset is no longer a multiple of the vector size, the ifft~ will not operate when signal processing is turned on.
win_bufname	symbol	RNBODefaultFftWindow	A {rnbo_buffer~} object can be used as an alternative lookup table for the IFFT window if a custom windowing function is necessary.
window	enum	rectangular	Specify which windowing function for the FFT to use (none, the 'rectangular' window, is the default). Enum Values: `rectangular \| hann \| hamming \| blackman`

Name	Type	Description
out1	number	The real part of the inverse Fourier transform of the input. The output begins after all the points of the input have been received.
out2	number	The imaginary part of the inverse Fourier transform of the input. The output begins after all the points of the input have been received.
out3	number	A sync signal that ramps from 0 to the number of points minus 1 over the period in which the IFFT output occurs. When the IFFT is not being output (in the case where the interval is larger than the number of points), the sync signal is 0.