19.02.2013 Views

2010318163752818

2010318163752818

2010318163752818

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

}<br />

output(a2);<br />

ISO/IEC 14496-3:2005(E)<br />

The two instances of sasbf operate simultaneously and in parallel. The first synthesises sound from preset 13,<br />

bank 1 (since this is the preset number to which the instrument responds); the second, from preset 48, bank 2.<br />

They return audio signals that are summed together and manipulated with the bandpass core opcode.<br />

5.8.6.8 Standard names<br />

5.8.6.8.1 Definition<br />

Not all identifiers to be referenced in an instrument or opcode are required to be declared as variables. Several<br />

identifiers, listed in this subclause, are termed standard names, shall not be used as variables, and have fixed<br />

semantics that shall be implemented in a compliant SAOL decoder. Standard names may otherwise be used as<br />

variables, embedded in expressions, etc. in any SAOL instrument or opcode. However, the semantics of using a<br />

standard name as an lvalue are undefined.<br />

The implicit definition of each standard name, showing the rate semantics and width of that standard name, is<br />

listed, and the semantics of the value of the standard name specified in the subsequent subclauses.<br />

5.8.6.8.2 k_rate<br />

ivar k_rate<br />

The standard name k_rate shall contain the control rate of the orchestra, in Hz.<br />

5.8.6.8.3 s_rate<br />

ivar s_rate<br />

The standard name s_rate shall contain the sampling rate of the orchestra, in Hz.<br />

5.8.6.8.4 inchan<br />

ivar inchan<br />

The standard name inchan, in each scope, shall contain the number of channels of input being provided to the<br />

instrument instantiation with which that scope is associated. “Associated” shall be taken to mean, for instrument<br />

code, the instrument instantiation for which the scope memory was created; for opcode code, the instrument<br />

instantiation that called the opcode, or called the opcode’s caller, etc.<br />

Different instances of the same instrument may have different numbers of input channels if, for example, they are<br />

the targets of different send statements. Instructions for calculating the value of this standard name are provided in<br />

subclause 5.7.3.3.5.2<br />

5.8.6.8.5 outchan<br />

ivar outchan<br />

The standard name outchan, in each scope, shall contain the number of channels of output provided by the<br />

instrument instantiation with which that scope is associated, in the sense described in subclause 5.8.6.8.4.<br />

5.8.6.8.6 time<br />

ivar time<br />

The standard name time, in each scope, shall contain the time at which the instrument instantiation associated<br />

with that scope was created.<br />

© ISO/IEC 2005— All rights reserved 49

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!