Welcome < Configuration < System Configuration < Command Mappings

Command Mappings

Command Mappings are used to map and configure external devices, such as special keyboards and cards, to send and receive keyboard strokes, GPIO events and Cue Point events to commonly used tasks in Zetta^®. Such devices already defined in Zetta are the Preh and Tipro keyboards, the SeaLevel, RS232 and PCI-1760 cards and the Axia Console. See the GPIO / Route Devices section of this guide for more information on these GPIO devices. A default System Keyboard Mappings has been created, which represents preset mappings from keyboard key strokes to actions in Zetta. To see a list of Zetta Commands available for Input and Output devices see the Zetta Commands topic in the Appendix section of this guide.

Click any area in this image for additional help

Click any area in this image for additional help

In this Topic: show/hideshow/hide

Command Mappings Toolbar

Command Mappings List

The List below the toolbar show all the existing command mappings. These columns can be sorted, in ascending or descending order, by clicking the column heading and the Columns can be reorganized to fit the user’s needs. The data can be customized using Custom Filtering. The Active column only applies to GPIO Mappings. To clear the filter, click the filter button to the right of the filter field or use the ESC key on the keyboard.

Mapping Toolbar

The Mapping toolbar is available when a Shortcut Key Mapping, GPIO Mapping or Cue Point Mapping is created.

Add Keyboard Shortcut Mapping

The Add keyboard shortcut mapping option from the Add new mapping drop-down button is used to create mappings to control specific execute commands from the keyboard . The following fields are used to configure Keyboard mappings:

System Default – The Keyboard Mapping created can be assigned as the system default or a specific user. See Account Configuration Step-by-Step for assigning Keyboard Mapping to a user.

Name – The name is the title of the Keyboard Mapping

Description – The description field is used to add a more detailed description about the mapping.

Keyboard Mapping Configuration - There are four columns to configure for the keyboard commands:

• Active – Select the Active checkbox to enable and disable the Keyboard mapping.
• Context – The Context drop-down menu defines which area of the UI the keyboard shortcut is applicable for; Global means the shortcut will work, no matter where in the UI the user currently is, any other option defines the area that needs to be active (= needs to have a focus) for the shortcut(s) to work. This is useful for scenarios where the same shortcut (e.g. F12) is to perform different operations in different areas of Zetta.
• Shortcut Key – Type the key sequence to use for the Execute Command, such as the F9 key on the keyboard. Standalone keys, like letters and digits ("P" or "7") cannot be used as a shortcut, only in combination with keys like SHIFT, ALT and CTRL; F2 to F12 can be used as a standalone shortcut. F1 is reserved and will bring up this Help file. The Space key can also not be used at this time.
• Execute Command – When the Execute Command field is selected the Properties pane is populated. This is where the user will select the Task Type and any Parameters needed.

Task Type - The Task Type is the task for Zetta® to perform when the Shortcut key is used. This field has an Auto Complete feature where the user can start typing the name of the execute command and Zetta will match what is typed with the existing entries.

Properties – The Properties are specific parameters based on the Task Type selected. Such as the Module Stream field. This field is used with Hotkeys.* and ZPlayer.* tasks to specify the Audio Output Short name of the stream assigned. This feature is currently only used with the Z-Player and Hot Keys to identify the stream that will be affected by the Task Type mapped.

For Example: If two Z-Player modules were open at the same time one using Stream 1Z1 and the other using Stream 1Z2 and a mapping was desired to start playing the Z-Player using Stream 1Z1 the mapping would look like the following illustration:

Default System Keyboard Mappings

To see a list of Zetta Commands available for input and output devices see the Zetta Commands topic in the Appendix section of this guide. The following table lists the default System Keyboard Mappings.

Add GPIO Event Mapping

Use the Add GPIO Event Mapping option from the Add new mapping drop-down button to create mapping groups to control GPIO events for a computer. The following fields are used to configure GPIO Event Mappings:

