dumpk2
Prev | Orchestra Opcodes and Operators | Next

## dumpk2

dumpk2 — Periodically writes two orchestra control-signal values to an external file.

## Description

Periodically writes two orchestra control-signal values to a named external file in a specific format.

## Syntax

    dumpk2 ksig1, ksig2, ifilname, iformat, iprd

## Initialization

ifilname -- character string (in double quotes, spaces permitted) denoting the external file name. May either be a full path name with target directory specified or a simple filename to be created within the current directory

iformat -- specifies the output data format:

- 1 = 8-bit signed char(high order 8 bits of a 16-bit integer

- 4 = 16-bit short integers

- 5 = 32-bit long integers

- 6 = 32-bit floats

- 7 = ASCII long integers

- 8 = ASCII floats (2 decimal places)

Note that A-law and U-law output are not available, and that all formats except the last two are binary. The output file contains no header information.

iprd -- the period of ksig output i seconds, rounded to the nearest orchestra control period. A value of 0 implies one control period (the enforced minimum), which will create an output file sampled at the orchestra control rate.

## Performance

ksig1, ksig2 -- control-rate signals.

This opcode allows two generated control signal values to be saved in a named external file. The file contains no self-defining header information. But it contains a regularly sampled time series, suitable for later input or analysis. There may be any number of dumpk2 opcodes in an instrument or orchestra but each must write to a different file.

## Examples

See the example for dumpk. The only difference between dumpk and dumpk2 is that dumpk2 can write two values at a time from the file.

## See Also

dumpk, dumpk3, dumpk4, readk, readk2, readk3, readk4

## Credits

By: John ffitch and Barry Vercoe

1999 or earlier

Prev | Up | Next
dumpk | Home | dumpk3