QTAKE LITE USER GUIDE 3.0

About

QTAKE Pro is the most advanced software designed and developed for video assist and DIT professionals. It logs, captures, plays, edits, and processes digital cinema camera’s video output and RAW recording. The main purpose of any video assist system is to provide immediate playback for the crew, but QTAKE Pro goes far beyond that. It provides a unique database, customizable to fit any project, real-time image processing up to 8K resolution, multi-camera support, on-set color grading, live editing, and much more.

The ability to capture metadata from a camera and other on-set devices makes QTAKE Pro an essential part of the workflow that fills the gap between production and postproduction. VFX supervisors around the world rely on QTAKE Pro to perform real-time on-set compositing with support for motion control and motion-tracking systems, GPI triggering, and CGI integration. QTAKE Pro offers unique stereoscopy support with industry-standard 3D output in live or playback mode and various 3D alignment modes using PLUS 3D View.

After the magazine is ejected from the camera, you can import RAW files into QTAKE Pro and match them to video recordings to preserve all metadata and on-set color grading. QTAKE Pro then provides the fastest and most effortless dailies export and sharing. The QTAKE ecosystem also includes QTAKE Sync (formerly QTAKE Server) and QTAKE Monitor for on-set and cloud-based collaboration. QTAKE Pro provides low-latency streaming and talkback to QTAKE Monitor, while QTAKE Sync provides project and media synchronization, independent playback, and metadata collaboration rather than streaming.

Thank you for taking your on-set video services to a new level.

---

New in 3.0

QTAKE Pro 3.0 introduces major enhancements to project management, synchronization, monitoring, and output routing, alongside a more customizable user interface and streamlined everyday workflows.

The release integrates project and access management directly into QTAKE, adds I/O monitoring sidebars, and expands source routing flexibility across GPU, SDI, and stream outputs. A dedicated UI toolbar and right-click support provide additional control over the user experience.

• New Project Window
• Integrated QTAKE Sync
• ThunderFace 4K Duo+
• I/O Sidebars
• Stream & Sync in QTAKE Lite
• Project Migration
• SRT Stream Input
• OSD Auto-record
• OSD Scan
• Slate Scan
• 6DOF Camera Tracking
• License Update
• UI Update
• Right-click Control

New in 2.5

QTAKE Pro 2.5 introduces a set of enhancements designed to help you move at the speed of film set. It brings more control to your fingertips and strengthens QTAKE as a single, efficient solution for lean productions. With highly anticipated Stream Deck integration, precise motion control playback, and an all-in-one approach to dailies, this update simplifies complex tasks and expands what a single operator can achieve on set.

• Stream Deck Integration
• Editor’s Timeline STRIP Mode
• TechnoDolly Updated Support
• Merge & Un-Merge Clips
• Match Method During Import/Link
• Media Type During Import/Link
• Intermediate LQ and Proxy HQ media types
• Garbage Matte Animation
• Multi-Line OSD

New in 2.4

QTAKE Pro 2.4 introduces major advancements in on-set creative workflows and interactive learning. This release features the new Multitrack Editor, enabling sophisticated on-set assembly with multi-layered blended sequences and more.

Additionally, version 2.4 introduces QTAKE Academy for integrated step-by-step training, expands immersive workflows for the Apple Vision Pro ecosystem, and implements NDI® 6 ADVANCED support for high-performance IP video integration.

• Multitrack Editor
• FX Animation
• Script Coverage
• QTAKE Academy
• Immersive Stream
• False Color FX
• STMap FX
• ILPD FX
• Wipe FX
• Conditional FX Groups
• HFR Support
• NDI® 6 Advanced Support
• Import QuickTime Metadata
• Export QuickTime Metadata
• AVID Export
• AUTO EXPORT Update
• DOCK Gesture Support
• Ovide Smart Antenna
• LUT FX Name in OSD
• Custom Bitrate for HEVC Export
• Shot Letter Increment Shortcut
• Ignore Record State
• View FX Auto-Enable Option
• Thumbnails Selector for EDIT’s Timeline

---

New in 2.3

QTAKE Pro 2.3 introduced powerful new features and enhanced functionality to streamline production workflows. A major milestone in this release is the integration of support for the new ThunderFace 4K Duo, enabling superior GPU-driven SDI output.

Version 2.3 introduces a range of significant enhancements, including:

• ThunderFace 4K Duo Support
• GPU OUT iCMU Output
• Dolby Vision® Trims Target Monitor
• Stereoscopic 3D Stream
• Stereoscopic 3D Export to MV-HEVC
• Overlapping Videohub Groups
• MRMC Flair Motion Control
• Garbage Matte Comp Mode
• FSI BoxIO Support
• Biometric Login
• Day For Night
• QTAKE Rehearsal Recording Indication
• Use IN2CORE Devices Only Preference in GPU Group
• Customizable FX Names
• Stream Authentication Requirements
• New LOAD Function
• Growing Files
• New Range Between Existing Ones

---

New in 2.2

Version 2.2 introduces a new set of industry-first features to redefine the standards of video assist tools and empower QTAKE Pro users with new, innovative capabilities and other enhancements.

• Dolby Vision® iCMU Output
• Dolby Vision® iCMU Preview
• Forensic Watermarking
• Interpolated Off-Speed Playback
• AJA ColorBox Support
• Export to Dolby Vision® HEVC
• Canvas Settings
• Right-Click Fast Clip Selection
• New LOOP/PONG Playback Options
• Individual Audio Gain Control
• MUTE LIVE Based on Recording
• MUTE LIVE Options per Input
• Permanent Delete
• New LIVE PASS Mode
• False Color Log
• QTAKE Monitor Nine Views Support
• UI Output to Views
• GPU OUT Full area mode
• Video Window Mode when Hiding

---

New in 2.1

Version 2.1 brings another major update to QTAKE Video Assist software, this time focused on performance. With the increasing demand for multi-camera 4K capture and playback as well as High Dynamic Range support, real-time rendering requires every bit of processing power from available hardware.

The most important new features in QTAKE Pro v2.1 are listed below:

• Metal Support
• Unlimited DOCK Slots
• QOD HDR Output
• UI HDR Support
• Local Media Management
• Clip List Selection
• Mono Audio Support
• Blackmagic Design URSA Auto Recording
• NDI v5
• Pipeline Update
• GPU OUT Orientation
• Task Progress

New in 2.0

Version 2.0 marks an immense milestone in the development of QTAKE, with the new licensing model and substantial under-the-hood improvements. The application name has been changed to QTAKE Pro not just to emphasize its dedication to filmmaking professionals, but also to mark the beginning of the tighter collaboration with its user base, in the form of a public roadmap, features voting, educational webinars as well as premium technical support, which is essential to any flawless product use.

Following is the list of the most important features:

• Installation
• Licensing
• License Activation
• Custom Bundles
• Integrated QTAKE Lite
• Apple Silicon Support
• Unlimited Streaming
• Instant Playback
• Blackmagic Design RAW
• SAML Integration

---

Software Requirements

The change log for the latest release of QTAKE Pro can be found here. The following requirements may differ if you run an older version of a newer beta build.

QTAKE Pro requires macOS 14.6 or newer.

• Recommended AJA video cards driver version is 17.6 or newer (including version 18).
  • Avoid using UFC firmware on cards that support it.
• Supported Blackmagic Design video cards driver version is 16 or newer.
• Recommended Deltacast video cards driver version is 6.18 or newer.

---

Upgrading from QTAKE 1.6

There is a major change to QTAKE installation starting with version 2.0. To support multiple macOS system users without permission conflicts, the database and other supporting files are stored inside the home folder of each system user. Existing users will be prompted with the migration offer on the first run of QTAKE Pro 2.0.

If you want to keep your old projects, click the MIGRATE USERS AND PROJECTS button. This will copy the complete database to keep all data intact. Required media files will be copied to a new QTAKE PRO STORAGE folder on all your media drives using the hard-link method which doesn’t require additional disk space because it is just referring to original files. This way you can still access media through the old QTAKE version, but keep in mind any change made there will not be propagated to QTAKE Pro 2.0, or vice-versa.

The migration prompt will appear only once at the first run of QTAKE Pro or QTAKE Pro NFR.
If you need to migrate legacy QTAKE project(s), use QTAKE Sync, XML Export & Import options, or contact us.

Live clip FX
After migration from QTAKE 1.6 to QTAKE Pro 2.0 you will notice that clip effects are missing from live clips. This is unfriendly, but expected behavior. In most cases, your live clip effects will be the same as the ones on the last recorded clips, so you can simply copy them from the previous recording.

Automatic Updates

In addition to manual installation, there is an automated update process available in QTAKE Pro. As soon as a new version is released, you will be notified using a red badge in the Status Bar. When you click on it, the list of NOTIFICATIONS will open, displaying what update is available:

Here you can DISMISS the notification or SHOW the update. If you decide to proceed, a dialog with update details will pop up:

Based on the notes, you can decide whether to proceed with the update using the DOWNLOAD button. In case you want to do the update later, click the DISMISS button and you will be presented with the same update on the next run of QTAKE Pro. If you want to skip all minor updates and wait until the version number is changed, click the SKIP THIS VERSION button. It is always recommended to keep your app up-to-date.

---

Network Requirements

Networking has become a significant part of the video assist and DIT profession. Whether you are connecting multiple QTAKE Pro systems to provide master/slave control, or streaming video to on-set and remote clients, or just connecting external devices to your computer, a network connection is inevitable.

Bandwidth

Required network bandwidth depends on the use case. The most demanding functionality is video streaming, which can average around 3-4Mbps per client per camera for high-quality HD feeds. A single access point can handle around 10 wireless streaming clients, so you should scale your network accordingly. Use a Wi-Fi scanner and manually select radio channels to avoid dropped network packets caused by interference. When possible, use an ethernet cable instead of wireless connectivity.

Ports

In most cases, no additional configuration is necessary to use QTAKE Pro on your network. However, users on restrictive networks may need to allow traffic on specific ports depending on the QTAKE functionality they want to use.

License activation

To activate and deactivate an existing license package, the following port must be enabled:

• shop.qtakehd.com, TCP port 443

QTAKE Stream

To stream over the local network, enable traffic to and from the following ports on the QTAKE Pro Video Assist System:

• TCP 8560
• UDP 8567 – 8570

For QTAKE Cloud Stream, enable traffic for the following:

• api.qtake.cloud, TCP 443
• sync.qtake.cloud, TCP 8500
• stream.qtake.live, UDP 8550 – 8551

Do not rely on any particular IP address these currently resolve to. The stream.qtake.live record is updated on each new deployment of QTAKE Cloud service instances, which may happen at any time. If you use it to configure your firewall, ensure it polls for changes every few minutes.

Due to enhanced security updates and the discontinuation of new features and bug-fix support for QTAKE 1.6, local streaming from QTAKE Pro to QTAKE 1.6 is no longer supported. However, Cloud stream functionality is not affected.
Additionally, QTAKE Pro remains backward compatible with QTAKE 1.6 and can receive its stream.

QTAKE Sync (formerly QTAKE Server)

To access independent playback over the local network, enable traffic to and from the following ports on the QTAKE Sync system:

• TCP 8500 – 8600
• TCP 44443

For QTAKE Cloud Sync, enable traffic for the following:

• api.qtake.cloud, TCP 443, 44443
• sync.qtake.cloud, TCP 8500, 8501, 443 and 44443
• storage.googleapis.com, TCP 443
• qtake.storage.googleapis.com, TCP 443

---

Hardware Requirements

The basic configuration of a working QTAKE system consists of a computer, a video capture card for input (and optionally output), storage for the recorded and imported media, a GPU output device, and optionally external audio device. Recording, processing, and outputting multi-channel HD and 4K video is taxing these components, and some older computers will work with standard playback requirements. Adding image processing, compositing, or higher-quality codecs could result in dropped frames if the system is not up to the task.

QTAKE LITE is a self-contained, entry-level, dual-channel software built on the same technology as QTAKE Pro. It works with a multitude of Apple Mac computers, video cards, and audio devices. Listed below is a recommended hardware configuration for the LITE version.

Apple Silicon Support

Apple Silicon has brought the next level of performance and thermal management to Mac computers. With QTAKE Pro, which runs natively on Apple Silicon machines using universal binary code, this new, powerful platform can be used to its full extent, eliminating the limitations imposed by the previous architecture.

Secure Enclave

To fully support flexible QTAKE Pro licensing, which allows you to easily transfer licenses between computers, Mac with T1, T2, or Apple Silicon is required. Without Secure Enclave contained in these chips, you will not be able to deactivate the license. The activated license will be locked to a single computer until it expires.

Apple Metal Support

The METAL framework provides unparalleled graphics performance on Apple hardware. Using this modern programming interface QTAKE can perform real-time image processing of multiple 4K streams in high color fidelity. In addition to accelerating video and CGI rendering it is also essential in producing HDR image representation in QTAKE UI.

---

SECURITY NOTICE

USE OF LEGACY SOFTWARE

The use of legacy software is strongly discouraged, particularly in environments with security, data integrity, or compliance requirements. Although some components may remain technically compatible, legacy software such as QTAKE 1.6 lacks critical controls to ensure data consistency and prevent undetected transfer errors.

Moreover, legacy software no longer receives security updates and has not been validated against recent security assessments. Known issues affecting database consistency and synchronization remain unresolved. For security-focused workflows, use of the currently maintained applications, such as QTAKE Pro and QTAKE Sync, is strongly recommended.

---

Configurations

The following configurations are recommended to achieve optimal performance across QTAKE versions. Performance varies greatly depending on the selected video codecs and image processing requirements. Generally, we recommend getting top-of-the-line Mac models to allow enough headroom for complex projects.

---

---

QTAKE Lite

QTAKE LITE is a lightweight, dual-camera version of QTAKE. It can run on less powerful hardware because it lacks advanced image processing, proxy recording, and other CPU and GPU-intensive features.

CPU
M1 (or Intel quad-core i7)

RAM
8GB memory or more

GPU
M1 (or AMD Radeon Pro)

MEDIA STORAGE (recommended read/write speed of 150 MB/s)
External USB 3 or Thunderbolt Drive

VIDEO CARD I/O
Two 1-channel or one 2-channel video card. In the case of live processing, either two full-duplex or two 2-channel cards are required.

ANALOG AUDIO IO
Focusrite Scarlett 2i2 (or any other external audio card with Core Audio driver)

VIDEO OUT AND GPU OUT
The LITE version is designed to be a simple but powerful 2-channel recorder. QTAKE Lite supports VIDEO OUT through supported video I/O cards, including processed output and hardware passthrough where supported. It also supports GPU OUT through compatible ThunderFace 4K Duo+, ThunderFace 4K Duo, and QOD+ devices. Output functionality is included in QTAKE Lite and is not activated through an additional OUTPUT module.

---

VIDEO CARDS

Following SDI video cards are natively supported in QTAKE. Additionally, QTAKE can capture video coming from NDI®, RTSP (Teradek Cube), QLS (QTAKE Live Stream), or video cards supported by the macOS system, such as USB-3 connected Teradek Bolt Receiver.

1. Multi-channel SDI Passthrough requires frame-synced inputs.
2. Not possible to mute SDI passthrough audio.
3. Passthrough video has 2 frames of delay.
4. Only available in 10bit mode.
5. Does not support VITC1 timecode.

What if I use more than one video card?
The information in the table is only valid as a comparison between single cards. Multiple video cards can be used to allow for up to eight HD or four 4K inputs and outputs.

Output
The term “output” in this chart only refers to SDI output from the video card. GPU output from ThunderFace 4K Duo+, ThunderFace 4K Duo and QOD+ is independent of video card outputs.

---

---

Installation

Installer places the QTAKE Pro application into the Applications folder to make it available to all system users. With each new release, you will get an email with a link to download Installer containing the latest build of QTAKE Pro. Running this Installer will update your system without affecting your settings or projects. If you prefer an automatic update process, see more details in the Automatic Updates section.

System User Accounts

Starting with version 2.0, the QTAKE Pro application can be used by multiple system user accounts. However note, that each system user will have their own database, which means his own set of projects. If you want multiple users to share the same projects, use a single system account and multiple QTAKE users.

---

Before you start