Active - The Active button can be used to set the GPIO instance as active or inactive. Optionally, the GPO command event 'GPIO.DisableMappingGroup' can be used to make the group inactive. The GPO command event 'GPIO.EnableMappingGroup' can be used to make the group active.

Name – The Name is the title of the GPIO mapping

Description – The Description field is used to add a more detailed description about the mapping.

GPIO Mapping Type - The GPIO Mapping Type is used to select the type of GPIO the defined mapping will be used for. A Standard GPIO Mapping is used for general command mappings that can contain mappings for a specific station or can contain mappings that are not specific to a station. A Standard GPIO Mapping can be assigned as a GPIO Mapping Group for the Station in the Details tab of the Station Configuration. A Hot Spare GPIO Mapping is used for Hot Sparing and can be used with any station assigned to the Hot Spare. Hot Spare Mappings do not need to be active when saved. Zetta will activate the assigned GPIO Mapping Group when the Hot Spare is switched. Hot Spare GPIO Mappings are shown in the GPIO Mapping Group for this Hot Spare drop-down in the Hot Spare Configuration window. Hot Sparing GPIO mappings is useful if a studio can be used to control multiple stations.

Example: The ‘On’ button of fader 1 can be used  to start stream 1 of Station A, Station B or Station C. Whichever station is currently Hot Spared to that studio at the time will be triggered by that button.

Processed By –The Processed By drop-down menu is used to select the computer that will process the GPIO mapping created.

Input Trigger Mappings (GPIs) – This tab is used to create Input GPI mappings. The following columns are used to configure GPI commands:

• Active – The Active checkbox allows the user to enable or disable the use of the GPI mapping.
• Capture - The Capture checkbox tells Zetta to allow the capture of this command in a record control event. This is typically used for Background Recordings when the 'Capture Station GPI Triggers' is enabled in the Record Properties. Clear the checkbox to prevent the command from being captured.
• Name – The name field is used to name each GPI mapping.
• Context - All Input commands will have two Context options. Context options are used for UI based tasks such as opening modules, Non-UI tasks such as sequencer commands do not use these Context options:
  • Global - This means the command will be triggered if Zetta is open, even if there is no active window in focus. If Global is used, the command will work for the module if only ONE module of the command type is open, even if it does not have focus. Otherwise, if multiple windows of the same module are open, the command will be sent to the window with focus.
  • with Focus - If the GPIO Input event is triggered, Zetta will only pass the COMMAND to the window with active window focus. If the window does not have focus it will not receive the command!
• GPI Trigger – The GPI Trigger is the device input trigger to tell Zetta® to perform the command assigned in the Execute Command field. This field has an Auto Complete feature where the user can start typing the name of the GPI and Zetta will match what is typed with the existing entries.
• Directional Arrow - This arrow simply shows the direction of work flow for this window.
• Execute Command – When the Execute Command field is selected the Properties pane is populated. This is where the user will select the Task Type and any Parameters needed. Not all tasks have Parameters. Use the Delete keyboard key to clear the contents of the selected Execute Command field.

Task Type - The Task Type is the task for Zetta® to perform when a GPI is received. This field has an Auto Complete feature where the user can start typing the name of the task type and Zetta will match what is typed with the existing entries.

Properties – The Properties are specific parameters based on the Execute Command selected. Such as the Module Stream field. This field is used with Hotkeys.* and ZPlayer.* tasks to specify the Audio Output Short name of the stream assigned. This feature is currently only used with the Z-Player and Hot Keys to identify the stream that will be affected by the Task Type mapped.

For Example: If two Z-Player modules were open at the same time one using Module Stream A and the other using Module Stream B and a mapping was desired to start playing the Z-Player using Module Stream A the mapping would look like the following illustration:

Output Event Mappings (GPOs) – This tab is used to create the Output GPO mappings. The following columns are used to configure GPO commands:

