With each Telestra system, the user purchases a defined modeling credit limit as needed to meet their application software requirements. The credit system defines the limit of functionality to which the user can build and run models on the system. This limit is covered under the software licensing agreement.
Within the Model Builder Visual development environment the user builds sound and communications models using the library of building blocks known as Components. As the user builds a model, certain building blocks and feature settings consume the available credits licensed on the system. When all credits are consumed in the course of model development, further additions can still be made to the model, however the model will not run without either removing functionality to free up modeling credits or increasing the modeling credit limit on the system.
Since the modeling credit limit is just that, a limit, the user can run any model created by any user or system as long as the model functionality does not exceed the licensed credit amount.
The Modeling Credit System was created in order to scale system prices to fairly match the complexity of the user's application. Complex systems with greater numbers of audio channels, capabilities and modeling requirements require more modeling credits to meet the application requirements than simpler applications. Smaller systems will require less capability, translating into a lower cost platform.
The credit limit purchased with the system can be identified in several ways:
Telestra 3 MBV Modeling Credits provides a list of modeling components and their credit consumption. Note that as new software versions are released, the list of available Components and their modeling credit consumption may change.
Modeling credits are not permanently consumed, nor do they ever expire! The modeling credit limit licensed for the system simply represents a limit to the size and complexity of the model that can be developed or run on the system.
An Options disk containing a software license key file is shipped with each system. This license key file contains the modeling credit limit purchased with the system and must be installed on the system for proper operation. When a model is loaded, the system software scans the model, checks for additional system configuration settings and options that affect the model credits consumption and compares the amount of credits used against the credit limit established by the license. If the modeling credits used exceeds the licensed limit, an error message is generated and the model does not run.
As stated in the software license agreement, modeling credits are not transferable between systems. Once a license key file is issued for a particular system there is not an easy mechanism to permanently remove previously licensed capability. The recommended approach is to ensure that all systems have sufficient credits to run any complexity of model for the application. Modeling credit limits can, however, be increased for a particular system.
Modeling credits can be added to the system by purchasing additional credits through ASTi. When purchased, ASTi will send an updated Options disk with a license key file. Once this new key file is installed on the system, the increased capability is available.
The list below identifies the modeling credits consumed by each Component in a model within the Model Builder Visual (MBV) development and runtime environment. When a model is loaded, the system scans the model, tallies the total credits and checks this amount against the model credit limit purchased with the system. If the amount used exceeds the licensed limit, the model will not load and an error message is generated.
Note that the list below is subject to change with new software releases.
* All components in the Control group consume 0 credits.