For performance reasons, make sure to UNCHECK the following features in the macOS System Preferences:

• Energy Saver - Put hard disk(s) to sleep when possible
• Energy Saver - Automatic graphics switching (in case you are running a computer with this option)

It is also recommended to set the Computer sleep and Monitor sleep to NEVER and disable any screen saver. Turn off the Spotlight indexing service for your media drives in the System Preferences by putting the hard drive into the Privacy section.

We recommend using static refresh rate of 60Hz on GUI or External monitors to prevent unexpected screen flashing. Variable refresh rate or Apple’s ProMotion is not recommended as it can create excessive screen refresh or black frames.

EULA

QTAKE Pro will present an End User License Agreement on the first start. Enter your LICENSEE NAME, LICENSEE COMPANY, LICENSEE EMAIL, and LICENSEE ADDRESS into corresponding fields and agree to the terms of the agreement if you want to proceed.

Migration

If you are an existing QTAKE user and you want to preserve current projects, refer to the Upgrading from QTAKE 1.6 section.

Custom Logo for No Video Signal Screen

To use a custom logo for the NO VIDEO DETECTED screen in QTAKE Pro View, drag and drop a PNG file named QTAKE_View_Logo.png onto the QTAKE Pro application icon in the macOS Dock. QTAKE will confirm the successful application with a SYSTEM INFO message saying Stored New QTAKE View Logo.

---

Features

The following sections describe the available QTAKE versions, their operational modes, feature availability, and module requirements.

---

Feature Details

Input

Recording

Proxy

Streaming

1. Up to eight devices can stream concurrently in QTAKE Lite.

Playback

Clip Navigation

Database

Import

Export

View FX

Clip FX

Color Grading

Stereoscopy

Editing

Compositing

CGI

Output

Scopes

Network

Integrations

---

Licensing

To provide sustainable development with frequent updates and premium technical support, there is no permanent licensing possible starting with QTAKE Pro 2.0. In addition to daily, weekly, and monthly rates available in the online shop, new 1-year and 3-year license pool options are offered exclusively through the sales network. Contact your dealer for more info.

QTAKE Rental Shop

Licenses for QTAKE applications are ordered through the online QTAKE Rental Shop. When creating a rental, select the intended application as well as the required MODULES, DATE RANGE, and OPERATORS, and enter a RENTAL NAME, which is used as an identifier of the license. Only selected operators will be able to activate or deactivate the license in the application for which it was created. To access the online shop and order rentals you will need to create an OWNER shop account.

You can access QTAKE Rental Shop directly from the QTAKE Pro user interface. See the LICENSE section for more information.

To create a shop account and rent modules visit: QTAKE Rental shop

For instructions on how to use the shop, see: QTAKE Rental Shop User Guide

Custom Bundles

Unlike previous versions of QTAKE, where discounted bundles were locked to a specific set of modules, with QTAKE Pro you can create any combination of modules, and each additional module will increase the discount percentage. A similar policy is available for customers with multiple licenses. Contact your dealer for more info.

License Pool

All QTAKE owners registered in the online shop have a pool of licenses associated with their accounts. When a long-term license is purchased, it will be added to this pool. Subsequently, creating a new rental will result in a free license for modules that are available in the license pool for the specified date range. You can combine free modules with paid modules at will. Usually, your license pool will contain long-term licenses with the most commonly used modules. However, if your current job requires some special module, which is not part of your long-term license, you can simply add it to your rental and pay for it on a need-to-use basis.

The SYNC module pool is shared between QTAKE Pro and QTAKE Sync, and the CENTRAL module pool is shared in the same way. Using either module to create a license for one application reduces the available capacity of the corresponding shared module pool.

A shared module pool does not make application licenses interchangeable. A license is created for either QTAKE Pro or QTAKE Sync and appears only in that application’s activation window.

License Activation

Each license for QTAKE Pro is created in the online shop using the NEW RENTAL page, whether it is a paid rental or a free one created from your license pool. However, instead of specifying a machine, you will now select operators who can activate the license. Activation is performed directly in the QTAKE Pro application to avoid misconfiguration. Each license can be deactivated at any time to provide seamless transfer to another computer, effectively replacing USB dongles. This transfers the license between computers for the same application; it does not change the application for which the license was created.

Select the intended application when creating the license in QTAKE Rental Shop. A license created for QTAKE Pro is not displayed in the QTAKE Sync activation window, and a license created for QTAKE Sync is not displayed in the QTAKE Pro activation window, even when its SYNC or CENTRAL module was drawn from a shared pool.

An internet connection is required at the time of activation for necessary communication with the License server. When connected to a restrictive network at the time of activation, refer to the firewall ports section.

See ACTIVATE LICENSE for instructions on activating a license and interpreting its activation status.

When upgrading an existing QTAKE Pro 2.x installation to QTAKE Pro 3.x, see Reactivating a QTAKE Pro 2.x License.

---

QTAKE CREDITS

Unlike other QTAKE functionality, which requires a license file with specific modules, QTAKE Cloud Stream and QTAKE Cloud SYNC services uses consumable CREDITS.
See more info in the

• Cloud Stream section,
• Cloud SYNC section of the QTAKE Sync User Guide (formerly QTAKE Server).

---

Workflow

Originally designed as a feature-rich video assist tool, QTAKE now goes way beyond its roots. It offers complete on-set workflow, from recording camera output to exporting RAW-based dailies. Using a single tool for all these tasks saves a lot of time because there is no need to export, import, and convert projects between various 3rd party apps.

For example, you can apply the same look to RAW files you used during live monitoring. It simplifies rendering dailies to a single-click action.

---

Core Concepts

Before working with recording, playback, metadata, and exports, it is helpful to understand a few core concepts used throughout QTAKE Pro and the whole ecosystem.

Clip

A Clip is the central container used to organize media throughout the production workflow.

Rather than representing a single media file, a Clip groups all related media, metadata, and visual effects into a single entity. This allows different media representations of the same content to remain associated with a single Clip throughout the project.

Depending on the workflow, a Clip may contain one or more media types, including Recorded, Proxy, Intermediate, RAW, or other supported media types.

Metadata is stored at the Clip level and is shared across all associated media.

LIVE Clip

A LIVE Clip represents the current LIVE input from the selected source.

It is used while working with a LIVE signal for monitoring, live image processing, metadata entry, and recording.

When recording finishes, QTAKE creates a new Clip and associates it with the recorded media together with all metadata collected during recording.

While working with a LIVE signal, the LIVE Clip uses a temporary internal representation. A permanent Clip ID is assigned automatically when a new Clip is created by recording.

INPUTS AND RECORDING

QTAKE can record video, audio, and metadata from various sources. It usually captures uncompressed signals using the SDI video card, encoding it to the efficient Apple ProRes codec and storing it in Apple QuickTime file format. See the PROJECT Menu section for more details about the Project setup.

Following is an overview of the recording features:

• Recording 8 camera feeds with up to 16 channels of audio
• Video, audio, and metadata mixed from different sources
• Adjustable delay for video, audio, and timecode
• Pulldown removal recording mode
• Manual or automatic record start and stop
• Setting multiple ranges during recording
• Thumbnail frame selection during recording
• Full-resolution screenshots
• Entering metadata during live monitoring or recording
• Automatic incrementation of the take number
• Capturing metadata from SDI signal or network interface
• Simultaneously recording processed PROXY media files
• Recording live composites if quick export is needed

For more details about recording, see the RECORD Menu section.

---

PLAYBACK

There are numerous playback options available in QTAKE to provide the best possible navigation through clips, which sometimes contain multiple takes recorded in a single run.

• Regular speed forward and reverse playback
• Variable speed forward and reverse playback
• Speed ramping with multiple keyframes
• Frame-by-frame and custom time skip function
• Jump to IN or OUT mark
• Jog and shuttle playback
• Time slider
• Multiple IN/OUT ranges with multiple groups
• Chapter markers with conversion to ranges
• Loop single range or all ranges
• Timecode or frame count display
• Slave playback with custom offset
• Synced playback with custom offset for each View
• GPI-triggered playback

For more details about playback see the PLAY Menu section.

Instant Playback

All video assist operators know how frustrating it is to wait for the camera to cut to provide playback. With the Instant Playback feature, you can start playback as soon as the director asks for it, even if the camera is still rolling. QTAKE will record the rest of the take in the background so you can have edit-ready proxy files exactly matching the camera recording, including off-speed shots up to 60 fps.

To use this feature, set the Enable Instant Playback preference to YES. PLAY command activates the feature. It’s triggered by using the keyboard shortcut or clicking the PLAY button in the PLAY toolbar. You can continue monitoring the LIVE signal by clicking on the LIVE clip from the LIST or clicking the LIVE button in the PATCH toolbar. Instant playback clip is available during the whole recording process.

Note that PATCH to DISK always loads the last played clip in the View. It might be the Instant Playback clip during recording or an already recorded clip.

Instant Playback mode uses a fragmented recording method that puts additional strain on the media drive. Consider using faster drives if you wish to enable this feature.

Personal Playback

Traditionally, the video assist operator has provided playback for the director. The big downside of this centralized playback concept is that all on-set monitors show the same clip. However, sometimes it is required to show a different clip to the producer, script supervisor, VFX supervisor, etc.

QTAKE Sync application (formerly QTAKE Server) solves this problem by providing independent playback for any authorized crew member. You can access a QTAKE project through the QTAKE MONITOR app on personal portable devices such as iPhones and iPads. In addition to clip browsing and playback, crew members can enter metadata values independently of the QTAKE operator.

All data is automatically synchronized so you can share all information, while QTAKE Sync will not allow duplicate value entries. For example, the script supervisor doesn’t need to enter lens info because it has already been entered by the assistant camera or extracted directly from the SDI camera feed.

---

OUTPUTS AND STREAMING

The most common output from QTAKE is over the SDI interface. You can achieve this using a video card output, or you can also use a dedicated ThunderFace 4K Duo+, ThunderFace 4K Duo or QOD+ (QTAKE Output Device), which offers lower latency and more advanced output options, such as multi-view, stereoscopic output, etc. In addition to traditional SDI, you can use the NDI® interface, which provides high-quality output over standard network infrastructure. NDI input and output require STREAM module license.

WIRELESS STREAMING

One of the many powerful features of QTAKE is wireless streaming to iOS devices. Using a custom streaming protocol, QTAKE provides secure, ultra-low latency output of the processed image for up to 160 clients. Streaming can work over a local Wi-Fi network, but it can use QTAKE Cloud to establish a remote session over the Internet. See more details in the STREAM Menu section.

---

Dolby Vision®

QTAKE integrates support for the Dolby Vision set of technologies for HDR mastering and delivery, developed by Dolby Laboratories. One of the most important use cases this integration enables is remote color-grading. There are many cases when clients can not attend editing or color-grading session in person and can not rely on exported clips because of the slow turn-around. QTAKE offers a solution for interactive and effective remote grading thanks to its high-quality, low-latency streaming of Dolby Vision-enabled content. Current Dolby Vision functionality is included in the GRADE Module.

10-bit color depth required
Dolby Vision integration in QTAKE was designed for the 10-bit QTAKE version to provide the best experience. Most of the features work only with a project set to 10-bit color depth. If COLOR DEPTH is set to 8-bit and you try to switch the project HDR mode to Dolby Vision, you will be prompted to switch to 10-bit or revert to HDR10 mode. The same prompt requires action if the project is already set to Dolby Vision and you attempt to lower COLOR DEPTH to 8-bit in the COLOR tab of the Project Settings > Project Area Detail View.

Setup

Set HDR MODE to Dolby Vision® 2.9 or 4.0 in the HDR tab of the Project Settings > Project Area Detail View.

Next, select the MASTERING and TARGET monitors from the available presets.

Alternatively, turn on CUSTOM to manually set PRIMARIES, WHITE POINT, MINIMUM LUMINANCE, and MAXIMUM LUMINANCE according to your monitor specifications.

Analysis Tuning

When HDR MODE is set to Dolby Vision® 4.0, the HDR tab also provides ANALYSIS TUNING.

Analysis Tuning controls the balance between highlight detail and content mapping used by Dolby Vision analysis. The tuning applies different spatial filtering to less relevant highlight detail such as small speculars, noise, and compression artifacts, providing different starting points for content mapping and trimming. Depending on the selected tuning, L1 metadata values for the same image may vary.

The following Analysis Tuning options are available:

• Legacy CM4 L1 matches the analysis of the original, very conservative CMv4.0 algorithm.
• Most Highlight Detail / Most Mapping uses the lowest-strength filter of the new analysis options. It retains the most highlight detail and should result in no visible clipping, but requires the most mapping and produces the darkest starting point of the new analysis options. Clipping should be restricted to detail-less speculars, noise, and artifacts. Compared with Legacy CM4 L1, this filtering is substantially stronger and more tolerant of speculars, artifacts, and noise.
• More Highlight Detail / More Mapping
• Balanced permits some clipping to reduce the strength of mapping while keeping clipping minimized to preserve highlight detail.
• Less Highlight Detail / Less Mapping
• Least Highlight Detail / Least Mapping uses the highest-strength filter. It can result in visibly clipped highlights but requires the least mapping, producing the brightest mapped image. This can provide a brighter overall image when mapping to SDR 100 nits.

The selected Analysis Tuning also determines which analysis modes are available in the DOLBY VISION Menu.

Input

If available, QTAKE will extract frame-based Dolby Vision® metadata when capturing live HDMI signal using a compatible video card. In the case of SDI, QTAKE will extract Dolby Vision metadata if the signal was generated by another QTAKE system. In addition to live input, QTAKE can also import video files with metadata contained in the external XML file.

Output

When using HDMI output, Dolby Vision® metadata is embedded into the signal using the “tunneling” method, compatible with Dolby Vision TV devices. Additionally, QTAKE can output Dolby Vision-enabled content over SDI output. In this case, metadata is embedded into the SDI signal to provide a connection to another QTAKE system. When remote monitoring is required, QTAKE will embed Dolby Vision metadata into QTAKE Cloud Stream. See more info in the Live Stream section below.

Live Analysis

When Dolby Vision® output is enabled and no metadata is detected in the input signal, QTAKE will automatically perform Dolby Vision Live Analysis in real-time. The result of this analysis is the L1 metadata, used to provide Dolby Vision enabled output to supported systems, such as Dolby Vision TV devices or another QTAKE system.

PAUSE DOLBY VISION® LIVE ANALYSIS

To pause real-time image analysis performed by the Dolby Vision processing use the HERO FRAME mode for the LIVE clip. It will keep the Dolby Vision metadata set to the HERO FRAME value. This function is useful when performing live color grading that would otherwise be dynamically compensated by the Dolby Vision processing. When you finish live color adjustments, you can switch the Dolby Vision mode to Live Analysis to resume dynamic processing.

Live Stream

As mentioned, the most common use case empowered by Dolby Vision® support in QTAKE is the remote color grading or editing session. This setup requires two QTAKE systems:

SENDER - QTAKE System residing in the color-grading or editing suite, capturing color-graded Dolby Vision output and streaming it over the QTAKE Cloud.

RECEIVER - client-side QTAKE system responsible for receiving QTAKE Stream and providing output to Dolby Vision-enabled HDMI monitor or a TV device.

To enable Dolby Vision metadata in QTAKE Stream, open the connected-devices interface on the sender QTAKE system, reveal the secondary device options, and set HDR to Dolby Vision for the required stream. On the receiver system, enable Dolby Vision output as described in the Dolby Vision output section.

iCMU

QTAKE can perform real-time Dolby Vision® analysis, output Dolby Vision over SDI and HDMI, and stream from QTAKE to QTAKE. It supports the Dolby Vision modes available for the selected Analysis Tuning and an Internal Content Mapping Unit (iCMU) with Trim Controls. The Dolby Vision Content Mapping Unit (CMU) enables real-time Content Mapping processing for Dolby Vision-mastered content to move color grading in QTAKE Pro to the next level. During the content creation, the Dolby Vision Content Mapping also enables HDMI Tunneling, allowing you to preview the Dolby Vision work on a Dolby Vision consumer television.

HDR to SDR Mapping

If there are both HDR and SDR monitors on set, QTAKE can convert the HDR content to SDR using precise Dolby Vision tone mapping.

Note that the DOLBY module is required.