• Active – The Active checkbox allows the used to enable or disable the use of the GPO mapping.
• Capture - The Capture checkbox tells Zetta to allow the capture of this command in a record control event. This is typically used for Background Recordings when the 'Capture Station Output Events' is enabled in the Record Properties. Clear the checkbox to prevent the command from being captured.
• Name – The name field is used to name each GPO mapping.
• Output Event – Output Event is the task for Zetta to perform. When the Output Event field is selected the Properties pane for the Output event is populated. Use the Delete keyboard key to clear the contents of the selected Output Event field.
  • Task Type - The Task Type is the command for Zetta® to perform when a GPO is received. This field has an Auto Complete feature where the user can start typing the name of the task type and Zetta will match what is typed with the existing entries.
  • Properties – The Properties are specific parameters based on the Task Type selected. Such as a Station.
    
• Directional Arrow - This arrow simply shows the direction of work flow for this window.
• Execute Command – When the Execute Command field is selected the Properties pane is populated. This is where the user will select the Task Type and any parameters needed. Not all tasks have parameters. To map a GPO use the Gpio.TriggerGpo Task Type. Use the Delete keyboard key to clear the contents of the selected Execute Command field.
  • Task Type - The Task Type is the command for Zetta to perform when a GPO is received. The Task Type will default to Gpio.TriggerGpo when the Add button is set to Trigger GPO. This field has an Auto Complete feature where the user can start typing the name of the task type and Zetta will match what is typed with the existing entries.
  • Properties – The Properties are specific parameters based on the Task Type selected. Such as a GPO. The GPO is the device event trigger to tell Zetta to perform the Output Event assigned. This field has an Auto Complete feature where the user can start typing the name of the GPO and Zetta will match what is typed with the existing entries.
    

Add Cue Point Mapping

Use the Add Cue Point Mapping option from the Add new mapping drop-down button to create a mapping for Cue Points for a station. Only one Cue Point mapping can be created, however multiple tasks can be added to the mapping. The following fields are used to configure a Cue Point Mapping:

Name – The Name is the title of the Cue Point mapping instance.

Description – The Description field is used to add a more detailed description about the mapping.

Name – The Name column is used to enter a name for the Cue Point mapping.

Execute Command – When the Execute Command field is selected the Properties pane is populated. This is where the user will select the Task Type and any Parameters needed. Not all tasks have Parameters. Use the Delete keyboard key to clear the contents of the selected Execute Command field.

• Task Type - The Task Type is the task for Zetta to perform. This field has an Auto Complete feature where the user can start typing the name of the Task Type and Zetta will match what is typed with the existing entries.
• Properties – The Properties are specific parameters based on the Task Type selected. Such as the Module Stream field, this field is used with Execute Commands such as Hotkeys.* and ZPlayer.* to specify the Audio Output Short name of the stream assigned. This feature is currently only used with the Z-Player and Hot Keys to identify the stream that will be affected by the Execute Command mapped.

For Example: If two Z-Player modules were open at the same time one using Stream A and the other using Stream B and a mapping was desired to start playing the Z-Player using Stream A the mapping would look like the following illustration:

To create a custom cue point for an asset, see the Marks Editor topic.

Command Mappings Tab Step-by-Step Topics

This section will provide step-by-step instructions for common tasks using the Command Mappings Tab in the System Configuration window.

In this section: show/hideshow/hide

Adding Custom Keyboard Shortcut Mappings

