Enabling watermarking
Overview
OpenTV Video Platform is integrated with QuickMark, the client-side watermarking solution that is offered as part of NAGRA's Security Services Platform (SSP).
This is enabled or disabled by NAGRA per deployment. To enable watermarking, please contact your NAGRA representative.
Prerequisites
- For QuickMark watermarking to work end-to-end, the following SSP services must be deployed/enabled:
- NexGuard QuickMark service
- Watermark detection service
- Make sure that devices are provisioned/added with the correct device information. This is necessary so that QuickMark can provide the correct type of surface for devices that support playback of HDR content.
That is:- Provisioned devices (STBs, etc.) must have
deviceInformation.device.hardware
set correctly. - When adding an open device (first-time sign-on), the request must include the correct
deviceInformation
. See Authentication.
For devices that have already been provisioned (for example, ones already being used by customers), you must ensure that the correct device information is set for them (for example, by means of a script).
- Provisioned devices (STBs, etc.) must have
Enabling QuickMark watermarking
In addition to enabling watermarking in Platform, you need to:
- Set a usage rule profile for watermark-enabled channels to enable any restrictions required by content owners (e.g., disable AirPlay) and apply it to the appropriate channels. See:
- Indicate the channels/content for which watermarking is to be enabled. You can do this:
- At ingest, by setting
qmWaterMark
totrue
in the relevant entity'sSecurityInfo
block. See: - When creating a channel or content via API, by setting
qmWaterMark
. See: In OpCon, by editing the appropriate technical channel or content.
Re-ingesting the content will overwrite any changes made to the watermark flag that you have made in OpCon.
- At ingest, by setting
- Indicate the dynamic ranges for the content/channel. QuickMark requires this so that it can provide the appropriate surface. (Different surfaces are required for HDR content.) You can do this:
- At ingest, by setting a value for the
dynamicRange
attribute on the technical content/channel. See: - When ingesting via API, by setting
dynamicRange
. See: In OpCon, by editing the appropriate technical channel or content.
- At ingest, by setting a value for the
- Enable watermarking in your client application. See Client-side watermarking.
See also
Client-side watermarking (in the Client integration guide)