Workflow

1) Set HDR Project settings to Dolby Vision® 4.0.

2) Set the MASTERING monitor type according to the source HDR signal.

3) Set the TARGET monitor type according to the monitoring display.

4) If the camera supports HDR color space, set COLORSPACE to AUTO in Project Settings > Video Source, or select the color space manually.

5) To Allow iCMU mapping, go to SHOOT room -> VIDEO OUT menu -> Double arrow (») -> Set Dolby Vision® iCMU on desired View.

To customize Dolby Vision iCMU even further, check Dolby Vision Trim Controls.

Note that when using HDMI OUT and V-OUT simultaneously, QTAKE reserves the channel selected in the HDMI OUT menu for HDMI output, and you cannot set it for HDR to SDR mapping.

Simultaneous HDR and SDR output

With the introduction of iCMU, you can create a preview of Dolby Vision on HDR TV via HDMI Tunneling and simultaneously have Dolby Vision Tone Mapped output on your SDI Monitor (Rec.709) via iCMU Content Mapping.

Note that the DOLBY module is required.

Workflow

1) Set HDR Project settings to Dolby Vision® 4.0.

2) Set the MASTERING monitor type according to the source HDR signal.

3) Set the TARGET monitor type according to the monitoring display.

4) In Project Settings > Video Source, set COLORSPACE to AUTO or select the color space manually.

5) To activate HDMI tunneling, go to SHOOT room -> HDMI OUT menu -> Activate the HDMI OUT button and select the source View. Then click the double arrow (») and select Dolby Vision® 4.0 HDR Mode.

6) To allow iCMU mapping, go to SHOOT room -> VIDEO OUT menu -> Double arrows -> Set Dolby Vision® iCMU on desired View. Note that the channel selected in the HDMI OUT menu is reserved for HDMI output and cannot be used for iCMU mapping.

To customize Dolby Vision iCMU even further, check Dolby Vision Trim Controls.

---

METADATA

QTAKE is second to none when it comes to metadata. Projects and clips contain pre-defined metadata fields to store the most common information, but you can create additional custom metadata to fit any production type. Following is an overview of the metadata features:

• Fast metadata entry using choices and keywords
• Selection of the metadata source per field
• Metadata synchronization between cameras
• Automatic copy of value for Shot, Scene, or Episode
• Custom metadata fields with different value types
• Support for regional settings and units
• Access permissions using metadata groups
• Synchronization over local network or cloud
• Static and dynamic (frame-based) metadata support

See the META section for more details about metadata.

ALE

Avid Log Exchange is the most popular format for metadata exchange between 3rd party systems. QTAKE provides custom mapping for both the import and export of ALE files. You can find more details in the Import ALE and Export METADATA sections.

RAW

RAW module enables import, playback, and processing of RAW camera media. It is the highest quality media, comparable to analog negative stock. Usually, it is an uncompressed or slightly compressed read-out of the bayer sensor, which means it needs heavy-duty computing to transform it into a regular RGB image suitable for viewing. Each camera vendor has a different format and color science. QTAKE supports the following RAW file formats:

• ARRI RAW (.ari) and ARRI MXF (.mxf), including HDE
• SONY RAW and SONY X-OCN (.mxf)
• RED RAW (.r3d)
• CANON RAW MXF (.mxf)
• Blackmagic Design RAW (.braw)
• DMG (.dmg)

MATCHER

The Matcher compares imported or linked media with existing QTAKE clips to identify matching clips automatically.

Matching can be performed during importing or linking, or later using Merge Clips.

QTAKE supports multiple matching methods that use different combinations of clip metadata to determine the best match.

Since QTAKE is used to record camera output for video assist purposes, it contains all clips captured by the camera. However, the SDI interface used on most professional cameras limits the media resolution, frame rate, and color fidelity. To provide full-quality dailies, you can import or link original camera media.

After importing or linking camera media, QTAKE attempts to match the media with existing clips to preserve metadata, live grading, clip effects, ranges, and other clip information. The best matching method is based on CMF (Camera Media Filename) because it is 100% accurate. If no CMF is recorded, timecode, date, and camera letter is used instead. If the result is not 100% accurate, QTAKE will show all hits and let you decide which clip new media should link to.

Each imported or linked file will be represented by one row in the matching table. Clicking the row will toggle its color. If the row is discolored, it will be skipped, and only colored files will be imported. You can expand each row to select the import method. There are 4 options available based on the result of the matching process:

• CREATE - media file will be imported and stored as a new clip
• USE - media file will be attached to existing matched clip as respective media type
• CLONE - media file will be imported and stored as a new clip, but QTAKE will clone existing matched clip metadata
• AV SYNC - new audio clip will be created, and audio media will be attached to matching video clips

If imported or linked media is not attached to an existing clip using USE, QTAKE creates a new clip for that media. This can happen when no suitable match is found, or when you manually choose CREATE instead of USE. These newly created clips can be matched later with respective existing clips using Merge Clips from the LIST’s FUNCTION menu.

In some cases, you may need to narrow down the number of clips that QTAKE is trying to match to avoid false matches. You can do this using UNIT and SHOOT DAY filters, which will match import only to clips from the specific unit or shoot day. Additionally, you can easily discard the import of the MATCHED or UNMATCHED clips using the SKIP filter.

NOTE:
Matching identifies corresponding clips only.
It does not determine how imported media are classified.
Media classification is controlled by Media Type during Import or Link.

AUDIO SYNC

After matching and importing audio media, QTAKE will automatically synchronize it to video media, based on timecode. If the timecode is off, you use MEDIA Toolbar to adjust AV sync manually in 1/4 frame increments, providing sufficient precision even for the most demanding audio synchronization tasks.

RAW PROCESSING

Unlike video files, which are stored as RGB or YCbCr pixel data, RAW files are usually representing Bayer-type sensor readout that needs de-compression, de-mosaic, sharpening, color correction, and other image processing techniques applied to be visualized. This work is usually done by the vendor-supplied processing engine, which is mostly automated, but certain aspects of the process can be modified. QTAKE is using the INPUT FX page of the FX panel to present you with available options for each RAW format.

QUALITY CONTROL

Using RAW media playback and multiple in-out ranges, QTAKE can be used to create frame-based metadata, passing the QC info about image imperfections to post-production. For more information on how to create a new set of in-out ranges, see the RANGES section.

ON-SET DAILIES

During production, the first role of QTAKE is the video assist role, automatically recording the camera video output, while the camera is recording its full-quality original media files. After filling out the magazine, it is taken out of the camera to create backup copies and export dailies for editorial. This is where the second, DIT role of QTAKE comes into play. Having all the metadata and color decisions collected during recording, QTAKE can automatically use this extensive information to process RAW media into edit-friendly Apple ProRes, Avid DNxHD, or any other supported file format and codec, saving production time and issues caused by data transfers between different systems. See the Automated Pipeline Export section for more details.

REAL-TIME IMAGE PROCESSING

All image processing is executed in real-time, which means it can be used both for live feed and recorded clips. It is recommended to always record clean log image without LUTs or overlays applied. This non-destructive workflow will allow you to tweak any aspect of the final image at any time during the life cycle of each clip.

COLOR GRADING

Most professional cameras will record and output flat signal with a wide gamut color space to provide as much dynamic range as possible. For on-set monitoring, you can just apply a simple Log to Rec.709 conversion using pre-defined LUTs to provide a standard contrast image. But filmmakers often want to establish a specific look when preparing and lighting the scene.

QTAKE offers professional color correction tools. In addition to internal processing, QTAKE can send live color grading data to an external LUT box to provide zero-delay processing. For more details on color correction see COLOR CATEGORY section.

LIVE VFX COMPOSITING

QTAKE has a dedicated room for compositing. It uses two video channels to perform real-time dual-layer composite using Chroma Key, Luma Key, Wipe, and various blending modes. Each layer can have an unlimited number of effects, such as transformation, masking, color correction, blur, etc. If more layers are required, the composite can be rendered and used as a single layer while adding a new one. QTAKE has full control over the timing of each layer, so compositing can be used for stacking motion control passes.

In addition to GPI triggering, QTAKE provides Slave Playback for synchronizing playback with an external source.

Depending on the workflow, Slave Playback can synchronize to an external timecode (TC Slave Playback) or to incoming motion-control rig data (Rig Slave Playback), allowing accurate synchronization of prerecorded background plates during motion-control compositing.

CGI

When the pre-recorded or pre-rendered background is not good enough, there is an option to import a 3D CGI scene. In combination with capturing motion control or motion tracking data, QTAKE can create a virtual 2D or stereoscopic camera to render a CGI background and composite it with a live or playback image. You can place a live layer at a certain 3D depth to have CGI elements appear in the foreground and background.

ON-SET EDITING

A simple built-in editor helps the director quickly check continuity. Fast trimming with all popular trimming types works both with precision frame-by-frame and view-drag modes. After switching back from the EDIT room, the sequence is accessible inside the SHOOT or COMPOSITE room as a regular clip.

AUTOMATED PIPELINE EXPORT

One of the most powerful features of QTAKE Pro is file export. After selecting clips in the LIST, click the FUNCTION button and choose EXPORT TO FILE.

Pipeline Export organizes export processing into reusable workflows.

Each Pipeline defines how source media are processed into the final deliverables. By combining processing nodes into connected workflows, a single Pipeline can automate grading, overlays, encoding, and delivery, making it easy to create consistent exports for different production workflows.

Pipeline Workflow

A Pipeline is organized into a series of processing stages. Each stage can contain one or more processing nodes that define how the media continues through the export workflow.

The workflow can branch at any stage, allowing multiple versions of the same source media to be processed simultaneously.

For example, a single Pipeline can:

• create both clean and processed versions of the same source media,
• apply different overlays or watermarks to different outputs,
• generate multiple output formats or codecs in a single export,
• export one version to an external location while storing another as a QTAKE-managed media file.

This allows all required deliverables to be created automatically during a single export operation.

The export dialog lets you choose the PIPELINE used for the export.

Click EDIT PIPELINE to create or modify the selected Pipeline.

Enable OVERWRITE if previously exported files should be replaced.

PIPELINE

The PIPELINE editor organizes the export workflow into five processing stages:

• READ – selects the source media.
• PROCESS – applies media processing and clip effects.
• OVERLAY – adds overlays, burn-ins, masks, or watermarking.
• ENCODE – defines the output format and codec.
• WRITE – determines where the generated media will be stored.

Each stage can contain multiple processing nodes, allowing the workflow to branch into one or more processing paths.

By branching the workflow, a single Pipeline can create multiple deliverables from the same source media while applying different processing, overlays, encoding settings, or storage destinations to each output.

READ

The READ node is used to specify the rendering source. Set the SOURCE MEDIA TYPE to define what type of media will be used to process selected clips. The AUDIO option is used to select if embedded or external audio should be used. IN/OUT RANGE defines if the whole clip duration is rendered or only part of it. In case of RAW media, you can select FILE-based or QTAKE-based INPUT FX RAW SETTINGS as well as RAW DEBAYER QUALITY. If set to AUTO, it will use quality settings from the playback interface. Read node can branch into multiple process nodes to speed up the rendering of multiple look versions.

PROCESS

Process node is used to apply MEDIA FX and CLIP FX.

• You can choose to render selected clips with all media effects stored for a specified media type or no media effects.
• You can choose to render selected clips with all effects stored for specified media type or only the LUT effect.

By default, the processing is done in the NATIVE resolution of the incoming frames, but you can select CUSTOM working resolution to automatically scale incoming frames to selected WIDTH and HEIGHT, using the selected FITTING method. Process nodes can branch into multiple overlay nodes to speed up the rendering of multiple deliverables using different overlays.

OVERLAY

The overlay node is used to apply FRAME LINES and BURN IN. Both of these functions are using templates, which can be customized by clicking the EDIT button. Overlay nodes can branch into multiple encode nodes to speed up exporting of multiple deliverables using different file formats and codecs.

ENCODE

Encode node is used to specify the output file format using MEDIA FILE TEMPLATE. Click the EDIT button to create new templates. Encode nodes can branch into multiple write nodes to provide multiple file copies in a single pass.

No Encode

When you choose to disable the ENCODE node, PIPELINE will effectively process only the READ and WRITE nodes. This will be the case in a situation like demonstrated in the screenshot below, where the PROCESS node is checked. Since no transcoding will take place, it will be ignored.
WRITE node will create hard link copies of clips to be processed, based on the criteria defined in the READ node, and name the files per FILENAME TEMPLATE selected. Hard-linked files do not occupy extra disk space. If hard links are not an option, e.g., the TARGET FOLDER is located on a different volume than the QTAKE Storage folder resides, the PIPELINE will copy clips and name them per FILENAME TEMPLATE selected.

Export to Dolby Vision® HEVC

Dolby Impact is a software encoder for the international H.265(HEVC) video compression standard, designed to create streams with the highest coding efficiency. The resulting output proudly delivers superior quality and lower bitrates, with the codec aiming to optimize content for the human eye.

To ensure correct export settings, users are advised to check the following:

• Dolby Vision Profile - 5 / 8.1 / 8.4
• OVERWRITE HDR10 Data - NO / YES
• Video Codec Quality
• Video Resolution
• Include Metadata
• Color Space - Source / Project

Files generated using Dolby Impact are compatible with playback on any device or software player equipped with a standard H.265 (HEVC) decoder.

Stereoscopic 3D Export to MV-HEVC

For correct stereoscopic export, clips being exported must be tagged as left or right eye. You can tag a clip in two ways:

• Before recording, select the input’s Video Source cell in Project Settings and use the STEREO 3D selector
• On an existing clip, set the tag using the STEREO 3D selector on the second page (») of the MEDIA toolbar

The tag is also visible in the LIST’s CAM column next to the camera letter in brackets, which helps you identify a stereoscopic clip.

Initiating EXPORT TO FILE (or AUTO EXPORT) with a stereoscopic template will create a new type of EXPORT TASK, which handles 3D export. It reads buffers from the left eye and right eye clips and processes both buffers in sync to allow storing inside 3D capable media files.

CLIP SELECTION

When exporting stereoscopic clips, the exporter scans through the selected clips and checks if each of them has a 3D pair. You can select only left-eye clips, or only right-eye clips, or both. The exporter handles all these cases and informs you about the result before an export task is created.

To set up the PIPELINE, start by choosing 3D MODE in the READ node. PROCESS and OVERLAY nodes are optional, and you may set them according to your needs.

ENCODING

Define a new MEDIA FILE TEMPLATE of the ENCODE node and choose HEVC/H.265 video codec. There are three 3D modes available automatically enabled when the 3D mode is set in the READ node:

• 3D - stereoscopic
• LEFT eye
• RIGHT eye

In case ENCODE NODE has 3D MODE set to LEFT or RIGHT, the other eye will be dropped, and only the selected eye will be encoded and stored. In case you want to store both eyes, create two ENCODE and two WRITE nodes, each for one eye, where you can specify separate filenames.

Custom Bitrate for HEVC Export

For HEVC (H.265) exports, the interface now provides the option to set a precise, custom bitrate, which is essential for professional delivery, editing and quality control.

Previously, users were limited to seven pre-defined quality presets (ranging from Ultra Low to Ultra High). Now, you can override these general presets by selecting the Custom quality option and manually entering a desired bitrate value in kilobits per second (kbps).

The available range for the custom bitrate is highly flexible, supporting values from 100 kbps up to 800,000 kbps. This control ensures you can meet specific technical requirements for file size and quality demanded by external NLEs.

WRITE

Write nodes are used to write the resulting file to TARGET STORAGE.

• INTERNAL
  Media file will be attached to the source clip with specified TARGET MEDIA TYPE and will use internal storage, just as if it was recorded or imported. It is limited to full duration because each media type for the clip should have the same duration. You can export clip as Proxy, Intermediate and Proxy Transcoded media type.
  
  Note that one media type can store only one media file. If you are exporting a clip to INTERNAL storage and the clip already has a media file of the selected type, you have to use the OVERWRITE option.
• EXTERNAL
  Used when exporting to 3rd party systems, so clips can be rendered with any duration and written to any destination using a FILENAME TEMPLATE. The filename can be customized using different metadata values as well as static text. In addition to media, you can export metadata in XML or use metadata TEMPLATE. While XML contains complete QTAKE metadata, metadata TEMPLATE export can be customized using EXPORT METADATA.

