This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.


System object: dsp.UniformEncoder
Package: dsp

Quantize and encode input


Y = step(ue,X)



Starting in R2016b, instead of using the step method to perform the operation defined by the System object™, you can call the object with arguments, as if it were a function. For example, y = step(obj,x) and y = obj(x) perform equivalent operations.

Y = step(ue,X) quantizes and encodes the input X to Y. Input X can be real or complex, double-, or single-precision values. The uniform encoder chooses the output data type according to the following table.

Number of BitsUnsigned IntegerSigned Integer
2 to 8uint8int8
9 to 16uint16int16
17 to 32uint32int32

The row corresponds to the value of the NumBits property, and the column corresponds to the value of the OutputDataType property.


obj specifies the System object on which to run this step method.

The object performs an initialization the first time the step method is executed. This initialization locks nontunable properties (MATLAB) and input specifications, such as dimensions, complexity, and data type of the input data. If you change a nontunable property or an input specification, the System object issues an error. To change nontunable properties or inputs, you must first call the release method to unlock the object.

Was this topic helpful?