• Profiles.AssignHandleProfile
• Profiles.GetHandleProfileId

• profileId

setProfile.xml

<?xml version="1.0" encoding="utf-8"?>
<avolites.macros xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Avolites.Menus.xsd">
  <macro name="Set Key Profile to UN11047" id="Wiki.Macros.SetplaybackProfile">
    <sequence>
      <step>Profiles.AssignHandleProfile(handle:"chaseHandleUN=10555", 
        Profiles.GetHandleProfileId(handle:"chaseHandleUN=11047"))</step>
    </sequence>
  </macro>
 
  <macro name="Set Key Profile of chaser 5563" id="Wiki.Macros.SetplaybackProfile.Ex1">
    <sequence>
      <step>Profiles.AssignHandleProfile(handle:"chaseHandleUN=5963",493461)</step>
    </sequence>
  </macro>
 
</avolites.macros>

This explains the functional steps within the sequence. For all the other XML details please refer to Formats and syntax

As the Profile IDs of user-defined key profiles are random, te first example might be much more useful than the second: it sets the key profile of one playback to the key profile of another playback:

• Profiles.GetHandleProfileId(handle:“chaseHandleUN=11047”) retrieves the profile id of the playback with user number 11047.
• Profiles.AssignHandleProfile(handle:“chaseHandleUN=10555”, …) sassigns this as profile id for another playback

The second example directly sets a profile id - however, as the correct ID cannot be predicted, you'd need to find the correct dd e.g. with this example and manually enter the number in the macro - not very handy.

1. make this macro available
2. create a chaser with #11047 as dummy playback and set its key profile.
3. in order to apply this to another chaser re-legend that other chaser to #10555 and fire the macro

The second macro is merely for documentation purposes - you'd need to edit it to match the profile id of your show.