It is possible that, depending on the selected criteria, the FILENAME TEMPLATE could generate duplicate filenames for different clips. In this case, QTAKE won’t overwrite the files, but an incremented suffix will be added automatically at the end of each duplicated name.

---

Touchscreen UI

QTAKE is primarily designed for use with a touchscreen monitor. This provides you with a high level of interactivity, comfort, and speed. However, the software can be easily used with standard input peripherals, like a keyboard and mouse. Almost every control has its dedicated keyboard shortcut to make your work faster using the keyboard. While QTAKE allows you to customize these shortcuts this document will refer to the default values.

---

USER INTERFACE

The application does not use standard OS controls. We have designed custom, finger-sized controls to accommodate the touch nature of the UI as well as resolution independence.

BUTTON is a basic element of the UI. By pressing and releasing a button you activate a specific command. Some buttons have a secondary function, activated by a “long click” (hold the button pressed for 1 second). Buttons that contain secondary function are marked by a little dot in their lower right corner.

Right-clicking a control (not limited to buttons) that supports long-click invokes its long-click action, provided the control does not already have its own native right-click function. Long-click remains available for touchscreen operation; right-click is an alternative for mouse operation.

SEGMENTED BUTTON is a set of buttons used to select one out of two or more options. By selecting one segment of this button you automatically deselect a previously selected option.

INPUT FIELD is used to enter numeric or alphanumeric values for various data fields. By pressing this button you invoke the on-screen keyboard used to enter characters in the touch-screen application. Note that you can also use a physical keyboard to enter values. Some input fields act as toggle switches where each click cycles through the available options.

SLIDER is a special-purpose control used to adjust numeric values. Dragging the slider knob to the left side decrements the value. By dragging to the right side you increment the value. The filled area of the slider bar indicates where the selected value falls within the range of values. Most sliders also have an associated input field next to it that lets you enter an exact value.

Some sliders can be set into AUTO mode. In auto mode, the slider will transition between the START and END values with no interaction necessary. To enable auto mode click on the associated input field and toggle AUTO to YES. In case the SHOW KEYBOARD option (FILE room -> OPTIONS -> double arrow (»)) is set to NO, the dot in the top left corner of associated input field will be missing and you will have to click on the input field name to be able to set AUTO mode. Alternatively, double-click the slider to start auto mode without entering the on-screen keyboard. The LOOP MODE changes how the slider moves and it can be set to LOOP (from start to end), PONG(from start to end, then back to start), and A/B (alternates between start and end values). TIME INTERVAL sets the interval between transitions.

User interface controls are disabled (greyed out) for the commands that can not be executed in the current context.

---

ENHANCED INPUT FIELD is used to enter numerical values. The button has three separate functions. By pressing the buttons left side (where the value is displayed) you invoke an on-screen keyboard similar to a regular input field. By long-clicking the left side of the button you reset the field to its default value. And finally, by pressing and holding the right side of the button you invoke a RADIAL SLIDER that lets you input values by moving the cursor or your finger around its center. The radial slider lets you return to the previous value by moving the cursor or your finger to its center.

LABEL is used to display various states/values of the system. By clicking on some labels you can cycle through various display options.

TOOLBAR is a set of buttons grouped to form a complex function, like PLAYBACK. Sometimes it features a double arrow (») icon to provide access to 2nd set of controls.

MENU BUTTONS are used to toggle the display of toolbars. They can be locked to disallow accidental clicks.

User interface uses 4 horizontal blocks by default, which provides good readability even on smaller MacBook Pro screens. Increase SCREEN BLOCKS in the FILE room UI toolbar to scale the interface down and fit more content on bigger or wider screens.

---

CONTROL SURFACES

In addition to keyboard, mouse, and touchscreen control, QTAKE can also be controlled by various third-party hardware controllers. Any controller that emulates keyboard key presses will work in QTAKE. See the section called KEYBOARD SHORTCUTS for more information on assigning button functionality. Native support also exists for the following devices:

STREAM DECK

Stream Deck integration is available in both QTAKE Pro and QTAKE Lite. QTAKE Pro provides full integration with Elgato Stream Deck, allowing supported Stream Deck devices to control QTAKE using dedicated actions, custom buttons, and dials. QTAKE Pro supports all Stream Deck models, including the Stream Deck mobile app.

The Stream Deck interface automatically reflects the current state of QTAKE Pro. For example, action buttons update automatically when the active Room changes, even if the change was initiated directly from the QTAKE user interface.

Stream Deck can be used to control playback, recording, room navigation, transport controls, and many other QTAKE workflows using fully customizable layouts. Layouts can be freely customized, allowing operators to build control surfaces tailored to their own workflows.

Stream Deck Installation

To use Stream Deck with QTAKE Pro, install the official Elgato Stream Deck application.

When QTAKE Pro starts, it automatically checks whether the Stream Deck application is installed. If necessary, QTAKE installs or updates the bundled QTAKE Stream Deck plug-in. When QTAKE Pro is connected, the Stream Deck application displays the connection status and provides immediate feedback for supported actions.

If the Stream Deck application is running during the update, it may be restarted automatically so the updated plug-in can be loaded.

QTAKE Pro installs only the QTAKE Stream Deck plug-in. The Stream Deck application itself must already be installed.

After the installation completes successfully, the QTAKE action group becomes available in the Stream Deck application.

To resolve a port conflict with another application, change the port used for communication between QTAKE and the Stream Deck application using the Stream Deck Port preference.
Changes take effect immediately without restarting QTAKE.

Stream Deck Actions

The QTAKE Stream Deck plug-in provides a collection of dedicated Stream Deck actions that can be assigned to Stream Deck keys or dials.

Actions are grouped according to the supported Stream Deck control type:

• Keys – actions assigned to Stream Deck buttons.
• Dials – actions assigned to rotary controls available on supported Stream Deck devices.

To assign an action, drag it from the QTAKE action group onto a key or dial in the Stream Deck application.

After assigning an action, its properties can be configured in the lower part of the Stream Deck window.

Many predefined actions require selecting a QTAKE object, such as a Room or View.

For example, the Room action automatically indicates that the defined Room is currently active in QTAKE. If you leave the Room, either using a different Room action or directly in QTAKE, the indication changes to reflect that the Room is no longer active.

Stream Deck dial actions use different display layouts depending on the type of function being controlled.

When supported by the controlled function, the layout also includes a visual indicator showing the current value within its available range.

Predefined RECORD Key

The predefined RECORD action uses its own RECORD icon and displays live status information for the configured camera input. Configure the action for the required camera input. The key displays RECORD with the configured camera letter, such as A, B, C, or D, together with the detected input format, for example 1080p 25. This format information reflects the corresponding information shown by the QTAKE RECORD button:

• GREEN – the detected format matches the format configured for that input in Project Settings.
• GRAY – the detected signal format differs from the format configured for that input. This can occur when AUTO CHANGE is disabled for the input.
• RED – a record trigger is detected in the incoming signal.

Ovide Smart Keys

When any OVIDE SMART MODE is enabled in QTAKE Preferences > GUI group, the QTAKE Stream Deck plugin automatically provides three additional predefined Keys actions:

• Ovide Output Group
• Ovide Output Preset
• Ovide Live Pass

These actions provide direct access to controls specific to Ovide Smart Assists, which use a dedicated output panel for their integrated video-routing hardware.

They are available only when QTAKE is running in an Ovide Smart Mode.

Stream Deck Active Field Dial

The Active Field Dial automatically controls the currently active compatible field.

For example, the dial can adjust numeric fields such as CAM SPEED or increment and decrement the SHOT field. See Shot Number for more information about its increment and decrement options.

Turning the dial changes the value of the active field. The change takes effect immediately while the field remains active. For supported numeric fields, the adjustment respects the minimum and maximum values defined by the field.

• Short-click ACTIVE DIAL to keep the current value and deactivate the active field.
• Long-click ACTIVE DIAL to reset the field to its defined default value, if it has one, and deactivate the active field.

This behavior applies whether the field was activated directly in the QTAKE User Interface or using a CUSTOM BUTTON.

The Stream Deck displays the title of the currently active field. If no compatible field is active, it displays No Active Field.

• To adjust a QTAKE input field from Stream Deck, assign its Action ID to a CUSTOM BUTTON and press the key to activate the field in QTAKE.
• Rotate ACTIVE DIAL to adjust the value. Press the CUSTOM BUTTON again to keep the current value and deactivate the field.

If the corresponding input field is not currently visible in the QTAKE User Interface—for example, because its toolbar is not active or the currently active Room does not offer the toolbar—QTAKE presents the field in a modal manual-input popover. The modal input is also used when SHOW KEYBOARD is enabled.

When the modal input is displayed, ACTIVE DIAL can adjust the field value.

Both the CUSTOM BUTTON and ACTIVE DIAL reflect the current value as it changes and also update when the value is changed directly in QTAKE.

Predefined Stream Deck Keys and Dials that directly operate a parameter do not require the corresponding QTAKE input field to be activated first; they change the value directly.

Active Dial for Picker Fields

The predefined ACTIVE DIAL action in QTAKE Dials can be used to navigate items in picker fields, such as drop-down menus.

When a picker is open, rotate the dial to move through the available items and press the dial to select the current item.

To use a picker with a CUSTOM BUTTON and ACTIVE DIAL:

1. Assign the picker control’s Action ID to a CUSTOM BUTTON.
2. Press the CUSTOM BUTTON to activate and open the picker in QTAKE.
3. Rotate ACTIVE DIAL to move through the available choices.
4. Press the dial to select the desired choice.
5. The CUSTOM BUTTON reflects the selected value. If the value is later changed directly in QTAKE, the key updates as well.

For example, you can assign the ACTIVE MEDIA selector in the MEDIA toolbar to a CUSTOM BUTTON, then use ACTIVE DIAL to navigate and select its items.

Stream Deck Custom Buttons

Custom Buttons provide access to any QTAKE control that has its own Action ID and can be assigned as a QTAKE Global Shortcut.

Instead of selecting one of the predefined actions, you can specify the identifier of any supported QTAKE control.

Click the Action ID field to display the complete list of available control identifiers.

The list is searchable. As you type, the list is automatically filtered to match identifiers, making it easy to locate a specific control even when a great number of identifiers are available.

For example, entering rev filters the list to identifiers such as Menu.Play.Reverse.

Selecting an identifier assigns the corresponding QTAKE control to the Stream Deck button.

The CUSTOM BUTTON operates the assigned control and displays relevant current information received from QTAKE. Depending on the control, the key can display its title, such as for buttons and segmented buttons, or its current value, such as for input fields and multi-choice selectors.

When the represented value or state changes, the key display updates accordingly. This also applies when the control is changed directly in QTAKE rather than from Stream Deck.

For workflows that use CUSTOM BUTTON to activate a field and ACTIVE DIAL to change it, see Stream Deck Active Field Dial and Active Dial for Picker Fields.

Cycling Through Segmented Buttons

A CUSTOM BUTTON can cycle through the enabled segments of a QTAKE segmented button using a single Stream Deck key.

Assign the Action ID of the segmented button rather than the identifier of one of its individual segments. Each press of the CUSTOM BUTTON advances to the next enabled segment in the button’s order and, after the last enabled segment, cycles back to the first.

For example, List.Clip.Size identifies the complete segmented button, while List.Clip.Size.3, List.Clip.Size.2, and List.Clip.Size.1 identify its individual segments. Assign List.Clip.Size to a CUSTOM BUTTON to cycle through the currently available LIST size options.

Disabled segments are skipped automatically. For example, if the largest LIST size is unavailable because the current UI layout does not have enough space for it, the CUSTOM BUTTON cycles only through the remaining enabled sizes.

This behavior is available for segmented buttons generally and is especially useful for controls with a small number of segments.

Global Shortcut identifiers, including how to assign a shortcut to a segmented button, are described in the Global Shortcuts section.

Stream Deck Custom Dials

Custom Dials work similarly to Custom Buttons but are intended for rotary controls available on supported Stream Deck devices.

Specify the identifier of a QTAKE field that supports continuous adjustment.

The searchable Action ID field works the same way as for Custom Buttons, making it easy to locate compatible controls.

CUSTOM UI LAYOUT

By pressing a MENU button you enable or disable the corresponding toolbar. The button will change its background color from grey to green. If you press the MENU button again you will hide its toolbar. You can arrange toolbars for each room simply by displaying them in the correct order.

Toolbars always appear from left to right. If you hide any toolbar, all other boxes are moved to fill the gap. There is an arrow on top of each Menu title that indicates if the toolbar will appear in the upper or lower zone. You can toggle the arrow direction with a long-click on the MENU button.

You can prevent Menu Boxes from accidentally hiding by pressing the LOCK button.

Each ROOM in the application can have its own layout. The orange LAYOUT button allows you to save and recall up to eight different layouts. Click the LAYOUT button to reveal the current layout and the eight slots where you can store layouts, by default named LAYOUT 1 - LAYOUT 8. The currently selected layout is highlighted in orange. The first, - (dash) layout, will become active when you modify a saved layout. To store the current layout long-click one of the slots, now you can rename your layout and save it. On the right side of the bar, you can CLEAR or RESET the currently configured layout to the default state of the current room.

Fast keyboard access to layouts
You can bind keyboard shortcuts to your layouts for quick access (default shortcuts Alt+1-8)

---

VISUAL KEYBOARDS

Visual keyboards are used for data input. They are displayed by pressing the data input fields. Above the input field, there is a set of keyword buttons containing commonly used values, words, or phrases. These buttons can be customized by entering the desired phrase in the input field and long-clicking on the button you wish to change. When using a physical keyboard you can disable visual keyboards by turning off the SHOW KEYBOARD setting. You still have access to keywords by right-clicking on the field you are editing.

---

KEYBOARD SHORTCUTS

Hotkeys (or keyboard shortcuts) in QTAKE are configurable and saved per user allowing each user to customize their work environment. Reveal hotkeys for each control element by pressing the Fn key on your keyboard. While holding this key each command TITLE is temporarily replaced by its keyboard shortcut representation.

If you click a button while holding down your Fn key a popup window will appear that lets you define a new keyboard shortcut for that button. In this window you also can CLEAR (remove any existing shortcut from that button), RESET (set default shortcut for that button) / RESET ALL (set default shortcuts for all buttons).

Cycle through Segmented buttons
For segmented buttons, hold Fn+Option (Alt) while assigning a shortcut to use the identifier of the segmented button instead of an individual segment. Pressing the resulting shortcut cycles through the enabled segments in the button’s order and, after the last enabled segment, returns to the first. Disabled segments are skipped automatically.

Global Shortcut identifiers are also used to assign QTAKE controls to Stream Deck Custom Buttons and Custom Dials.

Keyboard shortcuts context
Keyboard shortcuts have to be unique for each button in each room because all rooms make up a single context. Exceptions are windows that appear on top of the standard UI. Windows are modal and therefore allow the hotkeys from the main context to be re-used.

---

SCREEN ZONES

Screen area is divided into seven zones.

1. ROOM BUTTONS ZONE
   This is the zone where you choose what part of the application (ROOM) you want to work in.

2. STATUS BAR ZONE
   System status and log messages are displayed in this zone.

3. SPECIAL BUTTONS ZONE
   This zone contains the most commonly used commands, such as toggling the display of panels or hiding the application.

4. UPPER TOOLBARS ZONE
   This is the zone where toolbars appear when you click MENU buttons set to top mode.

5. VIEWS ZONE
   This zone is used to display video content, as well as panels.

6. LOWER TOOLBARS ZONE
   This is the zone where toolbars appear when you click MENU buttons set to bottom mode.

7. MENU BUTTONS ZONE
   The green and black Menu buttons control what UI elements are displayed in each room.

---

UI Output to Views

This feature provides a unique set of functions, enabling you to output specific elements of the user interface to external monitors. Displaying elements such as the Clip Browser or META panel can significantly improve communication with other crew members on set.

For example, if the director is not located near the QTAKE rig, you can display the Visual Clip Browser directly on their monitor for more effective collaboration.

Operation

UI elements that contain a circle icon (UI Output indicator) in the bottom right corner can be sent to output by displaying them within the QTAKE Pro Views.

