Other preprocessing methods

Watermarking supports other methods for preprocessing content, including the use of separate subdirectories to house variant content, and the use of unlabeled "A" variant segments to support easy disabling of watermarking. However, these methods are currently not self-serviceable.

Before you begin

  • To support these methods, you need to work with Akamai professional services to implement advanced metadata in your AMD property. Review what's here, then contact your account representative ("rep") for assistance.
  • We recommend that you use the "filename-prefix AB naming" method for preprocessing. If you include advanced metadata in your AMD property, it may limit self-service modifications of it in the future.

Convert and store using the "directory-prefix AB naming" method

Instead of prefixing the filename, the path just before the segments/fragments are prefixed with "/a/" and "/b/" subdirectories. Below is an example that uses a presentation called "baseball," with a master playlist, a media playlist, and several TS segments.

<base_path>/baseball/master.m3u8This contains relative paths to variants: 1080-media.m3u8, 720-media.m3u8

<base_path>/baseball/1080-media.m3u8This references relative paths to segments: /1080/segment_1.ts

<base_path>/baseball/1080/a/segment_1.ts

<base_path>/baseball/1080/a/segment_2.ts

<base_path>/baseball/1080/b/segment_1.ts

<base_path>/baseball/1080/b/segment_2.ts

<base_path>/baseball/720-media.m3u8This references relative paths to segments: /720/segment_1.ts

<base_path>/baseball/720/a/segment_1.ts

<base_path>/baseball/720/a/segment_2.ts

<base_path>/baseball/720/b/segment_1.ts

<base_path>/baseball/720/b/segment_2.ts

Additional requirements with this method

  • Advanced metadata. Your account rep needs to work with you to get an advanced metadata variable incorporated so that the Akamai edge recognizes that a subdirectory defines the variant for switching. You also need to work with your rep to ensure that you apply the appropriate settings in the Watermarking behavior in Property Manager.
  • Associated, non-video content. If you use this method, associated, non-video segment file content must be stored in the default location named in the various manifest files. This applies only if the files for this non-video content use different file extensions from the video segments. For example, if associated audio segment file content does not use the same file extension, the audio segment files must be stored in the default location named in the manifest file. This is covered in more detail in Separate audio and video segments.

Convert and store using the "unlabeled A variant" method

This is an additional support that can be applied to either of the available convert and store methods. It lets you easily disable watermarking once the requirement has passed. The watermarking vendor needs to leave out the specific "A" label from your content, based on your selected method—either no "a" leading the filename, or no "/a/" subdirectory in the path. Essentially, the "A" variant content just needs to maintain its standard naming and exist in the default location called out in the manifest file.

Additional requirements with this method

How do I "easily" disable watermarking with this method?

  1. Disable it in your AMD property.
  2. Update your client application (player) to request segment content from the default location called out in the manifest file.

Preprocessing examples

These show how segments might be stored on your origin, after conversion by your watermarking vendor if you're also using this method.

  • I'm using the "filename-prefix AB naming" method.

    <base_path>/baseball/master.m3u8This contains relative paths to variants: 1080-media.m3u8, 720-media.m3u8

    <base_path>/baseball/1080-media.m3u8This references relative paths to segments: /1080/segment_1.ts

    <base_path>/baseball/1080/segment_1.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/1080/segment_2.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/1080/b.segment_1.ts

    <base_path>/baseball/1080/b.segment_2.ts

    <base_path>/baseball/720-media.m3u8This references relative paths to segments: /720/segment_1.ts

    <base_path>/baseball/720/segment_1.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/720/segment_2.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/720/b.segment_1.ts

    <base_path>/baseball/720/b.segment_2.ts

    .
  • I'm using the "directory-prefix AB naming" method.

    <base_path>/baseball/master.m3u8This contains relative paths to variants: 1080-media.m3u8, 720-media.m3u8

    <base_path>/baseball/1080-media.m3u8This references relative paths to segments: /1080/segment_1.ts

    <base_path>/baseball/1080/segment_1.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/1080/segment_2.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/1080/b/segment_1.ts

    <base_path>/baseball/1080/b/segment_2.ts

    <base_path>/baseball/720-media.m3u8This references relative paths to segments: /720/segment_1.ts

    <base_path>/baseball/720/segment_1.tsUnlabeled, this facilitates easy disabling of watermarking.

    <base_path>/baseball/720/segment_2.ts

    <base_path>/baseball/720/b/segment_1.ts

    <base_path>/baseball/720/b/segment_2.ts