Creating a Profile with Channel Parameters - AWS Elemental Conductor Live 3

This is version 3.17 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

Creating a Profile with Channel Parameters

You can create a profile in which some parameters have variables as values, instead of real values. Then when you create a channel using that profile, you assign real values to the variables. In AWS Elemental Conductor Live 3, these variables are called “channel parameters.”

Fields that can be set up with parameters have a blue background in the user interface. For a list of these fields, go to the AWS Elemental User Community and search for "supported channel parameters."

Warning

While it is possible to create profiles with parameters in other fields, doing so can cause problems when creating channels from these profiles and importing profiles after upgrades. AWS Elemental does not support use of parameters with fields other than those listed.

To create a profile with channel parameters

  1. Start creating the profile in the usual way.

    Fields that can be a channel parameter have a light blue background on the New Profile screen.

  2. In the desired field, create a channel parameter name by enter all or part of the field value between double brace brackets. For example:

    • {{primary destination}}

    • udp://235.10.10.10:{{port}}

      
         Image file create-channel.png
  3. For each parameter you created, enter a validation value in the Parameters panel. When the validation value is entered, the system checks that it is valid. For example, the Network Location field requires a network address. If the validation value entered does not meet the field’s requirements, you receive an error. The validation value does not populate in the channel – it is only used at profile creation.

    
       Image file new-profile-channel-params.png

If you try to set up a channel parameter in a non-eligible field, you receive an error when you save the profile.

Planning Ahead for Bulk Changes

Plan your channel parameter names carefully in case you want to make a bulk change to switch several channels to a different profile (Changing the Profile Used by Multiple Channels). When you create a channel parameter that you may use in another profile, note its name carefully so you can enter the exact same name in the other profile.

For an example:

You create profile_A that has one channel parameter called {{input_network_location}}. You create profile_B that has one channel parameter called {{input_nw_location}}. You assign each profile to one channel: channel_1 and channel_2. You later want to use Task to change the profile of channel_1 and channel_2 to use profile_C.

However, because the two profiles have differently named channel parameters, you won’t be able to complete the task without making adjustments. Plan ahead with consistent parameter names.