• View Assignment (LONG-CLICK): To specify which video View will be used for the output, perform a long-click on the circle icon. The number inside the circle reflects the ID of the assigned View.
• Activating Output (REGULAR CLICK): A single click on the circle icon activates the output, and the icon turns blue. The UI element is then immediately routed to the assigned View.
• Deactivating Output: Another click on the blue icon deactivates the output and restores the standard View PATCH. UI Output is also automatically deactivated if the source window is closed or if a different UI element is activated for the same View.

Sub-window Support

This feature supports the output of sub-windows originating from windows already sent to Views as a UI Output.

To deactivate UI Output when a sub-window has been opened, use one of the following methods:

• Click the circle button on the sub-window (if available).
• Click the circle button on the original UI element.
• Send a different UI element to the View.

---

TOP BAR

The Top Bar menu contains the most frequently used global commands in QTAKE Pro.

ROOMS

The main menu of QTAKE Pro consists of 5 specialized Rooms, each designed for a different stage of the production workflow.

---

---

---

---

DELETE

The DELETE button eases the workflow when you need to quickly remove clips from QTAKE. This action cannot be undone.

The DELETE button performs the same action as the PERMANENTLY DELETE function from TRASH. When the SELECT button is active, the DELETE button removes selected clips (excluding LIVE clips) if at least one clip is selected. If you select no clip and click the DELETE, the button deletes the clip loaded in the active View. If active View is patched to LIVE, it deletes the last recorded or last loaded clip in the active View. The DELETE button also respects CLIP SYNC, meaning if CLIP SYNC is active it will delete all synced clips. There is a confirmation pop-up before the delete action.

Note that by permanently deleting media files from QTAKE you will not free up the disk space, as files are moved to macOS Bin. To free up the disk space, you have to empty Bin.

LIST TOOLBAR

At the bottom of the list, you will find buttons that provide additional functionality to the list of clips.

The FUNCTION button displays the list of options for selected clips.

FAST CLIP LIST SELECTION

Unlike previous versions of QTAKE, when the View is in DISK mode, the FUNCTION button is always enabled. When clicked and no clip is selected in the LIST table, an active clip will be automatically selected and the FUNCTION dialog will pop up.

SELECT button has a long-click mode, which will select all clips in the LIST, except LIVE ones.
When SELECT mode is active, the SEARCH field is hidden and FAST SELECTION buttons appear:
ALL CAMERAS will select all recorded and LIVE clips of all cameras with matching SCENE/SHOT/TAKE metadata.
ALL UNITS will expand ALL CAMERAS to include cameras from other units.
ALL TAKES will select ALL TAKEs matching CAMERA letter/SCENE/SHOT metadata of the selected clips.
ALL SHOTS will select all TAKEs of all SHOTs of the SCENEs metadata respecting the camera letter of the selected clips.
ALL DAY will select all clips matching SHOOT DAYs of the selected clips.

When you right-click in the LIST, it triggers the SELECT mode and automatically selects the clip in the corresponding row. A contextual menu will appear, providing access to all FUNCTION options and LIST FUNCTIONS.
If you accidentally initiated a fast selection, you can simply click the SELECT button to return to the normal mode and exit the SELECT mode. This allows you to resume your regular operations in the LIST without any unintended selections.

SHOW IN FINDER

Use this FUNCTION when you need to make a quick copy of selected clips to a 3rd party application. This is not a recommended way of exporting media files, because it doesn’t include clip metadata, but some information can be smuggled inside filenames. Since QTAKE doesn’t use human-readable filenames for its internal media, an additional step is necessary to show media files in a single Finder folder.

First, you need to select what type of media you want to reveal (Recorded, Proxy, RAW,…) and then select what FILENAME TEMPLATE should be used to generate filenames. If none of the pre-defined templates works for you, you can create your own by clicking the EDIT button.

In EDIT mode, you can define how the FILE name will look like and you can define directory structure, based on different metadata. For example, hard links to clips with a matching scene and take are stored in separate folders with a filename consisting of ” Camera Media Filename.FileID “ would be defined as in the picture above. In this example, FileID was added to create unique file names, but it can happen that based on the criteria selected, this function would create duplicated Filenames for different clips. In this case, QTAKE will give information in the main Show in Finder window and also a warning that SHOW IN FINDER will create duplicated file names if you confirm the selection by clicking on SHOW IN FINDER button. If you decide to continue anyway, an incremented suffix will be added automatically at the end of each duplicated name.

SHOW IN FINDER operates differently based on MEDIA LOCATION. For files stored internally, the Filename template will be used to create hard links to media files in a new folder. Press the SHOW IN FINDER button and QTAKE will hide and a finder window with an appropriate new folder will be displayed.

On the other hand for files stored externally finder will open selected folders to reveal the media files.

LOAD

The LOAD function allows quick loading of multiple clips into available Views.

To use the function, select multiple clips from the LIST. They will be loaded into available Views (based on the HDx/4K version) in the exact order you selected them. This is particularly useful when working with clips not recorded in SYNC that are adjacent in the LIST.

1) Click the SELECT button and choose the desired clips from the LIST.

2) Open the FUNCTION menu and click LOAD.

For instance:
If you select clips with IDs 172, 170, and 175 in that order, and View 1 is currently active:
Clip 172 will be loaded into View 1
Clip 170 into View 2
Clip 175 into View 3

The function always starts loading from the currently active View and proceeds sequentially. If the number of selected clips exceeds the number of available Views, a prompt will appear asking whether to load only into the remaining available Views.

For example,
If View 3 is active in the HDx4 system and you select five clips, QTAKE will prompt you to load the first two clips into Views 3 and 4 or CANCEL the operation.

Since the LIST follows the active View, this function eliminates the LIST following when switching between Views, allowing you to load adjacent clips in multiple Views.

MANAGE MEDIA FILES

This function allows you to copy, move or delete local media files for selected clips. After choosing the MEDIA TYPE of the clips you want to manage, you have to select the SOURCE storage volume and TARGET storage volume.
SOURCE table is multi-select enabled so you can select all rows except greyed-out ones, which show unmounted volumes.
On the other hand, TARGET table lets you choose only one row. Greyed-out rows don’t have enough free space to accommodate selected media files.

COPY will copy all the media files from SOURCE to TARGET.
QTAKE will look for QTAKE Pro Storage folder in the ROOT folder of selected volume, if no such folder is found, it will be created and used.

MOVE will move all media files from SOURCE storage to TARGET.
QTAKE will look for QTAKE Pro Storage folder in the ROOT folder of selected volume, if no such folder is found, it will be created and used.

DELETE will delete all the media files from SOURCE.

If you select DELETE and no other copy is present on another storage volume, a warning popup will require confirmation to delete selected media files as this operation cannot be undone.

Important

QTAKE manages its media in QTAKE PRO STORAGE folder.

Do not move, rename, or reorganize files inside the QTAKE PRO STORAGE folder manually in Finder, as this may break the relationship between the database and its managed media.

To move or copy managed media between storage volumes while preserving database integrity and clip references, always use MANAGE MEDIA FILES.

Files stored inside QTAKE PRO PROJECTS, such as reports, screenshots, or other exported files, may be managed independently without affecting media integrity.

MOVE TO TRASH

This function will move clips to the trash bin by pressing the FUNCTION button and selecting MOVE TO TRASH. This will only move selected media files to the trash. You can either PUT BACK FROM TRASH or PERMANENTLY DELETE media files from the storage. This operation cannot be undone.

Note that by permanently deleting media files from QTAKE you will not free up the disk space, as files are moved to macOS Bin. To free up the disk space, you have to empty Bin.

RELINK

Relink searches for linked media files whose original location has changed.

This function applies only to media imported using LINK, where QTAKE stores references to files that remain outside the QTAKE-managed storage structure.

Select an approximate location, and QTAKE will recursively search all subfolders to locate matching media files.

Relink does not apply to media managed inside QTAKE PRO STORAGE. If managed media need to be moved to another storage device, use MANAGE MEDIA FILES instead.

CREATE SCREENSHOTS

Use this function to generate screenshots for all selected clips using the poster frame.

CREATE THUMBNAILS

Use this function to generate thumbnails for all selected clips using the poster frame. This function will create both clean and processed thumbnails.

BINS

The BINS function will open a dialog that will show you all created bins and a number of clips inside those bins that match the current selection of clips. Here you can add selected clips to selected bins or remove them.

BINS can also be used to filter clips in the LIST; see LIST Filters.

PDF REPORT

This function lets you create a PDF report using selected clips the same way as using PDF Report.

SEND TO SEQUENCE

Selected clips will be sent to sequence in the order they were selected and QTAKE will switch to the EDIT room.

RENDER PROXY

Use this function to render proxy media for selected clips. The encoder resolution and quality are taken from Project Settings > Proxy Codec.
QTAKE storage is limited to one media file for the selected media type per clip. If you use this function multiple times on a clip, QTAKE will keep only the most recent one.

TRANSCODE TO PRORES

Proxy media can’t be played back with a variable frame-rate. To do so, you need to transcode it to the Apple ProRes codec.

EXPORT METADATA

This function will create an ALE or CSV export for selected clips using the selected ALE Template.

EXPORT LOOKS

Exporting color grading to 3rd party apps. You can export CDLs and LUTs used on selected clips. Optionally, CDLs can be exported as CCC.

EXPORT QTAKE XML

Export selected clips to QTAKE XML format which contains complete metadata. Media files of the selected type can be exported in addition to XML.

EXPORT TO FILE

This function is used to export clips using the Pipeline.
Click the EXPORT TO FILE button to export multiple takes to iPhone/iPod or Apple TV compatible .m4v format. If you choose to export a file to QT Movie, you can add LUT and OSD to the video frames. Press the BACKGROUND button to start the export in the background. Export to file uses IN and OUT marks to define the export range of each clip.

EDIT CLIP DATA

In case you are not using the META panel, you can use this function to edit multi-clip metadata values in a standalone window. Press the SELECT button to enable clip selection. Select the clip, press the FUNCTION button, and then select the EDIT CLIP DATA option.

EDITING CLIP DATA FOR MULTIPLE CLIPS

Press the SELECT button to enable clip selection. Select the takes you want to edit, then click the FUNCTION button and EDIT CLIP DATA option. A dialog similar to the EDIT CLIP DATA dialog will appear but with each element blanked out. When editing the TAKE attribute a secondary option called AUTO-INCREMENT TAKE will appear. To number your takes sequentially select YES. Note that the order you selected the files is the order they will be numbered.

RUN DOLBY VISION® ANALYSIS

On top of Live Analysis, you can perform Dolby Vision analysis for clips missing Dolby Vision metadata. The function creates a background task.

Note that GRADE and DOLBY modules are required.

OPTICAL FLOW ANALYSIS

The function triggers a background task to calculate and cache the motion vectors for all clip ranges of selected clips. You can use these vectors to get a smooth interpolated off-speed playback.
Unlike manually triggered action by clicking the Speed mode button, the function triggers a background task, which you can monitor by clicking the TASK.

DELETE OPTICAL FLOW ANALYSIS

If you need to save disk space, you can use this function to significantly reduce the disk space that clips with motion vectors calculated occupy.

MARK AS REFERENCE

Use this function to quickly mark selected clips as a reference. If selected clips contain reference clips, an additional function will be shown allowing you to unmark clips as a reference.

Merge Clips

Merge Clips lets you match media from existing clips to other existing clips after import or linking.

This is useful when imported or linked media was not attached to an existing clip during the original import or link operation.

If no suitable match is found, or if you choose CREATE instead of USE, QTAKE creates a new clip for the imported or linked media.

Select these newly created clips in the LIST, then choose FUNCTION > Merge Clips.

Select the media type to be matched. Only media of the selected type are considered during the matching process.

QTAKE opens the Matcher window so you can review the matching results before completing the merge.

See Matcher for more information about clip matching.

Un-merge Clips

Un-Merge Clips restores clips to their original state before a previous Merge Clips operation.

Select one or more merged clips in the LIST, then choose FUNCTIONS > Unmerge Clips.

PUT BACK FROM TRASH

This function is available only in TRASH mode. Use it to put back clips that were accidentally moved into the trash.

PERMANENTLY DELETE

This function is available only in TRASH mode. Use it to permanently delete clips and all associated files.

---

---

---

---

---

---

---

FILE Room

File room is used to set up the project, import or export files, and access various settings needed for your work environment.

---

---

---

---

Auto-load

By default, QTAKE automatically loads the most recently used project when starting the application. To disable this behavior, set the following preference: Autoload Project = NO

---

---

Migrating Projects from QTAKE 2.x

When a project created in QTAKE Pro 2.x is opened in QTAKE Pro 3.0 for the first time, QTAKE automatically migrates its project configuration to the new Project Settings.

The migration reconstructs the existing configuration where possible, including input and output device assignments and settings that were previously stored in Preferences but are now configured per project.

This migration is performed only the first time the legacy project is opened in QTAKE 3.0. Review the resulting Project Settings to make sure the migrated configuration matches the required hardware and workflow.

---

---

STORAGE STRUCTURE

This section provides insight into how QTAKE stores recorded and imported media files, thumbnails, and other internal files.

QTAKE Pro Storage Folder

Since version 1.5 QTAKE uses new file storage based on unique filenames, compatible with QTAKE Sync (formerly QTAKE Server). The main purpose of this system is to provide the most robust way of linking a database to files, especially in the new, distributed environment, where files can be accessed by the asynchronous upload or download process.

The main file storage folder is called “QTAKE Pro Storage” and it resides in the root of the volume selected in the PROJECT STORAGE field.

Important

The QTAKE PRO STORAGE folder is managed internally by QTAKE and should not be modified manually.

Moving, renaming, or reorganizing files inside this folder in Finder may break the association between the database and managed media.

Use MANAGE MEDIA FILES whenever media needs to be copied or moved to another storage volume.

The QTAKE PRO PROJECTS folder contains project-specific files such as project hard links, reports, screenshots, and exports, and may be accessed directly if needed.

QTAKE Pro Projects Folder

In addition to the main file storage folder, there is additional “QTAKE Pro Projects” folder that contains folders such as FINDER, EXPORT, or SCREENSHOTS, which serves as an output location for specific FUNCTIONs.

Additionally, QTAKE will automatically create hard links with human-readable filenames to media files inside the MEDIA folder, for compatibility purposes. 3rd party tools that need automatic access to QTAKE media files can use these hard links.

The following filename scheme is used for hard links: [SCENE_SHOT_TAKE_CAMERA] SOURCE-CLIP-INPUT

Automatic hard links inside the QTAKE Pro Projects folder will not have their filenames updated after the clip metadata change.

Copy clips to 3rd party apps

In case you need to copy QTAKE media files to external storage using the current metadata values, you should use the SHOW IN FINDER function. Typical use is copying media files for the editor or director.

Spanning multiple volumes

In case your file storage gets full, you can simply attach new storage to your system and select a new volume using the PROJECT STORAGE field. The old volume will still be used to access old files.

Never try to move or delete files inside QTAKE Pro Storage manually. If you need to free up drive space, delete clips inside the QTAKE app and empty TRASH in the LIST. Afterward, go to macOS Bin and delete media files from the macOS Bin as well.

---

### UPLOAD TO QTAKE Sync (formerly QTAKE Server) {#upload-to-qtake-server} When you click the **UPLOAD** button in the **OPEN PROJECT** window, you will be presented with the following dialog prompting you to select destination QTAKE Sync. Usually, this will be the instance of the QTAKE Sync running on your local machine. After clicking **OK**, your project upload will have to be approved by the administrator of the selected QTAKE Sync instance. --- ### DOWNLOAD FROM QTAKE Sync (formerly QTAKE Server) {#download-from-qtake-server} Sometimes, you will not be the one who is creating the QTAKE project. The most common scenario is the 2nd unit QTAKE system, which is deployed after the shooting has already started. In this case, you should use the **REMOTE** tab of the **OPEN PROJECT** window to select an existing project residing on QTAKE Sync and click the **DOWNLOAD** button to download the project to your QTAKE. If you don't see a specific project listed in the table, ask the QTAKE Sync administrator to send you the project link. Double-clicking the link will add this project to the list of remote projects and allow you to download it. --- --->

