Here is a list of parameters needed by the test. This table lists only the parameters that have some special information about parameters or that override or adds new parameters to the common test parameters list.
Parameter | Value | Description | R/O |
---|---|---|---|
class | GenericABC | A class alias (GenericABC) or a fully qualified java class name of the class that handles the test. | Req. |
generic.sampleParams | list of names | A comma-separated list of names of parameters that are samples. | Req. |
Note: All other test classes in GP use the generic test as their base and they predefine the sampleParams parameter automatically. The parameter is only required if using the generic test directly or using special item features.
# Sample parameters that are sample IDs generic.sampleParams: A,B,C,DThe list of item parameters would be like this (like in other tests):
Parameter | Value | Description | R/O |
---|---|---|---|
A | sample ID | Sample ID of sample A. | Req. |
B | sample ID | Sample ID of sample B. | Req. |
C | sample ID | Sample ID of sample C. | Req. |
D | sample ID | Sample ID of sample D. | Req. |
Here is an example of such an item:
item2.A=pirr22 item2.B=pirr32 item2.C=pirr16 item2.D=pirr11The item's itemID is 'item2'.
For example, defining a template for a test where three sets of speaker systems are tested using different virtual players and samples: The needed parameters would perhaps look like this:
Parameter | Value | Description | R/O |
---|---|---|---|
A | sample ID | Sample ID of sample A. | Req. |
B | sample ID | Sample ID of sample B. | Req. |
C | sample ID | Sample ID of sample C. | Req. |
A_player | player ID | The ID of the player that is used as player for sample A. | Opt. |
B_player | player ID | The ID of the player that is used as player for sample B. | Opt. |
C_player | player ID | The ID of the player that is used as player for sample C. | Opt. |
The *_player parameters are not sample ID, so they cannot be given in sampleParams. They are also optional, they do not have to be defined.
The configuration definitions needed for such test would then be:
# Default item template: # Define which parameters are used itemTemplates.default.parameters: A,B,C,A_player,B_player,C_player # Which parameters are required (others are optional) itemTemplates.default.requiredParameters: A,B,C # # Which parameters are samples: generic.sampleParams: A,B,C
A test item would then look like this in the items file:
item6.A: samp34_1ch item6.A_player: set1ch item6.B: samp34_5ch item6.B_player: set5ch item6.C: samp34_2ch item6.C_player: set2ch
For this to work, the <sampleParam>_player parameters must be defined as item parameters. See examples above in special items.
See also sound player configuration for information on how to define virtual players.