# Introduction The **3Q Streaming Platform** is a comprehensive solution for managing, delivering, and analyzing the usage of professional video content. It enables organizations to stream live and on-demand video securely, manage media assets efficiently, and reach audiences across devices and platforms. This documentation describes the **current generation of the 3Q platform user interface**, which introduces a modernized design focused on clarity, speed, and ease of use. Core workflows have been streamlined, and access to key features has been optimized to support efficient day-to-day operations. The new interface is being rolled out progressively. While it already covers essential functionality, some modules and advanced features from the Classic UI are not yet available. Existing documentation for the Classic UI in the Help Center remains valid unless explicitly stated otherwise. Where features overlap, behavior and functionality are identical across both interfaces. The platform will continue to evolve, with additional modules, features, and documentation sections added over time. {% hint style="info" %} We recommend subscribing to our [status page](https://3q-status.com/) to stay up to date with release notes, maintenance schedules, and important updates. {% endhint %} ### Login {% embed url="" %} ### Platform Tutorial {% embed url="" %} ### Compatibility
BrowserSupported versions
Chrome- Always the latest 3 Versions
- Chrome for android is supported
- Chrome for iOS is supported
Firefox- Always the latest 3 Versions (and the latest ESR Version)
- Firefox for android is supported
- Firefox for iOS is supported
- Firefox Focus is supported
Safari- Supported, starting with Safari 16
- Safari for iOS is supported
Edge- Always the latest 3 versions (and the last EdgeHTML version)
- Edge for android is supported
- Edge for iOS is supported
Other browsers- Opera (latest 3 versions)
- Samsung browser (latest 3 versions)
- Huawei browser (latest 3 versions)
# First steps This guide helps new users get started with the 3Q platform. It explains the basic steps required to set up an account, prepare projects, invite team members, upload on-demand content, start livestreaming, and embed media on external websites or applications. The recommended onboarding workflow is: 1. Register and access your account 2. Set up projects 3. Create categories and types 4. Invite colleagues and assign permissions 5. Upload content and stream live 6. Embed and share your content *** ### Registering an Account To start using 3Q, you need access to a [registered](https://sdn.3qsdn.com/en/register) account. Depending on your organization, the account may already be created by an administrator or provided during onboarding. After registration, users can [log in](https://platform.3qsdn.com/) to the platform and access the modules, projects, and features that are enabled for their account. After signing in for the first time, check the following: * Your user profile is available * Your account is active (subscription) * The required modules are enabled * You have access to the projects you need * Your role includes the required permissions Some features are controlled by account configuration and user rights. If a feature is not visible, it may need to be enabled or booked in [Module Management ](/user-guide-new-ui/modules)or assigned through [User Management](/user-guide-new-ui/account/users). *** ### Setting Up Projects Projects are the main workspaces in 3Q. They define where content is uploaded, managed, streamed, recorded, or published. Before uploading or streaming content, create or configure the projects you need for your workflow. Common project types include: * [**On-Demand Projects**](/user-guide-new-ui/projects/on-demand)\ Used for uploaded video and audio files that are processed, managed, and published as media assets. * [**Livestream Projects**](/user-guide-new-ui/projects/livestreaming)\ Used for live events, recurring streams, and live playback workflows. When setting up a project, define the basic project settings, review access rights, and configure the metadata and publishing options required for your use case. A common setup is to create separate projects or content pools for different departments, customers, brands, or workflows. Example project structures: * Public Videos * Internal Training * Webinars * Townhalls * Product Videos * Event Livestreams * Podcast Episodes *** ### Creating Categories and Types (optional) Categories and types help structure metadata for on-demand content. They are defined globally for the account and can then be used across projects and content pools. Per project or content pool, users can define whether all global categories and types should be available or whether only selected ones should be used. This makes it easier to keep metadata consistent while still allowing project-specific workflows. #### Categories Categories are used to group content by topic, department, format, or editorial area. Examples: * Tutorials * Product Videos * Town-Halls * Movies * Talkshows * Music Videos #### Types Types are used to define the content format or content purpose. Examples: * Movie * Preview * Recording * Trailer * Webinar * Interview Categories and types can later be assigned to on-demand assets and used for search, filtering, playlist automation, and frontend integrations. *** ### Inviting Colleagues and Assigning Rights After the account and projects are prepared, invite colleagues who should work with the platform. User access is managed through [User Management](/user-guide-new-ui/account/users). Depending on their role, users can be allowed to upload content, edit metadata, manage players, create playlists, configure modules, or administer account settings. When inviting colleagues, consider which responsibilities each user should have. Typical roles include: * Account administrators * Project managers * Editors * Upload users * Livestream operators * Technical integration users * Read-only or review users Assign permissions carefully so that each user has access to the features and projects they need, but not more than required. If modules are enabled on the account level, users may still need explicit permissions before they can access or use them. *** ### Uploading On-Demand Content Once projects and permissions are ready, users can start uploading on-demand content. On-demand content is managed inside an on-demand project or content pool. Uploaded files are processed by 3Q and then become available as media assets. After uploading a file, users can manage the asset in the project’s asset management area. Typical tasks include: * Reviewing the uploaded file * Editing title, description and other metadata * Assigning categories, types, and tags * Setting the release status (optiona) * Defining availability windows * Adding cover images * Managing audio tracks * Adding subtitles * Creating chapters * Preparing the asset for embedding or publishing The asset detail view provides access to playback, metadata, cover images, audio tracks, subtitles, chapters, file attachments, and playout and sharing options. *** ### Streaming Live [Livestream projects](/user-guide-new-ui/projects/livestreaming) are used to receive and publish live signals. To start livestreaming, create or open a livestream project and review the ingest settings. The ingest information is used by the encoder or production system to send the live signal to 3Q. A typical livestream workflow includes: 1. Open the livestream project. 2. Copy the ingest endpoint and stream name. 3. Configure the encoder or production system. 4. Send a test signal. 5. Check the signal status in the livestream control center. 6. Start the live event. 7. Monitor playback and stream status. Depending on the account configuration, additional livestream features may be available, such as Timeshift, Live Clipping, Livestream Distribution, or Livestream Recorder. Live Clipping can be used when Timeshift is enabled and allows users to create clips from an active or previous livestream and export them to an on-demand project. Livestream Recorder can be used to record livestream projects and store the recordings separately in a selected on-demand project or content pool. *** ### Embedding and Sharing Content After content has been uploaded, processed, or streamed, it can be embedded or shared. Embedding is handled through the Playout and Sharing area. Depending on the content type and configuration, users can generate integration codes or links for websites, portals, applications, or external systems. Common embed options include: * JavaScript embed code * iFrame embed code * Direct player URL * oEmbed link * Streaming URLs for custom players For most website and application integrations, the 3Q Player Web SDK is recommended because it supports player configuration, subtitles, audio tracks, chapters, analytics, adaptive streaming, and other platform features. When embedding content, select the appropriate playout configuration. The playout defines how the content is presented to viewers and which player settings are applied. Playlists can also be embedded and used for structured playback experiences, such as video collections, video carousels, or vertical reel-style players. *** ### Recommended First Setup Workflow For a new account, the following setup order is recommended: 1. Register or activate the account. 2. Enable the required modules in Module Management. 3. Create the required projects and content pools. 4. Define global categories and types. 5. Configure project-specific metadata availability. 6. Invite colleagues through User Management. 7. Assign project and module permissions. 8. Upload first on-demand test content. 9. Create or configure a livestream project. 10. Test upload, processing, playback, and livestream ingest. 11. Configure players and playouts. 12. Embed the first video, livestream, or playlist. This workflow ensures that the account structure, permissions, metadata, and publishing setup are ready before production content is added. *** ### Typical First Use Cases The first setup can support different workflows, for example: * Uploading and publishing on-demand videos * Creating a public video library * Managing internal training content * Streaming a live event * Recording livestreams for later on-demand use * Creating playlists and video carousels * Embedding videos on a website * Integrating 3Q with external systems through notifications or APIs *** ### Notes Available features may depend on account configuration, enabled modules, and user permissions. If a module, project, or action is not visible, check whether the module is enabled and whether the user has the required rights. For production workflows, it is recommended to test uploads, livestream ingest, player configuration, and embeds before publishing content publicly. # User interface The user interface follows a clear and consistent layout designed to provide quick access to all core functions.
### **Left Navigation (Main Menu)** The vertical navigation bar on the left side of the interface provides access to the main functional areas of the platform. Depending on the user role and permissions, the following sections may be available: * **Projects** - Central area for managing on-demand and livestream projects * **Players** - Configuration and management of media players * **Playlists** - Creation and administration of playlists * **Podcasts** - Management of audio and video podcasts * **People** - Manage persons for video / media metadata * **Analytics -** Analysis and evaluation of engagement and usage data * **Modules** - Optional platform extensions and features * **Account** - Account-related settings and configuration A link to the [**Classic UI**](https://sdn.3qsdn.com/) is available at the bottom of the navigation to access legacy features that are not yet part of the new interface. ### **Top Bar (Global Actions)**
The top bar spans the full width of the interface and contains global functions: * **Global Search** – Allows searching across all accessible content, including projects and assets This area remains consistent across all sections of the platform. ### **Project Overview Area** The central content area displays the active view. In the Projects section, projects are presented as tiles in a grid layout. Each tile includes: * Project preview image * Project name * Content type indicator (for example, On-Demand or Livestream) * Additional labels such as group assignments Above the grid, users can switch between different project views (All Projects, On-Demand, Livestream, Favorites), apply filters, group projects, or search within the current context. Selecting a project opens a detailed view or overlay with associated assets and metadata, such as on-demand files, creation dates, and playout configuration. ### **Right-Side Panels and Menus** The platform provides contextual panels and menus on the right side: * **Support Panel** – Offers direct access to platform status information, support tickets, API documentation, player documentation, and platform documentation * **User Account Menu** – Accessible via the user avatar in the top-right corner, providing access to personal settings, password and security options, support, and logout These panels open as overlays and do not interrupt the current workflow. ### Global search
The **Global Search** is available in the top navigation bar and allows users to search across different areas of the platform. It can be used to quickly find content, projects, playlists, categories, MediaRSS exports, and other available resources without navigating manually through each section. When entering a search term, the platform displays matching results in a structured search panel. Results are grouped by content area, such as: * On-Demand Files * Events * Projects * Playlists * Categories * MediaRSS Exporter * Groups Users can switch between the result tabs to narrow the search to a specific section. Each search result can include relevant information such as: * Title * Number of items * Type or content label * ID * Creation date * Last updated date * Playout ID, where available * Quick actions, depending on the result type The Global Search is useful for quickly locating items across the account, especially in accounts with many projects, files, playlists, or metadata entries. #### Using Global Search To use the Global Search: 1. Click the search field in the top navigation bar. 2. Enter a search term. 3. Review the results in the search panel. 4. Select the relevant result tab, if needed. 5. Open the desired item or use the available quick actions. #### Typical Use Cases Global Search can be used for workflows such as: * Finding a specific video or audio file * Opening a project directly * Searching for a playlist * Locating categories or metadata structures * Finding a MediaRSS export * Accessing related items without changing the current page manually #### Notes The displayed search results depend on the user’s permissions. Users only see items they are allowed to access. The available result tabs and quick actions may depend on account configuration, enabled modules, and the type of search result. # Projects ### Project Management (Content Pools) Projects - also referred to as **Content Pools** - are the central organizational units for media content on the platform. In **On-Demand projects**, you can upload and manage an unlimited number of media files, while **Livestream projects** represent a dedicated livestream channel used to create and manage live broadcasts. *** ### Projects Overview
The **Projects** section provides an overview of all available content pools within the account. Here you can: * View all existing projects * Filter projects by type (**On-Demand** or **Livestream**) * Mark projects as favorites * Search for projects by name * Create new projects Projects are displayed as tiles showing the project name, type, and assigned group. *** ### Project Types Two project types are available: #### On-Demand Projects On-Demand projects are used to manage pre-recorded media content. Within an On-Demand project, you can: * Upload video and audio files * [Organize and manage media assets](/user-guide-new-ui/projects/on-demand) * Publish content for on-demand playback #### Livestream Projects Livestream projects are used for live video events. Within a Livestream project, you can: * Stream video and audio content * [Configure and manage live streams](/user-guide-new-ui/projects/livestreaming) * Store and manage livestream recordings (depending on enabled modules) *** ### Creating a Project ### Required Permissions for Creating Projects {% hint style="info" %} To create projects, one of the following conditions must apply: * You created the customer account and therefore automatically have all user permissions. * You were invited to the account as a user and have been granted the permission. * You have the **Admin** role for the customer account. {% endhint %} New projects can be created directly from the Projects overview. When creating a project, you define: * **Title** of the project * **Project type** (On-Demand or Livestream) * [**Group assignment**](/user-guide-new-ui/account/groups) * **Default publication status** * **Default metadata language** These settings apply to all content within the project. *** ### Project Configuration Additional configuration options depend on the selected project type and enabled modules. Detailed configuration settings for: * [**On-Demand projects**](/user-guide-new-ui/projects/livestreaming) * [**Livestream projects**](/user-guide-new-ui/projects/on-demand) are described in the corresponding chapters of this documentation. *** ### Accessing Project Options
Each project provides a context menu with additional project actions. Depending on the selected view, you can access these options in different ways: * In the **tile view**, move the mouse over the project card. The available project action icons appear directly on the card. Click the **three-dot menu** to open further options. * In the **list view**, move the mouse over the project row. The available actions appear on the right side of the row. Click the **three-dot badge** to open the project options menu. Depending on the project type and your permissions, the menu may include options such as: * **Tag Management** * **Input Signal Settings** for livestream projects * **Transcoding Settings** for livestream projects * **Encoding Settings** for on demand projects * **Playout and Sharing** * **Create Copy** * **Delete** *** ### Deleting a Project Projects can be deleted from the project options menu.
To delete a project: 1. Open the **Projects** overview. 2. Move the mouse over the project you want to delete. 3. Open the project options menu using the **three-dot menu**. 4. Select **Delete**. 5. Confirm the deletion when prompted. {% hint style="info" %} Deleting a project removes the project from the account. Before deleting a project, make sure that the project and its content are no longer required. Depending on your account configuration and permissions, deletion may also affect media files, livestream settings, playouts, and integrations connected to this project. {% endhint %} # General Settings
Project settings define the basic behavior, metadata defaults, access rules, and project-specific options of a project. The available settings depend on the project type. On-demand projects and livestream projects share several basic settings, but also include project-specific options. Project settings can be opened from the project overview by selecting the settings action of a project. From the project settings, users can: * Edit the project image * Change the project title * Assign the project to a group * Manage the project key * Enable content protection through the project key * Define the default metadata language * Set default publication behavior * Configure project-specific advanced settings * Configure livestream-specific options such as automatic event creation or eCDN provider settings *** ### Opening Project Settings To open the settings of a project: 1. Open **Projects** in the main navigation. 2. Find the project you want to configure. 3. Open the project actions. 4. Select the **Settings** icon. 5. The **Project Settings** side panel opens. The side panel contains the available settings for the selected project. Depending on the project type, the following tabs may be available: * **General** * **Advanced Settings** *** ### General Settings The **General** tab contains the main project configuration. These settings define the project’s identity, language defaults, publication defaults, and access behavior. *** ### Project Image The project image is used as the visual representation of the project in the project overview and in other platform areas where the project is displayed. Users can upload or select an image for the project. The image area may show: * Current project image * Image dimensions * Image selection button * Image actions such as replace, download, or delete, depending on permissions Use a clear and recognizable image, especially when multiple projects or content pools are used in the same account. *** ### Title The **Title** is the visible name of the project. Choose a clear and descriptive title so users can easily identify the project in lists, filters, upload workflows, analytics, notifications, playlists, and other modules. Example project titles: * Public Videos * Product Videos * Tutorials * Townhalls * Webinars * Internal Training * Event Livestreams *** ### Group {% hint style="info" %} **Availability note:** The **Groups** feature is not available for all accounts (tenants). The available groups depend on the account configuration and your desired account structure. {% endhint %} The **Group** setting assigns the project to a project group. Groups help organize projects in larger accounts and make it easier to manage multiple content pools, departments, brands, customers, or workflows. Example groups: * Default * Demo Group * Marketing * Internal Communications * Customer Projects * Event Production *** ### Project key {% hint style="info" %} Handle project keys carefully, especially when they are used for protected content or external integrations. {% endhint %} The **Project Key** is private technical key associated with the project. It can be used for the player token protection as well as the content protection for the CDN. The project key can be copied from the settings panel. Depending on permissions and configuration, users may also be able to regenerate or edit the key. *** ### Content protection through project key The **Content Protection through Project Key** option restricts access to content by requiring valid tokens calculated from the project key. {% hint style="info" %} When this option is enabled, content can only be accessed using tokens that are generated from the project key. {% endhint %} This is useful for protected delivery workflows where content should not be accessible through unprotected URLs. Use this option when: * Content access must be restricted * Token-based access is required * Content should only be available through authorized systems * External integrations need controlled access When content protection is enabled, make sure that the consuming application or website can generate or request the required tokens. *** ### Default Metadata Language The **Default Metadata Language** defines the primary language used for metadata in the project. This setting affects metadata fields such as titles, descriptions, and other localized values. Example: * German (Germany) * English * Other available account languages Choose the language that matches the main editorial workflow of the project. *** ### Hide Local Language Variants and Scripts The **Hide Local Language Variants and Scripts** option can be used to simplify language selection by hiding local variants and script-specific language options. This can make metadata editing easier when users should only work with general language options. *** ### Default Publication Status The **Default Publication Status** defines the release status that is applied to new content by default. For on-demand projects, this setting controls how newly uploaded or processed media is published initially. For example, if the default publication status is set to **Published**, newly processed content may become available automatically after processing. Use this setting carefully, especially in projects with required metadata fields. If a project contains several required fields, it is not recommended to publish media automatically, because it cannot be guaranteed that all required fields have already been completed. Common use cases: * Use **Published** when uploaded content should become available automatically. * Use a restricted or unpublished default status when content should be reviewed before publication. The available publication statuses depend on the account configuration. *** ### Apply Publication Period to Playout The **Apply Publication Period to Playout** option controls whether content can be accessed outside its defined publication period. When this option is active, content can no longer be accessed through the playout outside the publication period. This is useful for workflows with: * Licensed content windows * Time-limited campaigns * Event-specific availability * Scheduled publication and expiration * Internal release control *** ## Advanced Settings for On-Demand Projects The **Advanced Settings** tab contains additional project-specific options for on-demand projects. These settings can affect metadata behavior, upload workflows, image handling, and automatic deletion. *** ### Activate Recommendations The **Activate Recommendations** option allows the system to create recommendations for files based on their metadata. When enabled, recommendation data can be generated and updated continuously. This can be used to support related-content workflows or frontend recommendation features, depending on the account and player configuration. *** ### Limit Categories By default, all globally defined categories are available in every project. The **Limit Categories** setting allows users to restrict which categories are available in the selected project. This is useful when a project should only use a specific subset of the account’s global category structure. To limit categories: 1. Open the project settings. 2. Open **Advanced Settings**. 3. Click **Set Categories**. 4. Select the categories that should be available in the project. 5. Save the configuration. After limiting categories, editors will only see the selected categories when managing content in this project. This is useful for: * Department-specific content pools * Customer-specific projects * Editorial workflows with restricted metadata * Preventing incorrect category assignment * Keeping upload and editing workflows simpler *** ### Upload Confirmation Template The **Upload Confirmation Template** allows administrators to define a text that users must confirm before uploading files to the project. If this field is filled out, each user must explicitly confirm the text before each file upload. This can be used for legal, editorial, or operational confirmations. Example use cases: * Confirming that upload rights are cleared * Confirming that content does not contain restricted material * Confirming internal compliance rules * Informing upload users about project-specific requirements * Adding customer-specific upload instructions The template supports multilingual input where available. *** ### Activate Image Gallery The **Activate Image Gallery** option allows users to create and manage an image gallery for each file. Images from the gallery can then be displayed, for example, in a frontend integration. This is useful for workflows where video files should be accompanied by multiple images, stills, or visual assets. Example use cases: * Product videos with additional product images * Editorial videos with image galleries * Event videos with supporting photos * Frontend pages that display video and image content together *** ### Automatically Delete Media The **Automatically Delete Media** setting defines whether new uploads should be deleted automatically after a specified number of days. If a value greater than **0** is entered, each new upload is automatically configured so that it is deleted after the specified number of days. Use this setting for projects where media should only be stored temporarily. Example use cases: * Temporary upload projects * Review workflows * Short-term campaign material * Automatically expiring test uploads * Compliance-related deletion rules Set the value to **0 days** if media should not be automatically deleted by this project setting. *** ## General Settings for Livestream Projects Livestream projects include several settings that are specific to live workflows. In addition to the common project settings such as title, group, project key, and default metadata language, livestream projects may include options for automatic event creation and eCDN delivery. *** ### Create Events Automatically The **Create Events Automatically** option allows the system to create livestream events automatically when a signal is detected. When this option is enabled, the system automatically creates events when a signal is present or ends. This is useful for the analytics for the livestreams. *** ### eCDN Provider {% hint style="info" %} This option is available after you have connected a E-CDN Provider in the [Partner and Services](/user-guide-new-ui/account/partners-and-services) section. {% endhint %} The **eCDN Provider** setting defines the enterprise CDN provider used for the livestream project. An eCDN provider can be used to optimize livestream delivery in enterprise or internal network environments. Use this setting when livestreams should be distributed efficiently inside corporate networks or controlled enterprise environments. More Information you can find [here](/user-guide-new-ui/projects/livestreaming/e-cdn-for-livestreaming). *** ## Difference Between On-Demand and Livestream Project Settings On-demand and livestream projects share several general settings, but each project type also has specific options. **On-demand projects** focus on uploaded media, metadata management, publication behavior, image galleries, category restrictions, and automatic deletion. **Livestream projects** focus on live signal workflows, automatic event creation, livestream delivery, and eCDN configuration. When editing project settings, always check the project type and review the available options carefully. *** ## Typical Use Cases Project settings can be used for different workflows, for example: * Creating separate projects for departments or customers * Defining default metadata and publication behavior * Protecting content with project-key-based tokens * Restricting available categories per project * Adding upload confirmation text for compliance workflows * Enabling automatic deletion for temporary projects * Creating livestream events automatically * Configuring eCDN delivery for livestream projects *** ## Notes The available project settings depend on the project type, account configuration, enabled modules, and user permissions. Changes to project settings may affect uploads, publication behavior, metadata editing, content access, livestream workflows, and frontend integrations. Review settings carefully before applying changes to production projects. # Livestreaming This section describes a typical end-to-end workflow for running a livestream in the 3Q platform, from preparing ingest settings to sharing the player and creating recordings. The steps reflect the live control view shown in the screenshots. *** ### Live Control View
1. In **Projects**, open the livestream project you want to broadcast. 2. The project opens in the **Live Control View**. A **Live** badge indicates the project type and current state. {% hint style="info" %} During the event, you can view the current number of viewers in real time at any moment, and afterwards analyse usage in detail within the Analytics module. {% endhint %} The Live Control View is split into: * **Live Player** (monitoring output) * **Player Status** (state-dependent visuals) * **Signal Status** (ingest monitoring) * **Log** (technical events) * **Recorder** (recording control) * Optional panels (Comments, Settings, Playout and Sharing) *** #### Stream Health in Signal Status 1. Review the **Signal Status** graph to confirm stable ingest. 2. Verify key values: * **Bitrate** * **Resolution** * **FPS** * **Codecs** (for example, H.264 / AAC) If values are missing or unstable, check encoder configuration and network conditions, then review the Log for warnings. *** #### Monitor Technical Events in the Log 1. Use the **Log** panel to track processing events and potential issues. 2. Use the **Detail Level** filter to switch between: * All entries * Warnings and errors * Only errors 3. Use **Search** to find specific messages (for example, transcoding, ingest endpoint, audio layout). For deeper context, use the **Info** action on a log entry when available. *** ### Player status assets (Recommended)
Player status assets define what viewers see in the embedded video player during different phases of a live stream. Configuring these assets ensures a consistent and predictable viewing experience - especially before a stream starts, after it ends, or if technical issues occur. {% hint style="info" %} When switching between player states, it can take **3–8 seconds** for updates to propagate and become visible to viewers in the embedded player. {% endhint %} You can control exactly what users see in the player embedded in your app or website by assigning images or videos to the following states: * **Stream** (active live playback) * **Pre-Live Image** (waiting screen before livestream event starts) * **Pre-Live Video** (optional waiting video) * **Post-Live Image** (shown after ingest ends) * **Technical Difficulties Image** (fallback screen for interruptions) Ensure these assets are configured before going live to provide a predictable viewer experience. *** ### Create and manage a recording
Recordings are managed in the **Recorder** section. To create a recorder: 1. In **Recorder**, select **Create Recorder**. 2. In the settings panel, define: * **Title** and optional **Description** * **Target Project** (destination project for the resulting recording) * **Enable Auto Recording** (recording starts/stops automatically with signal presence) * Optional: **Enable Interval Recording** (splits long recordings into segments based on the selected interval) After saving, active recorders are listed in the Recorder area with their status. *** ### Publish and Share the Livestream (Playout and Sharing)
To embed or distribute the livestream, use **Playout and Sharing**: 1. Select **Playout and Sharing** in the top-right area. 2. In **Playout Management**: * Choose the playout configuration (for example, the default playout). * If required, select **Create Playout** to create an additional playout configuration. * Copy the **embed code** (iframe, javascript) for websites and portals. * Optional settings may include display behavior such as dynamic scaling and performance options such as lazy loading. 3. In **Streaming URLs**: * Access the platform-generated stream URLs (for example **HLS (H.264)**). * Copy the required URL for distribution, monitoring, or external systems. {% hint style="info" %} Use playout options when you want a controlled player integration. Use streaming URLs when you need direct stream access (for example custom videoplayers or monitoring). {% endhint %} *** ### Reset Timeshift {% hint style="info" %} The **Reset Timeshift** option is only available when Timeshift is enabled for the project **and** the live ingest signal is currently offline. {% endhint %} If timeshift is enabled for the project, the UI may provide a **Reset Timeshift** button in the top-right control area. Use this function to reset the timeshift buffer when needed (for example after ingest changes or operational resets). This action is typically used during production operations and should be applied deliberately. *** ### End a Livestream When the broadcast is finished: 1. Stop the encoder output (recommended as the primary stop action). After ingest ends: * We recommend to switch the embed state to **Post-Live.** * The **Log** will show finalization events. * Recorder output is completed and delivered to the configured target project (depending on recorder settings). # Ingest Settings
1. Select **Settings** in the top-right area of the project. 2. Open **Input Signal Settings** (right-side panel). In **General**, configure: * **Stream Type** (e.g., *RTMP Push, SRT Push or HLS Pull*) * **Primary Ingest Endpoint** (region/endpoint selection) * Optional: **Latency Control** * No optimization: 12 - 18 secs delay * Low Latency: 3 - 6 secs delay * Optional: **Automatic Failover** * Optional: **Stream Stabilisation** * Optional: **Available Timeshift Duration** (if supported/required) {% hint style="info" %} Using subtitles or automatic dubbing adds an additional **40–50 seconds** of latency to the live stream. This delay ensures the highest possible quality for transcripts and translations. {% endhint %} In **Advanced Settings** (if available, see [Partners & Services](/user-guide-new-ui/account/partners-and-services)), configure: * **Source Language** * **Generate Subtitles Automatically** * Optional**: Automatically Translated Subtitles** (target languages) * Optional: **Automatic Dubbing** * **Signal Delay** (adds a defined delay to the stream) Save the settings and keep the panel open if you still need the ingest parameters for your encoder. # Signal Guidelines To ensure uninterrupted livestream delivery and optimal quality, the incoming signal must be delivered to the platform with sufficient quality and via a reliable connection. Please consider the following recommendations carefully. ### Compatible Encoders In general, the 3Q streaming platform is compatible with all encoders that support the streaming protocols used by the platform. This includes most professional hardware and software encoders commonly used in live production workflows. While many encoders are technically supported, we strongly recommend testing your chosen encoder thoroughly before using it in a production environment. Encoder behavior can vary depending on configuration, firmware, and network conditions, and proper testing helps ensure stable ingest and reliable stream quality. {% hint style="info" %} 3Q supports all **RTMP**, **SRT**, and **HLS-compatible encoders** for the signal ingest. The encoder hardware and software listed below have been tested and confirmed to work with the 3Q platform. If you use an encoder that is not listed here, **please let us know** whether it works well with your setup. {% endhint %} #### Hardware | Manufacturer | Supported Protocols | | ------------ | ------------------- | | Haivision | RTMP, SRT | | Teradek | RTMP, SRT | | AJA HELO | RTMP | #### Software | Product | Supported Protocols | | ------------------ | ------------------- | | Wirecast | RTMP | | OBS | RTMP | | XSplit Broadcaster | RTMP, SRT | | FFmpeg | RTMP, SRT | | vMix | RTMP, SRT | *** ### Recommended Resolutions, Bitrates, and Frame rates
ResolutionFrame RateMinimum BitrateRecommended BitrateMaximum Bitrate
1080p25–29.97 fps3 Mbit/s6 Mbit/s10 Mbit/s
1080p50–60 fps6 Mbit/s8 Mbit/s15 Mbit/s
720p25–29.97 fps2.5 Mbit/s4 Mbit/s6 Mbit/s
720p50–60 fps4 Mbit/s5 Mbit/s8 Mbit/s
Note on Frame Rates * **25–29.97 fps** is recommended for most standard broadcasts and presentations. * **50–60 fps** is recommended for sports, motion-heavy content, or detailed screen captures. * Higher frame rates require **significantly more upload bandwidth** and a stable connection. #### Video Settings {% hint style="info" %} Using **CBR encoding** and correctly configured **keyframe intervals** is essential for a stable and reliable livestream. {% endhint %}
SettingRecommendation
CodecH.264, H.265/HEVC, VP9
Resolution1920x1080
Frame rate