---

OPEN LINK

QTAKE supports QTAKE, QTAKE Sync (formerly QTAKE Server), and QTAKE Monitor invitation links for local network and Cloud operation.

If you do not see the desired project in the OPEN PROJECT > REMOTE tab list or you do not see a remote QTAKE stream in Project Settings -> VIDEO INPUT -> STREAM tab, you can request an invitation link from the QTAKE operator.

Afterward, you can either click on the link or you can copy the link and paste it into OPEN PROJECT -> SERVERS tab -> OPEN LINK.

---

CAMERA METADATA COMPARISON TABLE

This is a comparison table detailing what embedded metadata QTAKE can read from various cameras.

* Blackmagic Design video cards will only receive SDI metadata when QTAKE is set to 10-bit capture mode.

---

FULL RANGE VIDEO

SDI video usually contains image data encoded in YCbCr color space. QTAKE converts the image into RGB color space to perform GPU-based processing. Standard YCbCr conversion uses SMPTE levels, which means that the legal range YCbCr will be converted to full range RGB. However, some cameras use full-range YCbCr to store the higher luminance range. QTAKE supports conversion to RGB using full range YCbCr to avoid clipping of super-blacks and super-whites. This is controlled using the following preference:

Full Range Video = NO

When using FULL RANGE VIDEO preference, your video card output and QOD+ will be automatically set to match the input, but if you are using 3rd party GPU to SDI converters, you may need to set the correct video range using the following preference:

Legal Range GPU Output = NO

Full-range video processing is slower. Use it only in case your signal source requires the processing of super-black and super-white pixel values.

---

---

---

---

---

---

---

---

---

---

DRAG AND DROP IMPORT AND LINK

Dragging supported files onto the QTAKE Pro application icon in the macOS Dock is an alternative way to start the same Import/Link workflow. The macOS Dock application icon is distinct from QTAKE’s internal DOCK toolbar; dropping media files onto the internal DOCK is not a supported import action. It supports the same media-matching workflow, metadata extraction, filename parsing, and Media Type options. The difference is that IMPORT copies media into QTAKE-managed storage, while LINK keeps media in their original location.

In addition to QuickTime movies, you can import still images, audio files, and CDL color corrections. When dragging a media file to the QTAKE Pro application icon in the macOS Dock, the DRAG AND DROP window will appear, letting you set options such as FILENAME PARSING, STILL IMAGE SCALING, STILL IMAGE DURATION. Importing a still image can be useful for reference frames, logos, or background images for VFX shots.

FILENAME PARSING

When using drag-and-drop import QTAKE can extract metadata from the filename of the imported material but you have to select the correct parsing filter.

Some external recorders can read Camera Media Filename and rename files accordingly. When importing files that are named by camera filename use the appropriate camera import filter even if they were recorded on one of the devices in the list.

NONE The NONE filter will mark the imported clips as belonging to a scene called Import.

QTAKE The QTAKE filter uses the native QTAKE naming convention. Files will be organized in the same way as they were created. Scene_Shot_Take-Sbtk_CamReel_(Rt)_IDx.mov

RED The RED filter will import media with RED filenames to a scene called RED (magazine number), The Camera position will be used as shot and clip number as take. CamReel_[CLR]Clip_MMDDXX.mov

ALEXA The Alexa filter will import Alexa files to a scene called Alexa (reel number). CamReelCClip_DDMMYY_CamID.mov

KIPRO The Ki Pro filter will use Scene and Take numbers as entered. SCSceneTKTake.mov

PIX The PIX 220 or 240 needs to be set to Reel_Scene_Take naming. QTAKE will then use those values. Reel_Scene_Take.mov

ATOMOS The Atomos filter uses Scene, Shot, and Take numbers. UnitName_SceneNum_ShotNum_TakeNum.mov

CANON Use this parsing template to extract information from Canon media files.

SONY Use this parsing template to extract information from Sony media files.

Enter Metadata

As an alternative to PARSE FILENAME, the ENTER METADATA part of the segmented button lets you enter the data manually. You can enter Camera letter, Episode, Scene, Shot, and Take number.

STEREO 3D

When importing stereoscopic footage, recorded as muxed side by side, set the segmented button to SIDE BY SIDE. Non-muxed footage can be imported as FAKE SIDE BY SIDE. This can be useful when using 2D footage as a background plate for a stereoscopic chroma key.

MULTIVIEW

When importing quad split footage, set this field to QUAD to enable related functionality.

VR 360

When importing virtual reality 360 footage, tag it using EQUIRECTANGULAR or CUBEMAP options to enable correct interpretation by QTAKE.

ORIENTATION

When importing footage captured in portrait mode or upside-down, set this field to 90 CW, 90 CCW, or 180 value.

Layer

This field allows you to specify the intended layering role of the imported footage within your composite.

• Fg (Foreground): Designates the clip as a foreground element, typically intended to be composited over other layers.
• Bg (Background): Designates the clip as a background element, commonly used as a plate beneath foreground elements.

Channel

Use this field to explicitly specify the primary data type or channel information contained within the imported footage. It ensures the application correctly interprets and utilizes specialized media, which is crucial for advanced compositing and rendering.

• Color: For standard video footage containing typical RGB (Red, Green, Blue) color information.
• Alpha: For footage containing a transparency channel, it is essential for compositing elements with pre-keyed or embedded transparency.
• Depth: For footage containing depth map information, often used in 3D compositing, relighting, or depth-based effects.
• Normals: For footage containing normal map data, which defines surface orientation and is vital for advanced lighting and shading in 3D environments.
• Motion: For footage containing motion vector data, typically used for accurate motion blur, advanced re-timing, or sophisticated tracking and stabilization.

STILL IMAGES

QTAKE can import various still image formats. On import, the image is converted to a QuickTime movie. Adjust the duration of this movie by entering the desired number of seconds in the STILL DURATION input field. To adjust the scaling of the imported image in relation to the View use the STILL IMAGE SCALING segmented button. QTAKE will preserve the transparency of imported images.

USE FILE METADATA

Set this option to YES to extract metadata from the imported file and insert it into the QTAKE database.

QUICKTIME METADATA IMPORT TEMPLATE

When USE FILE METADATA is set to YES, you can choose an existing template, add a new one, or edit an existing template via the EDIT button. See the QuickTime metadata import section for more information.

ATTACH TO EXISTING CLIPS

Set this field to YES when importing new media for existing clips. Read more about this in the MATCHER section.

OVERRIDE FILE DATE

When importing new media for existing clips, it is important to use correct data to make matching successful. If CMF is not present in the existing clips, CAMERA, TIMECODE, and DATE information is used instead. QTAKE is using file date if it can’t find embedded metadata inside imported media. However, the file date can be misleading, because usually it is set to the time of transcoding and not the time of recording. Using the OVERRIDE FILE DATE field you can set the correct date of the imported file.

Match Method

Determines how QTAKE searches for matching existing clips during import or linking.

By default, Auto automatically selects the most appropriate matching method based on the available metadata.

If necessary, a specific matching method can be selected manually.

• Auto
• CMF
• Cam Roll + Time Code
• Date + Time Code

NOTE:
Match Method only determines how imported or linked media are matched to existing clips during the import or link operation.
If media are not attached to an existing clip, QTAKE creates a new clip for that media.
These newly created clips can still be matched later using Merge Clips.
See Matcher and Merge Clips.

Media Type

Defines how the imported or linked media will be classified.

In most cases, Auto correctly identifies the media type.

If the media cannot be classified correctly, select the appropriate media type manually before importing or linking.

For example, some cameras record original camera files using H.264 in a MOV container. Such files may be automatically classified as Proxy media, even though they should be imported as Original media.

• Auto
• QTAKE Recorded
• Proxy
• Intermediate
• Proxy Transcoded
• Original
• Intermediate LQ
• RAW

---

---

---

---

---

EDIT TEMPLATES

QTAKE comes with two pre-made PDF Report templates. Project Report and Camera Report. To create a new PDF report template first select the report you would like to base your new report on and click DUPLICATE.

The left half of the template editor control what metadata fields are included and the sorting order of the clips in the report. Use the segmented button to choose whether the fields should be added to the page header or the individual clip entries in the report. To add a field select it from the Available Fields list and use the arrow button (>) to add it. When the report is in Flow Layout both the Page Header and the clip entries have a heading and a data section. These are separated by a horizontal line in the Included Fields list.

Drag the field to move it between the data section and the heading. Each field in the Included Fields list also has a drop-down menu to define its relation to the next field. The options are No Space, Slash, Space and New Line.

Fields added to the Page Header will show up in the gray section of the preview. The Page Header will be repeated at the top of each page in the report. The header would normally be populated with fields from the Project Data group but you can optionally add fields from other groups. If fields with multiple values are added the header will show all values separated by commas.

The Sort Order tab lets you control the sorting of clips and the page breaks of the report. Clips in the report are sorted, in order from top to bottom, by the fields in the Included Fields list. There is a horizontal bar dividing the Included Fields list into two sections just like in the Clip and Page Header. Fields added above this line will cause the report to be divided into sections separated by page breaks based on their values.

REPORT LAYOUT

The right half of the template editor contains a preview of the report and controls for the page layout of the report. A segmented button near the top lets you choose between a Flow Layout and a Table Layout for the report. Click TEMPLATE and select the Camera Report for an example of a report in the table layout. You can add the name of the template and the date when the report was generated to the report header by setting Show template title in page header and Show date in page header to YES. Setting Full header on the first page only to YES will remove fields below the horizontal line in the Page Header tab on all pages of the report except for the first.

The bottom row of controls allows you to change the layout of the clip entries. Setting Begin each group on a new line to NO allows for a more compact layout by putting the metadata groups closer together. Use fixed field positions and sizes will make sure the fields stay in the same place in each clip entry by adjusting the size of the field in the report to accommodate the clip with the largest amount of characters in that field. Use full-width clip headers will adjust the thumbnail to allow more information in the header. Skip empty fields will remove fields without data from the report. You can also adjust the thumbnail position and row decoration for the clips.

---

---

---

BROWSE CLIP in the LIST works based on EPISODE, SCENE, SHOT, TAKE metadata. These metadata values have to be unique so the BROWSE CLIP could work as expected. In case there are multiple clips with matching EPISODE, SCENE, SHOT TAKE metadata values ( including empty values ), it is not possible to determine which clip was selected on the MASTER side, so SLAVE will select the first clip with matching EPISODE, SCENE, SHOT, TAKE.

---

---

---

---

---

---

Immersive 3D Stream to Apple Vision Pro

QTAKE Pro supports streaming immersive 3D streams to Apple Vision Pro devices using the QTAKE Monitor AVP native application, building upon the existing stereoscopic 3D stream functionality accessed via the 3D View toolbar. This advanced workflow enables a new level of on-set visualization for spatial video.

Camera Inputs and Project Setup

Immersive 3D streams can originate from two primary camera configurations:

• Dual Camera Setup: Two separate cameras, one for each eye, each equipped with fisheye lenses.
• Single Camera Dual Fisheye: A single camera featuring dual fisheye lenses that outputs a combined Full Side-by-Side (SBS) signal.

In Project Settings > Video Source, configure the STEREO 3D property for each input:

• For dual camera setups (separate eyes), tag the individual inputs as 3D Left and 3D Right.
• For a single-camera, dual-fisheye signal, set the STEREO 3D field to FULL SBS to tag the clip as 3D side by side without squeezing.

Set VR 360 to FISHEYE to tag the clip’s lens type.
In Format and Canvas, set CANVAS to a CUSTOM resolution with a 2:1 aspect ratio (e.g., 2000 x 1000 for HD or 4000 x 2000 for 4K).

Single Camera Dual Fisheye Workflow

This workflow considers a camera with a dual fisheye lens that outputs a Full SBS signal. You will need the MUXER license module in addition to the STREAM license.

1. Use any supported video card to capture an SDI or HDMI feed from your dual fisheye camera. You should observe two circular images within the 16:9 video frame.
2. Open your project and apply the necessary Canvas and Project settings as described above.
3. In Clip FX for the LIVE signal, add the SWAP MUXED 3D to swap eyes and ALIGN MUXED 3D effects (from the TRANSFORM group).
4. Open the PLUS 3D VIEW using the 3D VIEW toolbar and set the mode to DIFFERENCE. This mode helps you precisely align your two eyes.
5. Use the ALIGN MUXED 3D effect to carefully center each circular image within its respective half of the frame. The goal is to achieve as much flat grey color as possible, which indicates no or little difference between eyes. When the eyes are aligned, change the 3D VIEW mode from DIFFERENCE to NONE or SBS.
6. Add the VR VIEW effect and set its mode to EQUIRECT. This effect converts the fisheye images into an equirectangular projection. After this step, you should see two rounded squares, which are the projection format used by the QTAKE Monitor application for viewing spatial video.
7. Turn on STREAM and invite your Monitor application user to the project. In the connected-devices interface, select the Plus 3D option from the STREAM VIEW 1 bottom selector.

QTAKE Monitor (Apple Vision Pro) Workflow: With the native visionOS application available in the App Store, viewing immersive 3D streams on Apple Vision Pro is straightforward.

1. Open the invitation link from the application, and the stream should appear in the VIEW.
2. Open the right panel using the rightmost button in the top bar.
3. Navigate to the FX page within the panel.
4. Activate the VR and 3D checkboxes.
5. Set VR to Half-Equirectangular.
6. Set 3D to SBS (Side by Side).
7. Click the IMMERSIVE button in the middle of the top bar to enter spatial mode.

Quality Considerations: For optimal viewing quality in VR, it is highly recommended to use 4K input and ensure 4K streaming for each eye, as HD resolution in a virtual reality environment will result in noticeably low quality.

STREAMING NETWORK BEST PRACTICES

The recommendations below provide practical guidance for a reliable QTAKE streaming network setup and a starting point for troubleshooting network-related streaming issues. For technical bandwidth and port guidance, see Network Requirements.

QTAKE STREAM SOURCE CONNECTION

For the most reliable streaming, we strongly recommend connecting the Mac running QTAKE to the streaming network using wired Ethernet whenever possible. QTAKE is the source of the outgoing stream, so the reliability and capacity of its network connection directly affect streaming.

LOCAL STREAM NETWORK

For LOCAL streaming, QTAKE serves local stream clients directly.

On managed or corporate networks, we strongly recommend keeping QTAKE and local stream clients on the same subnet. If this is not possible, consult the network administrator to ensure that Bonjour discovery and QTAKE Stream traffic can pass correctly between the required network segments.

MULTIPLE NETWORK INTERFACES

When the QTAKE Mac uses separate network interfaces for LOCAL streaming and Internet access, use the following configuration as a best practice and one of the first troubleshooting checks:

• LOCAL STREAM interface - use wired Ethernet whenever possible, configure a static local IP address, leave the Router field empty, and place the service first in macOS network service order.
• INTERNET interface - provides Internet access and the default Internet route, and follows the dedicated local-stream service in the macOS network service order.

For a dedicated local streaming network, a subnet mask of 255.255.255.0 is recommended unless the network configuration requires otherwise. Leaving the Router field empty on the dedicated local-stream interface prevents that interface from becoming an unintended default route for Internet traffic. This configuration is a recommended best practice, not a technical requirement for QTAKE streaming.

IF BONJOUR DISCOVERY REMAINS UNRELIABLE

Bonjour provides convenient automatic discovery of QTAKE on the local network. If Bonjour discovery remains unreliable after basic network troubleshooting:

1. Set Enable Bonjour Services to NO in QTAKE Preferences.
2. Use a static, stable IP address for the QTAKE local-stream interface.
3. In QTAKE Monitor, open Left Sidebar > Connect > Servers and enter the IP address of the QTAKE Mac manually.

Bonjour is not required when QTAKE Monitor connects manually using the IP address of the QTAKE Mac.

CLOUD STREAM

For Cloud streaming, see STREAM MODE for more information about RELAY and DIRECT modes. In RELAY mode, QTAKE uploads one stream to QTAKE Cloud, which distributes it to connected clients. In DIRECT mode, QTAKE sends streams directly to connected clients, so QTAKE upload demand increases with the number of direct connections.

---

---

---