1. From the Configuration menu, click System.
2. Click the Command Mappings tab
3. Click Add keyboard shortcut mapping option from the Add new mapping drop-down button.
4. Click System Default to make the Custom Keyboard Mapping the system default. See Accounts Configuration Step-By-step Topics to assign the Keyboard Mapping to specific user(s)
5. Enter a Name for the Keyboard Mapping.
6. Enter a Description for the Keyboard Mapping (optional)
7. Optionally, use the Import Command Mapping to import an exported mapping from another Zetta system.
8. Click the Add New Mapping button
9. Using the Context column drop-down to select the module or specific area for the keyboard shortcut to be active
10. In the Shortcut Key column, press the keyboard key or combination to enter the value.
11. Select the Execute Command field to view the options in the Properties window.
12. Select the Task Type from the drop-down list. This field has an Auto Complete feature where the user can start typing the name of the Task Type and Zetta will match what is typed to shorten the list of possible task types.
13. Select the Properties based on the Task Type selected.
14. Enter the Stream in the Module Stream field if needed for the Hot Keys and Z-Player commands.
15. Repeat from step 8 as needed to add additional shortcut keys.
16. Click Save to save the Mappings.

Adding GPIO Event Mappings

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab
3. Click Add GPIO Event Mapping option from the Add new mapping drop-down button.
4. The New GPIO will be active by default deselect the Active option to make the GPIO mapping inactive.
5. Enter a Name for the GPIO Mapping (default is New Mapping GPIO).
6. Enter a Description for the GPIO Mapping (optional)
7. Select the GPIO Mapping Type.
8. Using the Processed By drop-down select the computer that has the device installed and configured, see the Adding GPIO Devices section of this guide for details on configuring a GPIO device for a computer.
9. Select the Input Trigger Mappings tab
10. Click the Add New Mapping button the mapping is enabled by default.
11. Enter a Name for the mapping
12. Select the Context
13. In the GPI Trigger column, use the drop-down to select the GPI Input to use.
14. Select the Execute Command field to view the Properties window for the mapping.
15. Select the Task Type from the drop-down list. This field has an Auto Complete feature where the user can start typing the name of the Task Type and Zetta will match what is typed to shorten the list of possible task types.
16. Select the Properties based on the Task Type selected.
17. Enter the Stream in the Module Stream field if needed for the Hot Keys and Z-Player modules.
18. Repeat from Step 9 as necessary until all GPI Inputs are defined
19. Select the Output Event Mappings tab
20. Click the Add New Mapping button to add a Trigger GPO. Optionally, select the drop-down arrow next to the add button to selected Execute Command.
21. Enter a Name for the mapping
22. Select the Output Event field to view the options in the Properties window.
23. Select the Task Type from the drop-down list. This field has an Auto Complete feature where the user can start typing the name of the Task Type and Zetta will match what is typed to shorten the list of possible task types.
24. Select the Properties based on the Task Type selected.
25. Select the Execute Command field to view the Properties window for the mapping. If GPO Trigger was selected to add the new mapping the task type field will default to Gpio.Trigger.Gpo.
26. Select the Task Type from the drop-down list. This field has an Auto Complete feature where the user can start typing the name of the Task Type and Zetta will match what is typed to shorten the list of possible task types.
27. Select the Properties based on the Task Type selected. Such as, the GPO. Use the drop-down to select the GPO Output to use.
28. Enter the Stream in the Module Stream field if needed for the Hot Keys and Z-Player modules.
29. Click Save to save the mappings.

Adding Cue Point Mappings

1. From the Configuration Menu, click System.
2. Click the Command Mappings tab.
3. Click Add Cue Point Mapping option from the Add new mapping drop-down button.
4. Enter a Name for the Cue Point Mapping (default is Cue Point Mapping).
5. Enter a Description for the Mapping (optional)
6. Click the Add New Mapping button.
7. Enter a Name for the command mapping.
8. Select the Execute Command field to view the options in the Properties window.
9. Select a Task Type from the drop-down list. This field has an Auto Complete feature where the user can start typing the name of the Task Type and Zetta will match what is typed to shorten the list of possible task types.
10. Select the Properties based on the Task Type selected.
11. Enter the Stream in the Module Stream field if needed for the Hot Keys and Z-Player modules.
12. Repeat from Step 6 as necessary until Execute Commands are defined.
    
13. Click Save to save the mappings.

Welcome < Configuration < System Configuration < Command Mappings