SCTE-35 Modification Profiles

overview scte 35 is the industry standard for embedding metadata markers into video transport streams these markers signal precise start and end times for events like ad breaks, content replacement, and blackouts by identifying these windows, downstream systems can dynamically insert localized or targeted ads tailored to specific regions and viewer demographics zixi supports scte 35 manipulation across sources and targets, allowing you to insert new messages and modify or remove existing messages scte 35 modification profiles provide an easy way to define changes and apply them across multiple targets each scte 35 message is evaluated against your defined rule sets if a message matches a rule, it triggers a specific action to keep , remove , or modify that message scte 35 modification profiles is a paid add on for zen master if you are interested in exploring whether it would be useful to you, contact your zixi representative notes scte 25 modification profiles can only be applied to targets (for now) for details, see docid\ xikxi521hxggj5wezlcl7 you can use the zen master api to list existing scte 35 modification profiles, but you have to use the ui to create a profile scte 25 modification profiles require the docid\ osyzvsqm3mnsyzo76amby to be installed on the broadcaster creating scte 35 modification profiles in the zen master navigation menu, go to transformations>scte 35 modification profiles in the scte 35 modification profiles section, click the add button on the create new scte 35 modification profile screen, note that all fields are required enter a unique name for the profile select one or more tags for the profile select a default action ( keep or remove ) which will be invoked when a scte 35 message in the screen does not match any of the rules defined in the profile click + add to add one or more rules to the profile note if there are multiple triggers, the scte 35 message should match all criteria in order to action the rule if not, the default action (keep or remove) will be applied the create new rule dialog will open select the action that should be triggered when a scte 35 message is found that matches the rule(s) the possible actions are keep the scte 35 message as is remove the scte 35 message from the stream note that remove behaves differently if the section is descriptor, removing only the descriptor, not the entire message modify the scte 35 message by changing the message to the modifications defined in the rule note that when you select modify as the action, you need to specify the trigger used to identify a matching scte 35 message, and also the modifications that should be made to the message the options available for each part of the trigger and the modification to be performed are interdependent , and will vary according to the options already selected so, select them in order from left to right, with triggers first, then modifications select the section for the trigger from the three available options, which are parts of the scte 35 message select the field for the trigger note that the available options will depend on which section you selected select the operation for the trigger as with other parts of the trigger, the options depend on the section and field already selected in most cases, the only option will be equals to check for a matching value finally, indicate the value that you are looking for a match on this is generally something you will need to type in based on the systems you work with and knowledge of the scte messages in the stream for rules where the action is modify , you need to define the section , field , operation , and value for the modification essentially, you are defining the message you want to replace the existing scte 35 message with to add additional rules, click + add above the triggers in the create new rule dialogand repeat the steps above when you are finished, click save to save the rules and close the create new rule dialog click save again on the create new scte 35 modification profile screen to save the profile testing rules using the scte 35 modification rule simulator once created, scte 35 modification rules can be tested directly within the zen master interface we strongly recommend using the simulator to test known scte 35 messages to ensure the expected results using the scte 35 modification rule simulator click the simulator tab on your profile after choosing the simulator tab, you can enter an example message in the input field and run it against your defined rules if you want to use a message from an existing source, go to the source details here, you can select a scte 35 message and copy it source scte log the scte35 column does not appear by default, but you can reveal it by selecting it in the columns selector the rules and associated priorities of actions will be matched in turn and applied against the example input the decoded message and modification result are made available in json or xml format