Pressing a GROUP button in the left segmented button will show the 10 PRESETS in that GROUP on the right. Press SETUP to configure your routing, groups, and presets. See the PRESETS AND GROUPS section below.

DEFAULT PORT NUMBERS
AJA Kumo default port: 80
BMD videohub default port: 9990

The LOCK button will lock output to an input. While locked the route is not available for routing.

---

---

HDR OUTPUT

ThunderFace and QOD support High Dynamic Range output. SDI Monitors with HDR payload detection will correctly set the colorspace and other HDR metadata.

---

---

---

SHOOT ROOM

This room is used for general video assist work - recording and playback.

---

---

COPY LIVE METADATA DIALOG

When activating REC SYNC, metadata of all inputs to be synchronised might not be synced. If this is the case, you will be presented with the dialog window asking to:

• either Copy LIVE Metadata
  • The metadata of items with the SYNC tag will copy for all LIVE inputs to be synchronized based on the LIVE clip in Active View.
• or Disable Metadata Sync
  • The synchronized recording will be active without synchronizing metadata.

The selection will adjust CLIP LIVE METADATA in the REC SYNC setup window. You can change it at any time in the setup window.

---

REHEARSAL CHECK

Using camera record flag detection, QTAKE can automatically check your clip metadata for incorrect Take value. In case you have marked the clip as a Rehearsal, but the camera was recording (or you have not marked it as a Rehearsal, but the camera was not recording), you will be presented with a warning window.

You can disable this warning by setting this preference to NO: Enable Rehearsal Warning = YES.

---

RECORD CONTROLS

During the recording process, you can use the following features:

IN & OUT ON THE FLY
During recording, you can set the IN and OUT (I and O keys) points to mark the important part of the clip.

CHAPTERS ON THE FLY
Besides the IN and OUT points you can create CHAPTER MARKS during recording (J key) to help you quickly navigate to the interesting parts of the shot during playback (< and > keys).

SUBCLIPS ON THE FLY
If you press the MAKE SUB button (P key), the subclip is created based on IN and OUT marks. If there is no OUT mark, the subclip range is determined by the IN mark and the current time. After creating the subclip, a new IN mark is set at the end of the subclip range. You can repeat this action to create the subclip for each take of the series. In addition, CHAPTERS are created for each IN and OUT point used to create a subclip.

CREATE THUMBNAIL
Press the THUMB button (U key) to set the current frame as the thumbnail for the recorded clip. If you don’t specify thumbnail time, IN point will be used to generate a thumbnail.

ABORT RECORD
You can abort recording at any time by pressing the ABORT button in the RECORD toolbar. The current clip will be discarded. The keyboard shortcut is Esc.

---

RECORD MULTI IN & OUT

When shooting a series or multiple actions in a single take, you can use multiple IN and OUT points to mark more than one selection. After pressing IN and OUT points for the first time, this selection is automatically stored and you can set different IN and OUT points.

---

BIT DEPTH

Video is usually recorded in YCbCr color code. You can choose to record in either 8-bit, 10-bit, or 12-bit mode. A higher bit depth mode will store video in higher quality, but it also requires more disk space and more processing power.

Set COLOR DEPTH in Project Settings > Project Area > COLOR.

---

CODEC

QTAKE records clips in Apple QuickTime file format. You can compress video to various codecs during a recording. Select the codec that best fits your postproduction workflow or make your selection based on space and quality requirements. QTAKE lets you use any of the following codecs: Apple ProRes Proxy, Apple ProRes LT, Apple ProRes, Apple ProRes HQ, Apple ProRes4444, and H.264 or HEVC. The codec that requires the least CPU resources is Apple ProRes Proxy.

---

TERADEK CUBE Support

QTAKE can record RTSP (Real Time Streaming Protocol) from Teradek CUBE over Wi-Fi, without the need for additional video input hardware. To enable the Teradek CUBEs video input you will need to enter the RTSP address in the PROJECT window. The Teradek CUBE has a bonjour-enabled web interface that is used to set up the device and update its firmware.

Step by step for connecting Teradek CUBE to QTAKE:

1. Connect to the Cubes admin interface. Click the Show All Bookmarks item in the Safari Bookmarks toolbar and select your Cube device from the devices listed under the Bonjour heading. For troubleshooting your connection refer to the Teradek Cube manual.
2. Make sure Teradek Cube is running the latest Firmware. Note that the text on the bottom of the Info > About window in the admin interface should say “Your device firmware is up to date.”
3. Set your Compression profile. Go to Video Setup > Encoder Settings and set it to Baseline.
4. Disable Quickview. You will need to disable Quickview for proper operation of the Teradek Cube in 1080 resolution. Go to Video Setup > Stream Settings, then click on the QuickView Stream tab and set the radio button to disabled.
5. Make note of Cube settings. Write down your Primary (RTSP) address and your Output Resolution from the Dashboard section of the admin interface.
6. Set up QTAKE. In Project Settings, select the channel’s VIDEO INPUT cell and open the URL tab. Enter the Primary RTSP address, then set the required input format in Format and Canvas. Refer to the Teradek CUBE manual for more setup information.

CUBE video reception is dependent on Wi-Fi signal strength. Using a router with external antennas can improve performance.

Only hardware that supports VDA decoding of H.264s can use other Profiles than Baseline.

QTAKE uses “LIVE555 Streaming Media” software licensed under LGPL. Live Networks, Inc. http://www.live555.com/

Growing Files (Live Clip Editing)

QTAKE Pro introduces the revolutionary Growing Files feature, empowering editors to begin working with recorded clips in their NLE (Non-Linear Editing) software while recording is still in progress. It significantly accelerates post-production workflows by eliminating the need to wait for a clip to finalize before beginning the edit.

This functionality extends the existing SHOW IN FINDER function to LIVE clips when recording progress. When “SHOW IN FINDER” is selected for a live growing clip, QTAKE Pro creates a temporary file on disk that continuously updates as the recording progresses. This “LIVE clip” can be directly imported into supported NLEs, such as Final Cut Pro (FCP), for immediate editing. As QTAKE continues to record, FCP (or other compatible NLEs) will automatically refresh the clip, reflecting the newly recorded frames at regular intervals.

A new preference, Instant Playback Interval, has been added to the Playback group to manage this behavior. With a default minimum value of 5 seconds, this setting defines the chunk size at which the temporary live clip file is refreshed on disk. A shorter interval means more frequent updates in your NLE, providing an even more “live” editing experience.

The Growing Files feature dramatically speeds up the overall editing process, allowing for parallel recording and editing and ultimately delivering content faster.

---

---

---

---

---

A take can be marked as a REHEARSAL and tagged with REF (for reference), P/T (for partial take), and P/U (for pick-up) in the TAKE window. Takes tagged with REF will automatically show up in the REFERENCE section of the browser.

The TAKE value is automatically incremented if entered in LIVE mode, before or during recording. If RECORD-SYNC is enabled, clip data entered in LIVE mode is automatically copied to other camera clips.

You can access extended clip data in the META panel and the DATA toolbar.
Each clip can be marked as Circle Take or Print Take. These marks are part of the CLIP DATA metadata category, and you can assign them a global keyboard shortcut. They also have a visual representation in the LIST next to the TAKE number. Circle Take’s mark is a FULL CIRCLE, and Print Take’s mark is an EMPTY CIRCLE.

Shot Field

UK Slating
You can replace the SHOT field with a SLATE field to conform with UK (European) slating. The SLATE field will auto-increment each time SCENE is changed. Change the slating system in the GENERAL tab of the Project Settings > Project Area Detail View.

The SHOT value can still be entered in the META panel.

The Shot field in Clip Metadata now includes enhanced functionality to speed up the traditional on-set slating process. When the Shot field contains either a single letter, a double-letter combination, or is empty (in line with standard film production Shot conventions), you can use the keyboard Up and Down arrow keys. These shortcuts will automatically increment the Shot value through the alphabet, up to two-letter combinations (e.g., A, B, C… AA, AB, AC…).

A similar approach applies to incrementing and decrementing the SLATE number when using the UK Stating system. Arrow Up increments the SLATE number, and arrow Down decrements it. This navigation is independent of SCENE bound, which means navigation is not limited to already existing SLATE numbers in a particular SCENE.

Shot Letter Exclusion

To maintain clean slate metadata and avoid confusion with numbers, you can define specific letters to be excluded from this automatic incrementing process:

• Select the Project Area in Project Settings and open GENERAL.
• Use the SHOT EXCLUSION field to enter letters that should not be used in the automatic sequencing.
• The system will automatically exclude all double-letter combinations that utilize the defined letters. For example, if you exclude ‘I’ and ‘O’, the system will automatically exclude ‘I’, ‘O’, ‘II’, ‘IO’, ‘OI’, and ‘OO’, as well as any double-letter combination that includes ‘I’ or ‘O’ in its sequence.

Global Shortcut and Stream Deck

For keyboard control, use the global shortcut Alt + H to focus on the Shot field. Once active, you can use the Up or Down arrow keys to increment or decrement the Shot value.

For Stream Deck control, use a CUSTOM BUTTON and ACTIVE DIAL from the QTAKE Stream Deck plug-in:

1. Assign the Shot field’s Action ID to a CUSTOM BUTTON.
2. Assign ACTIVE DIAL to an available Stream Deck dial, or replace an existing dial action.
3. Press the CUSTOM BUTTON to activate the Shot field.
4. Rotate the ACTIVE DIAL to adjust the active Shot value.
5. Press the CUSTOM BUTTON again or press the ACTIVE DIAL to use the current value and deactivate the field.

Visual Keyboard

Even when in a room where the CLIP toolbar or META panel is not visible, using the Alt + H global shortcut opens a visual keyboard interface for entering the Shot value. The new increment/decrement shortcuts remain fully functional within this visual keyboard, allowing you to slate shots regardless of the current room layout quickly.

It also applies with the SHOW KEYBOARD option disabled.

CLIP NAMING CONVENTION

Recording, importing, or rendering clips is producing Quicktime movie files encoded with the selected codec. All media files are located in the QTAKE Pro Storage folder on the PROJECT STORAGE volume, using unique, persistent filenames.

Additionally, the /QTAKE Pro Projects/PROJECT_NAME/Media folder on the same volume is used to store screenshots and exported files as well as hard links to your media files. These links can be created using CMF (Camera Media Filename) or pre-defined QTAKE filename structure:

[Scene_Shot_Take_Cam]SourceID-ClipID-InputID.mov

When using CMF, hard links will be named according to corresponding clips on the camera magazine. This only applies to clips that are recorded while QTAKE receives a valid record flag and filename metadata embedded in the SDI output of the camera. Clips that are recorded while the camera is not recording will be named by the standard QTAKE clip naming convention.

IMPORT CLIPS and LINK CLIPS functions can parse multiple types of filenames, select the appropriate import parsing filter in the Import dialog. See IMPORT QT MOVIES for specifics on each parsing filter.

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

SYNC SETUP

QTAKE will by default synchronize actions across all Views (1+2+3+4) when a sync button such as REC SYNC or CLIP SYNC is enabled. The SYNC SETUP window lets you exclude Views or break down the Views into smaller groups. Long-click one of the sync buttons to enter the SYNC SETUP window. The Views indicated in blue belong to the current sync group. Click one or more of the Views to exclude it from the group.

Views that are excluded from a sync group can be added to their group by closing the SYNC SETUP window, activating the View, and entering the SYNC SETUP window again. The sync buttons will indicate what Views are part of the current group in parentheses under the button title.

---

---

---

---

---

---

---

---

Why is the WAVE button inactive?
To use the waveform audio display you will need to set:
Enable Audio Waveform = YES

However you should be aware that enabling audio waveform will increase the performance requirements for the system.

Configure each channel’s AUDIO INPUT in Project Settings.

---

---

SIMULTANEOUS SDI INPUT & OUTPUT

Live passthrough provides an unprocessed output signal without QTAKE image-processing delay. When a processed LIVE output is used instead, QTAKE captures the input, processes the image, and sends the result through a configured video-card output.

To enable this simultaneous input and processed-output workflow, set:

Constant Playout Mode = YES

Because each frame must be captured, processed, and sent back through the video output, this workflow adds approximately 2–4 frames of latency compared with hardware live passthrough.

Some video cards provide full-duplex channels, allowing simultaneous input and output on the same channel through separate input and output connectors.

For instance, most AJA video cards support full-duplex operation, allowing simultaneous input and output. A four-channel AJA card can use:

• two channels for input and the other two for output,
• all four channels for input, or
• all four channels for output.

AJA video cards also use a single output clock, so all outputs on the same card must use the same format.

See VIDEO CARDS for details about supported video hardware.

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

QTAKE Preferences

This section describes each of QTAKE’s preferences. Preferences control various aspects of QTAKE operation and are independent of the user or project.

Preferences marked with an asterisk (*) require restarting QTAKE for changes to take effect.

GPU GROUP

Enable GPU Output *

Set this preference to NO to disable graphics card output. If you have multiple monitors connected to your computer, the first one will be used for QTAKE GUI and the others will not be used.

Use IN2CORE Devices Only *

The number of available slots for GPU OUT is always twice the HDx version.

When this preference is set to YES, only IN2CORE devices — ThunderFace 4K Duo+, ThunderFace 4K Duo, and QOD+ — are used for GPU output. External displays connected to the Mac’s GPU are ignored, ensuring that QTAKE’s GPU-based output is exclusive to IN2CORE devices. This setup allows external displays for background applications while QTAKE’s GUI remains on the main display.

When the preference is set to NO, external displays are allowed for GPU output, but IN2CORE devices are still prioritized.

Full Range Video

Set this preference to YES to enable Full Range video processing. The default value (NO) uses SMPTE legal levels, which will clip the super-black and super-white values.

Chroma Upsampling

Controls the Chroma Upsampling setting in the GPU group.

Legal Range GPU Output

Set this preference to YES to output legal range RGB through the GPU output.

QOD GPU Vendor *

Sets the manufacturer of your GPU. AUTO means automatic detection.

PROXY GROUP

Status In Proxy OSD

Set to YES to burn in the LIVE, DISK, REC, PLAY OSD status on STREAM proxies.

Local Stream Packet Loss Correction

This preference provides automatic resending of lost packets to significantly improve local streaming on poor-quality networks.

Cloud Stream Packet Loss Correction

This preference provides automatic resending of lost packets to significantly improve cloud streaming on poor-quality networks.

Stream Packet Size

Use this preference to limit the stream packet size if your network rejects default size packets. The default value is 1400.

Stream DSCP Value

Use this preference to set the Differentiated Services Code Point flag to streaming packets.

Input Stream Mode

This preference is used to adjust input stream buffering. More info is in the STREAMING FROM QTAKE TO QTAKE section.

VIDEO BOARD GROUP

Signal Detection Retry *

Sometimes it takes longer than one frame for AJA cards to adapt to a new input format. A side effect of this can be corrupted audio. If you experience such issues, set this preference to 25.

Autorecording Start Threshold

Set this to the number of frames by which you wish to delay the recording start. Can add robustness in bad signal conditions.

Autorecording Stop Threshold

Set this to the number of frames by which you wish to delay the recording stop. Can add robustness in bad signal conditions.

SDI OUTPUT GROUP

Constant Playout Mode *

Set this preference to YES for simultaneous input and output with compatible cards. This mode enables processed live output.

Enable Video Output *

Set to YES to enable video outputs. In case this is set to NO, a video board outputs only live passthrough and all other preferences affecting Video Output will be ignored.

Enable TC Output *

Set to YES to enable timecode output. This only applies to compatible video cards.

Use Free Genlock For Playback *

Set to YES to switch to free Genlock automatically when in DISK mode. This will keep stable SDI output if the camera is disconnected and you have no external reference signal. This setting is ignored when the Constant Playout Mode preference is set to YES.

Optimize PSF Input *

Set it to YES to improve performance with PSF format input when using AJA video cards.

LTC Output Source

Sets the source of the analog LTC output based on the video output of the video card.

FILE GROUP

Audio File Format

Sets the audio recording format. AUTO will set the recording format to match the input audio. 16bit, 24bit, and 32bit will record audio as integers at the selected bit-depth. 32bit Float will record audio as 32bit floating point values.

Ignore External Timecode

Set to YES to override the embedded timecode. The system clock is used instead.

