MIDI In CHOP node

MIDI Interface to listen to: hardware port, internal, file.

The name of the MIDI file to read, if reading a file.

Read the whole file versus using the Start/End.

The MIDI channel(s) to read from (1-16). The input streams from multiple channels will be combined into one if no Channel Prefix is given.

When acquiring multiple MIDI channels, the channels can be merged or kept separate. If this field is not blank (try “ch”), one set of CHOP channels is made per MIDI channel: all CHOP channels will be prefixed with this string and MIDI channel number.

Logs all input MIDI messages to the textport.

Selects one of four record methods:

A button used to manually start and stop recording.

Resets the CHOP output channels to be 1 sample long.

To read note events put a channel base name. (try n)

The notes to record. Ranges (try 41-60) can be used.

Notes can be recorded into one channel or each note number can have their own channel (Single Channels).

The velocity can be recorded as part of the note (Note Amplitude), as a different channel (Separate Channels), or not at all (Off).

The base name of velocity-only channels. (try v)

The base name of the polyphonic aftertouch channels.

The name of the channel pressure channel(s).

Note velocity, pressure & aftertouch can be normalized.

The name of the pitch wheel channel.

To read controller events, put a base name. (try c)

There are 128 controllers available. You can specify controllers by index or choose one from the list.

The index range of the controllers. (try 1-8)

Selects either 7 (most common) or 14 bit controllers.

Controller values can be normalized to simple ranges.

Allows cyclic controllers to extend beyond MIDI limits.

The name of the program change channels(s).

The name of a channel that pulses on MIDI beats.

Name of channel that ramps 0 to 1 between MIDI beats.

Name of channels with start/period values of beats.

The number of timer pulses per MIDI beat.

Name of channel that ramps 0 to 1 between MIDI bars.

Name of channels with start/period values of the bar.

Series of hexadecimal bytes describing the Bar message.

The name of the song position pointer channel.

Output channel name for each System Exclusive message

Series of hexadecimal bytes describing SysEx message. (* = dont care, V = value 0-127, v = value 0-1 range)

To determine which channels get affected, some CHOPs have a scope string. Patterns can be used in the scope, for example * (match all), and ? (match single character).

The following are examples of possible channel name matching options:

The Sample Rate Match Options handle cases where multiple input CHOPs’ sample rates are different.

The units for which time parameters are specified.

For example, you can specify the amount of time a lag should last for in seconds (default), frames (at the Houdini FPS), or samples (in the CHOP’s sample rate).

Time Slicing is a feature which boosts cooking performance and reduces memory usage. Traditionally, CHOPs calculate the channel over its entire frame range. If the channel does need to be evaluated every frame, then cooking the entire range of the channel is unnecessary. It is more efficient to calculate only the fraction of the channel that is needed. This fraction is known as a Time Slice.

Causes the memory consumed by a CHOP to be released after it is cooked and the data passed to the next CHOP.

The Export prefix is prepended to CHOP channel names to determine where to export to.

For example, if the CHOP channel was named geo1:tx, and the prefix was /obj, the channel would be exported to /obj/geo1/tx.

Every CHOP has this option. Each CHOP gets a default color assigned for display in the Graph port, but you can override the color in the Common page under Graph Color. There are 36 RGB color combinations in the Palette.

When the graph displays the animation curves and a CHOP has two or more channels, this defines the difference in color from one channel to the next, giving a rainbow spectrum of colors.