QuVIS Acuity, User Manual

Page: 53 / 200

DCI JPEG2000 2K Playback Support
The QuVIS Acuity provides native full-resolution playback support for 2K 12-bit 4:4:4:0 JPEG2000 image formats.
This includes full-container (2048x1080) and partial container formats including: scope, flat, scope-on-flat, and flat-
on-scope aspect ratios.
DCI JPEG2000 3D (2K) Playback Support
The QuVIS Acuity provides native playback of 3D (2K) Digital Cinema content. 3D Digital Cinema content is a 2K
image format. Both left eye and right eye image data (12-bit 4:4:4) is stored in a single file (per reel) but played as
two synchronized video streams.
Note: The QuVIS Acuity must be configured with a VSP card version 9 to be capable of supporting 3D JPEG2000
playback. A minimum software version is also required. If you have any questions, please contact QuVIS.
DCI JPEG2000 4K Playback Support
The QuVIS Acuity supports the ability to extract and playback (output) a 2K picture from a 4K composition. Due to
the architecture of a wavelet-encoded image, the 2K image is created by partially decoding the 4K image so that 2K
(2048x1080 or partial container) of image data is extracted and can be displayed. This 2K-from-4K capability allows
the Acuity to be used in combination with QuVIS QuStudio to master and preview a 4K Digital Cinema Composition
using the Virtual Tape Editor.
Encrypted Content Processing
The QuVIS Acuity natively supports Digital Cinema Content Encryption standards for both playback (content
decryption) and mastering (content encryption).
Encrypted Content Playback
Content encrypted using Digital Cinema encryption standards are protected from unauthorized use and require the
use of machine specific decryption keys delivered as Key Delivery Messages or KDMs (SMPTE 430-1: D-Cinema
Operations – Key Delivery Messages). The KDM files enables the Acuity to decrypt the encrypted content for
playback purposes.
Before a KDM file can be generated for a QuVIS Acuity, the server must be registered with the content
management system by providing the public key of the machine via a signed “X.509” device certificate file. The
signed device certificate file is generated by QuVIS and is stored in the
/users directory on the system storage
volume.
The KDM file, issued by the content distribution authority, includes the necessary decryption information for the
target playback server to play the encrypted content.
IMPORTANT! The QuVIS Acuity is a content mastering server and is not intended to operate in insecure
environments without manual intervention. The QuVIS Acuity is capable of playing encrypted digital Cinema content
without Secure Link Encryption or Forensic Watermarking for content mastering and post-production preview
purposes. Secure Link Encryption and Forensic Watermarking is a Digital Cinema
Exhibition requirement and does
not apply to the QuVIS Acuity when used in a secure mastering environment.
Mastering Encrypted Content
The QuVIS Acuity is capable of encrypting both DCI JPEG2000 and QPE Composition media files including
individual assets or entire tracks.
The Acuity does not provide content management services (e.g. KDM authoring) to create decryption keys for
content it encrypts. To facilitate key authoring, the Acuity must be registered with a content management system
(e.g. QuVIS QuStudio). The Acuity will use public key of the content management system to encrypt the selected
content. This structure allows the Acuity to encrypt the content and the content management system to generate
decryption keys in the form of KDM files for content encrypted using its public key. The public key of the content
management system is stored in the
/users directory on the system storage volume in the form of a “*.pub.pem” file.
QuVIS Acuity
™
Page 52 QSR Version 3.3