ScreenShot File Format

Selects file format for screenshots. Options are JPEG, PNG, BMP, JPEG 2000, GIF, and TIFF.

ScreenShot Compression Quality

Set JPEG compression quality for Screenshots in the range of 1 to 10. The lower number means lower quality. The default value is 10.

ScreenShot Video Range

Set this preference to define a video range of the screenshot images. The following options are available: Auto, Legal, or Full Range.

PLAYBACK GROUP

Enable Instant Playback *

Set to YES to enable Instant Playback feature.

Instant Playback Interval

The preference sets the refresh rate (in seconds) and defines the size of the temporary file chunks continuously updated on the disk during recording. It allows playback of the LIVE during recording (Instant Playback) and Growing Files for NLEs.

The default and recommended minimum value is 5 seconds. A shorter interval means more frequent updates for LIVE clips in editing software, impacting data freshness and system I/O overhead.

PreRoll And PostRoll For PlaySync *

Set to YES to enable pre-roll and post-roll for Play Synced clips. This will allow you to play back clips with various duration in sync.

Use Audio For Varispeed

When set to YES, this preference enables audio monitoring for clips playing at non-100% PLAY SPEEDs. It ensures that audio remains active and audible during all variable-speed playback.

Enable Play Sync Auto Mute

QTAKE will mute Views 2-4 when playing back clips with play sync enabled to avoid the same audio playing from multiple Views. Set this to NO to disable this feature.

Set Play Sync Offset By TC

Set to YES if you want QTAKE to determine PLAY SYNC OFFSET using the timecode of the clips.

GUI GROUP

Use Film Style Scene Sorting

Set to YES to ignore letters before numbers when sorting Scene names. For example 33, A33, 34.

OSD Speed In FPS

Set to YES if you want to display OSD speed in FPS, instead of percentage.

Imperial Distance Units

Will convert values (such as focus distance) to imperial units.

Logo Opacity

Use this preference to set the NO VIDEO INPUT screen logo opacity. The default value is 0.25.

GPU Out X Label *

Sets the label shown for the corresponding GPU OUT slot. Separate fields are provided for GPU Out 1 Label through GPU Out 16 Label.

Multiclip Metadata Toolbars Mode

This preference is used to make CLIP, DATA, and CONTROL toolbars work with multi-clip selection.

Ovide Smart Mode *

Use the following values if using Ovide hardware for QTAKE: SmartAssist HD2, SmartAssist 4, SmartAssist Evo 2, and SmartAssist Evo 4.

On Screen Controls

Enables playback control overlay on the Views. The following options are available: Off, Disk only, Live & Disk.

Kiosk Mode *

QTAKE runs in kiosk mode by default. Set this preference to NO to disable kiosk mode. This will allow you to Cmd-Tab between running applications or display a window of another application in front of QTAKE UI.

Default Viewer Background

The Viewer background can be set to Black or Clear, by default.

AUTOLOAD GROUP

Autoload Project

Set to YES to automatically load the user and project after starting QTAKE.

Autostart Stream

Set to YES to enable the Stream function automatically after starting QTAKE.

RECORD GROUP

Prevent Media Drive Sleep

Prevent Media Drive Sleep by recording a small file for each specified number of seconds. Set to zero to disable.

Stop Recording On System Slow *

Set to NO to allow recording to continue even if QTAKE is dropping frames.

Enable Rehearsal Warning

Allows to control whether the WARNING about clip being marked as REHEARSAL and camera was recording is displayed after recording is finished or not. If the preference is set to YES, AUTO REC is set to SDI Flag and the clip is marked as REHEARSAL, after the recording is finished warning will pop up. This is also triggered when a recorded clip is marked as REHEARSAL.

EXTERNAL GROUP

Use Videohub *

Set to YES to enable control of the BMD Videohub or AJA Kumo SDI routers.

Enable Bonjour Services *

QTAKE advertises its presence on the local network via Bonjour service. This allows QTAKE Monitor clients to connect without knowing the IP address of the QTAKE machine. Set to NO to disable the Bonjour service and use static IP addresses instead.

Stream Deck Port

Sets the port used for communication between QTAKE and the Stream Deck application. Changes take effect immediately without restarting QTAKE. Use a different port if the configured port conflicts with another application.

DIAGNOSTICS GROUP

Report Main Thread Blocking *

This preference is used to test the performance of QTAKE and send a report if the user interface is blocked.

---

---

Acknowledgements

Portions of QTAKE Software may be using copyrighted third-party material. The following list includes the general license agreements that may cover multiple packages, and the agreements specific to those packages.

ACES

Academy Color Encoding System (ACES) software and tools are provided by the Academy under the following terms and conditions: A worldwide, royalty-free, non-exclusive right to copy, modify, create derivatives, and use, in source and binary forms, is hereby granted, subject to acceptance of this license. Copyright © 2015 Academy of Motion Picture Arts and Sciences (A.M.P.A.S.). Portions contributed by others as indicated. All rights reserved. Performance of any of the aforementioned acts indicates acceptance to be bound by the following terms and conditions: Copies of source code, in whole or in part, must retain the above copyright notice, this list of conditions, and the Disclaimer of Warranty. Use in binary form must retain the above copyright notice, this list of conditions, and the Disclaimer of Warranty in the documentation and/or other materials provided with the distribution. Nothing in this license shall be deemed to grant any rights to trademarks, copyrights, patents, trade secrets, or any other intellectual property of A.M.P.A.S. or any contributors, except as expressly stated herein. Neither the name “A.M.P.A.S.” nor the name of any other contributors to this software may be used to endorse or promote products derivative of or based on this software without express prior written permission of A.M.P.A.S. or the contributors, as appropriate. This license shall be construed pursuant to the laws of the State of California, and any disputes related thereto shall be subject to the jurisdiction of the courts therein. Disclaimer of Warranty: THIS SOFTWARE IS PROVIDED BY A.M.P.A.S. AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL A.M.P.A.S., OR ANY CONTRIBUTORS OR DISTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, RESITUTIONARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, THE ACADEMY SPECIFICALLY DISCLAIMS ANY REPRESENTATIONS OR WARRANTIES WHATSOEVER RELATED TO PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS IN THE ACADEMY COLOR ENCODING SYSTEM, OR APPLICATIONS THEREOF, HELD BY PARTIES OTHER THAN A.M.P.A.S.,WHETHER DISCLOSED OR UNDISCLOSED.

Boost

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the “Software”) to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

CocoaAsyncSocket

This library is in the public domain. However, not all organizations are allowed to use such a license. For example, Germany doesn’t recognize the Public Domain and one is not allowed to use libraries under such license (or similar).

Thus, the library is now dual licensed, and one is allowed to choose which license they would like to use.

###########################
License Option #1 :
###########################
Public Domain
###########################
License Option #2 :
###########################
Software License Agreement (BSD License)

Copyright (c) 2017, Deusty, LLC All rights reserved.

Redistribution and use of this software in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
• Neither the name of Deusty LLC nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission of Deusty LLC.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

CocoaLumberJack

BSD 3-Clause License

Copyright (c) 2010-2022, Deusty, LLC All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of Deusty nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission of Deusty, LLC.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

CocoaLUT

The MIT License (MIT)

Copyright (c) 2014 Wil Gieseler wil@wilgieseler.com & Greg Cotten greg@gregcotten.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Apple Core Audio Utility Classes

Disclaimer: IMPORTANT: This Apple software is supplied to you by Apple Inc. (“Apple”) in consideration of your agreement to the following terms, and your use, installation, modification or redistribution of this Apple software constitutes acceptance of these terms. If you do not agree with these terms, please do not use, install, modify or redistribute this Apple software.

In consideration of your agreement to abide by the following terms, and subject to these terms, Apple grants you a personal, non-exclusive license, under Apple’s copyrights in this original Apple software (the “Apple Software”), to use, reproduce, modify and redistribute the Apple Software, with or without modifications, in source and/or binary forms; provided that if you redistribute the Apple Software in its entirety and without modifications, you must retain this notice and the following text and disclaimers in all such redistributions of the Apple Software. Neither the name, trademarks, service marks or logos of Apple Inc. may be used to endorse or promote products derived from the Apple Software without specific prior written permission from Apple. Except as expressly stated in this notice, no other rights or licenses, express or implied, are granted by Apple herein, including but not limited to any patent rights that may be infringed by your derivative works or by other works in which the Apple Software may be incorporated.

The Apple Software is provided by Apple on an “AS IS” basis. APPLE MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE APPLE SOFTWARE OR ITS USE AND OPERATION ALONE OR IN COMBINATION WITH YOUR PRODUCTS.

IN NO EVENT SHALL APPLE BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE, REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OF THE APPLE SOFTWARE, HOWEVER CAUSED AND WHETHER UNDER THEORY OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright (C) 2013 Apple Inc. All Rights Reserved.

Avid DNxHD/DNxHR®

Avid DNxHD/DNxHR technology may be included with the QTAKE Software. Avid Technology Inc. requires this notice: “End User shall have no right to provide to others access to the QTAKE Software by cloud services or SaaS arrangements, for production, editing, or archiving services, except as otherwise provided elsewhere herein. Portions of QTAKE Software Copyright 2016-2022, Avid Technology, Inc.”

GNU LGPL v2.1

Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software–to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially designated software packages–typically libraries–of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author’s reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

We call this license the “Lesser” General Public License because it does Less to protect the user’s freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users’ freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a “work based on the library” and a “work that uses the library”. The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

1. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called “this License”). Each licensee is addressed as “you”.
   A “library” means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.
   The “Library”, below, refers to any such software library or work which has been distributed under these terms. A “work based on the Library” means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term “modification”.)
   “Source code” for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.
   Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.
2. You may copy and distribute verbatim copies of the Library’s complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.
   You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
3. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
   
   a) The modified work must itself be a software library.
   
   b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.
   
   c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.
   
   d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)
   These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
   Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.
   In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
4. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
   Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.
   This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
5. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
   If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
6. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a “work that uses the Library”. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.
   However, linking a “work that uses the Library” with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a “work that uses the library”. The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.
   When a “work that uses the Library” uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.
   If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)
   Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.
7. As an exception to the Sections above, you may also combine or link a “work that uses the Library” with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer’s own use and reverse engineering for debugging such modifications.
   You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:
   
   a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable “work that uses the Library”, as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)
   
   b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user’s computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.
   
   c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.
   
   d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.
   
   e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the “work that uses the Library” must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
   It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.
8. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:
   
   a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.
   
   b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
9. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
10. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.
11. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.
12. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.
    If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.
    It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
    This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
13. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
14. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
    Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.
15. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

1. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
2. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF GNU LESSER GENERAL PUBLIC LICENSE 2.1

GNU LGPL v3

GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.

1. Additional Definitions.
   As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
   “The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
   An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
   A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
   The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
   The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
2. Exception to Section 3 of the GNU GPL.
   You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
3. Conveying Modified Versions.
   If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
   
   a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
   
   b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
4. Object Code Incorporating Material from Library Header Files.
   The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
   
   a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
   
   b) Accompany the object code with a copy of the GNU GPL and this license document.
5. Combined Works.
   You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
   
   a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
   
   b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
   
   c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
   
   d) Do one of the following:
   0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
   1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user’s computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
   
   e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
6. Combined Libraries.
   You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
   
   a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
   
   b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
7. Revised Versions of the GNU Lesser General Public License.
   The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
   Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
   If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy’s public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

END OF GNU LESSER GENERAL PUBLIC LICENSE 3.0

Apache v2.0

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.
   “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
   “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
   
   “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
   “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.
   “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
   “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
   “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
   “Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
   “Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”
   “Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
   (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
   (b) You must cause any modified files to carry prominent notices stating that You changed the files; and
   (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
   (d) If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
   You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

Dolby Vision®

Dolby Vision technology may be included with the QTAKE Software. Dolby, Dolby Vision, and the double-D symbol are trademarks of Dolby Laboratories Licensing Corporation. Confidential unpublished works. Copyright 2013-2022 Dolby Laboratories. All rights reserved.

x264

x264 technology may be included with the QTAKE Software. Copyright and IPR of this technology is owned by and licensed from x264, LLC, which requires this notice: “You are granted a limited, non-exclusive, non-transferable license to run one copy of the object code version of the x264 software on one machine, device, dongle, or instrument solely as integrated and for running in combination with QTAKE Software. You have permission to make copies of the x264 software only for backup, trial and archival purposes. You are not allowed to: (i) copy the x264 software onto any public or distributed network; (ii) use the x264 software to operate in or as a time-sharing, outsourcing, service bureau, application service provider or managed service provider environment; (iii) use the x264 software as a standalone application or other than as integrated into QTAKE Software under this license; (iv) change any proprietary rights notices which appear in the x264 software or QTAKE Software; or (v) modify the x264 software. All third party licensors and suppliers retain all right, title and interest in third party software and all copies thereof, including all copyright and other intellectual property rights. You are allowed to transfer the license granted by the EULA only if (i) you comply with any transfer terms imposed by IN2CORE and deliver all copies of QTAKE Software to the transferee along with the EULA, (ii) transferee accepts the terms and conditions of the EULA as a condition to any transfer, and (iii) your license to use QTAKE Software terminates upon transfer. You are obliged to comply with all applicable export laws and regulations. You are also obliged to immediately destroy all copies of the x264 software upon termination of the EULA.”

NDI®

NDI technology may be included with the QTAKE Software. NewTek, Inc. requires this notice:

“This product includes NDI® software and technology licensed from NewTek, Inc. NDI® is a trademark of NewTek, Inc. NewTek and/or its licensors own all copyright rights in the NDI® Software and NDI® copyrightable technology utilized in the Product. All software herein, including the NDI® software and technology, is subject to the restrictions in this End User License, including the following restrictions, limitations and exclusions: 1) you may not reverse engineer, disassemble, or recompile the Product, including the NDI® Software, or any part thereof, or any NDI® protocols used in the Product, nor attempt to do any of the foregoing; 2) you may not copy, distribute, or create derivative works of the NDI® Software (except one copy may be made for archival backup purposes); 3) NewTek is not liable for any damages, whether direct, indirect, incidental or consequential, arising from the use of the Product and/or NDI®; 4) You accept the Product and NDI® software “as is” without warranties of any kind; all warranties, express or implied, of merchantability, fitness for a particular purpose, and warranty of title, are expressly disclaimed and excluded. To the extent any of the foregoing disclaimers is not allowed by applicable law such term shall not apply and in such case you agree not to utilize the NDI® in the Product.”

Live555

Live555 technology may be included with the QTAKE software. The Live555 Streaming Media source code is copyright of Live Networks, Inc., 2009-2019 and it is licensed under LGPL (Lesser General Public License).

OpenEXR

Copyright (c) 2006-2019 OpenEXR a Series of LF Projects, LLC. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

© 2022 Copyright OpenEXR a Series of LF Projects, LLC and/or its contributors. All documentation on this website made available under a Creative Commons Attribution 4.0 International License. All rights reserved.

ORSerialPort

Copyright (c) 2011-2012 Andrew R. Madsen andrew@openreelsoftware.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

PeerTalk

Copyright (c) 2012 Rasmus Andersson http://rsms.me/

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Sparkle

Copyright (c) 2006-2013 Andy Matuschak. Copyright (c) 2009-2013 Elgato Systems GmbH. Copyright (c) 2011-2014 Kornel Lesiński. Copyright (c) 2015-2017 Mayur Pawashe. Copyright (c) 2014 C.W. Betts. Copyright (c) 2014 Petroules Corporation. Copyright (c) 2014 Big Nerd Ranch. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

EXTERNAL LICENSES

bspatch.c and bsdiff.c, from bsdiff 4.3 http://www.daemonology.net/bsdiff/: Copyright (c) 2003-2005 Colin Percival.

sais.c and sais.c, from sais-lite (2010/08/07): Copyright (c) 2008-2010 Yuta Mori.

SUDSAVerifier.m: Copyright (c) 2011 Mark Hamlin.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted providing that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS’’ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

STPrivilegedTask

BSD 3-Clause License

Copyright (c) 2008-2021, Sveinbjorn Thordarson All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
• Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

websocket-kit

The MIT License (MIT)

Copyright (c) 2020 Qutheory, LLC

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

---