Supported frame rates are 25, 30 (29.97), 50, and 60 (59.94) frames per second, using progressive scan.

For higher resolutions (2K and above), frame rates are currently limited to 25–30 fps.

Bitratesee, Recommended Resolutions, Bitrates.
Bitrate ModeCBR
KeyframesEvery 2 seconds, or 1 second for low latency
Level≥ 4.1
ProfileMain or higher (High for 1080p)
Scene CutDisabled
Keyframe AlignmentEnabled (align on PTS)
#### Audio Settings | Setting | Recommendation | | ----------- | ------------------------------------- | | Codec | AAC, VORBIS (for VP9), OPUS (for VP9) | | Sample Rate | 44,1 or 48 kHz | | Bitrate | 192 kbit/s or higher | ### Network Requirements * The internet connection used for the livestream must be **stable, uninterrupted, and dedicated** exclusively to the livestream. This should be clarified and prepared well in advance. * A **technical contact person on site** is required. This person must be authorized and capable of configuring and testing the network according to the specified requirements. * To deliver an **HD livestream in 1080p at 25 fps (approx. 6 Mbit/s)**, a **minimum upload bandwidth of 10 Mbit/s** is required. * Always use **wired network connections (Ethernet)**. **Wi-Fi connections are strongly discouraged.** *** ### Firewall The following ports must be accessible from the streaming location. #### RTMP * **Ports:** TCP 1935, 80 (443 using RTMPS) #### SRT * **Ports:**\ An individual port is defined per livestream *** ### Internet Connection The maximum upload bandwidth of your internet connection directly impacts the **stability, resolution, and bitrate** of the incoming signal. You can test your upload bandwidth using the following services: * * * #### Bandwidth Recommendation * Use **no more than two-thirds (≈ 66%)** of the upload bandwidth specified by your Internet Service Provider (ISP). * Ensure that **no other users or applications** are using the same connection during the livestream. * If the connection is **not dedicated**, the full upload bandwidth may not be available consistently. # Live-Clipping Live Clipping allows you to create video clips from an active or previous livestream and export them directly to an on-demand project in 3Q. {% hint style="info" %} Live Clipping is available when **Timeshift** is enabled for a livestream. With Timeshift, the stream is temporarily available while it is still running, which makes it possible to select a specific time range and export it as a separate on-demand video. {% endhint %} This feature is useful for creating highlights, short segments, or individual clips from a live event without waiting for the full livestream recording to be processed.
*** ### Accessing Live Clipping Live Clipping can be accessed from the livestream’s control center. To open Live Clipping: 1. Open the desired livestream project. 2. Make sure **Timeshift** is enabled. 3. Open the **Timeshift & Clipping** panel. 4. Select a live or historical timeshift entry. 5. Click the clipping icon to create a new clip. The **Create Clip** panel opens on the right side of the screen. *** ### Timeshift & Clipping Panel The **Timeshift & Clipping** panel shows available live and historical timeshift recordings. The panel is divided into the following sections: * **Live**\ Shows the currently available live timeshift stream. * **History**\ Shows previous timeshift sessions or recorded livestream segments. Each entry displays information such as the resolution, duration, stream status, date, and time. Users can select an available entry and define the section that should be exported as a clip. *** ### Selecting a Clip Range After opening the clipping interface, the video preview and timeline are displayed. The timeline allows users to define the start and end point of the clip. Users can: * Move the start marker * Move the end marker * Preview the selected section * Adjust the clip range before export The selected time range determines which part of the livestream will be exported to the on-demand project. For more precise clipping, use the preview player to review the selected segment before saving. *** ### Creating a Clip To create a new clip: 1. Open the **Timeshift & Clipping** panel. 2. Select the live or historical timeshift entry. 3. Define the desired start and end time in the timeline. 4. Choose the **Target Project**. 5. Enter a **Title** for the new clip. 6. Select the export method. 7. Click **Save**. After saving, the selected section is exported as a new video in the selected on-demand project. *** ### Target Project The **Target Project** defines where the exported clip will be created. Only on-demand projects can be selected as target projects. After the export is complete, the new clip appears as a video in the selected on-demand project and can be managed like any other on-demand video in 3Q. *** ### Title The **Title** field defines the name of the exported clip. Choose a clear and descriptive title, especially when creating multiple clips from the same livestream. Example titles include: * Event Opening * Keynote Highlight * Interview Segment * Product Demo Clip * Q\&A Section *** ### Export Options When creating a clip, users can choose between two export options. #### Complete Encoding **Complete Encoding** creates a fully encoded new video from the selected clip range. This option may take longer, but can provide better quality and compatibility. Use Complete Encoding when the clip should be prepared as a regular on-demand video for publishing, distribution, or further processing. #### Simple Transmuxing **Simple Transmuxing** creates the clip faster by repackaging the selected stream segment. This option is faster, but may result in reduced compatibility or quality depending on the source stream and target workflow. Use Simple Transmuxing when speed is more important than full re-encoding. *** ### Export Entirely The **Export Entirely** option exports the full available timeshift period as a new video. When this option is enabled, the entire available time range is used and no manual start or end selection is required. This is useful when the complete livestream segment should be transferred to an on-demand project. *** ### Typical Use Cases Live Clipping can be used for many livestream workflows, for example: * Creating highlight clips during a live event * Exporting a speaker segment or presentation * Saving individual sessions from a longer livestream * Publishing short clips shortly after they happen * Creating on-demand videos from selected livestream sections * Reusing parts of a livestream for internal or external communication *** ### Notes Live Clipping requires Timeshift to be enabled for the livestream. The available clipping range depends on the configured Timeshift duration and the currently available stream history. Clips are exported to on-demand projects and are then processed as on-demand videos. Processing time may vary depending on the selected export option, clip length, source quality, and account configuration. # Live-Chat The **Live Chat** feature allows viewers to submit comments during a livestream. Comments can be displayed in the player interface and managed directly from the livestream control center. Live Chat is useful for interactive livestream formats such as townhalls, webinars, conferences, Q\&A sessions, presentations, or internal events. From the livestream control center, users can: * View incoming comments * Add comments manually * Reply to viewer comments * Edit comments * Delete individual comments * Delete all comments * Activate or deactivate comments * Automatically activate new comments * Export the complete comment list * Configure notification settings for comments *** ### Accessing Live Chat
Live Chat is managed from the livestream control center. To access the Live Chat area: 1. Open **Projects** in the main navigation. 2. Open the desired livestream project. 3. Go to the livestream control center. 4. Open or review the **Comments** area. The Comments area is displayed next to the live player and provides all moderation and management tools for the livestream chat. *** ### Comments Area The **Comments** area shows all submitted livestream comments. Each comment can display: * Name of the commenter * Date and time * Comment text * Replies * Visibility status * Available moderation actions Users can search comments, add new comments, export the comment list, delete comments, and manage visibility. *** ### Adding a Comment Users can add a comment manually from the control center. To add a comment: 1. Click **Add Comment**. 2. Enter the required comment information. 3. Save the comment. Manually added comments can be useful for moderation, testing, editorial input, or posting official messages during a live event. *** ### Viewer Comments in the Player
When Live Chat is enabled in the player, viewers can submit comments directly from the livestream player interface. The player displays the comment panel beside the video. Viewers can enter their name and comment text, then submit the comment. Depending on the moderation settings, comments may appear immediately or require activation before they become publicly visible. *** ### Automatically Activate New Comments The **Automatically Activate New Comments** option controls whether new viewer comments are made visible automatically. When this option is enabled, new comments become visible without manual approval. When this option is disabled, new comments can be reviewed and activated manually by a moderator. Use manual activation when comments should be moderated before publication, for example for public events, compliance-sensitive livestreams, or large audiences. *** ### Activating and Deactivating Comments Each comment can be activated or deactivated. * **Activated comments** are visible to viewers in the player. * **Deactivated comments** are hidden from viewers but remain available in the control center. This allows moderators to hide inappropriate, outdated, duplicate, or irrelevant comments without deleting them. *** ### Replying to Comments Moderators can reply to viewer comments from the control center. To reply to a comment: 1. Select the reply action on the comment. 2. Enter a **Name**. 3. Enter the reply text. 4. Choose whether the reply should be publicly visible. 5. Save the reply. Replies can be used to answer questions, provide additional information, or respond officially during a livestream. If the reply is marked as publicly visible, it can be shown in the player comment panel. *** ### Editing Comments Existing comments can be edited from the control center. Use the edit action to update the text or correct a comment. Editing is useful for: * Correcting spelling mistakes * Removing sensitive information * Adjusting official responses * Cleaning up comments before publication *** ### Deleting Comments Comments can be deleted individually. Use the delete action on a comment to remove it from the comment list. This is useful for removing comments that should no longer be stored or displayed. Depending on the moderation workflow, deactivating a comment may be preferable if the comment should be hidden but retained for reference. *** ### Deleting All Comments The **Delete All Comments** action removes all comments from the livestream. Use this action carefully, especially during or after a live event. Typical use cases include: * Clearing test comments before an event starts * Resetting the chat for a new session * Removing all comments after a rehearsal *** ### Exporting Comments The **Export Complete List** action exports all comments from the livestream. This is useful for: * Archiving audience questions * Preparing follow-up communication * Reviewing feedback after an event * Documenting Q\&A sessions * Sharing comments with event organizers or moderators The export includes the available comment information and can be used for further processing outside the platform. *** ### Notification Settings The **Notification Settings** action allows users to configure notifications for comment-related activity. This can be useful when moderators or event teams should be informed about new comments or important chat activity. The available notification options may depend on the account configuration and enabled modules. *** ### Live Chat Moderation Workflow A typical moderated live chat workflow can look like this: 1. Disable automatic activation before the event. 2. Viewers submit comments through the player. 3. Moderators review incoming comments in the control center. 4. Suitable comments are activated. 5. Moderators reply to selected questions. 6. Public replies appear in the player if marked as visible. 7. After the event, comments are exported for documentation or follow-up. For smaller internal events, automatic activation can be enabled so that new comments appear immediately. *** ### Typical Use Cases Live Chat can be used for different livestream formats, for example: * Audience questions during webinars * Interactive townhall sessions * Internal company events * Live Q\&A sessions * Moderated panel discussions * Event feedback collection * Support or training livestreams * Public livestream interaction *** ### Notes Live Chat is available for livestream projects, depending on account configuration and user permissions. The public visibility of comments depends on the activation status and moderation settings. Before using Live Chat in a production event, it is recommended to test the player integration, comment submission, moderation actions, and export workflow. # E-CDN for Livestreaming The **E-CDN for Livestreaming** feature allows livestreams to be distributed more efficiently within corporate networks. An eCDN, or Enterprise Content Delivery Network, helps reduce network load by distributing livestream data inside the company network instead of having every viewer request the full stream directly from the external CDN. This is especially useful for livestreams with many viewers in the same organization, such as townhalls, internal conferences, trainings, or corporate events. 3Q supports eCDN integrations for Livestreaming, including provider-based enterprise delivery solutions such as Hive or Kollective, depending on the account configuration. From the livestream project settings, users can: * Select an eCDN provider for a livestream project * Enable optimized delivery for corporate networks * Reduce bandwidth usage during large internal livestreams * Improve livestream stability for high viewer numbers * Use eCDN delivery together with the 3Q Player *** ### Connecting E-CDN Provider
To configure an E-CDN Provider: 1. Open **Accounts** in the main navigation. 2. Navigate to [Partner & Services](/user-guide-new-ui/account/partners-and-services). 3. Open Connect Partners. 4. Select E-CDN Provider and insert the credentials. *** ### Configuring eCDN for a Livestream Project {% hint style="info" %} To use a E-CDN with a livestream project, you need to connect the Provider of your choice with our platform. You can find more information [here](/user-guide-new-ui/account/partners-and-services). {% endhint %} The eCDN provider is configured in the livestream project settings. To configure eCDN: 1. Open **Projects** in the main navigation. 2. Select the livestream project you want to configure. 3. Open the project **Settings**. 4. In the **General** tab, scroll to the **eCDN Provider** setting. 5. Select the configured eCDN provider. 6. Save the project settings. After saving, the livestream project uses the selected eCDN provider for supported playback workflows. *** ### When to use a E-CDN eCDN is recommended when many viewers access the same livestream from the same company network. Without eCDN, each viewer may request the livestream individually from the CDN. In large organizations, this can create high bandwidth usage at internet gateways, firewalls, proxies, or corporate network connections. With eCDN, livestream traffic can be distributed more efficiently inside the corporate network. This helps improve scalability and can reduce the load on the external network connection. Typical use cases include: * Company townhalls * Internal executive broadcasts * Employee livestreams * Training sessions * Corporate webinars * Internal product launches * Events with many viewers in offices or shared networks *** ### E-CDN Provider The **E-CDN Provider** setting defines which enterprise delivery provider should be used for the livestream project. The available providers depend on the account configuration and booked services. Example providers may include: * Hive eCDN * Kollective eCDN * Other configured enterprise CDN providers If no eCDN provider is available in the project settings, the feature may not be enabled for the account or may require additional configuration. *** ### Preparing an eCDN Livestream Before using eCDN for a production livestream, the configuration should be tested with the intended network environment. A recommended preparation workflow is: 1. Configure the eCDN provider in the livestream project settings. 2. Embed or open the livestream with the intended player configuration. 3. Start a test livestream signal. 4. Test playback from the corporate network. 5. Confirm that the selected eCDN provider is active. 6. Test with multiple viewers or test clients if possible. 7. Review playback quality and network behavior. 8. Coordinate with the customer’s IT or network team if required. Testing is especially important for large events because corporate firewalls, proxies, VPNs, and network segmentation can affect eCDN behavior. *** ### Working with Corporate IT For enterprise livestreams, the customer’s IT or network team may need to be involved. Depending on the selected eCDN provider and company environment, IT teams may need to review: * Firewall rules * Proxy behavior * Browser support * WebRTC availability * Internal network routing * VPN behavior * Security policies * eCDN provider requirements The exact requirements depend on the selected eCDN provider. *** ### Difference between CDN and eCDN A regular CDN distributes content through external delivery infrastructure. Viewers request the livestream from CDN servers that are optimized for scalable internet delivery. An eCDN focuses on enterprise environments. It helps distribute the livestream inside the corporate network and reduces the amount of traffic that must pass through the company’s internet connection. In many livestream workflows, CDN and eCDN work together: * The CDN delivers the stream to the organization. * The eCDN optimizes distribution inside the organization’s network. * The 3Q player handles playback for the viewer. *** ### Notes eCDN availability depends on the account configuration, booked modules, selected provider, and user permissions. The eCDN provider must be configured before it can be selected in a livestream project. For production events with many viewers, always test the eCDN setup in advance with the target network environment. If playback issues occur in a corporate network, involve the customer’s IT or network team and verify the eCDN provider requirements. # On-Demand
The **Asset Management** area is the central workspace for managing all On-Demand media within a project. This is where video and audio files are uploaded, organized, reviewed, and maintained throughout their lifecycle. From this view, users can: * Upload new On-Demand content * Manage existing media assets * Edit editorial and technical metadata * Control publication status and availability * Organize content using categories, types, and tags The Asset Management interface provides both high-level visibility and detailed control, making it suitable for daily editorial work as well as large-scale media operations. ### Video List Overview The **Video List** displays all media assets available within the current project in a structured, tabular view. Each row represents a single asset and provides immediate access to its most relevant metadata and status information. By default, the list includes: * A thumbnail preview of the asset * The unique media ID * The asset title * Assigned categories * Duration * Available subtitle languages * Available audio tracks * Publication status * Creation date The list supports pagination and sorting, allowing efficient navigation even in large media libraries. {% hint style="info" %} The video list is fully customizable. Users can choose which columns and metadata fields are displayed, allowing the list to be tailored to individual workflows and preferences. This makes it easy to focus on the information that is most relevant for specific tasks such as content review, quality control, or publishing. {% endhint %} ### List Controls and Options At the top of the video list, several controls are available to refine and customize the view: * **Search** allows filtering assets by various metadata fields such as ID, title, description, tags, or uploader. * **Filters** enable narrowing results by status, category, and additional metadata attributes. * **View customization** lets users define which columns and attributes are displayed in the list. * **Bulk selection** via checkboxes enables batch operations on multiple assets at once. These options allow users to adapt the video list to different workflows, such as editorial review, content preparation, or operational monitoring. ### Editing Media
Clicking on a media item in the video list opens the **asset detail view**, which provides access to playback, metadata, and all configuration options for the selected asset. The asset detail view is divided into two main areas: * **Preview Player**\ The integrated player allows immediate playback of the asset for review and quality control. It reflects the currently available audio tracks, subtitles, and chapters, enabling quick validation without leaving the management interface. * **Properties Panel**\ The properties panel contains all editable settings for the asset and is organized into dedicated tabs, including: * **Metadata** and **Extended Metadata** for editorial information such as titles, descriptions, categories, tags, availability windows, and publication status * **Cover** for managing poster images and thumbnails * **Audio Tracks** for configuring multiple language versions, commentary tracks, and default playback behavior * **Subtitles** for managing subtitle languages and files * **Chapters** for defining navigation points within the video * **File Attachments** for related documents or additional assets Changes made in the properties panel are applied directly to the asset and affect how it is presented and delivered across players and platforms. This structured approach allows precise control over each media asset while keeping editorial, technical, and distribution-related settings clearly separated. #### File Actions in the Asset list
Each video in the on-demand file list provides quick actions directly from the row. These actions allow you to manage, update, process, and share individual videos without opening the full file details first. To open the action menu, move the cursor over a video entry and click the **three-dot menu** on the right side of the row. {% hint style="info" %} When you replace a file with a new version, copy it, or move it to another project, the embedded **playout ID** remains unchanged. This means existing embed codes continue to work. Direct streaming URLs, such as **HLS** or **DASH** URLs, may change when actions such as replacing a file, trimming, repackaging, copying, or moving are performed. If you use direct streaming URLs in your workflow, we recommend using [**webhooks**](/rest-api/webhooks) in the [**Alerts**](/rest-api/webhooks) module to be notified about relevant changes automatically. {% endhint %} Depending on your permissions and the file status, the following actions may be available:
ActionDescription
Current RecommendationsOpens the current recommendations for this video, if recommendations are enabled for the project.
Replace with New VersionUpload a new version of the video while keeping the existing file entry, metadata, and integrations.
TrimCut the video and create a shortened version based on the selected start and end points.
Schedule VoD-to-LiveSchedule the on-demand video to be played out as a livestream at a defined time.
Copy / MoveCopy or move the video to another project or content pool.
Re-encodeStart a new encoding process for the video. This can be useful if encoding settings have changed or if the file needs to be processed again.
RepackagingRepackage the existing video files, for example to update delivery formats without uploading the source file again.
DeleteDelete the video from the project.
#### Bulk Operations in the Asset-list
You can perform bulk operations on several assets at the same time. To do this, select one or more files in the asset list using the checkboxes on the left side of each row. As soon as at least one file is selected, a bulk action bar appears at the top of the list. The number of selected files is displayed on the left side of the bar. The following bulk operations are available:
OptionDescription
StatusChange the publication status of the selected files to Published, Unpublished, or Draft.
CategoryAssign one or more categories to the selected files.
TypeAssign a content type to the selected files.
PersonAdd or update people metadata for the selected files.
PlaylistAdd the selected files to one or more playlists.
MediaRSS ExportAdd the selected files to a MediaRSS export feed.
ActionsOpens additional bulk actions for the selected files, depending on your permissions and the enabled modules.
#### Metadata The **Metadata** tab contains the core editorial information of an asset.\ Here you define how the video is identified, described, and scheduled within the platform. Key options include: * **Title** and optional display titles * **Description**, which can be written manually or generated with AI assistance * **Categories** and **tags** for classification and discovery * **Availability windows** (available from / until) * **Release status** (e.g. draft, published) * **Recommendation behavior**, controlling whether the asset may appear in recommendations This information is used across players, APIs, and recommendation systems. *** #### Metadata (Extended) The **Metadata (Extended)** tab allows you to enrich the asset with additional contextual and technical information. Typical use cases: * Assigning **people** (e.g. contributors or protagonists) * Adding **geolocation data** (latitude/longitude) * Defining **country of production** and **source** * Setting **initial release dates** * Controlling distribution-related flags such as mobile publishing or ad availability These fields are optional but valuable for advanced workflows, editorial context, and integrations. *** #### Cover The **Cover** tab is used to manage the visual representation of the asset. Available options: * Select a **cover image** from existing video frames * Upload a **custom image** * Replace or update covers at any time The cover image is used in asset lists, players, and front-end applications, making it a key element for user engagement. *** #### Audio Tracks
In the **Audio Tracks** tab you can manage all audio versions associated with the video. Supported actions: * Define one or more **main audio tracks** * Add **additional language tracks** * Create **AI-generated audio tracks** from subtitles * Assign roles such as main track, commentary, or audio description * Set a **default audio track** for playback This enables multilingual delivery and accessibility use cases without duplicating video assets. *** #### Subtitles
The **Subtitles** tab provides full subtitle management. Features include: * Uploading subtitle files (e.g. SRT, VTT) * Managing multiple **subtitle languages** * Editing subtitles directly in a synchronized editor * Automatically **translating subtitles** into additional languages * Downloading existing subtitle files Subtitles can be used for accessibility, localization, and as a basis for AI audio generation. *** #### Chapters
The **Chapters** tab allows you to structure long-form video content into clearly defined segments, improving navigation and viewer orientation within the player. Chapters can be created and managed manually or generated automatically using AI. When using AI-based chapter generation, the system analyzes the available audio tracks and subtitles to propose meaningful chapter titles and timecodes. The maximum number of chapters can be configured before generation, allowing control over the level of detail. **Capabilities include:** * Creating, editing, and deleting chapters * Defining precise start times and descriptive titles * Automatically generating chapters using AI based on content analysis * Reviewing and adjusting AI-generated chapters before saving Chapters are displayed directly in the video player and enable viewers to jump to specific sections of the content. This is especially beneficial for documentaries, talk shows, sports analysis, and educational or informational formats. *** #### File Attachments The **File Attachments** tab lets you associate additional files with the asset. Typical attachments include: * Editorial documents * PDFs or supplementary material * Production-related files Attachments are stored alongside the video and can be accessed by users in the video player if enabled in the player configuration. ### Embedding and Sharing The **Playout and Sharing** section allows you to publish, embed, and distribute your media assets using different delivery and integration options. It is designed to support both quick embeds and fully customized frontend integrations.
#### Recommended Integration: Web SDK {% hint style="info" %} For most use cases, we strongly recommend using the [**3Q Player Web SDK**](https://player.docs.3q.video/) for embedding videos into customer websites or applications. {% endhint %} The [Web SDK](https://player.docs.3qsdn.com/) enables a dynamic and flexible integration into the customer’s frontend and ensures: * Full compatibility with all platform features (subtitles, audio tracks, chapters, analytics, DRM, etc.) * Automatic handling of adaptive streaming (HLS/DASH) * Centralized updates and player configuration via playouts * Consistent user experience across devices and browsers This approach is ideal for **production environments** and **scalable** deployments. #### Embed Options Within **Playout Management**, multiple embed options are available depending on the integration requirements: * **JavaScript Embed Code**\ Recommended for dynamic websites and applications. Provides full player functionality and configuration via the selected playout. * **iFrame Embed Code**\ Suitable for simple integrations where minimal configuration is required. * **Direct Player URL / oEmbed Link**\ Useful for quick previews, CMS integrations, or sharing content internally. Optionally, **JSON-LD metadata** can be included to improve SEO and enable search engines to better understand the media content. {% hint style="info" %} **Note:** JSON-LD is a form of structured data designed for search engines and AI systems to better understand and interpret media content. In most cases, JSON-LD metadata is automatically injected by the 3Q video player when enabled in the player settings, making manual integration unnecessary. This option is therefore only required for advanced or custom SEO setups where structured data is managed outside of the player. {% endhint %} #### Streaming URLs (Custom Player Support) Customers who prefer to use their **own video player** can do so by accessing the **Streaming URLs**. The platform provides ready-to-use streaming endpoints for: * HLS (H.264, HEVC, or mixed) * MPEG-DASH (H.264, HEVC, or mixed) These URLs can be integrated into third-party or proprietary players, allowing full control over the playback experience while still benefiting from the platform’s encoding and delivery infrastructure. #### File Downloads In the **File Downloads** section, users can download media files directly. Available downloads include: * All generated renditions (e.g. 1080p, 720p, 480p, H.264 and HEVC) * Audio-only tracks (if available) * The original source file (if permitted) This is especially useful for archiving, offline usage, editorial workflows, or external distribution. # General Settings ### Creating and Configuring an On-Demand Project This chapter describes how to create and configure an **On-Demand (Video on Demand) project** in the 3Q Platform. An On-Demand project is used to upload, encode, manage, and publish video content that can be accessed at any time by end users. *** ### Creating an On-Demand Project
1. Open **Projects** from the main navigation. 2. Select the **On-Demand** tab. 3. Click **Create Project**, or select an existing On-Demand project to edit its configuration. Once a project is created, all settings are managed through the **Project Settings** panel. *** ### Project Settings – General Open the project and access **Project Settings → General**. #### General Configuration * **Title**\ Defines the project name as shown in the platform. * **Group**\ Assigns the project to a project group (for example, *Default*). * **Project Image (optional)**\ A visual identifier used in the project overview. * **Default Metadata Language**\ Sets the default language for metadata fields. * **Default Publication Status**\ Defines the initial publication state of uploaded media: * *Unpublished* (recommended): content must be explicitly published. * *Published*: content becomes publicly available immediately after upload. *** ### Limiting Available Categories Navigate to **Project Settings → Advanced Settings**. * **Limit Categories**\ Allows restricting which categories are available within this project.\ This is useful when a project should only support a predefined subset of categories. Categories are fully configurable and project-specific. *** ### Metadata Configuration Open **Metadata Settings** for the project. #### Metadata Rules Metadata rules define which fields are mandatory or visible. Common mandatory or visible fields include: * Title * Description * Categories * Typesd * Tags #### Additional Metadata Fields Under **Additional Metadata**, custom fields can be added: * Input Field * Numeric Input * Selection * Multiple Selection * Checkbox * URL * Email Typical use cases: * Editorial flags * Rights information * Source identifiers * Platform-specific control flags Both **Categories** and **Types** are fully configurable and can be defined according to editorial or organizational requirements. *** ### Tag Management The **Tag Management** view allows maintaining a list of reusable tags.\ Tags can later be assigned to media items for search and filtering purposes. # Encoding Settings ### General Open **Encoding Settings** for the project. #### Encoding Activation * **Activate Encoding ****(Must have)**\ Enables automatic encoding after media upload. * **Default Source File Language**\ Defines the language of the original audio track. #### Subtitles and Language Processing * **Generate Subtitles Automatically**\ Automatically creates subtitles from the source audio. * **Automatically Translated Subtitles**\ Select the target languages for automatic subtitle translation. * **Automatic Dubbing**\ Optional. Can be enabled if dubbing is required. *** ### Output Formats
Under **Encoding Settings → Output Formats**, define which renditions are generated during encoding. {% hint style="info" %} The platform provides a **preconfigured default setup** that covers the requirements of most standard use cases. This default configuration is suitable for typical editorial, corporate, and informational video content and does not require adjustment in most scenarios. {% endhint %} A commonly used setup includes the following resolutions: * 1080p * 720p * 480p * 360p * 240p Higher resolutions such as **1440p** or **2160p** can be enabled if required, but should only be activated when necessary, as they increase encoding time, storage usage, and delivery bandwidth. {% hint style="info" %} **H.264** and other output formats can be combined. Mixed codec formats are created automacially and merged as combined streaming format in HLS and DASH. {% endhint %} **Custom Encoding Profiles** For specialized content types, such as **sports, live recordings, or high-motion footage**, the default settings can be adapted: * Target video bitrate can be adjusted per rendition * Frame rates such as **50 fps or 60 fps** can be configured (We recommend to use the default setting passthrough) * Audio bitrate, sample rate, and channel layout can be modified * Video profile and codec settings can be fine-tuned These options allow customers to optimize output quality for specific content characteristics while maintaining full control over resource usage and playback compatibility. *** ### Advanced Options Under **Encoding Settings → Advanced Settings**: * **CMAF Packaging (Fragmented MP4)**\ Recommended for modern HLS and DASH delivery. (Default in the near future.) * **Cover Creation Control**\ Automatically generates multiple thumbnails at defined intervals. * **Normalize Audio**\ Optional loudness normalization. * **Include Audio-only Version**\ Adds an audio-only track to the streaming manifest. *** ### Watermark Configuration Under **Encoding Settings → Watermark**: 1. Upload a watermark image (PNG with transparency recommended). 2. Enable **Use Watermarks**. 3. Select position and transparency level. Watermarks are applied during encoding. ### Glossary
The **AI Glossary** feature allows you to improve the accuracy of automatically generated subtitles and AI-based audio processing by providing a custom pronunciation and terminology reference. An AI glossary can be uploaded in **CSV** or **JSON** format and defines specific terms, names, abbreviations, or technical expressions, along with their intended pronunciation. This is especially useful for: * Proper names (e.g. people, brands, locations) * Technical terminology * Foreign words or abbreviations * Domain-specific vocabulary **Uploading an AI Glossary** To upload a glossary: 1. Open **Encoding Settings → AI Glossary** 2. Select a glossary file in **CSV** or **JSON** format 3. Specify the language the glossary applies to 4. Upload the file Once uploaded, the glossary is automatically applied during subtitle generation and AI-driven language processing for this project. **Supported File Formats** **CSV format**\ Each entry consists of a term and one or more pronunciation examples. **JSON format**\ Allows structured definitions with multiple pronunciation variants per term. Example structures are displayed directly in the interface to ensure correct formatting. **Scope and Behavior** * The glossary applies **project-wide** to all newly processed media * Existing subtitles are not retroactively updated * Multiple glossary entries can be maintained and updated over time * If no glossary is uploaded, standard AI language processing is used Using an AI glossary helps ensure consistent terminology and significantly improves subtitle quality for specialized or branded content. # Content Protection With **Content Protection**, you can secure the delivery of content when using our player, direct streaming URLs, or download URLs. This option is enabled by default and when you integrate our player, token generation for content protection is handled automatically. Only if you do not use our player - for example, when using progressive download or a third-party video player - you need to generate the access tokens yourself. You can enable or disable this feature in **Project Settings → Content Protection** for the desired project. Once activated, all content delivered through our video player will automatically be protected by this mechanism. Content Protection secures media delivery by **signing and tokenizing every video chunk** that is requested during playback or download. Each request is validated against a time-limited token before the chunk is delivered. If the token is missing, invalid, or expired, access to the requested video segment is denied. This prevents unauthorized access and sharing of direct streaming or download URLs. *** ### Using a custom player with Content protection {% hint style="info" %} A new token must be generated for every request. Reusing tokens is not supported and may result in access being denied. {% endhint %} #### Generate a token (PHP example) ```php // token.php function generateToken() { $expires = time() + 600; // Token validity: current time + 10 minutes $_user_agent = ''; // User Agent (required). $project_key = ''; // Your private project key (required). $md5 = md5($expires . $project_key . $_user_agent, false); return $md5 . '/' . $expires; } ``` #### Generate the streaming URL ``` https://sdn-global-streaming-cache.3qsdn.com/s/{generateToken()}/3144/files/17/11/766971/3144-F98zkwncqTR7BMg2.ism/manifest.m3u8?format=hls&mime=mp4&source=html5 ``` ### Adding DRM {% hint style="info" %} To use DRM, you must connect your Castlabs Account under [Partner & Services](/user-guide-new-ui/account/partners-and-services). {% endhint %} **DRM protection** can be used to protect premium or restricted video content against unauthorized playback and redistribution. DRM stands for **Digital Rights Management**. It adds an additional security layer to the playback workflow by ensuring that protected content can only be played in supported players and environments after a valid license has been requested. 3Q currently supports the following DRM technologies: * **Google Widevine** * **Apple FairPlay** * **Microsoft PlayReady** These DRM systems cover the most common playback environments, including modern desktop browsers, Android devices, iOS and iPadOS devices, Apple Safari, smart TVs, and other supported playback devices. *** #### When to Use DRM DRM protection is recommended for content that requires a higher level of access control than standard token protection or publication settings. Typical use cases include: * Premium video content * Paid content * Licensed movies or series * Internal confidential videos * Partner-restricted content * Content with contractual protection requirements * Content that must not be downloadable or freely redistributed *** # Players
Players define **how media is presented and played back**. They control the UI, behavior, features, security, and sharing options for videos, playlists, podcasts, and live streams. {% hint style="info" %} Changes made to an existing player configuration are applied automatically wherever this player is already embedded. You do not need to copy or replace the embed code again after updating player settings. {% endhint %} From the **Players** module, you can centrally manage all player configurations. Using our [**Player SDK**](broken://pages/x4eD1BmEFwkorOtoo10X) is recommended when working with a large number of videos or when you want to tightly integrate the player with your frontend and control it via methods and events. The player automatically fetches the configured settings from our backend. If needed, you can override specific parameters by passing them to the SDK during initialization. *** ### **Player overview** The **Players** view lists all available players with: * **Title** * **Project scope**: Global or project-specific * **Description** * **Creation date** You can search, sort, and switch between **All Players**, **Global Players**, and **Project-Specific Players**. *** **Create & manage players** Click **Create Player** to define a new player configuration. Players can be: * **Global** – available across all projects * **Project-specific** – restricted to a single project One player can be marked as the **default player** for a project or globally. The player name is shown in the player overview and in the playout management of projects. The optional description helps identify the purpose of the player configuration. {% hint style="info" %} If a player is assigned to a specific project, it is used for that project’s playouts. If no dedicated project-specific player is assigned, the global or default player configuration is used. {% endhint %} *** #### Player settings Player configuration is organized into clear sections.
**Basics** Define general metadata and availability: * **Title & Description** * **UI language** * **Project availability** * **Default player** selection *** **Settings** Control playback behavior and appearance: * **Accent color** * **Autoplay options**: muted, scroll-based, etc. * **Initial audio & subtitle language** * **Initial video quality** * Metadata display preferences * End-of-playback behavior: loop, recommendations, continuous playback *** ### **Features** {% hint style="info" %} Some player settings only become effective if the corresponding module has been activated for the account. This applies, for example, to playlists, podcasts, advertising, live comments, Geo/IP blocking, and other optional features. {% endhint %}
Feature / settingDescription
More Layout SettingsOpens advanced UI detail settings for customizing the player layout.
Prefer Container MetadataFor playlists and podcasts, the player displays metadata from the active container instead of the active media element.
Collect AnalyticsEnables GDPR-compliant analytics collection for media playback in real time.
Trick-playAllows users to change the playback speed for on-demand media.
Transcript SearchEnables searchable transcripts. Users can search for text passages and jump directly to the matching playback position.
Picture-in-PictureAllows the player to continue playback in a small floating window, if supported by the browser.
Pop-out / Sticky PlaybackKeeps the player visible while the user scrolls by anchoring it on the page.
AdvertisingEnables advertising support for the player. Advertising rules are managed separately.
Sharing ServicesDefines which sharing options are available in the player, such as Facebook, LinkedIn, Reddit, WhatsApp, Bluesky, or others.
Embed CodeAllows users to generate an embed code directly from the player interface.
Disable TimeshiftPrevents users from scrolling back during a livestream, even if the stream itself supports timeshift.
Live CommentsEnables comments on live streams and displays comments from users.
Live ReactionsAllows users to send live reactions during an active livestream. Reactions can be disabled or shown in the sidebar or control bar.
Playlist / Podcast SettingsContains settings for playlist and podcast playback behavior.
Show Container Elements on LoadOpens the list of active playlist or podcast elements when the container is loaded.
Maximum Available ItemsLimits the number of playlist or podcast items available in the player.
Automatic ShuffleRandomizes the playlist order each time the list is loaded.
Reel ModeDisplays playlist videos as reels and allows users to switch between active media items.
Show Playlist SearchEnables search within playlist or podcast elements during playback.
Use Categories as FiltersUses assigned categories as filters inside the playlist or podcast element list.
Muted StartForces playback to always start muted, regardless of whether the user previously enabled audio manually.
Force Audio PlayerUses the player as an audio player, even when video content is played.
SEO OptimizationAdds microdata and JSON-LD metadata to make media information visible to search engines.
Download of Current Media FileControls whether users can download the current media file, and whether downloads use the source file, a rendition, or both.
Remote PlaybackEnables Chromecast or AirPlay playback if supported by the user’s device.
*** ### **Security** {% hint style="info" %} We recommend protecting your player to ensure that only authorized users can access your content. For more information on integrating the player with token protection, please refer to our player documentation. {% endhint %} Protect your content with: * **Token protection** * **Domain restrictions** * **AES encryption** * **DRM** * **Playback preview limits** * **Geo/IP blocking templates**, if the module is enabled *** #### Visual & playback enhancements **Badges** Badges are overlays permanently displayed on the player. You can: * Upload a badge image * Choose the badge position * Add titles or links * Use badges for branding, labels, or visual markers *** ### # Playlists
Playlists allow you to group and organize media files into structured collections. A playlist can contain video files, audio files, or a mix of both, depending on the selected playlist type. Playlists can be used for manual content collections, automated content feeds, carousel layouts, reel-style video experiences, or embedded playlist players. From the Playlists area, users can: * Create video, audio, or mixed playlists * Add files manually to a playlist * Create automatic playlists based on metadata and filters * Configure release settings * Manage playlist elements * Generate playout and embed codes * Use playlists for video carousels and vertical reel players The Playlists section is available from the main navigation under **Playlists**. *** ### Playlist Overview The playlist overview displays all playlists available in the account. Each row represents one playlist and includes the most relevant information: * Playlist thumbnail * Playlist ID * Playlist title * Source project * Number of elements * Release status * Playout IDs * Creation date The overview can be filtered by playlist content type: * **All Playlists** * **Video** * **Audio** * **Mixed** Additional filters are available for: * **Status** * **Scope** A search field can be used to find playlists by title or related metadata. *** ### Playlist Types When creating a playlist, users can define the content type of the playlist. Available options are: * **Video**\ The playlist contains video files. * **Audio**\ The playlist contains audio files. * **Mixed**\ The playlist can contain both video and audio files. The selected content type determines which files can be added to the playlist. *** ### Creating a Playlist To create a new playlist: 1. Open **Playlists** in the main navigation. 2. Click **Create Playlist**. 3. The **Create Playlist** side panel opens. 4. In the **Basics** tab, select or upload a playlist image. 5. Enter a **Title**. 6. Select the playlist content type: * **Video** * **Audio** * **Mixed** 7. Optionally select a **Source Project**. 8. Choose whether the playlist should be created manually or as an automatic playlist. 9. Optionally add a **Description**. 10. Open the **Release** tab. 11. Define the release status and availability period. 12. Save the playlist. After saving, the playlist appears in the playlist overview. *** ### Playlist Image A playlist image can be added in the **Basics** tab. Supported image formats include: * AVIF * BMP * GIF * JPEG * JPG * PNG * WEBP The image can be used as a visual representation of the playlist in players, carousel layouts, or other frontend integrations. *** ### Title The **Title** is the visible name of the playlist. Choose a clear and descriptive title, especially when playlists are used for public playouts, carousels, or automated content feeds. Example titles: * Product Videos * Latest News * Carousel Demo * Reel Player Playlist * Webinar Collection * Featured Videos *** ### Source Project The **Source Project** defines where playlist elements can be selected from. If a source project is defined, only files from that project can be added to the playlist. If no source project is selected, files from all available projects can be used as a source. This setting is especially useful when playlists should be limited to a specific content pool or editorial workflow. *** ### Manual Playlists Manual playlists are managed by adding and arranging files directly.
Users can: * Add files to the playlist * Remove files from the playlist * Change the order of elements * Review the number of elements * Review the total playlist duration Manual playlists are useful when the exact content and order should be controlled by an editor. Typical use cases include: * Curated video collections * Training playlists * Event playlists * Product video selections * Editorially managed playlists *** ### Automatic Playlists Automatic playlists update themselves regularly in the background based on rules and filters defined by the user.
Instead of adding files manually, users define which content should be included. The system then updates the playlist automatically when matching files are added, changed, or removed. Automatic playlists are especially useful for dynamic content experiences such as: * Video carousels * Vertical video or reel players * Latest videos * News playlists * Topic-based playlists * Category-based collections * Continuously updated content feeds For example, an automatic playlist can be configured to show the latest 100 videos from a specific source project, filtered by category, type, aspect ratio, people, or metadata fields. *** ### Automatic Playlist Configuration Automatic playlist rules can be configured in the **Elements and Configuration** area. The configuration defines which files are included in the playlist and in which order they appear. Available filter options may include: * **Categories** * **Types** * **People** * **Aspect Ratio** * Additional metadata fields such as: * Title * Description * Display Title * Display Title Second Line * Tags * Program * Series The available filter fields may depend on the account configuration, metadata setup, and project structure. *** ### Aspect Ratio Filtering Automatic playlists can be filtered by aspect ratio. This is especially useful for frontend experiences that require a specific format. For example: * **Landscape 16:9** for standard video players or carousels * **Portrait / vertical formats** for reel-style players * Other aspect ratios depending on the available content and player configuration By filtering playlists by aspect ratio, users can make sure that only suitable videos are used in the intended playout experience. *** ### Sorting and Order Automatic playlists can be sorted by selected metadata fields. For example, playlists can be sorted by: * Creation date * Title * Other available metadata fields The order can be set to: * **Ascending** * **Descending** For dynamic playlists, descending order by creation date is commonly used to show the newest content first. *** ### Number of Elements Automatic playlists can be limited to a defined number of elements. This allows users to control how many videos are included in a playlist, carousel, or reel player. For example: * A carousel may show the latest 10 videos. * A reel player may use the latest 50 vertical videos. * A news playlist may contain the latest 100 clips. Limiting the number of elements helps keep playlists focused and improves performance in frontend integrations. *** ### Video Carousel Use Case Playlists can be used as the content source for video carousel experiences. A video carousel displays multiple videos in a scrollable or swipeable layout and is often used to present selected or automatically updated content collections. Automatic playlists are especially useful for carousels because they can keep the content up to date without manual playlist editing. Example carousel workflows: * Latest videos carousel * Featured content carousel * Category-based carousel * News carousel * Product video carousel * Project-specific carousel A carousel playlist can be configured with filters such as category, type, people, aspect ratio, or metadata fields. The playlist then provides the matching elements to the carousel playout. *** ### Vertical Video and Reel Player Use Case Playlists can also be used for vertical video and reel-style playback experiences. A reel player is designed for short-form or vertical content and usually benefits from automatically updated playlists. For this workflow, users can create an automatic playlist that only includes videos matching the required vertical format or metadata rules. Example reel player workflows: * Vertical news clips * Social-style short videos * Mobile-first video feeds * Highlight clips * Short product videos * Event snippets * Automatically updated reel collections For best results, use aspect ratio filters and metadata filters to make sure that only suitable vertical videos are included in the playlist. *** ### Release Settings The **Release** tab controls the publication status and availability period of the playlist. #### Release Status The release status defines whether the playlist is available for use. Common release states include: * **Published** * Other available statuses depending on the account configuration Only published playlists are generally intended for public playback or integration. #### Available From The **Available from** field defines when the playlist becomes available. This can be used to schedule playlist publication. #### Available Until The **Available until** field defines when the playlist is no longer available. This can be used for temporary campaigns, events, or licensed content windows. *** ### Managing Playlist Elements The **Elements and Configuration** area shows the current playlist elements. For each playlist, users can review: * Number of elements * Total duration * Individual playlist items * Thumbnail * Title * Creation date * Duration For manual playlists, files can be added, removed, and reordered. For automatic playlists, the element list is generated based on the configured rules. Users can update the configuration to change which files appear in the playlist. *** ### Adding Files to a Manual Playlist To add files to a manual playlist: 1. Open the playlist. 2. Open **Edit Elements**. 3. Click **Add Files**. 4. Search for the files you want to add. 5. Select the desired files. 6. Add them to the playlist. After adding files, they appear in the playlist element list and can be reordered or removed. *** ### Playout and Sharing The **Playout and Sharing** area provides the embed and sharing options for a playlist. Users can select an available playout and copy the required integration code. Available sharing options may include: * Embed code * JavaScript integration * Direct link * Other integration formats depending on the playout configuration The selected playout determines how the playlist is presented to viewers. This is where playlists can be integrated into websites, portals, applications, or external systems. *** ### Playlist Playouts Playlist playouts define how a playlist is rendered and played back. Depending on the configuration, a playlist can be used for different playback experiences, such as: * Standard playlist player * Video carousel * Reel player * Embedded playlist * Custom frontend integration The available playouts depend on the account configuration and player setup. *** ### Start Playback at a Specific Time In the sharing options, users can define a start time for playback. This allows the embedded playlist player to start playback at a specific timestamp. This option is useful when a playlist should open at a particular point in the first item or when a predefined playback position is needed for sharing. *** ### Integration Options When generating embed codes, users can choose how the playlist player should be integrated into a website. Available integration options may include: * Width and height defined directly in the iframe code * Dynamic width with fixed aspect ratio * Dimensions and aspect ratio controlled by a container around the iframe These options help adapt the playlist player to different website layouts and responsive frontend requirements. *** ### Lazy Loading The **Use Lazy Loading** option can be enabled for playlist embeds. Lazy loading ensures that the browser only loads the playlist player when it is actually needed, for example when the iframe scrolls into the visible area of the page. This can improve page performance, especially when multiple players or playlist embeds are used on the same page. *** ### Typical Use Cases Playlists can be used for many different workflows, for example: * Creating curated video collections * Grouping audio or mixed media content * Publishing a series of related videos * Creating automatically updated latest-video feeds * Providing content for a video carousel * Providing vertical content for a reel player * Embedding playlist players on websites * Organizing videos by category, type, person, or metadata * Creating project-specific content selections *** ### Notes Automatic playlists are used for dynamic playlist experiences such as video carousels and vertical video or reel players. The availability of playlist features, playouts, filters, and integration options may depend on the account configuration, enabled modules, and user permissions. For vertical video and reel player workflows, make sure that the playlist configuration matches the intended player layout, especially regarding aspect ratio, sorting, and number of elements. # Podcasts The **Podcasts** module allows you to create, manage, organize, and publish audio or video podcasts. It covers everything from basic podcast setup to episode organization, seasons, playout, and sharing.
### Overview In the Podcasts module you can: * Create **audio or video podcasts** * Organize episodes into **seasons** * Manage **metadata and categories** * Configure **feed behavior** and ordering * Generate **embed codes and sharing options** * Control **playout and players** The main Podcasts view lists all existing podcasts and provides quick access to editing, playout, and sharing. *** ### Podcasts List View The list view shows all available podcasts with the following information: * **Preview Image** – Podcast cover image * **ID** – Unique podcast identifier * **Title** – Podcast name * **Source Project** – Linked project * **Categories** – Assigned podcast categories * **Episodes** – Number of episodes * **Status** – Publication status You can filter podcasts by **status** and **categories**, or search by title. *** ### Creating a Podcast Click **Add Podcast** to create a new podcast. #### Basics Required fields: * **Cover Image** – Supported formats: AVIF, BMP, GIF, JPEG, JPG, PNG, WEBP * **Title** – Podcast name * **Type** – Audio or Video * **Source Project** – Project providing the media * **Description** – Podcast description * **Release Status** – Draft or Published * **Language** – Podcast language Optional fields: * Subtitle * Author * Owner name and email * Website URL * Copyright notice * Explicit content flag #### Advanced Settings * **Feed Order** * Episodic (newest episodes first) * Serial (oldest episodes first) * **Categories** – Select one or more podcast categories *** ### Editing a Podcast Select a podcast and open **Edit Elements** to manage its structure. #### Episodes & Duration At the top of the editor you see: * **Episodes** – Total number of episodes * **Duration** – Combined runtime of all episodes *** ### Seasons Podcasts can be organized into **seasons**. * Each season contains one or more episodes * Seasons can be reordered * New seasons can be added at any time Typical use cases: * Grouping content by topic * Separating releases by year * Structuring courses or tutorial series *** ### Adding Episodes Click **Add Video Files** (or audio files depending on podcast type) to add new episodes. Each episode displays: * Thumbnail preview * Filename * Duration * Upload date Episodes can be moved between seasons. *** ### Playout & Sharing Open **Playout and Sharing** to configure how your podcast is delivered. #### Playout Management * Select an existing playout * Use the **default player** or create a custom playout #### Embed & Integration Options Available options include: * JavaScript embed code * Direct link * Iframe embed The generated embed code can be copied and used on external websites or platforms. # Analytics The **Analytics** section provides detailed insights into how content is viewed, accessed, and used across the account. It supports both high-level dashboards and detailed analysis views for playback performance, advertising, viewer environments, content usage, engagement, and charts. {% hint style="info" %} In the free version, only the Analytics dashboard is available. To access more detailed analytics, including extended views and statistics for each individual video, the **Analytics module** must be purchased and enabled for your account. {% endhint %} Analytics can be accessed from the main navigation under **Analytics**. The Analytics section is organized into the following tabs: * **Overview** * **Performance** * **Ads** * **Environment** * **Content Analysis** * **Engagement** * **Charts** The available data depends on the selected project scope, time range, filters, account configuration, and user permissions. *** ### Overview
The **Overview** tab provides a dashboard with the most important analytics data in one place. At the top of the dashboard, summary cards show key metrics for the selected time range, such as: * **Impressions** * **Playback Starts** * **Individual Users** * **Ad Requests** * **Ad Deliveries** * **Average Playback Time** * **Total Playback Time** Below the summary cards, the dashboard displays several charts at once. These can include playback starts, ad deliveries, total playback time, average playback time, device type overview, and country overview. Use the Overview tab to quickly understand account-wide or project-specific activity without opening each analytics view individually. *** ### Project Selection
The project selector defines which projects are included in the analytics view. Depending on permissions, users can select: * **All Projects** * **All On-Demand Projects** * **All Livestream Projects** * Individual on-demand projects * Individual livestream projects Use **All Projects** for an account-wide view. Select a specific project when you want to analyze one content pool, livestream project, campaign, customer portal, or event workflow. *** ### Time Range Analytics can be viewed for predefined time ranges or for a custom period. Available options include: * **T** – Today * **1D** – One day * **1W** – One week * **1M** – One month * **3M** – Three months * **1Y** – One year * Custom date range A custom time range can be selected with the calendar option. The selected time range affects all visible charts and metrics. *** ### Performance
The **Performance** tab focuses on playback-related metrics. The metric selector includes views such as: * **Playback Starts** * **Average Playback Time** * **Total Playback Time** * **Playback Progress** * **Renditions** * **Audio Track Languages** * **Subtitle Languages** * **Playback Start Conditions** The selected metric is shown as a chart for the chosen project scope and time range. #### Playback Starts The **Playback Starts** view shows how often playback was started. It can also display related values such as impressions and individual users. This helps compare how often content was displayed, how often users started playback, and how many unique users interacted with the content. #### Average Playback Time The **Average Playback Time** view shows how long users watched content on average. This helps evaluate whether viewers remain engaged after starting playback. #### Total Playback Time The **Total Playback Time** view shows the accumulated viewing time for the selected scope and time range. This is useful for reporting total watch time across projects, campaigns, events, or publication periods. #### Playback Progress The **Playback Progress** view shows how far viewers progressed through the content. This is especially useful for long-form videos, webinars, trainings, event recordings, and editorial content. #### Renditions The **Renditions** view shows which video quality levels were used during playback. This helps evaluate adaptive streaming behavior and whether viewers mainly consume lower, medium, or higher quality renditions. #### Audio Track and Subtitle Languages The **Audio Track Languages** and **Subtitle Languages** views show which audio and subtitle languages were used. These views are helpful for multilingual content, accessibility analysis, localization decisions, and translation workflows. #### Playback Start Conditions The **Playback Start Conditions** view shows how playback was started, for example manually or automatically, depending on the player configuration. This can help analyze how player behavior influences user interaction. *** ### Ads The **Ads** tab provides analytics for advertising-related activity. The screenshots show an **Ad Deliveries** view with values such as: * **Ad Requests** * **Ad Deliveries** * **Clicks** Use this tab to analyze whether ads are requested, whether they are delivered successfully, and whether viewers interact with them. This is useful for projects using advertising, monetization, or ad-related reporting. *** ### Environment The **Environment** tab provides insights into the technical and geographic context of viewers.
Available views include: * **Device Type Overview** * **Country Overview** * **Geo Heatmap** * **Domain Overview** * **Player Overview** * **Operating Systems Overview** * **Browser Overview** * **Screen Sizes** * **Integration Overview** These views help identify where viewers are located, which devices and browsers they use, on which domains content is played, and how the player is integrated. #### Geo Heatmap The **Geo Heatmap** displays viewer activity on a map. Users can zoom and navigate the map to inspect regional audience concentrations. #### Country Overview The **Country Overview** shows viewer activity grouped by country. Users can click a country to view additional regional details where available, for example a breakdown by federal state or region. #### Device Type Overview The **Device Type Overview** shows which device types were used for playback, such as desktop, smartphone, or tablet. This helps understand whether content is mainly consumed on desktop or mobile devices. #### Domain, Player, Browser, Operating System, Screen Size, and Integration Views Additional environment views help analyze where content is embedded, which player configurations are used, which browsers and operating systems viewers use, which screen sizes occur, and how content is integrated. *** ### Content Analysis The **Content Analysis** tab focuses on the structure and lifecycle of on-demand content. The screenshots show views such as: * **Category Overview** * **Types Overview** * **Media Age** * **Media Types** * **Project Overview** Use this tab to analyze how content is distributed across categories, types, media age groups, media types, and projects. For example, the **Media Age** view can help identify how much content was published recently and how much older content is still part of the selected scope. *** ### Engagement The **Engagement** tab shows how viewers interact with content and player features. The screenshots show views such as: * **Playback Modes** * **Attachment Downloads** * **Live Reactions** * **Sharing** Use this tab to understand whether viewers use inline or fullscreen playback, download attachments, interact with live reactions, or use sharing features. *** ### Charts The **Charts** tab shows ranked content performance for the selected scope, metric, filter, and time range.
For example, when **Playback Starts** is selected, the chart lists the most-played content items. Each entry can include: * Ranking position * Thumbnail * Project or category context * Title * Relative performance bar * Measured value * Playback preview button Use the Charts tab to identify top-performing content, compare individual videos, and quickly find assets with high activity. *** ### Exporting Analytics Data Depending on user permissions and account configuration, analytics data can be exported. The export reflects the selected project scope, metric, filters, and time range. Exporting is useful for internal reports, customer reporting, editorial evaluation, performance reviews, external analysis, and long-term documentation. *** ### Notes The available analytics views, dashboards, filters, and export options may depend on account configuration, enabled modules, and user permissions. For meaningful comparisons, use the same project scope, metric, time range, and filter settings across reports. Some detailed views are only available when enough analytics data exists for the selected scope and time range. # Modules Modules are optional platform components that extend the functionality of the account. Each module enables a specific feature or capability and can be booked or canceled individually. The **Modules** section provides an overview of all available modules and their current status. ### Module Management
# MediaRSS Exporter
The **MediaRSS Exporter** module allows you to create MediaRSS feeds from your content. These feeds can be used to provide selected media files to external systems, platforms, websites, apps, or syndication workflows. {% hint style="info" %} A MediaRSS export can be created manually by adding selected files, or automatically by defining rules that determine which files should be included in the feed. {% endhint %} From the MediaRSS Exporter module, users can: * View existing MediaRSS exports * Create new MediaRSS exports * Add files manually to a feed * Generate automatic MediaRSS feeds based on rules * Select source projects * Filter automatic feeds by metadata * Define the number and maximum age of feed elements * Share or use the generated MediaRSS feed The MediaRSS Exporter module is available from the main navigation under **Modules**. *** ### MediaRSS Exporter Overview The MediaRSS Exporter overview displays all configured MediaRSS exports in a table. Each row represents one MediaRSS export and includes the most relevant information: * Export ID * Title * Assigned projects * Creation date * Available actions At the top of the page, users can switch between different views: * **All MediaRSS Exporters**\ Shows all configured MediaRSS exports. * **Only with Automatic Content**\ Shows only MediaRSS exports that are generated automatically based on rules. * **Last Edited**\ Shows or sorts exports by their latest changes. A search field is available to quickly find existing MediaRSS exports. *** ### Manual and Automatic MediaRSS Exports A MediaRSS export can be managed in two different ways. #### Manual MediaRSS Export A manual MediaRSS export is created by adding selected files directly to the feed. This gives editors full control over which files are included. Manual feeds are useful when the exported content should be curated individually, for example for a specific partner, campaign, or publication workflow. #### Automatic MediaRSS Export An automatic MediaRSS export is generated by the system based on defined rules. Instead of adding files manually, users configure filters and limits. The system then compiles suitable files from the selected projects and updates the feed automatically. Automatic feeds are useful for recurring or dynamic workflows, such as latest videos, category-based feeds, partner feeds, or automated content syndication. *** ### Creating a MediaRSS Export To create a new MediaRSS export: 1. Open **Modules** in the main navigation. 2. Select **MediaRSS Exporter**. 3. Click **Add MediaRSS Export**. 4. The properties panel opens. 5. Enter a **Title**. 6. Optionally add a **Description**. 7. Optionally enter an **Author**. 8. Decide whether the export should be automatic. 9. For automatic exports, configure the rules in the **Configuration** tab. 10. Save the MediaRSS export. After saving, the export appears in the overview. *** ### Basic Settings #### Title The **Title** is the name of the MediaRSS export. Choose a clear and descriptive title, especially when multiple feeds are used for different projects, partners, or workflows. Example titles: * Automatic Feed * Public Videos Feed * Partner Export * Latest News Videos * Product Video Feed * Testfeed #### Description The **Description** field can be used to add internal notes or information about the purpose of the export. This field is optional. Useful information can include: * Intended target system * Partner or customer reference * Content rules * Editorial notes * Internal workflow information #### Author The **Author** field can be used to define the author information for the MediaRSS export. This field is optional and can be used when the receiving system expects author metadata in the feed. #### Automatic MediaRSS Export The **Automatic MediaRSS Export** option defines whether the feed is managed manually or generated automatically. When this option is enabled, the system creates the feed based on the rules defined in the **Configuration** tab. When this option is disabled, users can add files manually to the MediaRSS export. *** ### Managing Manual Feed Elements For manual MediaRSS exports, users can manage the feed content in the **Edit Elements** area. The element view shows: * Number of elements * Total duration * Existing files in the feed * Thumbnail * Source project * Title * Duration To add files manually: 1. Open the MediaRSS export. 2. Open **Edit Elements**. 3. Click **Add Files**. 4. Search for the files you want to include. 5. Add the selected files to the feed. Files can be removed from the feed if they should no longer be included. Manual element management is useful when the exact content of the feed should be controlled by an editor. *** ### Automatic Feed Configuration For automatic MediaRSS exports, the **Configuration** tab defines which files are included in the feed. The system compiles suitable files from the specified projects according to the configured rules. Available configuration options include: * Projects * Content type * Categories * Types * People * Aspect ratio * Number of elements * Maximum age of content The available filters may depend on the account configuration, metadata setup, and selected projects. *** ### Projects The **Projects** field defines which projects are used as the source for the automatic MediaRSS feed. Only files from the selected projects are considered for the feed. This is useful when a feed should only include content from a specific content pool, department, customer, or editorial workflow. Example use cases: * Export only files from a news project * Create a feed for a specific customer project * Provide only public videos to an external platform * Build a feed from a dedicated content pool *** ### Content Type The **Type** setting defines which kind of media content should be included. Available options include: * **Video** * **Audio** * **Mixed** Select the type that matches the target system or intended feed purpose. For example, use **Video** for video syndication feeds, **Audio** for audio-only workflows, and **Mixed** when both media types are allowed. *** ### Metadata Filters Automatic MediaRSS exports can be filtered by metadata. Available filters may include: * **Categories** * **Types** * **People** * **Aspect Ratio** These filters help control which files are included in the feed. For example, an automatic feed can be configured to include only videos from a selected project that belong to a specific category or type. This is useful for structured syndication workflows where external systems should only receive content matching certain editorial or technical criteria. *** ### Aspect Ratio The **Aspect Ratio** filter can be used to include only files with a specific video format. This is useful when a target platform requires a certain format or when feeds are created for specific frontend layouts. Example use cases: * Landscape videos for standard video portals * Portrait videos for vertical video experiences * Format-specific exports for partner platforms *** ### Number of Elements The **Number of Elements** setting defines how many files should be included in the automatic feed. This allows users to limit the feed size. Example configurations: * Latest 10 videos * Latest 50 clips * Latest 100 files Limiting the number of elements helps keep the feed focused and easier to process by external systems. *** ### Maximum Age of Content The **Maximum Age of Content** setting defines how old files may be to appear in the automatic feed. For example, if the maximum age is set to **100 days**, only matching files created or updated within that period are considered for the feed. This is useful for feeds that should only contain recent or currently relevant content. *** ### Sharing and Using the Feed MediaRSS exports can be shared or connected to external systems. Depending on the configuration, users can use the generated MediaRSS feed for: * External websites * Apps * Content portals * Partner platforms * Syndication workflows * Automated import workflows * CMS or MAM integrations The receiving system can use the MediaRSS feed to retrieve media information and process the exported content. *** ### Typical Use Cases MediaRSS Exporter can be used for different workflows, for example: * Providing a curated feed to a partner platform * Creating an automatic latest-videos feed * Exporting selected files to an external system * Building a category-based syndication feed * Supplying video metadata to a website or app * Creating project-specific content feeds * Exporting only recent content from a selected content pool * Automating content delivery to downstream systems *** ### Notes The MediaRSS Exporter module can be booked in **Module Management**. The available filters and configuration options may depend on the account configuration, project setup, metadata fields, and user permissions. For automatic exports, review the selected projects, filters, number of elements, and maximum content age carefully to make sure the feed contains the expected files. Before connecting a MediaRSS feed to a production system, it is recommended to test the feed with representative content. # Notifications The **Notifications** module allows you to create automated notifications and workflows for selected events in 3Q.
Notifications can be used to inform users or external systems when specific actions happen, for example when a new file has been processed, file metadata has changed, or a file has been deleted. Depending on the selected notification type, notifications can be sent by: * Webhook * Email * SMS This makes the module useful both for technical integrations and for editorial or operational alerts. From the Notifications module, users can: * View existing notifications * Create new notifications * Select the project the notification applies to * Select the event that should trigger the notification * Choose the notification type * Configure webhook, email, or SMS notifications * Filter notifications by project or type The Notifications module is available from the main navigation under **Modules**. *** ### Notifications Overview The Notifications overview displays all configured notifications in a table. Each row represents one notification and includes the most relevant information: * Notification ID * Title * Assigned project * Trigger event * Notification type * Creation date At the top of the page, users can switch between different views: * **All Notifications**\ Shows all configured notifications. * **Only for On-Demand**\ Shows notifications assigned to on-demand projects. * **Only for Podcasts**\ Shows notifications assigned to podcast projects. * **Only for Livestreams**\ Shows notifications assigned to livestream projects. The overview also provides search and filter options. Available filters include: * **Type**\ Filters notifications by notification type, such as webhook, email, or SMS. * **Project**\ Filters notifications by the assigned project. *** ### Creating a Notification To create a new notification: 1. Open **Modules** in the main navigation. 2. Select **Notifications**. 3. Click **Create Notification**. 4. The **Create Notification** side panel opens. 5. Enter a **Title**. 6. Select the **Project**. 7. Select the **Event** that should trigger the notification. 8. Select the notification **Type**. 9. Configure the type-specific settings. 10. Optionally add a **Description**. 11. Click **Save**. After saving, the notification appears in the overview and is triggered automatically when the selected event occurs. *** ### Notification Settings #### Title The **Title** is the internal name of the notification. Choose a clear title that describes the purpose of the notification. Example titles: * Webhook – New File Processed * Email Alert – File Deleted * SMS Alert – Livestream Event * Metadata Update Notification * Processing Workflow Trigger #### Project The **Project** defines where the notification is active. The available projects are grouped by project type, for example: * On-demand projects * Podcast projects * Livestream projects The selected project also determines which events are available for the notification. #### Event The **Event** defines what action triggers the notification. Available events depend on the selected project type. For on-demand file workflows, events include: * **New File Processed** * **New File in Pipeline** * **File Metadata Updated** * **File Source Updated** * **File Deleted** and many other events, also for podcasts or livestream projects. #### Type The **Type** defines how the notification is sent or executed. Available notification types include: * **Webhook** * **Email** * **SMS** The selected type determines which additional configuration fields are displayed. *** ### Webhook Notifications Webhook notifications are used to send event information to an external system. This is useful for building automated workflows and integrations, for example with a CMS, MAM, automation platform, monitoring system, or custom backend. When using a webhook notification, 3Q calls the configured endpoint when the selected event occurs. Typical webhook use cases include: * Triggering an external publishing workflow * Informing a CMS that a new video is ready * Updating an external database when metadata changes * Starting a downstream automation after processing * Synchronizing deleted files with another system Depending on the configuration, the webhook request method, such as **GET**, can be selected. *** ### Email Notifications Email notifications send an email when the selected event occurs. They are useful for editorial, support, or operational teams that need to be informed about important changes without connecting an external system. Typical email notification use cases include: * Informing editors when a new file has been processed * Notifying a team when metadata has been updated * Alerting responsible users when a file has been deleted * Sending operational updates for selected projects *** ### SMS Notifications SMS notifications send a text message when the selected event occurs. They are useful for time-sensitive workflows where users need to be informed quickly. Typical SMS notification use cases include: * Critical livestream-related alerts * Important processing notifications * Operational escalation workflows * Urgent project-specific events *** ### Building Automated Workflows Notifications can be used to build automated workflows around 3Q events. For example, when a new file is processed in an on-demand project, a webhook can notify an external system. That system can then publish the video, update a website, trigger a review workflow, or start additional processing. This allows 3Q to be connected to external tools and systems without requiring manual checks. Example workflow: 1. A new video is uploaded to a project. 2. The file is processed by 3Q. 3. The **New File Processed** event is triggered. 4. A webhook notification is sent to an external endpoint. 5. The external system continues the workflow automatically. *** ### Managing Existing Notifications Existing notifications can be reviewed in the Notifications overview. Depending on user permissions, users can open, edit, or delete notifications. When editing a notification, review the selected project, event, and type carefully. Changes may affect automated workflows or alerting behavior. *** ### Typical Use Cases Notifications can be used for different workflows, for example: * Sending an email when a new file is processed * Sending an SMS for urgent livestream-related events * Triggering a webhook when file metadata changes * Informing external systems when a file is deleted * Connecting 3Q with CMS, MAM, or automation systems * Building project-specific processing workflows * Notifying teams about content changes *** ### Notes The available events depend on the selected project type. The available notification types and configuration options may depend on the account configuration, enabled modules, and user permissions. For webhook workflows, make sure that the external endpoint is reachable and can process the event data sent by 3Q. # Livestream Recorder The **Livestream Recorder** module allows you to record livestream projects and store the resulting recordings separately in a selected on-demand project or content pool.
This module is useful when livestreams should be archived, published, or processed as on-demand content after or during a live event. Recordings are created from a selected source livestream project and saved into a defined target project. {% hint style="info" %} The Livestream Recorder can be used independently from [**Live Clipping**](/user-guide-new-ui/projects/livestreaming/live-clipping). Live Clipping is available when Timeshift is enabled and allows users to create selected clips from a livestream, while the Livestream Recorder is used to record the stream into a target project automatically or manually. {% endhint %} From the Livestream Recorder module, users can: * View existing recorder configurations * Create new livestream recorders * Select a source livestream project * Select a target on-demand project or content pool * Enable automatic recording * Enable interval recording * Filter recorders by source or target project * Review recorder status The Livestream Recorder module is available from the main navigation under **Modules**. *** ### Recorder Overview The Livestream Recorder overview displays all configured recorders in a table. Each row represents one recorder and includes the most relevant information: * Recorder ID * Title * Source project * Target project * Status * Creation date At the top of the page, users can switch between the following views: * **All Recorders**\ Shows all configured livestream recorders. * **Only with Auto Recording**\ Shows only recorders where automatic recording is enabled. * **Only with Interval Recording**\ Shows only recorders where interval recording is enabled. The overview also provides search and filter options. Available filters include: * **Source Project**\ Filters recorders by the livestream project that provides the incoming signal. * **Target Project**\ Filters recorders by the on-demand project or content pool where recordings are stored. *** ### Creating a Recorder To create a new livestream recorder: 1. Open **Modules** in the main navigation. 2. Select **Livestream Recorder**. 3. Click **Create Recorder**. 4. The **Create Recorder** side panel opens. 5. Enter a **Title**. 6. Optionally add a **Description**. 7. Select the **Source Project**. 8. Select the **Target Project**. 9. Optionally enable **Auto Recording**. 10. Optionally enable **Interval Recording**. 11. Save the recorder. After saving, the recorder appears in the overview and can be used for the selected livestream project. *** ### Recorder Settings #### Title The **Title** is the name of the recorder configuration. Choose a clear and descriptive title, especially when multiple recorders are used for different livestream projects or target content pools. Example titles: * Main Event Recorder * Townhall Recording * Webinar Archive * Manual Recorder * Auto Recording to Public Videos #### Description The **Description** field can be used to add internal notes or additional information about the recorder. This field is optional. Useful information can include: * Purpose of the recorder * Event or project reference * Recording workflow notes * Target project information * Internal publishing instructions #### Source Project The **Source Project** defines which livestream project should be recorded. This must be a livestream project that can receive a live signal. When the source project receives a signal, the recorder can create recordings from that livestream, depending on the selected recording settings. #### Target Project The **Target Project** defines where the recordings are stored. The target project is usually an on-demand project or content pool. After a recording is created, it appears in the selected target project and can be managed like other on-demand content. This allows livestream recordings to be separated from the livestream project itself and stored in a dedicated video library, archive, or publishing project. *** ### Auto Recording The **Enable Auto Recording** option allows the recorder to start automatically when the source project receives a live signal. When Auto Recording is enabled: * Recording starts automatically as soon as the source project receives a signal. * Recording stops when there is no more signal. * The resulting recording is saved to the selected target project. * No manual start action is required. Auto Recording is useful for recurring livestream workflows where every live signal should automatically be recorded. Typical use cases include: * Automatically recording all townhall livestreams * Archiving webinars without manual intervention * Recording regular internal broadcasts * Creating an automatic on-demand version of each livestream *** ### Interval Recording The **Enable Interval Recording** option allows the system to create separate recording files at defined intervals. If Interval Recording is not enabled, a recording file is created for the full duration of the signal. However, if the signal exceeds 24 hours, a new file is created automatically. By enabling Interval Recording, users can split long livestreams into shorter recording segments. This is useful for: * Long-running livestreams * Continuous event streams * 24/7 streams * Workflows where smaller recording files are easier to process * Separating recordings into shorter time-based parts *** ### Difference Between Livestream Recorder and Live Clipping The Livestream Recorder and Live Clipping can both be used to create on-demand content from livestreams, but they serve different purposes. **Livestream Recorder** is used to record a livestream and save the recording into a target on-demand project or content pool. It can run automatically when a signal is received and is suitable for full recordings or interval-based recording workflows. **Live Clipping** is used to create selected clips from a livestream. It is available when Timeshift is enabled and allows users to choose a specific time range and export only that section as a new on-demand video. Use the Livestream Recorder when the livestream should be recorded as a whole or in defined intervals. Use Live Clipping when only selected moments, highlights, or segments should be exported. *** ### Managing Existing Recorders Existing recorders can be reviewed in the Livestream Recorder overview. Depending on user permissions, users can open, edit, or remove recorder configurations. When editing an existing recorder, review the source project, target project, and recording options carefully. Changes may affect how future livestream signals are recorded and where recordings are stored. *** ### Typical Use Cases Livestream Recorder can be used for different recording workflows, for example: * Recording livestreams automatically for later on-demand use * Archiving internal company livestreams * Creating on-demand versions of webinars * Saving townhall recordings to a dedicated content pool * Recording events into a public video project * Splitting long livestreams into shorter interval recordings * Separating livestream production from on-demand publishing workflows *** ### Notes The Livestream Recorder module can be booked in **Module Management**. Recordings are stored separately in the selected target project or content pool. The selected target project should be an on-demand project or content pool where recorded videos can be processed and managed. The availability of recording options may depend on the account configuration, enabled modules, and user permissions. # Multi-CDN The Multi CDN module allows you to manage CDN profiles for content delivery across different providers. CDN profiles define how video content is distributed and can be configured globally or for specific projects. {% hint style="info" %} The available CDN providers and profile options may depend on the account configuration and booked modules. Access to the Multi CDN module is controlled by user permissions. Users who do not have the required rights may not see the module or may have limited access to create and manage CDN profiles. {% endhint %}
This module is designed to support flexible delivery strategies, allowing content to be routed through different CDN providers depending on geographical, operational, or project-specific requirements. From the Multi CDN area, users can: * View existing CDN profiles * Create new CDN profiles * Assign profiles globally or to individual projects * Select the CDN provider used for delivery * Review provider recommendations and usage guidance The Multi CDN module is available from the main navigation under **Modules**. *** ### CDN Profile Overview The Multi CDN overview displays all configured CDN profiles in a structured table. Each row represents one CDN profile and includes the most relevant information: * Thumbnail or provider preview * Unique profile ID * Profile title * Assigned project * CDN provider * Creation date The list supports sorting and filtering, making it easier to manage multiple CDN configurations. Available tabs include: * **All CDN Profiles**\ Shows all CDN profiles available in the account. * **Global CDN Profiles**\ Shows CDN profiles that are available across all projects. * **Project Specific CDN Profiles**\ Shows CDN profiles assigned to individual projects only. At the top of the list, the following controls are available: * **Search** to find CDN profiles by name or related metadata * **Project filter** to narrow the list to a specific project * **Provider filter** to filter profiles by CDN provider * **Add CDN Profile** to create a new CDN configuration *** ### Creating a CDN Profile To create a new CDN profile: 1. Open **Modules** in the main navigation. 2. Select **Multi CDN**. 3. Click **Add CDN Profile**. 4. The **Create Notification** side panel opens. 5. Enter a **Title** for the CDN profile. 6. Optionally add a **Description**. 7. Select a CDN **Provider**. 8. Define the profile availability. 9. Save the profile. The new CDN profile will appear in the overview after creation. *** ### Provider Selection When creating or editing a CDN profile, a CDN provider must be selected. Available providers include: * **3Q** * **Akamai** * **Wangsu** The provider selection determines which CDN infrastructure is used for content delivery. The interface also provides additional provider information to help users choose the most suitable CDN for their use case. Provider guidance includes: * **3Q**\ Optimized for performance in Europe and North America. * **Akamai**\ Recommended for global delivery scenarios without a specific geographical focus. * **Wangsu**\ Optimized for performance in China. This information is displayed in the **Multi-CDN Provider** information panel and can be used as guidance when configuring delivery strategies. *** ### Availability CDN profiles can be configured with different availability scopes. Available options are: * **Available in All Projects**\ The CDN profile can be used across all projects in the account. * **Only Available in One Project**\ The CDN profile is assigned to a specific project only. Use global availability for general delivery configurations that should be reused across projects. Use project-specific availability when a CDN setup is only required for a particular project, customer, region, or use case. *** ### Project-Specific CDN Profiles When a CDN profile is limited to a single project, the project assignment defines where the profile can be used. This is useful for workflows where individual projects require different delivery configurations, for example: * Regional streaming requirements * Customer-specific CDN setups * Dedicated event or livestream configurations * Testing alternative CDN providers * Separating production and internal delivery workflows Project-specific profiles are listed under the **Project Specific CDN Profiles** tab. *** ### Global CDN Profiles Global CDN profiles are available across all projects in the account. They are useful when the same CDN configuration should be reused consistently for multiple projects. Typical use cases include: * Standard account-wide CDN delivery * Default delivery configuration * Shared fallback profiles * Common delivery strategies for multiple teams or departments Global profiles are listed under the **Global CDN Profiles** tab. *** ### Managing Existing CDN Profiles Existing CDN profiles are displayed in the Multi CDN overview. From the list, users can review: * Profile title * Assigned project * Selected provider * Creation date Depending on user permissions, existing profiles can be opened and adjusted. Changes to CDN profiles may affect content delivery behavior. For this reason, provider and availability settings should be reviewed carefully before making changes in production environments. *** # IP/Geo-Blocking
The IP/Geo-Blocking module allows you to restrict or allow access to content based on countries and IP address rules. Profiles can be created as either **allowlists** or **denylists** and can then be used to control where content is accessible from. {% hint style="info" %} IP/Geoblocking profiles are applied through the player configuration. After a profile has been created, it can be selected in the [**Player Management**](/user-guide-new-ui/players) and assigned to a specific player configuration. Once assigned, the selected allowlist or denylist controls access for all content played through that player configuration. This allows users to manage access rules centrally in the IP/Geoblocking module and apply them flexibly to different players depending on the required use case, region, or licensing restrictions. {% endhint %} This module is useful when content access must be limited for licensing, regional availability, security, or internal access control reasons. From the IP/Geoblocking module, users can: * View existing geoblocking profiles * Create new allowlist or denylist profiles * Restrict access by country * Restrict access by IP address or IP range * Edit or delete existing profiles * Quickly filter profiles by type or last edited status {% hint style="info" %} The IP/Geoblocking module is available from the main navigation under [**Modules**](/user-guide-new-ui/modules). {% endhint %} *** ### Profile Overview The IP/Geoblocking overview displays all configured profiles in a table. Each row represents one profile and includes the most relevant information: * Profile ID * Profile title * Profile type * Selected countries * IP address rules * Creation date * Available profile actions At the top of the page, users can switch between different views: * **All Profiles**\ Shows all existing IP/Geoblocking profiles. * **Allowlists**\ Shows only profiles that allow access for selected countries or IP addresses. * **Denylists**\ Shows only profiles that block access for selected countries or IP addresses. * **Last Edited**\ Sorts or filters profiles by the most recently changed entries. A search field is available to quickly find profiles by title or related information. *** ### Allowlist and Denylist IP/Geoblocking profiles can be created as either an **allowlist** or a **denylist**. #### Allowlist An allowlist grants access only to the selected countries or IP addresses. Users outside the defined countries or IP rules will not be allowed to access the protected content. Use an allowlist when content should only be available in specific regions or for specific networks. Example use cases: * Content licensed only for Germany, Austria, and Switzerland * Internal company streams available only from office IP addresses * Test content available only for selected customer networks #### Denylist A denylist blocks access for the selected countries or IP addresses. Users from all other countries or IP addresses remain allowed unless blocked by another rule. Use a denylist when content should be generally available, except for specific regions or networks. Example use cases: * Blocking access from countries without distribution rights * Preventing access from known unwanted IP ranges * Restricting access for specific external networks *** ### Creating an IP/Geo-Blocking Profile
To create a new profile: 1. Open **Modules** in the main navigation. 2. Select **IP/Geoblocking**. 3. Click **Add Profile**. 4. The **Add Profile** side panel opens. 5. Enter a **Title**. 6. Optionally add a **Description**. 7. Select the profile **Type**: * **Allowlist** * **Denylist** 8. Select one or more **Countries**. 9. Optionally add **IP-Address Rules**. 10. Save the profile. After saving, the profile appears in the overview and can be selected wherever IP/Geoblocking profiles are supported. *** ### Profile Settings #### Title The title is the name of the IP/Geoblocking profile. Choose a clear and descriptive title, especially when multiple regional or customer-specific profiles are used. Example titles: * DACH * No License * Internal Access Only * Europe Allowlist * Blocked Regions #### Description The description field can be used for internal notes or additional context. This field is optional. Useful information can include: * Purpose of the profile * Licensing details * Customer or project reference * Notes about included IP ranges * Internal approval information #### Type The type defines how the selected countries and IP address rules are handled. Available options are: * **Allowlist**\ Only selected countries or IP addresses are allowed. * **Denylist**\ Selected countries or IP addresses are blocked. The selected type should be reviewed carefully before saving, as allowlists and denylists have opposite behavior. #### Countries The countries field allows users to select one or more countries for the profile. The country list includes country names with flags for easier identification. Selected countries are displayed in the profile overview after saving. For example, a DACH allowlist could include: * Austria * Switzerland * Germany A denylist could include a country where no streaming license is available. #### IP-Address Rules IP address rules allow more specific access control based on IP addresses or IP ranges. They can be used in addition to country-based rules. Supported input formats include: ``` 91.242.173.24 91.242.173 91.242 ``` These examples show that rules can be entered with different levels of specificity, from a full IP address to broader IP prefixes. *** ### Editing Existing Profiles Existing profiles can be edited from the overview. Use the action buttons on the right side of a profile row to open or modify a profile. When editing a profile, users can adjust: * Title * Description * Type * Countries * IP address rules Changes to a profile may affect content access immediately wherever the profile is used. Review all country and IP rules carefully before saving changes. *** ### Deleting Profiles Profiles can be deleted from the overview using the delete action. Before deleting a profile, make sure it is no longer used by any active content, player, project, or configuration. Deleting an active profile may affect access restrictions for content that previously relied on it. *** ### Typical Use Cases IP/Geoblocking can be used for different access control workflows, for example: * Restricting videos to licensed countries * Blocking countries where content rights are not available * Allowing access only from selected company networks * Creating regional availability profiles * Separating public and internal access rules * Applying customer-specific geographic restrictions *** ### Notes The IP/Geoblocking module can be booked in **Module Management**. The availability of IP/Geoblocking options may depend on the account configuration and user permissions. IP-based restrictions depend on the detected viewer IP address. Country-based restrictions depend on IP geolocation and may vary depending on the accuracy of the geolocation provider. When using both country rules and IP address rules, review the final access behavior carefully to avoid unintentionally blocking legitimate viewers. # Livestream Distribution The Livestream Distribution module allows you to forward a live stream from 3Q to external streaming platforms. It can be used to distribute an active livestream to platforms that support **RTMP** or **SRT**, including common third-party platforms such as YouTube, Twitch, and other custom streaming destinations. {% hint style="info" %} Livestream Distribution can be accessed either through the livestream’s control center or from the Livestream Distribution module. The module is available for booking in Module Management. {% endhint %}
This module is useful when a livestream should be published not only through the 3Q player, but also on external platforms or social channels. From the Livestream Distribution area, users can: * Create livestream distributions * Define a source project * Select a target platform * Configure RTMP or SRT target details * Enable automatic distribution * Adjust advanced stream settings * Monitor existing distributions The Livestream Distribution module is available from the main navigation under **Modules**. *** ### Distribution Overview The Livestream Distribution overview displays all configured livestream distributions. At the top of the page, users can switch between the following views: * **All Distributions**\ Shows all configured livestream distributions. * **Only with Auto Distribution**\ Shows only distributions where automatic distribution is enabled. The overview also provides search and filter options. Available filters include: * **Source Project**\ Filters distributions by the project that provides the incoming livestream. * **Target Platform**\ Filters distributions by the configured external destination. If no distributions have been created yet, the page displays an empty state with the option to create the first distribution. *** ### Creating a Distribution To create a new livestream distribution: 1. Open **Modules** in the main navigation. 2. Select **Livestream Distribution**. 3. Click **Create Distribution**. 4. The **Create Distribution** side panel opens. 5. Complete the required fields in the **General** tab. 6. Optionally configure additional settings in the **Advanced Settings** tab. 7. Click **Save**. After saving, the distribution becomes available in the distribution overview and, depending on the configuration, can be started manually or automatically. *** ### General Settings The **General** tab contains the basic configuration required to send a livestream to an external destination. #### Title Enter a name for the distribution. The title should clearly describe the destination or use case, for example: * YouTube Main Channel * Twitch Event Stream * Partner Platform RTMP * Backup SRT Distribution #### Description The description field can be used to add internal notes or additional information about the distribution. This field is optional. #### Source Project Select the project that provides the livestream signal. The selected source project is the origin of the stream that will be forwarded to the target platform. #### Target Platform Select the platform or destination that should receive the stream. Depending on the available configuration, this can be a predefined platform or a custom target. Supported destination types include platforms that accept: * RTMP streams * SRT streams Common target platforms include services such as YouTube, Twitch, and other livestreaming platforms that provide ingest URLs and stream keys. #### Server URL of the Target Platform Enter the server URL provided by the external platform. For RTMP destinations, this is usually the RTMP ingest server URL. For SRT destinations, this is the SRT target address supplied by the receiving platform or system. #### Stream Key / Stream Name of the Target Platform Enter the stream key or stream name provided by the target platform. Many platforms use this value to authenticate or identify the incoming stream. The stream key should be handled carefully and should not be shared publicly. *** ### Auto Distribution The **Enable Auto Distribution** option allows the distribution to start automatically when the selected source project receives a livestream signal. When this option is enabled: * The distribution starts automatically as soon as the source project receives a signal. * The distribution stops again when there is no more signal. * Manual intervention is not required for recurring livestream workflows. This is especially useful for scheduled or repeated events where the same external platform should always receive the stream. Auto distribution can be used for scenarios such as: * Automatically streaming all events from one project to YouTube * Sending a recurring livestream to Twitch * Forwarding a signal to a partner platform whenever the project goes live * Creating a persistent distribution workflow for regular broadcasts *** ### Advanced Settings The **Advanced Settings** tab provides additional configuration options for the outgoing stream. These settings allow users to control how the livestream is forwarded to the target platform. #### Preview URL of the Target Platform Enter the preview URL of the external platform. This URL can be used to open or review the stream on the destination platform. For example, this may be a YouTube Studio preview link, a Twitch channel URL, or another platform-specific preview page. #### Maximal Resolution Select the maximum resolution that should be sent to the target platform. Available options may depend on the source stream and account configuration. The default option is **Input Stream**, which uses the resolution of the incoming livestream. #### Video Profile Select the video profile used for the outgoing distribution. The default profile is **Main**. The selected profile determines which encoding profile is used for the outgoing stream. #### Keyframe Interval Set the keyframe interval for the outgoing stream. The keyframe interval defines how often keyframes are inserted into the video stream. Some platforms require specific keyframe settings for reliable playback or ingest compatibility. A common value is **2 seconds**, which is often required or recommended by major livestreaming platforms. #### Extract Audio Channel Enable **Extract Audio Channel** to separate the left and right audio channels. This can be useful when a stream contains multiple language versions or different audio signals in separate stereo channels. When enabled, the separated audio channels can be used differently depending on the streaming workflow. Example use cases include: * Separate language channels * Interpretation audio * Main audio and backup audio * Different audio mixes for different target platforms *** ### Creating a Distribution from a Project A distribution can also be created directly from a project view. Inside a project, open the **Distribution** area and click **Create Distribution**. When creating a distribution from a project, the current project is used as the source project. This makes it faster to configure distributions for a specific livestream. The same general and advanced settings are available. *** ### Target Platforms Livestream Distribution supports streaming to external platforms that accept RTMP or SRT input. Examples include: * YouTube * Twitch * Social media livestreaming platforms * Event platforms * Partner platforms * Custom RTMP servers * Custom SRT receivers For predefined platforms, some fields may be simplified or preconfigured. For custom targets, users need to enter the required server URL and stream key or stream name manually. The required ingest information is provided by the target platform. *** ### Managing Distributions Existing distributions can be reviewed in the Livestream Distribution overview. Users can use the search and filter options to find distributions by source project or target platform. Depending on user permissions, existing distributions can be opened, edited, or removed. When editing an existing distribution, review the target URL, stream key, and advanced settings carefully. Incorrect values can prevent the external platform from receiving the stream. *** ### Notes The availability of target platforms and advanced settings may depend on the account configuration and enabled modules. External platforms may have their own requirements for ingest URLs, stream keys, keyframe intervals, resolution, bitrate, and supported protocols. Before going live, it is recommended to test the distribution with the selected target platform. # People The **People** module is used to create and manage persons that can be linked to content across the platform, such as podcasts, videos, or other media elements. People entries typically represent contributors like actors, authors, musicians, or producers. *** ### Overview
With the People module you can: * Create and manage **persons** * Assign one or more **roles** to each person * Add profile images and aliases * Filter people by role or assignment * Reuse people consistently across different content types This ensures clean metadata, consistent naming, and structured contributor management. *** ### People List View The main People view displays all existing persons in a table. Displayed information includes: * **Profile Image** – Person avatar or placeholder * **ID** – Unique person identifier * **First Name** * **Last Name** * **Artist Name / Alias** – Optional display or stage name * **Role** – Assigned role (e.g. Actor, Author) * **Created On** – Creation date #### Filters & Search You can refine the list using: * **Search** – Find people by name * **Role Filter** – Show only people with a specific role * **Tabs** * All People * Only with Role * Only without Role *** ### Creating a Person Click **Add Person** to create a new entry. #### Basic Information Fields available when creating or editing a person: * **Profile Image** * Supported formats: AVIF, BMP, GIF, JPEG, JPG, PNG, WEBP * **First Name** * **Last Name** * **Artist Name / Alias** (optional) *** ### Roles Each person can be assigned one or more **roles** that describe their function. Available roles include (example list): * Actor * Anchor Person * Artist * Author * Composer * Director * Musician * Photographer * Producer * Reporter Roles can be: * Added via a dropdown selection * Removed individually * Used for filtering and organization A person may have multiple roles if applicable. *** ### Editing a Person Click on a person in the list to open the **Properties** panel. From here you can: * Change name or alias * Upload or replace the profile image * Add or remove roles All changes are saved immediately and reflected across all linked content. *** ### Linking People to Media Assets People entries can be **directly linked to media assets** (such as videos or audio files) via the asset’s **Metadata (Extended)** section.
Within a media asset: * Open the asset **Properties** * Navigate to **Metadata (Extended)** * Use the **People** field to select one or more persons * Each linked person keeps their assigned **role** (e.g. Actor, Author) This creates a persistent relationship between the person and the media asset. The same person can be reused across multiple assets without duplication. Typical use cases include: * Assigning actors to video content * Linking authors or speakers to recordings * Structuring credits and contributor metadata Changes to a person’s name, image, or role are automatically reflected wherever the person is linked. *** ### Best Practices * Use **real names** where possible and aliases only when needed * Assign at least one role for better filtering * Reuse existing people instead of creating duplicates * Keep profile images consistent for a clean UI # Categories and Types The **Categories and Types** module helps you to define global metadata structures for on-demand content in your account. {% hint style="info" %} This module is free for everybody and available in any account. {% endhint %} Categories and types help organize video content consistently across projects and content pools. They can be used to classify videos, improve searchability, and create a more structured metadata workflow. From the Categories and Types module, users can: * View existing categories and types * Create new categories * Create new types * Add multilingual titles and descriptions * Define individual IDs * Edit or delete existing entries * Use categories and types across on-demand projects The module is available from the main navigation under **Modules**. *** ### Categories and Types Overview
The overview page contains two tabs: * **Categories**\ Displays all categories created for the account. * **Types**\ Displays all content types created for the account. Both tabs use the same table structure and provide an overview of the existing entries. The table includes: * Preview image or placeholder * ID * Title * Description * Individual ID * Creation date * Available actions A search field is available at the top of the page to quickly find existing categories or types. Depending on user permissions, entries can be created, edited, or deleted. *** ### Categories Categories are used to group on-demand videos by topic, content area, or organizational structure. Examples of categories include: * Product videos * Tutorials * Town-Halls * Music videos * Talkshows * Movies Categories can help users structure larger video libraries and make content easier to manage. *** ### Types Types are used to define the content format or content purpose. Examples of types include: * Movie * Preview * Recording * Trailer * Webinar * Interview While categories usually describe the content topic, types can describe the format or intended use of the content. *** ### Creating a Category
To create a new category: 1. Open **Modules** in the main navigation. 2. Select **Categories and Types**. 3. Open the **Categories** tab. 4. Click **Add Category**. 5. The **Add Category** side panel opens. 6. Enter a **Title**. 7. Optionally add a **Description**. 8. Optionally enter an **Individual ID**. 9. Save the category. After saving, the new category appears in the category overview and can be used for on-demand content, depending on the project or content pool configuration. *** ### Creating a Type To create a new type: 1. Open **Modules** in the main navigation. 2. Select **Categories and Types**. 3. Open the **Types** tab. 4. Click **Add Category**. 5. The **Add Type** side panel opens. 6. Enter a **Title**. 7. Optionally add a **Description**. 8. Optionally enter an **Individual ID**. 9. Save the type. After saving, the new type appears in the types overview and can be used for on-demand content, depending on the project or content pool configuration. *** ### Title The **Title** is the visible name of the category or type. The title should clearly describe the category or type so that editors can easily select the correct value when managing on-demand content. The title field supports multilingual input. Users can enter translations for the available interface languages. *** ### Description The **Description** field can be used to provide additional information about the category or type. This field is optional. Descriptions are useful for internal documentation and can help editors understand when a category or type should be used. Example descriptions: * Used for internal company town hall recordings * Product-related tutorial and support videos * Preview videos for unpublished content * Full-length movie content The description field also supports multilingual input. *** ### Individual ID The **Individual ID** field allows users to define a custom identifier for a category or type. This can be useful when categories or types need to be matched with external systems, internal taxonomies, CMS structures, or import workflows. Examples: * `product_videos` * `tutorial` * `movie` * `preview` * `townhall` The individual ID is optional, but it can help create consistent metadata mappings across systems. *** ### Multilingual Metadata Categories and types support multilingual metadata fields. For title and description fields, users can enter values in the available languages directly in the side panel. This is useful when the account contains content for different audiences or when metadata should be displayed or maintained in multiple languages. *** ### Usage in Projects and Content Pools Categories and types are defined globally for the account. For each project or content pool, users can define whether all global categories and types should be available or whether only selected categories and types should be used. This allows flexible metadata management: * Account-wide categories and types can be created centrally. * Projects can reuse the global structure. * Individual projects or content pools can be limited to specific categories or types. * Editors only see the metadata options relevant to their project. This is useful for accounts with multiple departments, customers, regions, or content libraries. *** ### Managing Existing Categories and Types Existing categories and types can be edited from the overview. When hovering over or selecting a row, available actions are displayed on the right side. Depending on permissions, users can: * Edit an existing category or type * Delete an existing category or type When editing an entry, users can update the title, description, and individual ID. Changes may affect projects or content pools where the category or type is already available. *** ### Typical Use Cases Categories and types can be used for different metadata workflows, for example: * Structuring large on-demand video libraries * Grouping videos by topic or department * Separating content formats such as previews, movies, recordings, or tutorials * Supporting search and filtering workflows * Creating consistent metadata across projects * Mapping 3Q metadata to external systems * Limiting available metadata values per project or content pool *** ### Notes Categories and types are used for **on-demand content**. They are created globally for the account, but their availability can be controlled per project or content pool. The available options and actions may depend on account configuration and user permissions. # Account
The **Account menu** is used to manage **global account settings**. It applies to the entire organization and is not related to individual user profile or personal preferences. Within the Account menu, administrators can: * **Manage modules**\ Enable or disable platform features by booking or canceling modules. * **Manage groups and user rights**\ Create and organize groups, assign users, and control roles and permissions. * **Manage partners and services**\ Configure integrations, partner connections, and external services. * **Billing and invoices**\ View and download invoices related to the account. * **Usage details**\ Monitor usage data and consumption across the account. The Account menu provides full administrative control over features, access, billing, and usage for the entire account. # Modules Modules are optional platform components that extend the functionality of the account. Each module enables a specific feature or capability and can be booked or canceled individually. The **Modules** section provides an overview of all available modules and their current status. *** ### Module Management
Within the Modules section, administrators can: * View all available modules * Filter modules by status: * **All Modules** * **Only Booked Modules** * **Only Not Booked Modules** * Search for modules by name * Book new modules * Cancel already booked modules Each module is displayed as a card showing its name, a short description, booking status, and booking date. Paid modules also display pricing information. *** ### Module Availability {% hint style="info" %} When you book a module, access to that module is automatically granted at the account level.\ To allow other users to use the module, you must explicitly grant the required permissions in **User Management**. {% endhint %} * Modules are enabled on an **account level**. * Activating or canceling a module affects all users and projects within the account. * Some modules are **free**, while others require a **monthly subscription**. *** ### Module Configuration After booking a module, its configuration options become available in the relevant sections of the platform (for example within Projects, Players, or Account settings). Detailed configuration instructions for each module are described in the corresponding module chapters of this documentation. ### Access and Availability * Modules management is available at the **account level** * Only users with appropriate permissions can access the modules management # Groups {% hint style="info" %} **Availability note:** The **Groups** feature is not available for all accounts (tenants). We recommend to use this feature only in complex environments. If groups are not activated you can apply access to projects (content pools) direct to users. {% endhint %} Groups are used to structure access to projects (**content pools**) and users within an account. They provide an additional layer of access control by linking projects to groups and assigning users with specific roles to those groups.
#### Purpose of Groups Groups allow you to: * Link **projects (content pools)** to a groups * Grant **group-based access** to users * Assign **different roles** to users per group Access to a project is determined by the user’s role within the group the project is assigned to. #### Typical Use Cases Groups are commonly used to: * Separate content by department, team, or audience * Restrict access to specific projects * Manage permissions at scale without assigning rights per project If Groups are not enabled for your account, access control is handled without group-based assignments. ### Access and Availability * Groups are available at the **account level** * Only users with appropriate permissions can access group management # Users ### Users The **Users** section is used to manage user accounts and control access to the platform. It allows administrators to create users, assign roles, define permissions, and manage security-related settings. *** ### Users Overview {% embed url="" %} The Users overview displays all user accounts within the account. Here you can: * View all users * Filter users by status (active or deactivated) * Search for users by name or email address * Filter users by default role or group * Open detailed user settings Each user entry shows basic information such as name, email address, assigned groups, and default role. *** ### Creating a User New users can be created from the Users section. When creating a user, the following information can be defined: * First name and last name * Email address * Optional profile image * Language and time zone * Optional telephone number * Default layout preference After creation, roles, group assignments, and module access can be configured. *** ### Roles and Permissions {% hint style="info" %} If **Groups** are not available for the account, access rights and roles can be assigned **directly to users and projects** without using group-based assignments. {% endhint %}
Each user is assigned a **default role**, which defines their general permissions across the platform. Additionally: * Roles can be assigned **per group**, if Groups are enabled * Group-specific roles override the default role for projects linked to that group * Typical roles include **Reader**, **Uploader**, **Junior-Editor**, **Senior-Editor**, and **Administrator** This provides fine-grained permission control tailored to a user’s responsibilities. The **“More information on the roles”** action shows the permissions associated with each role.
*** ### Group and Module Assignment If enabled for the account, users can be: * Assigned to one or more **groups** * Granted access to specific **modules** Module access must be explicitly granted to users, even if the module is booked at the account level. *** ### User Settings For each user, individual settings can be configured, including: * Personal details (name, image, language, time zone) * Layout preferences * Upload and approval behavior * Group-specific roles * Assigned modules Changes take effect immediately and apply according to the user’s permissions. *** ### Security Settings User-specific security settings include: * Two-factor authentication (SMS or email) * Limiting the number of active sessions * Granting temporary support access (if available) These settings help enforce account security and compliance requirements. ### Access and Availability * Users are available at the **account level** * Only users with appropriate permissions can access users management * Availability and granularity of data may depend on enabled modules and services # Partners & Services ### Partners & Services The **Partners & Services** section is used to manage integrations with external service providers. These services extend platform functionality by enabling additional processing, automation, or third-party connectivity. {% hint style="info" %} Some AI-based services are only available after they have been explicitly activated under [**System Services**](#system-services). {% endhint %} *** ### Overview
The Partners & Services overview displays all external services that can be connected to the account. Here you can: * View all available services * Filter services by status (active or deactivated) * Search services by provider * Connect new external partners * Manage system-provided services Services are activated at the **account level** and are available to all projects and users, depending on permissions. *** ### Connecting External Partners External partners can be connected via the **Connect Partner** action. When connecting a partner, you define: * The **service provider** * Required **endpoints or credentials**, depending on the provider Once connected, the service becomes available for use within the platform. #### Available External Integrations & Services
ServiceDescription
Hive StreamingP2P E-CDN
KollectiveP2P E-CDN
DeepLUsed for translations
PusherLive Reactions
OpenAIGenerate pictures with AI
OpenAIUsed for automatic metadata insertion
*** ### System Services In addition to external partners, the platform provides built-in **system services** that can be activated or deactivated. Examples include: * Translation of texts and subtitles * Text-to-speech generation * Text and metadata generation * Image generation from text input * Realtime event handling for livestreams System services are managed via **Manage System Services** and can be enabled individually. *** ### Data Processing and Compliance Some services may process personal or content-related data. {% hint style="info" %} When activating external or system services, data may be processed by the respective service provider. Information about data processing and sub-processors is available directly within the Partners & Services section. {% endhint %} *** ### Availability and Permissions * Partners & Services are managed at the **account level** * Only administrators can connect or manage services * Availability of services may vary depending on the account (tenant) ### Available External Integrations & Services #### Partner/Integrations
ServiceDescription
Hive StreamingP2P E-CDN
KollectiveP2P E-CDN
BotTalkText2Speech Service Integration
CastLabsDRMToday Integration
Amazon CognitoUsed for Webhook Authentification & Verification if your are using AWS to receive notifications.
#### System Services
ServiceDescription
DeepLUsed for AI translations
PusherLive Reactions
OpenAIGenerate pictures with AI
OpenAIUsed for automatic metadata insertion
Google Used for Audio dubbing
# Billing The Billing section provides access to all billing documents related to the account. It allows authorized users to review, filter, and download invoices for accounting and auditing purposes. *** ### Invoice Overview
The invoice overview displays all invoices issued for the account. Here you can: * View all invoices * Filter invoices by status: * **All Invoices** * **Paid Invoices** * **Open Invoices** * Search invoices * Download invoices as files Each invoice entry includes key information such as invoice status and availability. *** ### Transactions In addition to invoices, the **Transactions** view provides a detailed list of billing-related transactions associated with the account. This allows users to: * Review transaction history * Track charges and payments * Support internal billing reconciliation *** ### Access and Availability * Invoices are generated at the **account level** * Only users with appropriate permissions can view or download invoices * Availability of invoices depends on the account’s billing status and activity # Usage details The **Usage Details** section provides insights into the account’s platform usage. It allows administrators to monitor consumption, analyze trends, and review usage across projects and services. *** ### Overview
The Usage Details overview summarizes key usage metrics for the selected time period. Displayed metrics may include: * Number of projects * Number of users * Storage usage (AVG in the specified period) * Bandwidth (Data transfer volume) * Encoding and transcoding time * AI service usage The displayed values reflect total usage across the account. *** ### Filtering and Time Range Usage data can be filtered to refine the displayed results. You can: * Select a custom **date range** * Filter by **project** * Filter by **usage category** (e.g. storage, data transfer) This allows detailed analysis of usage patterns. *** ### Usage History and Trends Usage data is visualized using charts to show changes over time. This helps to: * Identify usage peaks * Track growth or seasonal trends * Support capacity planning and cost optimization *** ### Project-Level Usage
The Usage Details section also supports project-level analysis. You can: * Review usage per project * Compare usage across different content pools * Identify projects with high resource consumption *** ### Access and Availability * Usage Details are available at the **account level** * Only users with appropriate permissions can access usage data * Availability and granularity of data may depend on enabled modules and services # Personal Area
The **Personal Area** is accessible through the user avatar in the top-right corner of the platform. It provides access to user-specific settings, account-related information, support options, and session actions. The available entries may depend on the account configuration and user permissions. From the Personal Area, users can access: {% hint style="info" %} On top of the menu you can find your Customer-ID which is important when you're calling our Support. {% endhint %} * Personal Settings * Password and Security * Contract Data * Support Tickets * Help and Status * Log Out *** ### Accessing the Personal Area To open the Personal Area: 1. Click your avatar in the top-right corner of the platform. 2. The personal menu opens. 3. Select the desired section. The menu displays the signed-in user, the assigned account, and the account ID. *** ### Personal Settings The **Personal Settings** section contains user-specific preferences and profile-related settings. Depending on the configuration, users may be able to manage personal information, interface preferences, language settings, or other user-level options. Use this section to adjust settings that apply only to your own user account. *** ### Password and Security The **Password and Security** section contains security-related user settings. This area can be used to manage authentication and account access options, depending on the available configuration. Typical use cases include: * Changing the account password * Reviewing security settings * Managing login-related options Access to some security settings may depend on the authentication method used by the account. *** ### Contract Data The **Contract Data** section provides access to company, billing, and contract-related information. This area contains the contract data of the account and can also include contact persons for different responsibilities, such as accounting, technical contacts, users, or external partners. Contract Data may include: * Company or account title * Legal representative * Legal structure * Address * VAT identification number * Commercial register information * Email address for invoice delivery * Telephone number * Contact persons Access to Contract Data is usually limited to users with the required account permissions. *** ### Support Tickets The **Support Tickets** section provides access to support-related communication. Users can use this area to review existing support requests or create new support tickets, depending on permissions and account configuration. This section is useful when users need help with platform usage, technical issues, account questions, or operational workflows. *** ### Help and Status The **Help and Status** section provides access to help resources and platform status information. Users can use this section to find documentation, support information, or status-related updates. This is useful when checking whether a platform issue is known or when looking for guidance on platform features. *** ### Log Out The **Log Out** option ends the current user session. Use this option when leaving the platform, especially on shared or public devices. *** ### Notes The Personal Area is always opened through the user avatar in the top-right corner. The available menu entries depend on user permissions, account configuration, and enabled features. Users may not see all sections if they do not have the required rights. # Personal Settings The **Personal Settings** area allows each user to manage their individual profile, preferences, and security-related options. These settings apply only to the currently logged-in user and do not affect the overall account configuration. ***
### Accessing Personal Settings The **Personal Settings** section is available through the user avatar in the top-right corner of the platform. To open Personal Settings: 1. Click your avatar in the top-right corner. 2. Open the menu. 3. Select **Personal Settings**. #### Profile Information Users can update their personal profile details, including: * Profile image * First and last name * Telephone number * Preferred language * Time zone These settings are used across the platform for localization, notifications, and user identification. *** ### Interface Preferences Users can customize how the platform is displayed: * **Layout:** * Default * Simplified * **Theme:** * Light * Dark * System setting (follows operating system preference) * **Items per page:**\ Controls how many items are displayed in lists.\ This setting is stored locally on the device and is not synchronized across devices. *** #### Upload and Workflow Preferences * **Query file upload source language**\ When enabled, the user is prompted to define the source language when uploading or importing files into on-demand projects. * **Activate approval queue**\ When enabled, additional indicators are shown for shared files and approval status across projects, allowing easier project switching during review workflows. *** ### Password and Security Users can manage security-related settings, including: * Changing their account password\ (After a password change, the user is logged out from all active sessions.) * **Two-Factor Authentication (2FA):** * SMS * Email * Disabled * **Number of active sessions**\ Limits how many concurrent sessions are allowed.\ Older sessions are automatically invalidated when the limit is reached. *** ### Active Sessions and Devices {% hint style="info" %} If you are using both the **UI and the API in parallel**, we recommend increasing the **number of allowed active sessions** to avoid unintended logouts. {% endhint %} * View currently active login sessions * Identify devices and locations * Revoke access for individual sessions or devices * Control browser permissions such as camera, microphone, and location access *** ### Support Access
* **Grant access to 3Q Support**\ When enabled, authorized support staff can temporarily access the account to assist with troubleshooting. # Contract Data
The **Contract Data** area allows account administrators to manage company, billing, and contact information for the account. {% hint style="info" %} This area is restriced to Users with the Adminsitrator role. {% endhint %} This section contains the legal and commercial information associated with the customer account. It can also be used to define important contact persons for different responsibilities, such as general users, accounting contacts, technical contacts, or external partners. From the Contract Data area, users can: * View and edit contract-related account information * Maintain company and address details * Add VAT and commercial register information * Define an email address for invoice delivery * Add important contact persons * Assign contact person roles * Store contact details such as email, phone number, and country The Contract Data area is available from the account-related settings, depending on user permissions. ### Accessing Contract Data The **Contract Data** section is available through the user avatar in the top-right corner of the platform. To open Contract Data: 1. Click your avatar in the top-right corner. 2. Open the account or contract-related menu. 3. Select **Contract Data**. The Contract Data panel opens and provides access to the **Contract Data** and **Contact Persons** tabs. *** ### Contract Data Overview The Contract Data panel contains two tabs: * **Contract Data** * **Contact Persons** The **Contract Data** tab contains company, billing, and legal information. The **Contact Persons** tab contains people who are relevant for communication, billing, support, technical operations, or external coordination. *** ### Contract Data The **Contract Data** tab contains the main account information used for contractual and billing-related purposes. Available fields may include: * Title * Legal Representative * Legal Structure * Address * VAT Identification Number * Commercial Register * Email for Invoice Delivery * Telephone Number The available fields may depend on account configuration and permissions. *** ### Title The **Title** field contains the account or company name. This name is used to identify the contract account within the platform. *** ### Legal Representative The **Legal Representative** field can be used to enter the person or entity legally representing the company. This field may be required depending on the account configuration or contractual setup. *** ### Legal Structure The **Legal Structure** field can be used to enter the company’s legal form. Examples include: * GmbH * AG * UG * Ltd. * Inc. * Association * Public institution Use the legal structure that matches the official company registration. *** ### Address The **Address** section contains the company’s postal address. It may include: * Street and house number * Additional address information * Postal code * City * Country Keep this information up to date, especially when it is used for billing, contract communication, or invoice delivery. *** ### VAT Identification Number The **VAT Identification Number** field can be used to store the company’s VAT ID. This is relevant for billing and tax-related documentation. If no VAT ID is available or required, the field may remain empty or contain a placeholder depending on the account setup. *** ### Commercial Register The **Commercial Register** field can be used to store registration information for the company. This may include the register court, register number, or equivalent commercial registration details. *** ### Email for Invoice Delivery The **Email for Invoice Delivery** field defines the email address used for invoice communication. Use a shared or monitored billing email address whenever possible, for example: * * * This helps ensure that invoices and billing-related messages reach the responsible team. *** ### Telephone Number The **Telephone Number** field can be used to store a general company or billing contact number. Depending on the interface, the country code can be selected separately from the phone number. *** ### Contact Persons The **Contact Persons** tab allows users to add important contacts for the account. If no contact person has been added yet, the page shows an empty state and offers the option to add a contact person. Contact persons can help 3Q or internal users identify who is responsible for specific topics. *** ### Adding a Contact Person To add a contact person: 1. Open **Contract Data**. 2. Select the **Contact Persons** tab. 3. Click **Add Contact Person**. 4. Select a **Role**. 5. Enter the required contact details. 6. Save the contact person. After saving, the contact person appears in the Contact Persons list. *** ### Contact Person Roles When adding a contact person, a role must be selected. Available roles may include: * **User** * **Accounting** * **Technician** * **External Partner** The role describes the person’s responsibility or relationship to the account. #### User Use the **User** role for general account users or contacts who should be associated with the account but do not have a specialized billing or technical role. #### Accounting Use the **Accounting** role for people responsible for billing, invoices, payments, or commercial communication. #### Technician Use the **Technician** role for technical contacts who may be responsible for integrations, livestream operations, platform configuration, or troubleshooting. #### External Partner Use the **External Partner** role for contacts from agencies, service providers, production partners, or other external organizations involved in the account workflow. *** ### Contact Person Details Depending on the selected role and account configuration, the following fields may be available: * First name * Last name * Email address * Telephone number * Country Required fields are marked with an asterisk. #### First Name and Last Name Enter the contact person’s first and last name. These fields help identify the person in internal and external communication. #### Email Address Enter the email address of the contact person. This field is required and should contain a valid, monitored email address. #### Telephone Number The telephone number can be added for direct contact. Depending on the interface, the country code can be selected separately. #### Country The country field can be used to define the contact person’s country or location. *** ### Managing Contact Persons Existing contact persons can be reviewed and updated in the **Contact Persons** tab. Depending on user permissions, contact persons can be added, edited, or removed. Keep contact persons up to date so that billing, support, technical, and partner communication can be routed correctly. *** ### Typical Use Cases Contract Data can be used for different account administration workflows, for example: * Maintaining billing and invoice information * Updating company address details * Adding a legal representative * Storing VAT and commercial register information * Defining an invoice delivery email address * Adding accounting contacts * Adding technical contacts for support or integration topics * Adding external partner contacts for project coordination *** ### Notes Access to Contract Data may be limited to account administrators or users with the required permissions. Changes to contract, billing, or invoice-related information may affect account communication and commercial processes. Make sure that company information, invoice email addresses, and contact persons are kept up to date. # Platform Status The **Platform Status** page shows the current availability and performance of the 3Q platform and its main services. It helps you quickly check whether a service is fully operational or whether an incident or maintenance activity is currently affecting the platform.
You can access the status information in two ways: * In the 3Q platform via **Help and Status → Platform Status** * Externally via [**https://3q-status.com**](https://3q-status.com) The external status page is especially useful if the 3Q platform interface itself is not available. ### Service overview The status overview lists the operational state of the main platform components, including:
ServiceDescription
PlatformGeneral availability of the 3Q platform
Customer Interface / Web UIAvailability of the user interface
REST API / SDN APIAvailability of the API services
DNSAvailability of DNS-related services
Live IngestAvailability of livestream ingest services
Encoding Engine / Encoding SystemAvailability of encoding and processing services
Media DeliveryAvailability of video and audio delivery services
Each component displays its current status, for example **Operational**, so you can identify whether a specific area of the platform is affected. #### System metrics The external status page also provides system metrics, such as encoding queue information and platform uptime. These metrics give additional insight into the current platform load and overall system performance. Depending on the selected view, metrics may be available for different time ranges such as **day**, **week**, or **month**. ### Incidents and maintenance The status page lists both **ongoing** and **past** events. This includes service incidents, scheduled maintenance, and completed maintenance work.
For each incident or maintenance entry, the page may show:
InformationDescription
TitleA short description of the incident or maintenance activity
StatusThe current state, such as investigating, monitoring, resolved, in progress, or completed
Affected servicesInformation about which platform components are impacted
UpdatesTime-stamped messages from 3Q with the latest information
Resolution or completion detailsInformation about when and how the issue was resolved or when maintenance was completed
### Subscribing to updates Customers can subscribe to status notifications on [**https://3q-status.com**](https://3q-status.com). This allows operational teams to receive updates about incidents, maintenance windows, and service changes in real time. {% hint style="info" %} We recommend subscribing to status notifications on **3q-status.com**, especially for teams that rely on the continuous availability of livestreaming, encoding, API access, or media delivery. {% endhint %} # Support tickets The **Support Tickets** section allows users to contact 3Q Support directly from the platform and manage support requests in one place. {% hint style="info" %} If you are experiencing a critical issue that affects the availability of your service, select **Malfunction** as the ticket category. After submitting the ticket, you will receive our support phone number so you can contact us directly. {% endhint %} Support tickets can be used to report problems, ask questions, request assistance, or submit feature requests. Users can create new tickets, review existing tickets, filter tickets by status, and follow the communication history of a ticket. The Support Tickets section is accessible through the user avatar in the top-right corner of the platform. From the Support Tickets section, users can: * View existing support tickets * Search for tickets * Filter tickets by status * Create new support requests * Select a support category * Provide details about the topic * Review the ticket conversation * Check the current ticket status * Re-open closed tickets, if needed *** ### Accessing Support Tickets
To open Support Tickets: 1. Click your avatar in the top-right corner of the platform. 2. Select **Support Tickets**. 3. The Support Tickets panel opens on the right side. The panel shows existing tickets and provides options to search, filter, or create a new support ticket. *** ### Support Tickets Overview The Support Tickets overview displays all support tickets available to the user. Each ticket entry can include: * Ticket title * Short description * Ticket ID * Creation date * Current status Users can click a ticket to open the ticket details and view the communication history. *** ### Searching Tickets The **Search Term** field can be used to search existing support tickets. This is useful when many tickets exist and users want to quickly find a specific topic, ticket ID, or previous support request. *** ### Filtering Tickets by Status Tickets can be filtered by status. Available status options may include: * **Open** * **In Progress** * **Waiting for Implementation** * **Waiting for Feedback** * **Closed** * **All Outstanding Tickets** * **All Tickets** Use the status filter to focus on active tickets, closed tickets, or tickets that require feedback. #### Open The ticket has been created and is waiting to be processed or answered. #### In Progress The ticket is currently being reviewed or worked on. #### Waiting for Implementation The ticket is related to a change or feature that is waiting for implementation. #### Waiting for Feedback Support is waiting for additional information or confirmation from the user. #### Closed The ticket has been closed. #### All Outstanding Tickets Shows tickets that are not yet closed. #### All Tickets Shows all tickets, including closed tickets. *** ### Creating a Support Ticket To create a new support ticket: 1. Open **Support Tickets**. 2. Click **Contact Support**. 3. Select a **Category**. 4. Select a more specific topic or area, if required. 5. Enter the ticket details. 6. Submit the support request. After submitting the request, the ticket appears in the Support Tickets overview. *** ### Ticket Categories When creating a support ticket, users select a category that describes the request. Available categories may include: * **Bug** * **Malfunction** * **Support Request** * **Administration** * **Feature Request** #### Bug Use this category when reporting a reproducible issue or incorrect platform behavior. #### Malfunction Use this category when a feature or workflow is not working as expected. #### Support Request Use this category for general questions or assistance with platform usage. #### Administration Use this category for administrative topics related to accounts, users, permissions, projects, or configuration. #### Feature Request Use this category to suggest a new feature or improvement. *** ### Topic and Details After selecting a category, users can provide more specific information about the affected area. Depending on the selected category, available topics may include platform areas such as: * 3Q Platform * Classic UI * Platform * User Management * Project Management * Group Management * Processing The selected topic helps route the support request to the correct team or context. In the details step, users should describe the request as clearly as possible. Helpful information includes: * What happened * What was expected * Which project or file is affected * Steps to reproduce the issue * Error messages, if available * Relevant IDs, such as project ID, file ID, player ID, or ticket ID * Time of occurrence * Browser and operating system, if relevant *** ### Ticket Details When opening an existing ticket, the ticket detail view shows the full conversation. The ticket detail view can include: * Ticket ID * Ticket title * Current status * Messages from the user * Replies from 3Q Support * Dates and times of messages * Status changes * Option to re-open the ticket, if available This allows users to follow the full support history and review previous answers or updates. *** ### Re-opening a Ticket Closed tickets may provide a **Re-open Ticket** action. Use this option when a closed topic is still relevant, the issue has not been resolved, or additional follow-up is required. When re-opening a ticket, add a clear message explaining why the ticket should be continued. # Guide ### Introduction The 3Q platform provides a REST-based API that enables automation of video workflows. It allows customers to programmatically create and manage projects, upload media assets, configure live streams, and manage playlists. The complete API documentation is available at:\ {% hint style="info" %} The REST-based API is not intended for direct use within a frontend application. We recommend caching or storing responses - such as **metadata** and **playoutIds** for videos hosted on our platform on your own servers. A dedicated Frontend API is on our product roadmap and is planned to be available by the end of 2026. {% endhint %} ### Base URL ``` https://api.3qsdn.com/v3/ ``` *** ### Authentication The API uses **JWT (JSON Web Tokens)** in Bearer format. A valid token must be included in the HTTP header of every request. Each token is linked to a specific user account and inherits the permissions assigned to that user. #### Example Request Headers ``` Authorization: Bearer Content-Type: application/json ``` *** ### General API Information * **Data format:** JSON * **Error handling:** HTTP status codes combined with a structured error object in the response body #### Supported HTTP Methods * **GET** – Retrieve resources * **POST** – Create new resources * **PUT** – Update existing resources * **DELETE** – Delete resources *** ### Resources & Endpoints (Excerpt) Depending on whether you are working with live or on-demand streaming, the following endpoints are most commonly used. A complete list of all available endpoints can be found in the full API documentation:\ *** #### Projects * `GET /projects` – List all projects * `POST /projects` – Create a new project * `GET /projects/{projectId}` – Retrieve project details * `PUT /projects/{projectId}` – Update a project * `DELETE /projects/{projectId}` – Delete a project *** #### Files (Video or Audio Assets) * `POST /projects/{projectId}/files` – Upload a media file * `GET /projects/{projectId}/files` – Retrieve the file list * `DELETE /projects/{projectId}/files/{fileId}` – Delete a file *** #### Livestreams * `(GET | PUT) /projects/{projectId}/live/ingest` – Configure or retrieve ingest settings * `GET /projects/{projectId}/live/output` – Retrieve playout URLs *** #### Playlists * `GET /modules/playlists` – Retrieve all playlists * `POST /modules/playlists` – Create a new playlist * `GET /modules/playlists/{playlistId}` – Retrieve a playlist * `PUT /modules/playlists/{playlistId}` – Update a playlist * `DELETE /modules/playlists/{playlistId}` – Delete a playlist *** ### Error Handling The API uses standard HTTP status codes to indicate the success or failure of a request. #### Common Status Codes * `200 OK` * `201 Created` * `400 Bad Request` * `401 Unauthorized` * `404 Not Found` * `500 Internal Server Error` #### Example Error Response ```json { "error": { "code": 401, "message": "Missing JWT Refresh Token" } } ``` *** ### Pagination & Filtering Many endpoints support pagination and filtering through query parameters. #### Example ``` GET /projects?limit=10&offset=20 ``` *** ### API Versioning * **Current version:** v3 * The API version is embedded in the URL path (e.g. `/v3/...`) # Webhooks #### What are Webhooks? Webhooks are server-side push notifications that are triggered by specific events within the 3Q platform. They allow external systems to react automatically to changes or actions without the need for polling. Typical webhook events include: * A video asset has been uploaded or updated * A livestream has started or ended * Processing or encoding states have changed *** #### Configuration
Webhooks can be configured in the **Notifications** module. For each webhook, the following settings can be defined: * Target URL (endpoint that receives the event) * Secret for request validation * Event types to subscribe to Once configured, the platform sends an HTTP request to the specified endpoint whenever the selected event occurs. *** #### Example Payload Webhook requests include event information as URL parameters and a structured JSON payload in the request body. **Example request URL:** ``` /{path}?ProjectId=105489&FileId=11778933&event=file.new ``` **Example payload:** ```json [ { "Event": "file.new", "ProjectId": 105489, "File": { "Id": 11778953, "Name": "uploads/105489-R4WnjV2PzrXY8yN6dTp9.mp4", "IsFinished": true, "IsEncoded": true, "UseEncoding": true, "EncodingPriority": 50, "HasErrors": false, "Metadata": { "StandardFilePicture": { "AspectRatio": "1:1", "AspectRatioClosest": "1:1", "FilePictureId": 13384417, "URI": "https://sdn-global-prog-cache.3qsdn.com/105489/files/25/07/28/11778953/483c1dd0-cb5d-4572-80b0-73376a000be3.jpg", "ThumbURI": "https://sdn-global-prog-cache.3qsdn.com/105489/files/25/07/28/11778953/c9040770-4129-4fcc-a4c1-3ff6c5aa54f8.jpg", "SrcPictureURI": "https://sdn-global-prog-cache.3qsdn.com/105489/files/25/07/28/11778953/7bac5606-9e16-48ee-9560-87c853204dec.jpg", "IsStandard": true, "ManualUpload": false }, "Title": "Rikscha Quadrat_Intern_1.mp4", "Description": "", "DisplayTitle": "", "DisplayTitleSecondLine": "", "ReleaseStatus": "unpublished", "Category": [], "IABCategory": [], "Share": [], "Videotype": [], "OriginalFileName": "Rikscha Quadrat_Intern_1.mp4", "CustomMetadata": { "adsDisabled": false } }, "CreatedAt": "2025-07-28T12:23:14+00:00", "LastUpdateAt": "2025-07-28T12:25:49+00:00" } } ] ``` *** #### Security Webhook requests can be secured using **AWS Cognito signature validation**. This allows recipients to verify the authenticity of incoming webhook requests. AWS Cognito can be connected to the 3Q platform in **Account → Partners & Services**. Once configured, webhook requests will be signed accordingly. # Release Notes ### Information about updates and maintenance work To ensure stable and secure operation, we continuously perform system updates and maintenance work on the 3Q platform. Updates are usually rolled out gradually. First, they are deployed to a limited part of the platform as a **canary release**. During this phase, we monitor the system closely to verify that all services continue to operate as expected. Once the update has been successfully validated, it is rolled out to the entire platform. Critical updates may be performed at short notice, especially when they are required for security, stability, or operational reasons. Current information about planned maintenance, ongoing maintenance work, or service incidents is published on our [status page](https://www.3q-status.com/). ## Releases ### 2026-08-17 New UI **New:** * Analytics now start with a Dashboard including KPI Tiles * The last Analytics Segment, Ads, is now available * Live Reactions are now supported in Analytics/Engagement * File Analytics now show Retention Curve (if enough Views and the Item is not too short to compute usefull insights - there are still Reporting Issues in the Player, we will take care of that asap) * File Analytics now have a "file version" filter (if the file was updated before) to allow to see performance for each Version * LiveStreams now show a new Tab with realtime Visitors per minute of the last hour (if online) * Platform now exposes a security.txt and therefore supports this standard * Live Status Widget shows FPS * TextTracks Properties can now be modified after Creation: * this is useful if the language/role was initially wrong or its an old subtitle and they want to indicate its AI-generated * that also means, that the edit button now edits the Properties and a new Button edits the Content of the TextTrack, which will be slightly confusing for a short time. **Fixed:** * Fixed Category/Type/People Adding from within Sidesheet crash when corresponding lists change * Fixed Podcast/Playlist/MRSS Export Multi Buttons lose all options after a new Item has been created in Files Area * Fixed Crash in File Wizard when Categories/Types/People were set as mandatory * Fixed changing chart-type in Analytics hides Legend * Fixed misleading "create Ticket" dialogue on Browsers with "custom Select", as the category was initially filled without showing the subcategory * Fixed Success Dialog when updating Impersonation Settings * Fixed "custom Select" shows always a Value, even if none is set and the Attribute is not mandatory * Fixed selecting one day as a free Date in Analytics destroys UI and renders in wrong Resolution (if at all) * Fixed Crash on comparing two different Date Periods when Grouping is Weekday * Fixed all Values are 0 on compared Date Range when comparing two different Date Periods in any KPI that is not PlayerStarts * Fixed while using Stacked-Bar Analysis on one Day, the Bars dont switch to Hours, they continue on Day Resolution * Fixed Content/Media Age does not load when Chart Display is Stacked-Bar * Fixed Chart Legend is not draggable on Touch Devices * Fixed Chart Legend might be invisible on small Desktop Devices * Fixed Charts sometimes show generic Error Message instead of Platform UI Error * Fixed Links Overview Page does not show History Tab * Fixed VOD2Live Events cant be saved if File is shorter than 1 Minute. * Fixed Navigating with Browser Controls back and forth on Analytics does not indicate the current Tab correctly * Fixed switching between LiveStreams via Navigation Rail leads to uncorrectly constructed Widgets * Fixed starting a Video Recording for the first time does not set the default Aspect-Ratio and allows non-restricted Recordings * Fixed Category/Type Sidesheet becomes unusable when the response had an error * Fixed Categories/Types dont actually update metadata when updating * Fixed Trimming does not show Audio Waveform if Project uses CSP * Fixed LiveStream "Stream" Player does not apply CSP correctly * Fixed iFrame "white flash" issue that happens on initial load in Darkmode, which was open since a very long time * Fixed closing a Ticket on mobile does not work * Fixed Playout Lists in the default Sidesheet dont show Options anymore * \[Safari] Fixed an issue with searchfields in Safari that made it impossible to enter new search term **Changed:** * Advanced Analytics is now in the list of promoted Modules for Users (with the necessary permissions) * reduced available Setting for Analytics on mobile devices to make Footer UI better useable * the Streamkey in LiveStream Distribution is not mandatory anymore * Geo Heatmap Analytics is now also available on File Level * Chart Analytics have been re-designed to look more like usual File Lists and less than a Graph * Ticket Creation has been updated to drop Area Input, when Category was set to "Administration" - also, "Area" is now optional * refactored robots.txt approach to at least allow URL Preview Cards * as the "Stream" Player in the LiveStream View is not actually openable in another Window, the "open" Button appears now only when the Live Player is shown * Live Reaction Analytics is now an Overview - it does show the given Reactions themselves now instead of only Sums per Day. ### 2026-08-17 API v3/Classic UI * The API v3 Analytics now support retention segment analysis. * We have made changes to how metadata is handled in the v3 API. The standard metadata field "Title" is now a translate object. * An issue resulting in preview pictures not being displayed in the Classic UI file list has been fixed. ### 2026-08-12 API v3 To improve consistency, user preferences endpoints now return null when they are empty. ### 2026-08-10 Backend We improved the handling of recorder states to improve the resiliency against irregular states. ### 2026-07-31 New UI **New:** * the new "Links" Module is now available. It allows adding lists of Links onto various Entities: * Files, LiveStreams, Playlists, Podcasts and People are supported, thats why a lot of Sidesheets have been changed and updated (if the Module is active) * Links are globally unique and dont apply to specific Projects only (unlike Tags) * if a Company books this (free) Module, any user with Edit Rights can add (new or existing) Links on any Model, they have access to * Links can be managed for Files in Default Metadata * Links can be exported in all Contexts in List Exports * only Editors/Admins have the right to edit or delete existing Links in a Link Overview * Links are included in GlobalSearch, but only if the User has Access to editing them * multiple changes and new functionality in Analytics: * All "Timeline based" Analytics show now additionally a "resolution" Filter where the time grouping can be controlled, so far it was only "hours" if the duration was one day or less and "days" if longer. * now, also Month, Weekday and "local time" are available * this works in main and file-based Analytics * Analytics "Charts" are now available (for Advanced Analytics only) * this type of Charts shows the "Top 10" Items for a selected set of KPIs. All Filters, Timelines and Project Sets still apply. * the Excel/CSV Export of Charts add the (not in the UI visible) ID of the File for better Reference * Analytics "Content Analysis" is now available (for Advanced Analytics only) * this type of Charts shows Information of streamed content, most often used is here: * list of Categories (or Types), how old the media was, when it was streamed * on clients with many projects, the overview of which projects deliver how much to the full amount is also often very interesting * Analytics "Engagement" is now available (for Advanced Analytics only) * this type of Charts shows Information on any form of interaction with the media, most often used is here: * display mode (Fullscreen, inline, pip, etc), downloads (attachments), sharing * The Group Management Area has been expanded to show the list of assigned users and assigned projects on each Group. * these lists are also searchable, and the Group Assignments of these "items" (i.e. Users or Projects) can be edited from within these lists directly * Users can now set a country in their Profiles (or, an Admin can set a Country for them - or, Company Details can define a country) which will be used to render Names (Country-Name-Ordering Rules), Week Starts (in Analytics/FASTChannel Calendar Views), Temperature and Distance Units * previously, this was done by the current country at session time, which was obviously not ideal * for consistency, People/Person and ContractPersons also support a country Attribute now **Fixed:** * Fixed Pipeline SourceLanguage allowed Languages that are not supported in SDN (for this context) * Fixed Geo Position UI opens even if no Value is set * Fixed the UI might ask for Geo Permission, even if it has been blocked before * Fixed People Cover cannot be deleted * Fixed minor UI Issues in Billing * Fixed inconsistent UI when on a no-results Screen with active Query and set Search Filter, the user clicks the offered "reset search" button * Fixed Issues with new "Customizable Select" not updating the currently selected value, if this value changes often and repeatedly * Fixed Export Attribute List is not searchable * Fixed Paginator is cleared when navigating between Tabs initially * Fixed an Issue with Favicon Animations when not initiated in time * Fixed LiveStream Distribution Target Platform is not updated and initially wrong during Editing * Fixed Cover Upload offered Cropping on SVG and ICO Files * Fixed Access Blocked on User Management, even if the User was Group User Admin (but not have global User Access Management) * Fixed if an Admin User manages their own Group Assignments, the list of "all groups" in their account was set to their Groups, not all Groups * Fixed Usage History shows only 1 Project even when multiple are available * Fixed Crash on mobile devices while scanning a QR Code as Link/VCard * Fixed User Area has no valid Texts for User Adding on mobile Devices * Fixed Module Order in Navigation Rail / Module List was never correct in FireFox * Fixed Category/Type/People Options in automatic Playlists offered to add new Options (which destroyed the layout) * Fixed "adding Query" Paper in automatic Playlists appearing out of Sight * Fixed Player Selection in Browsers with Support for "Custom Select" show a destroyed Layout * \[WCAG] Fixed Analytics TimePicker is not selectable by Keyboard * \[WCAG] Fixed navigating GlobalSearch with Keyboard does not memorize the last left entry when returning focus * \[FireFox] FireFox still has issues with various anchor-positioned Papers, some Fixes were applied to manually override its Issues to at least show them "somehow" at the right position until those Bugs are Fixed ### 2026-07-31 API v3 * You can now access the charts report in the v3 API. Please note that this report is only available to customers who have booked the Analytics Advanced module. * We have added additional insights to our analytics advanced API such as which player and playout was used and which types and categories were assigned to the file. Please note that these insights are only available to customers who have booked the Analytics Advanced module. ### 2026-07-30 API v3 * We now offer a new module for managing external links. Once created a link can be assigned to a file, podcast, livestream, playlist or person. * Fixed a bug which prevented the removal of cutouts from a file. ### 2026-07-30 API v3 * We have added engagement endpoints to our analytics advanced API. These endpoints give you information about downloads, reactions and other types of engagement with the files. Please note that these endpoints are only available to customers who have booked the Analytics Advanced module. * We fixed an error where empty custom metadata were not returned as "Null" as is the case with other empty fields. ### 2026-07-28 API v3 * The user endpoints now expose a country which affects user specific preferences like the start day for the week. * Fixed a bug that prevented the creation of custom metadata fields in the API v3. ### 2026-07-27 API v3 Analytics calls that accept a resolution now support the additional values "weekday" and "localHour" (this groups the events based on the local time of the playback sessions shown in the analytics). ### 2026-07-23 API v3 We now offer a new module for managing external links. Once created a link can be assigned to a file, podcast, livestream, playlist or person. ### 2026-07-20 Transcoding * Fixed a bug where the player would sometimes switch to DVR mode event though timeshift was not active for the stream. * Restreaming/3rd Party Publishing of VOD2Live signals is now supported. ### 2026-07-20 API v3/Backend * Fixed a bug that resulted in muxed URLs not working after moving a CMAF encoded file without encoding. * It is now possible to restream VOD2live signals with our livestream distribution module (previously called 3rdPartyPublishing). * Real time analytics data for livestreams are now available in API v3. * You can now access the charts report in the v3 API. Please note that this report is only available to customers who have booked the Analytics Advanced module. * Fixed a bug with our pipeline feature. Previously changing the source language of a file in the pipeline would return a 500 error. ### 2026-07-16 New UI **New:** * Categories, Types and People can now be added directly from within any File (or, in case of a LiveStream, the Stream Metadata) on the corresponding Pickers, if Module and Permissions are available * these Metadata are therefore now manageable directly in the Module UI, from within Files via Multi-Edit and now also directly from a File, if necessary **Fixed:** * Fixed Updating a Project Title from within the Project does not change the current Page Title * Fixed Creating a Category from within a Project does not check for Project Update Permissions when this Project is Category-Restricted and therefore must update the Project itself too * Fixed Accessing Project Settings from Navigation Rail while on Non-Project Area might crash the UI (Timing Issue in Page Update Mechanism) * Fixed login Page /saml Redirects were intercepted by new UI, but should have been moveed to a Server Request * Fixed a reload() Call was intercepted by the new UI, but should have acticely reloaded the Page **Changed:** * Phone Number Selectors have been refactored for a bigger Area to select Countries, highlight the Code, not the Country and cleaned up Error Handling * added Wakelock Management when uploading huge Attachments * added Network Status Warnings when uploading huge Attachments ### 2026-07-15 API v3 Fixed a bug where the language setting of a video's audio track was sometimes not used when manually triggering transcription. ### 2026-07-14 New UI **New:** * (Module) Notifications now have an Option to show their "history/log" like in classic UI * VodLive Events now also add a (Platform) Notification, shortly before this Event starts (this exists also in Logs, but now the UI will show a dedicated Notification here too) * Standard File Attributes can now have (custom) Titles in English and German - the UI will take care of those new Naming Options in (hopefully) all Scenarios and Places * the Company now has a setting to define a "custom embed Url", that the UI will apply to all playout management Panels * as this is the first and only "company setting", it is placed currently in the Players Area in a Modal, until we have more Company Settings for a full panel * added Support for Watermark Size and Offset in Transcoding (Worker will release this soon) * added Support for bitrateMultiplierForHighFrameRate in LiveStream Transcoder Settings, LiveStream Recorders and LiveStream Distributions * as this is a highly specific Setting which is hard to explain and understand, we added an "advanced Settings" Tag for Transcoding and Recorders to place it under (that existed already in LiveStream Distribution) **Fixed:** * Fixed max-block-size of main Analytics Chart View restrictions to not reach floating time selectors * Fixed width/height was rendered with "Thousand Seperators" which is not common practice on Dimensions * Fixed Analytics with StackedColumns dont format Dates correctly * Fixed VoDLive Error Handling when a User tries to create an Event when there is a different Event on this Stream already * Fixed Integration Sidesheet sends partly wrong Integration Config on all Providers * Fixed some Text Inconsistencies in Module Booking * Fixed Trimming UI not working with Touch * Fixed missing Translations in User Browser * Fixed Intl Numberformat in German where there should be a thin-space between Numbers, but Intl disagrees. * Fixed Crash on Company Contract Data View, when User was Group-Admin, but not regular Admin * Fixed broken Project Tag Management UI due to malformed Project Caching * Fixed Crash on Login on Samsung Browser (android) * Fixed Module Lists (on Users, on Multi-Select and on Filter) should only show assignable Modules, not all supported ones * Fixed Edgecase not resetting scroll-position on Content-Reset * Fixed Project Usage Overview does not render Project Names on Companies with huge Project Lists. * Fixed SRT Audio Language List UI * Fixed Navigation can go back to /login Page with Browser Navigation **Changed:** * removed Link to Classic Analytics * Analytics DrillDown and Analytics TimeCompare now need the AdvancedAnalytics Module and also the current User must have disabled basic mode * Chart Type Toggles was restricted by Basic Mode but is now available for anyone * Advanced Analytics are now available for any User that has Access to Analytics anyway - it is not assignable anymore * videoProfile was removed from HEVC Encoding Settings, as we currently only support (kindof) "main" * TextTrack Language Usage Analytics KPI now also shows "an estimate" of Playbacks without any used TextTrack. That is not easy to compute, so we use an estimation for better performance, that should work most of the times. * So far, Editors were able to see and sometimes even edit Company Data. This Permission was refactored to admin-only and the readonly option of Contract Data has been removed totally from the UI * the minimal Tag Length was reduced to 2 Characters (3 previously) * Project Usage Overview now renders Project Id and Project Name per Row, as both seem to be interesting ### 2026-07-13 API v3 * We now apply a high frame rate multiplier to the bitrate of livestreams with a FPS of higher than 30. The multiplier can be set via API v3 and defaults to 1.5x the bitrate set for each resolution. * We have made changes to how metadata is handled in the v3 API. The standard metadata field "Title" is now a translate object. ### 2026-07-10 API v3 You can now select the exact sizing and placement of your live watermark. ### 2026-07-08 Backend Fixed a bug where videos could still be played for some time after they were deleted. ### 2026-07-07 API v3/Backend * We have improved the timeouts of the emergency stop livestream functions. Now after triggering a stop, another stop or kill command can not be issued for one minute. After triggering kill, both commands are blocked for 5 minutes. * If you are using the Notifications module, you can now access a log of notification events via the API v3. ### 2026-07-01 New UI **New:** * the User Area now supports a Filter to filter Users by any assigned Module * Analytics are now available. This is a huge addition to the ui and is very different from the classic ui. * the "full" analytics are available for anyone who has at least one project of type live OR ondemand with full read rights (at least) * for now, only "performance" and "environment" Sections are supported and also only one KPI at a time * File-specific Analytics are supported (for anyone with at least read-rights on this file) * Chart-Type Toggles are supported * Free Date Ranges are supported * Drill Downs are supported (on some Pie Charts) * Comparisons are supported (on some Timeline Charts) **Fixed:** * Fixed Categories/Types dont show Option for Uploading Covers anymore * Fixed Category/Type "new" Button dont update on changing Context * Fixed Playout Toolbar Position on Custom UI * Fixed AI Glossary does not offer all Languages that TextTracks Support * Fixed LiveLog Search does not return results if Dates are not empty * Fixed new List-Item-Action Animation is not working correctly in DarkMode * Fixed Usage KPIs on Detail View are not updated * Fixed iFrame BG Color in Darkmode * Fixed Project Integrations did not distinguish between different Providers of the same Type during Project Assignments * Fixed OCR Confirmation Dialog * Fixed Issues in User Export * Fixed AmazonCognito Integration Config does not show URL * Fixed Login/Password Reset UI dont show Button Labels on mobile Devices * Fixed Date/Time/Month Inputs on android showed double Input Helpers (in Chrome) **Changed:** * updated Support Number when reporting a critial outage * Encoding Settings / Pipeline Settings now show an Error if the Settings have no CMAF BUT want additional AudioTracks ### 2026-07-01 API v3 + Backend * Core analytics performance calls are now available via the API v3. * We have added Indonesian and Vietnamese as translatable subtitle languages for live and on demand subtitle. ### 2026-06-26 API v3 Environment analytics data is now available in API v3. ### 2026-06-25 New UI **Fixed:** * Fixed Chatbox in Support Tickets blocks Text Paste for Files * Fixed an Issue when uploading Covers and Attachment with non ISO-8859-1 compatible Names * Fixed an Issue with initial URLs that will be opened in a Sidesheet, but dont belong to the main content. They opened and closed immediately after. * Fixed a broken Translation in Module Booking/Cancelling **Changed:** * The Ticket UI now shows the Ticket Id ### 2026-06-25 Backend Fixed a bug where processing got stuck on uploaded additional audio tracks. ### 2026-06-24 Backend Automatic playlists now update more often. A check is made for added or removed files every 15 minutes. ### 2026-06-23 Backend * Fixed a bug where csv files would be downloaded with a txt extension. * Fixed an OpenAPI validation error in our API v3 documentation ### 2026-06-22 Backend We now support an optional multiplier for livestream projects which is applied to streams using high frame rates. ### 2026-06-22 New UI **New:** * Live Stream Projects now support the Type "HLS Pull", which means, a HLS Stream (from a given URL) is "passed through" * A few UI Details work differently (no Endpoints, no Status Widget, no VOD2Live Events) * Some settings are not available (mostly Low-Latency and automatic Fallback). * Indonesian/Vietnamese were added as Live-Translateable TextTrack Language * Vietnamese was added as OnDemand Translatable TextTrack Language **Fixed:** * Fixed Sidesheet/Modal Buttons on mobile have no labels * Fixed SplitButton Flyouts on mobile have no translations * Fixed Covers with specific Origins dont upload successfully * Fixed if a Video is used as PreLive Video and the User tries to delete it anyway, the UI is misleading and does not show an error. * Fixed Trimming UI Sidesheet is not scrollable * Fixed Trimming UI does not apply ContentProtection if a source file must be played * Fixed Notications dont use optimized Images * Fixed Race Condition on API Access Token Updates between multiple Tabs * Fixed broken UI for Pipeline AudioTrack List with partly uploaded Tracks * Fixed Rendering of LiveEvent Time-Ranges in Stream Widget **Changed:** * marked PhoneNumber as mandatory, once a PhoneNumber has been set on the active User * AudioTrack Management has been removed for Audio Files (for now) * it has been decided, that Files without CMAF should not offer to add AudioTracks. Therefore, a new Error Dialog was added in case a User tries to added an Audio Track to a non-CMAF file * by heavy demand, the "CutOut" Tool in Trimming has been expanded to allow to use the Player to get the current Position as start/end of a CutOut * changed Display of width/height visual dimensions to comply with internal rendering rules here too ### 2026-06-19 API v3 * We now support HLS input to our livestream project. * Fixed a bug where changing personal settings would sometimes turn off 2 factor authentication for a user. * We have added Indonesian and Vietnamese as translatable subtitle languages for live and on demand subtitle. ### 2026-06-17 New UI **New:** MediaRSS Exports (previously known as MediaShare) are now available * they work very much like a Playlist/Podcast in the new UI, and are more visible as in the ClassicUI * they are integrated into Multi-Selection Operations in Files, you can also create new MediaRSS Exporters directly from the Files Selection * MediaRSS Exporters also appear in GlobalSearch * Manual Exporters can now show all currently existing Files (and you can remove them from the Feed) in the MediaRSS Section * Automatic Exports can now additionally filter: by category, by person, by filetype and by aspect ratio (like automatic Playlists) * at least for now, the (confusing) Fields that allow setting a "title field" and "deepLink field" are hidden (like the new UI so far does with the Podcast Field Settings too) The Navigation Rail now shows Promo Tiles under various Conditions * in general - if there is enough space and the user is missing "crucial" modules for his projects and they have the necessary permissions and they did not deny promos, the UI will decide in certain situations to show a "Promo Tile" for a module, that might be helpful for this user * The Media Analysis Pipeline has been massively refactored and is now based on MediaInfo (WASM). That means, that now all Browsers can read Audio Tracks and therefore preselect the right AudioLanguage in the Upload Dialogs (or, if MultiAudio or NoAudio, mark the specific Flag) * the UI now extracts Covers from Videos too (if there is a Cover Track, like it is doing already with Audio) and displays that Cover instead of a live Screenshot as before * although supported before, the UI can now far better detect HDR Video (and also, 360° Video :P) * the UI now also writes GPS Data, if some are found in the Videofile directly via API (if there are enough Rights) - this will be done in the Backend some day, but for now, the UI is handling this. * The Notification Modules now supports "Project Type" Notification (that are emitted on creating/deleting Projects) Trimming now supports "CutOuts" * meaning, besides trimming from the start/end, Users now can define Areas within the file that will be excluded from the final File (these are called "CutOuts") * the behavior of the UI also changed here - when a File was trimmed before, the form now shows the previous settings as a starting point * Trimming CutOuts are also supported in the Pipeline - as the UI now needs more Space for this bigger UI, Trimming is now in a seperate Tab **The Ticket System is now available (with a few differences from the current version):** * not everyone is allowed to use Tickets anymore, thats now a Right in the Role of the User * The Ticket UI will now start with a Pre-Page, that asks for Category, Severity and affected Areas, depending on Context might even suggest a Phone Number * Tickets and Replies now allow up to 10 Attachments each * Ticket Attachment are rendered fully (if an image) and can be forced to Fullscreen Display (unless its iOS) * Ticket Status now covers all new Status Values * Ticket Updates are now visually indicated by a Badge on the Users Profile Image and in the User Paper Ticket Item - if there was an Update to a Ticket, the currently logged-in user created **Fixed:** * Fixed confirming any Operation within a Modal doesnt close the Flyout on mobile Devices * Fixed Coverlist on Files dont show AI Options, even if available, on mobile * Fixed Modules Area in Navigation Drawer is not scrollable * Fixed Projects Label in Navigation Drawer is unreadable, if no access to Project Area itself is allowed * Fixed Query History was deleted every 15 Minutes * Fixed Crash on RenditionList if Files have no originalFilename * Fixed MediaRSS is not assignable to Users * Fixed some Modals with multiple Footers are not usable as the Footer never changed * Fixed Storage/Bandwidth Values in Usage were not consistently rounding to 2 Digits, so the values were sometimes hard to compare * Fixed Playouts were rendering Start Time on Non-File Contexts * Fixed an Issue with Videos, recorded in Portrait Mode on a mobile device might create distorted Preview Images * Fixed an Issue with the Geo API, which blocked all calls, even if not related to the User consent * Fixed editing Transcoding Settings does not highlight currently active Entry * Fixed navigating Usage Area is broken on mobile Devices * Fixed Trimming opened the Trim UI automatically, even if the Player would have to use the source file (as the file might not be encoded yet - or has been trimmed before) * Fixed Warning for Realtime Event Position could appear even if the User is not allowed to have Realtime Events (due to lack of Pusher Service) * Fixed Category/Type Names are not shown correctly when using Batch Action in Files * Fixed Rendering of Audio/Video Codecs with trying to gather the "real" Codecname and not the extremely verbose current Descriptions * Fixed long Papers with scrollable Areas are not navigable with Keyboard * Fixed AI Chapters dont create Descriptions, ignoring Preference * Fixed File Upload Wizard uses wrong Animations for Panels * Fixed Contract Persons cannot update their Phone Numbers * Fixed Async Tasks do not correctly show their Work Result in Notification UI * Fixed Charts dont update themselves to Darkmode when Theme is changed after Chart was rendered * Fixed Group-User-Admins cannot save new roles on Group-Users **Changed:** * added more LiveStream Distribution Target Platforms with Logo by parsing the ingest url for well-known Target Strings (not saved in API, yet) * added a way to localize the Order of Address Fields based on a Country - currently used only in Company Data (and as we don't have a User Country, currently using the Session Country) * updated UI for "Trailing Icons" in List Views to avoid resizing Labels * updated UI for "Bottom Buttons" in (very long) List Views to allow adding a new Item even when the list is scrollable * added explicit buttons to OS-Level Notifications for better visibility * Module Management and Banners now respect the "trial" State of a Company and adjust the Wording here * all module booking texts now respect the "trial state" of the company and adapt to its state * it was decided that all Live Widgets should have an identical search bar, so Recorders/LiveDistributions now offer a Search too. Main Reason for this is to remove the "bottom-add" List UI, which could move to the Searchbar now * furthermore, the Event Widget now has a Filter to toggle between the different Event Types * it was decided that while creating a VOD2Live Event from within a LiveStream and the User has the necessary Permissions, it should be shown initially (but inert) * Detail Usage will now update the KPI Tiles and KPI Selector to not include "Projects" when a single Project is selected * the Projects overview now also shows if a Project has active Notifications (if the User has the necesary Permissions) * The Filter UI and Handling has been refactored * the "close" Button is now red on focus/hover to visualize its importance * once a value is selected, the close button now stays active (the opposite behavior than before), changes its form, label and behavior - it now clears the value and NOT remove the button * when at least 2 Filters are active/selected, there is now a "clear all" Button ### 2026-06-17 API v3 In the API v3 it is now possible to remove unwanted sections from the middle of files using out trim function. ### 2026-06-11 API v3 Fixed an issue where a small number of preview pictures were not returned in the new UI. ### 2026-06-09 API v2 Fixed deprecated embed URLs in the v2 API. ### 2026-06-08 API v3 Our alerts module now includes an option for projects. With this event types you will receive updates if a project is created, deleted or updated. Please note that this new option can only be configured in our new UI or API v3. ### 2026-06-05 API v3 Fixed a bug which prevented a user from updating their last name in the new UI. ### 2026-06-04 Backend Fixed a bug where files with apac audio would not encode. ### 2026-06-03 Webcast Fixed a display bug with the size of the chat box in webcast template version 2. ### 2026-06-01 API v3 You can now manage your mrss feeds in API v3. Please note in the classic UI this module was called "Media Share" ### 2026-05-29 API v3 Fixed a bug in the podcast API where deleted files would sometimes be included in the list of episodes. ### 2026-05-15 New UI Release **New:** * AI Image Generation/Editing got a new Setting, the "quality" of the model can now be configured (that is now a new AI Preference, like the Text AI Preferences). It defaults to "medium" now. * AI Chapter Generation now has 2 more options: * the maximal length per title can be defined to avoid extremely lengthy title as before * optionally, the AI can now also return descriptions, that are also applied to all created Chapters (and shown in Preview) * the UI now extract Audio Covers from an uploaded Files Metadata, if available, and displays it in all relevant contexts * added "delete" as Multi-Action on the User Area, which was missing before * added "create new Group" as Multi-Action Option in the Group Multi-Action in the User Area * added "group" as Multi-Action on Project Area, including "create new Group" like in User Area * added "move/copy" as Multi-Action on Files Area, thanks to new Backend move/copy Queues * Player Settings support the "hide Menubar during Fullscreen" finally again * the new setting "constantMuxRate" is now supported in LiveStream Distributions * The personal Settings Area now has a second Tab, which (finally) allows to finetune some "preferences", that are not stored in the User Database, but are only used and defined by the UI (but are synchronized between all devices) * this was so far an issue, as some of these Settings were asked only once and couldnt be changed afterwards * the current list lists only settings that are already set (and the user might want to remove) or that would make sense to be set/changed at any time. Still this is a first selection, it will definitely change often. * all List Exporters now support "apply current view settings" * meaning, it wont export ALL existing items anymore, but it will apply the same Filters, Search and Tab Logic from the main view before Exporting. * still, the user can select, if they want this kind of Export or the previous "export all items" **Fixed:** * Fixed an issue with Playerlist does not update available Players on a Project, if the Playerlist of this project was opened before * Fixed "purge timeshift" Button appeared under certain circumstances, although there was no Timeshift to purge * Fixed Radio Options are forced into one line, even if they are too long and not readable like that * Fixed Card Icons are not visible on Firefox * Fixed Trimming UI Labels are broken in Firefox * Fixed StreamKey only accepts ASCII, but Youtube Keys also allows Hyphens. * Fixed Image Upload Errors are not removed in the UI after selecting another image * Fixed shown Unit for Stream Quality, its given in Kilobit, but was rendered as kB/s (which would be kiloBYTE/s) * Fixed LiveClipping allowed Times in the Future * Fixed LiveClipping does not react correctly to Online-State Change of the current Stream * Fixed Card Icon Hover does not work in Darkmode * Fixed Geo Permission is checked too early and Map Search might not work reliably after allowing Access * Fixed Creating an AI Image from File Covers has the wrong Context * Fixed adding/removing Users to Groups do not reset internal Cache (and Groups dont update their Reference Count, which might lead to they are deletable, but cannot be deleted) * Fixed adding a Category/Type/Person within the File Multi-Select Dialogue does not update the filters/multi-action papers with the new item * Fixed Issues with Errors for a minimal/maximal length in Multi-Language Input Fields * Fixed an Issue with Notification Settings do not clean up completely when changing type * Fixed an Issue with LiveStreamDistribution Settings, that cannot be saved again, once they were saved * Fixed Rendering, Texts and Logic of the "cannot start without internet" page, that appears in PWAs when offline * Fixed Issues with relative Time display, where the context is "date only". In this case, the ui still considered hours and minutes, not just days. * Fixed adding Text with SpeechRecognition clears current value and overrides it. Now, it will append newly spoken Text if the target is a TextArea. * Fixed broken QRCode Detector on mobile devices and apply latest Camera UI to its Layout * Fixed various Filters and Selects didnt order correctly by language rules but simple comparison. Those have been updated to use the sorting orders of the currently selected language * Fixed some Project-Change Issues in Files when search was active **Changed:** * LiveStream Projects are now better aware of the type of content they are streaming, if its a vod2live: * the Project Icon forms to a vod2live Icon * the signal-state and player-stream options are disabled in the project view * Players that have AES-Encryption Support active now show an Icon for AES in the Overview * AES-protected Manifests now show an Icon to signal that in the Streaming URl overview (and with a Text in the Url Detail View) * it is not possible anymore to update the current company name * if a user wants to clip timeshift, the Player will now automatically open (unless on a phone) * on Trimming (a file), the Player will also automatically open, unless on a phone OR the file was trimmed already OR the file is not encoded yet * when a user opens "Timeshift and Clipping" when the Stream is currently online, the UI automatically starts the editing process on the live clip * the Trimming bar is now accessible by keyboard and also includes now a lot of aria values to make it useful without a mouse/touch * for "basic mode" Users, the Trimming UI now shows a Help Text on how to use the ui * if a user opens Trimming when the Stream is live, the "live" part of the List will be automatically initially opened now * the File Upload Entries now also show their corresponding "Upload Speed" (in Mb/s) * for Performance Reasons, TextTrack Editing has been refactored (again) - the UI now only manages one contentEditable Container at a time instead or preparing all of them to be edited * besides processing Text Input before saving to remove potentially insecure html in Strings, the input is now also cleaned before it gets inserted into input fields, in case malicious code was inserted by api * Project Info in Navigation Rail, GlobalSearch and Selectboxes now also includes the assigned Group Title (if the Company uses Groups) * Screen Capturing has been refactored for Browsers without DocumentPiP Functionality - Firefox will add this feature with the next Version, so that would be only Safari. On those Browsers, the UI will not show any hint on its own anymore, that a Capture is active - the Browser will do that anyway. * with DocumentPiP, the Browser will open a Preview Window in Parallel, that also shows the current Recording Duration * various Changes for Permission Checks in AI Functions: * Ranking Image tested so far for the Company Text Permission, instead of the Company Image Permission * Image Description / Image OCR now need the Company to use Text AI and Image AI * For Image AI Usage, the current Consent Text made no sense, and an "image-analysis" context has been added for "personal consent". * Search in the Project Navigation Rail now also allows to search by Project Id * The UI now offers a Link to Classic UI, when a User without active Subscription tries to login (as currently, this situation can only be changed in Classic UI) * as the File Download Logic in SDN supports custom Filenames, the following Changes were made: * the Source File now has the "originalFileName", that was used to upload the file * all renditions now start with the original Filename and append Codec and Resolution (or, in case of an Audio-Only Track, the Audio Codec) * Attachments use the Attachment Title (+ FileType) * in all cases, the Filenames are processed to make them "download secure", so they might not 100% reflect the original File Name ### 2026-05-15 API v3 In API v3 we have made some changes to the player object: * added the setting to hide the control bar in full screen (menubarAutoHideFullscreenEnabled) * renamed enableContainerItems to enableOpenContainerItemsOnLoad * renamed podcastShowList to enableOpenPodcastItemsOnLoad ### 2026-05-13 Classic UI/new UI Fixed a bug where the UI would approve a new password even if it didn't fulfill all system password rules. ### 2026-05-11 API v3 * Fixed a bug where AI endpoints would return 200 even if the call failed. * We performed maintenance to decrease the response time of API v3 calls. ### 2026-05-08 Classic UI It is not possible to manage API v3 roles in the classic UI. This means every customer can now activate the new UI themselves. Please see our next newsletter for more information about migrating to the new UI or contact customer success. ### 2026-05-04 Backend * Fixed an issue where playout of VOD2live streams would sometimes pause in the player. * Fixed a bug where Brazilian Portuguese was not offered as a translation language for live subtitles. ### 2026-04-29 Backend * Fixed a bug with livestream source stabilization to improve compatibility when restreaming. * We have added live subtitle creation updates to the live project log. * DRM encrypted files can be streamed with the VOD to live module. ### 2026-04-28 API v2/API v3 Fixed a bug with the livestream recorder API where the status "isStarting" would be returned when trying to start the recorder even though no signal was present. ### 2026-04-24 Backend We have updated the alert module behavior. When a file is moved now, a files.removed event is triggered in the source project, and a files.new event is triggered in the target project. ### 2026-04-23 Backend * When a file is uploaded with embedded subtitles, a subtitle will be ignored if no language is set for it. * The encoding speed for On Demand videos has been improved. ### 2026-04-20 New UI There is a player setting "Use DRM". If enabled (and you have to do it), only the HLS AES manifest is in the player config yet, no DASH, no other sources. ### 2026-04-17 New UI Release **New:** * the new AudioTrack APIs are now available: * it is now possible to upload as many new Audio Tracks to any existing File as needed - with Support for all Languages and Roles * these "uploaded" AudioTracks can be deleted later (not only deactivated, fully deleted) * if the browser supports it, new Audio Tracks can be recorded by Microphone and uploaded directly * previously, there was only an "add audio tracks" Button, if AI was enabled and it led to a Page where AI Dubbing could be configured. Now "add an audio track" is basically always available and contains AI Dubbing, File Upload and Microphone Recording (all only if Permissions exist and the Browser supports it) * IP/Geoblocking Module is now available * it works like in Classic UI, but * each Profile now only has one Rule (with multiple values for countries and/or ip-patterns each) * if this Profile is from Classic UI, its rules have been merged into one * Countries and IP Patterns are now validated and removed if invalid * Geoblocking Profiles can now be added to Players * Geoblocking Profiles can now be copied when copying a Player * Geoblocking Profiles will be found in GlobalSearch * Company Management is now available * the Company Contract Details can be seen and edited (with the necessary Permissions) * "Contract Persons" are available, can be added, edited and deleted * Timeshift/Live Clipping is now available * as before, all available Timeshift Windows and the "live" Window are available and listed for "Clipping" * the UI will produce Thumbnails out of the Manifests the first time they are listed in the Background. This might take a moment the first time, but the generated images are stored in a local database afterwards. * the Clipping Feature makes use of the new Trimming UI * the Clipping Export can now have an (optional) Title, as this might help finding it later * Live Distribution (aka 3rd-Party-Publishing) Module is now available * like Recorders, there is a separate area to manage all Live Distributions globally (if Permissions exist) * like Recorders, if a user has Rights to a live project, they can be managed also directly on the Live View * like Recorders, (manual) Operations will also be published in the Notification Center * Live Distributions have a couple of new (advanced) Settings to help Issues with the previous configurations * Live Distributions will be found in GlobalSearch * File Covers can now be "edited with AI" after Upload (so - the AI wont create a NEW image, it will modify the selected image) * Platform will now read any existing Cover Metadata (like title, copyright) from the uploaded files and upload these metadata (if not empty) to the Backend. Also, it applies various Heuristics, if this Image may be of AI Origin. If AI is very likely, it will flag the Image as AI (even if it was not used by our AI). Both Operations will be handled by the Backend alone at some point. * uploaded Images can now be cropped/resized even after they have been saved (technically, they are re-uploaded as another image and their editable metadata is copied over) * TextTracks, that are AI-generated are now flagged as "ai-generated" in the TextTrack List (identical to AudioTracks and Covers) * Live Events now support Downloads as ICS. Also, existing ICS Files can now be imported as a new LiveEvent * Users can now be assigned to Modules per Multi-Select (Batch) * as more and more User Attributes are available, the "Users" Area is now also offering to select/remove/order the shown Attributes in List View (just like in Files). This setting is also stored and synchronized. * The UI for Recording of Audio, Video and Images has been refactored completely and besides a refreshed look, it also offers a couple of changed options for Camera/Microphone Settings * the UI for Trimming was refactored and now allows "visual trimming" to a certain degree by adding a resizable/draggable Trimming Bar. * for this to be more useful, a lot of minor Player Settings have been tweaked in this context - espcially noticeable is, that the main Player will always be used (ignoring the Users Preference here) and also to force the Player to be 16:9, even if its a Portrait Video **Fixed:** * Fixed Playlist Configuration Filters on mobile UI * Fixed Descriptions are not shown on Files in Table Views * Fixed Sidesheet primary Button always shows "save" * Fixed broken UI for Podcast Seasons * Fixed Podcast Season Sheet does not warn if closed without saving * Fixed Crash on Trimming UI when closing with a Video without Storyboard * Fixed various inconsistent Issues with Cover Upload UI after Upload completed * Fixed clicking on the title/cover of any item on listview might not open Edit Sheet, although its available * Fixed various Issues with Gallery UI after images were re-ordered and saved * Fixed Chapter Editing does not use Player Position, when command comes from Player Button * Fixed various Edgecases in VTT with additional Features where Parsing skipped the first real line * Fixed Recorders show Edit/Delete Buttons, when they are recording * Fixed some Edgecases with very small images, that did not enforce a fixed height and therefore could force the download of the actual sourceimage * Fixed NumberInput Steppers are never disabled, even if the input reached its min/max * Fixed Modal for Recording Audio/Video cannot be closed on mobile, when watching Recording **Changed:** * The GlobalSearch Panel now supports Navigation with ArrowKeys (mostly) - so its at least possible to switch from left to right panel with ArrowLeft/ArrowRight for Keyboard Users * The Tag Input Component handles Tag Validity now stricter. Values with less than 3 Characters wont show up anymore and will be deleted on the next save. Previously, those Tags were (depending on the way they were added) not removed but would lead to an Error in the API, which enforces a minimal length of 3 Characters anyway * the Modules Booking Page now supports a Filter for "primary module purpose" (live, ondemand or both) * when uploading a file, the list of languages, that can be used to set its "source language" to, has been updated to the full list (before, only translateable languages were allowed) * Recorders are now not automatically started and cannot be started manually, if a VOD2Live is currently running. * opening an Image for Cropping without a fixed target-aspectRatio now allows to change between (16:9, 9:16, 1:1 or free) instead of only allow free * changed Focus Management to reduce Effects of "sticky focus", that irritated somes users * Users in Accounts without active Subscriptions cannot login anymore and will instead receive a specific error message that explains why * the link for platform docs has been updated to docs.3q.video * changed card hover ui - removed gradient, aligned icon hover colors, added solid overlay with backdrop blur * as an Iframe must have a title Attribute for accessibility reasons, the Embed Code now also adds the Media Title (and type) as "title" Attribute * Projects as Results in GlobalSearch now also have a "direct link" Action to make it possible to directly jump to the project itself ### 2026-04-17 Backend We now use IETF BCP 47 language tags for languages in our streaming manifests. If you are using a fixed player version, please update to the latest version to avoid potential conflicts. ### 2026-04-16 API v3 * Our timeshift to VoD function is now available in API v3. * You can now manage your livestream distributions (formerly called 3rd Party Publishing) in the v3 API. ### 2026-04-15 API v3/Backend * We now filter uploaded subtitles in webvtt format and remove unsupported features to ensure your files are correctly displayed in our player. * Removed an erroneous error message which was shown when a VOD2live plays and a recorder is active. ### 2026-04-14 API v3 It is now possible to upload additional audio channels for a file. ### 2026-04-13 Backend * Fixed a bug where recorder failed when a dynamic watermark was active for a livestream. * We have made several general improvements to the quality of our live dubbing. ### 2026-03-30 API v3 There is new player setting for whether the player should have rounded corners or not. ### 2026-03-27 API v3/Backend * It is now possible to manage company data such as contact persons via the v3 API. * We've made improvements to the formatting of our AI generated on demand subtitles. ### 2026-03-26 Backend We now include changes to live polls, info points and the player status in the livestream log. ### 2026-03-25 API v2/API v3/New UI * In the API v2 events endpoint: File has been renamed to FileID and the documentation of put and delete event have been fixed. * Our IP/Geo Blocking module can now be managed via API v3 as well as in the new UI. ### 2026-03-23 Backend Fixed a bug where not all eligible files were included in automatically created playlists. ### 2026-03-20 API v3 Fixed a bug which prevented using our upload URL feature with .mov files. ### 2026-03-19 Player v5.4.5 * Added Carousel video player which are controlled by the `playlistMode` parameter * Improved vertical video reel playback * Temporary Disablement of HEVC Playback for Firefox ESR Versions * Fixed playback issues on websites utilizing RequireJS. * Added cornerShape and playerShape Options to the player. * Improved compatibility with modern image formats for better performance ### 2026-03-18 New UI **New:** * Live Events are now available * if available, they can be found on the "Log" Widget on a LiveStream * VOD2Live Management is available * Events show now with an icon, if they were created automatically or manually * Events show in the List, if they are VOD2Live (or not) * Event TextTrack Downloads are also available * VOD2Live Events can now be created also from the Overflow of any File, if Live Projects (and Permissions) are available * manually created Live Events now appear in GlobalSearch * as the Countdown Logic from Classic UI is replaced by the new Event Approach, the new UI now can handle Countdown, if a current or "close" upcoming event exists * new UI reminds Users with Event-Read Access for all manually created Events when they are "close to start" and "are starting" in the Notification Panel * Player Settings now support the 2 new Settings "playerShape" and "cornerShape" * Company Defaults now support the new "grant legacy access" Setting to restrict Access to APIv2/Classic UI. * User now also support the new "grant legacy access" Setting to forbid them accessing APIv2/Classic UI. **Fixed:** * Fixed UI allowed Creation of AI TextTracks, when there was no Audio Tracks yet (i.e. the audio language is unknown here and it cannot be tested, if that language is even supported) * Fixed UI allows TextTrack Uploads where start and end are EQUAL (it blocks only when start is smaller than end so far), but that is also not allowed. * Fixed UI does not disable "dubbing" when disabling TextTracks on LiveStream Ingest * Fixed slightly broken Notification in File Editing when the Text Language does not match the Project Language * Fixed new Passwords are accepted in the UI without containing a Number * Fixed PWA Topbar in DarkMode is visibly yellow * Fixed various Details on PWA lifecycle and Install Management **Changed:** * all Language-related DropDowns and Selections have been updated to now also support Scripts. That will also update the rendered "name" of a Language, that will be in some cases different from before. Please also note, that Language Scripts are irrelevant for DropDowns, that focus on Audio and will be reverted there. * The File Search Details have been changed again - for all customers except Ippen it should behave as before, but the hard limit of 100 has been removed. therefore, the hint about "more results" has also been removed as the api now returns always all results instead of only 100. * File Attachments now support CSP correctly in APIv3 and New UI ### 2026-03-18 API v3 * There is new player setting for whether the player should have rounded corners or not. * We added support for additional subtitle language codes including Albanian and different Chinese dialects and writing systems. * Added additional monitoring to catch errors with file encoding. * The /company/events endpoint is now available in API v3 to search for scheduled live events across projects. * Fixed a bug where attachments could not be downloaded when content protection was active for a project. * In our API v3 you can now select the search mode for your file search. Use natural language mode to find the best matches and boolean mode for a more exact search. You can use the search mode with the project/files endpoint and company/files endpoints. ### 2026-03-16 API v3 There is now a user setting in both the API v3 as well as the new UI to prevent users from logging into the classic UI and API v2. You can use this if you only want your users to work with the new UI. ### 2026-03-13 API v3 You can now schedule future livestream events. The countdown time shown before the stream will optionally be based on this scheduled time. ### 2026-03-02 Backend Fixed a bug where not all subtitles included in an uploaded file were available in the player. ### 2026-03-02 New UI **New:** * Companies can now disable "relevance search", so Files will never be sorted by "relevance", but always by id/date again. * all Batch Operations have been refactored to work more reliably even for huge amounts of items - it now respects browser concurrency limits, network policies, http versions and API Limits and Responses while trying to submit as many tasks in parallel as possible. If a big number of Tasks is commited, the UI will now also show a Progressbar, as this might take a while then. **Fixed:** * Fixed Live Recorder Widget is not scrollable * Fixed Recorder UI shows Filter for Projects even if the User does not have any active Projects * Fixed FilePicker show "select files" Buttons, even if the User does not have any active Projects * Fixed Attachments couldnt be downloaded if larger than a few MB * Fixed Project-based File Search does not leave relevance search, if only order, but not orderfield is changed * Fixed Pusher is blocked from iFrames when not used via WSS * Fixed leaving relevance-based Search does change order-direction when clicking original order-field again * Fixed a Crash on LiveStream UI, if a User only has Rights on Project Level * Fixed Recorders on a LiveStream are not shown, if the User has not Company Permissions * Fixed Audio Waveform Rendering on HiDPI Devices * Fixed LiveStream Analytics Overview KPIs, where Impressions and Plays were wrongly named * Fixed Delete TextTrack Row Confirmation does not close on continue * Fixed Usage View Detail Graph Rendering is not visible * Fixed Cover Preview in Image Metadata always loaded the original file, never a size-optimized Version * Fixed updating the "Items per Page" personal Setting does not actually change this Value until reload (but confusingly updates the Paginator UI) * Fixed a Crash on opening Project Settings directly from the Navigation Rail without cached Project Models * Fixed an Error in ListExporter which added Attributes that dont exist to selectable Attributes under certain circumstances * Fixed hard to understand and visibly broken UI in Audio Recording on devices with multipe Microphones but without a previously selected Id **Changed:** * Project List now shows an Icon, if a Project has a MultiCdn Profile connected (if the User can access this information) * Recorder Widget in Live View has been refactored and normalized * Watermark Covers dont offer Metadata Editing anymore * Change UI for Chapter Editing to always show the current "end" of the chapter (i.e. start of next chapter or end of file) and explain how this computes * Video Preview Thumbnails now use the new "v2/180p" Preview Thumbnails, that are bigger, better quality and respect portrait videos * File Covers now also feature a Downloadbutton - to align the options with the Options in the default Cover Upload UI * Files "in Encoding" now show additionally the current Progress as Tooltip on Hover, they also show the "phase" (i.e. packaging/cdn upload etc) after 100% Encoding has been reached, but the processing is not done yet * the Player Editing UI has been updated as some UI Settings were missing - those are now grouped under a new Segment "UI Settings" * renamed confusingly named "Hide Container Items" Settings, that were actually doing something completely different in Player Settings * renamed Download Urls to Download Urls (instead of Streaming Urls) in Rendition Download Info Dialogues * when a Geo Position on a File is changed AND the files does not have a country set, the UI will automatically update the Country to the Country of the given lat/lng Position from now on ### 2026-02-26 Backend We now support a new version of the media share mrss feed which fully supports the W3C standard. You can access this version by adding \&v=3 to the end of your media share URL. ### 2026-02-24 Classic UI * Fixed a bug which prevented the player countdown from being shown in webcasts with template version 2. * Fixed an error where new webcasts were created with an invalid status. ### 2026-02-20 New UI / API V3 There is a new player setting "enableReelMode" in the API v3 and the new UI. If this is active, playlists will be displayed in reel mode in the player. ### 2026-02-17 New UI **New:** * Files now support "relevance-based Search" * This will use an advanced database search algorithm that should bring "most relevant" items to the top. * As this is only supported (and necessary) in Files, it works like this: * If there is a query AND not a searchField, then the new "relevance" search is used. As the Order here is "relevance", the "normal order" (in the columns) is ignored (and the order icons here are also hidden). If a user clicks on a column AFTER relevance though, this Order is being applied and "relevance" deactivated, unless a new search has started. * It is possible to enable/disable "relevance" also by using a search field, the UI will toggle between relevance/normal search automatically * Relevance-based search supports (currently) maximum 100 results - the UI will show a hint when this limit has been reached (which probably means the search is not specific enough) * For cases with many search results in relevance mode, Files now support a new Filter: Period, which can restrict the search field by creationDate (but not order by it!) * Automatic Playlists are now supported * Can be added and edited in NewUI/APIv3 only - invisible in classic/v2 * Their "configuration" (rules for items) can be managed * The UI makes sure that these playlists cannot be reordered and no items can be added from anywhere to them (in contrast to "normal" Playlists) * MultiCDN Module is now supported * Unlike in classic UI, CDN profiles now have a title and a description * Unlike in classic UI, there can be only one global profile and one profile per project (intentionally, it's impossible to update existing profiles if other profiles for the same context exist) * MultiCDN profiles also appear in GlobalSearch (but only if they have a name/description, so old ones won't at the beginning) * The new Player Setting Reel-Mode is now supported * Branded Companies can now disable global Playlists * Trimming now shows and updates a waveform and/or video thumbnails of start/end, if available **Fixed:** * Fixed an Error in Cache-Updating Logic * Fixed Handling of SVG and ICO Assets in Various Contexts * Fixed handling of option images in DropDowns, they were never scaled down correctly * Fixed sourceProject is always empty on Playlists and Podcasts Export * Fixed rendering of OS/browser in "active Sessions" does not render correct OS/browser names in some cases * Fixed Playback of Audio Files in DocumentPiP Mode started muted, although that does not make sense * Fixed Integrations never shows "History" Tab * Fixed misleading text for empty deactivated Integration Text * Fixed Flickering when providing Files for Upload via DragnDrop * Fixed CMAF Dubbing Hint in Files * Fixed Attachment-Upload Form crashes when submitted without File * Fixed cannot save pipeline with dubbing on / Auto-TextTracks on, then off, which doesn't turn off dubbing completely, leading to an unsaveable form * Fixed Video/Audio Recording did not offer to playback recording after Recording stopped * Fixed crash on playback of non-encoded source files * Fixed opening the GlobalSearch with ctrl/k does focus the input but does not reopen the Overlay * Fixed "x" button on select menus with multiple options that showed a broken Aria Message **Changed:** * The behavior for player muted logic changed to the following: * If audio, UI will always start with sound now * If live, then (no change here) * No overrides are sent for the preview, so the "real" player settings are applied * Muted/autoplay are sent for the stream view * If VOD, then: * It will start muted in any case, but if started in Main Player AND unmuted in the first 30 seconds of playback, the UI will ask if you would prefer to start playback with sound (which is obviously not always possible). * This setting will be stored and synced (if enabled) and applied wherever possible * The minimum length to offer AI Chapters of a File has been reduced to 30 Minutes * Chapter descriptions can now also be composed/edited with AI writing tools * Attachment Description can now also be composed/edited with AI writing tools * The link to Terms & Conditions has been added to the Support Panel * Refactored UI for Uploading via DragnDrop without Snackbar * The UI will from now on block drag/drop operations globally - unless it's dragged over a designated file drop area (like Files itself or a cover/file upload) OR its text and the user tries to drop it on an input/area * On phones, the BottomSheet is now also closeable via a slide down, not only via click outside * Notifications now show an icon for their "target" (files, live, podcasts) on cards and lists - also, a tab for podcast-specific notifications was added (furthermore, the UI will not offer podcast events anymore, when the company hasn't booked the podcast module) * Player Settings will not offer Enable-Ads anymore, when the company hasn't booked the ad module. * Added a hint on the file downloads page if the file was trimmed at some point. In this case, the UI now shows a hint that the files themselves still contain the full length of the original files, not just the trimmed version. * The layout of a "timespan" input (like in Trimming / Pipeline) was refactored * Opening an AudioTrack with an "unknown" language does not automatically add the last-used language anymore but keeps the value empty to emphasize that an action is needed (this was also done to the "role" attribute on users of the "classic UI" a while back) ### 2026-02-13 API v3 We have made several small changes to the v3 API: system/integration no longer returns createdAt, account/modules no longer returns pricing information, and the on demand project object no longer returns the field concurrentViewers ### 2026-02-12 Backend * Fixed a bug causing the error image to not be shown in the output when using Source Stabilization. * Fixed several small edge cases which would prevent copying of files between projects in certain circumstances. ### 2026-02-06 API v3/new UI In the new UI and API V3 it is now possible to automatically create playlists of files based on their metadata ### 2026-02-05 Classic UI Fixed a bug preventing Webcast series deletion ### 2026-02-04 Classic UI Fixed a bug which caused a category to be required during the playlist creation process ### 2026-01-30 Classic UI Fixed a bug preventing the creation of infopoints for livestreams ### 2026-02-05 API v3 Fixed a bug where AI suggested text alternatives weren't returned ### 2026-01-29 API v3/New UI In order to improve system security, it is no longer possible to reuse previously used passwords when resetting your password. ### 2026-01-27 API v3 * Removed Metadatafields: \ we have removed several seldom used metadata fields in API v3: nativeLanguage, iabCategories, media shares, metaPictureUri, rating, genre, relationship, studio, licensor and licenseArea. If you currently use one of these fields, please contact our customer support about how to migrate to a custom metadata field * Changes to sourceLanguage:\ The API parameter sourceLanguage has been deprecated and split into two new parameters: audioLanguage, which is the language of first audio track of the file used for transcription and other features and displayLanguage, which is the language of any text which appears in the video * Fixed a bug where certain languages were not allowed as subtitle translations ### 2026-01-27 New UI Release **New:** * the Sync of personal Preferences over Devices should now work again. * the Copy Dialog of Projects now also allow to copy Notifications - if the source Project has Notifications and the loggedin User has the Right to create new Notifications * File Attachments are now supporting Sizes of over 20 Mb (by using chunked-upload) - the UI handles all of this, so there is no Change for Users **Fixed:** * Fixed TextTrack Language will not be updated automatically, if AI is confident to guessed the language correctly * Fixed TextTrack Language will not be saved as personal Preference after Selection * Fixed "in-progress" Button Animation on mobile Devices * Fixed Filters dont show explicit "remove-selection" Button anymore * Fixed editing a File with People always re-saves the value of "people", even if that is not necessary * Fixed custom Filter Order is not necessarily re-constructed after revisiting an area with custom Filter Order * Fixed SearchField DropDown in Files does not show Custom Labels, only default Field Labels * Fixed ListExporter in Files respects custom Labels in Titles, but not in Sorting * Fixed SearchFilters dont hide hidden Fields * Fixed AttributeList in Files might not close on saving * Fixed Files with multiple AudioTracks showed their Tracks in Alphabetical order, not by their StreamIndex. Also, Track Listings now show the Index explicitely * Fixed Branded UI does not respect custom BorderRadius on iFrames * Fixed broken Language Selector in some Edge Cases of Grid Layouts * Fixed deleting a TextTrack Block does not mark the Sidesheet as "having updates" * Fixed "keep original Framerate" Setting is missing in Encoding Settings * Fixed multiple Issues in Pipelinesettings with various Changes between settings for sourceLanguage, TextTracks and Dubbing * Fixed multiple Issues with Wizard Mode * Fixed Crash on LiveStream Sharing when Basic Mode is active * Fixed Modal is not closeable in some Media-related Situations on Browsers with Invoker Command API **Changed:** * changed all text templates to use typographically correct symbols for apostrophe, quotation mark, minus-sign, hyphen, em-dash and en-dash where appropriate * SplitButtons were redesigned to make it more obvious, that there are more Options * Filters were redesigned to get even more Space when not hovered and also to reduce the confusing "x" while having an active selection * deleting a TextText Row must now be confirmed in a modal (which is skippable with a synced Setting, so its not too annoying, if users dont want to see that) * after a lot of discussion, the list of Framerates in Encoding is kept, but a Hint has been added to inform Users if this setting is actually applied or not * also after a lot of discussion, the iFrame Options in the Share Dialogue have been refactored and were expanded to three Options * the "image purpose" is now explained in more details * Pipeline Audio Settings on Files with multiple Audio Tracks now use Toggles to allow a quicker enabling/disabling * the File Attributes "series" and "programId" are back in all File-related Contexts :) * Enhancing Converters for VTT and TTML to catch more Edge Cases in Converting to SRT ### 2026-01-23 API v3 The SDN API v3 now optionally supports chunked uploads for very large attachments. ### 2026-01-23 Webcast We've removed the text " | 3Q" from the title of our webcast pages. ### 2026-01-20 Player v5.4.4 * Refactored sticky functionality, added stickyPosition * Fixed an issue drawing chapters on the seekbar when player was moved or resized * Introduced vertical video player with swipeable reels. * Diverse UI improvements ### 2026-01-20 API v3 Fixed a bug where updating playout ids via API v3 would sometimes return 404 ### 2026-01-20 Live Comments Fixed a bug where a user wouldn't see all of his non public comments. ### 2026-01-16 API v3 Added the storyboard picture to the file object. ### 2026-01-13 Backend * Fixed a bug which prevented uploaded images ~~and attachments~~ from being included in account storage * Fixed a bug where sometimes livestream with HEVC were underbilled ### 2026-01-05 Backend We updated the email template used for video sharing ### 2026-01-05 Classic UI Fixed a bug with the sorting of podcast files in the classic UI *** **Disclaimer** Copyright (C) 2009 – 2025, 3Q GmbH, Munich, Europe. All Rights Reserved.
This source code and its use and distribution are subject to the terms and conditions of the applicable license agreement. More information at [www.3q.video](https://www.3q.video) # Firewall Playback of videos hosted on the 3Q platform does **not** require any special firewall configuration. Video and media delivery is handled via standard HTTP(S) and works without additional port releases. If content uploads or live stream ingestion are performed from a **restricted or secured network**, additional firewall rules may be required as described below. *** #### Video Player Requirements (Web SDK) To ensure successful video playback using the 3Q Web SDK, the following conditions must be met: #### Domain Accessibility The following domains must be reachable via HTTP and HTTPS on standard ports (80/443), including all subdomains: * `3qsdn.com` * `3q.video` #### Browser Support The browser in use must be a **vendor-supported, up-to-date version** of a common web browser. Only officially supported browsers are recommended for production use. *** #### Content Ingest #### On-Demand Uploads On-demand video content is uploaded exclusively via **HTTPS**. No additional protocols or ports are required beyond standard HTTPS connectivity. #### Livestream Ingest For livestream delivery to the 3Q platform, the following protocols are supported: * **RTMP** * **RTMPS** * **SRT** The corresponding protocols and ports must be allowed in the firewall configuration of the encoder or ingesting system. **RTMP** * **Protocol:** TCP * **Destination Port:** 1935 * **Destination Hosts:** * `de-origin-ingest-live.3qsdn.com` * `de-origin-ingest-live-02.3qsdn.com` * `at-origin-ingest-live.3qsdn.com` * `us-origin-live-nyk-01.3qsdn.com` **RTMPS** * **Protocol:** TCP * **Destination Port:** 443 * **Destination Hosts:** * `de-origin-ingest-live.3qsdn.com` * `de-origin-ingest-live-02.3qsdn.com` * `at-origin-ingest-live.3qsdn.com` * `us-origin-live-nyk-01.3qsdn.com` **SRT** * **Protocol:** UDP * **Destination Port:** * Individually assigned per livestream * Port range: **1024–65535** * **Destination Hosts:** * `de-origin-ingest-live.3qsdn.com` * `de-origin-ingest-live-02.3qsdn.com` * `at-origin-ingest-live.3qsdn.com` * `us-origin-live-nyk-01.3qsdn.com` *** #### Firewall Configuration Using IP Addresses If DNS-based firewall rules are not supported in your environment, it is recommended to allow outbound connections for the required destination ports without restricting the destination address. If your corporate security policies require explicit destination addresses, the following IP ranges may be used. **IPv4 Address Ranges** * `31.7.178.128/27` * `31.7.180.96/28` * `31.7.180.128/27` * `31.7.185.0/28` * `31.7.187.0/27` * `35.231.219.190/32` * `37.58.30.0/23` * `91.242.173.0/24` * `167.235.244.250/32` * `185.175.64.0/24` **IPv6 Address Ranges** * `2a14:30c0::/32` * `2a14:30c1::/32` * `2001:67c:6d8::/48` * `2a01:4a0:5::/48` > **Important:** These address ranges include all possible IPs used for livestream ingest. HTTP and HTTPS access **cannot** be reliably restricted by IP address and must always be permitted based on domain names. *** #### Recommendation Based on operational experience, maintaining manual IP-based firewall rules carries a significant risk of service disruption due to infrastructure changes. For this reason, it is strongly recommended to: * Use **DNS-based firewall rules** whenever possible, or * Allow the encoder system unrestricted outbound connections on the required destination ports This approach ensures long-term stability and uninterrupted content delivery.