Inputs

• Choose the right Input Protocol

  Quortex Play offers two different Protocols to submit Input Channels, SRT and RTMP. Since both Protocols have extremely different Characteristics in terms of Reliability and Security, we want to take a deeper look into both to help you understand the differences and choose the right one for your Workflow. The Real-Time Messaging Protocol (RTMP) is a mature, well established streaming protocol with a reputation for reliability thanks to its TCP-based packet-retransmit capabilities and adjusSome readers

• How to choose your SRT input type?

  Quortex Play offers two input modes: Listener (aka server mode): this is the default mode, where Quortex Play will act as a SRT server and listen for incoming connections from your SRT clients. Caller (aka client mode), where Quortex Play will act as a SRT client and will initiate the connection to your SRT server. We do not support the SRT "Rendez-Vous" mode You may wonder what are the differences between these two modes and why you should choose one or the other. BotFew readers

• Select your input regions

  When creating a new channel pool, the first thing to define is the "Input Region". In short, the rule of thumb is to select the region nearest to where your streams are being originated. Don't panic if you don't see a region that seems to fit with that rule. Just select the nearest one, really. The SRT protocol used to ingest the streams comes with a very effective error recoverFew readers

• Setting up a Highly Available input

  Quortex Play supports redundant inputs, to make sure your content is always delivered. Concepts An Quortex Play input is made of one of two streams. A stream can be a SRT caller/listener, a RTMP endpoint or a slate image. Different stream types can be mixed within a given input. | The input switch is made without any stream interruption on the output: playlists and segments will be generated without any discontinuities. Stream Selection The platform will automatically select the iFew readers

• Using the RTMP Input

  Quortex Play supports RTMP and RTMPS as input protocols. Although it offers less flexibility and resiliency than SRT, RTMP is still widely available and can be used for ingesting your stream. You can check this article if you want to learn more about SRT and RTMP protocols. Selecting RTMP When using RTMP, the endpoint will be automatically created by the platform. Hence, you don't have any parameter to enter. ![](https://storage.crisp.chat/users/helpdesk/website/9845223dbfb4e800/rtmpinput_1jFew readers

• Input Loss Management

  Configuring Output Behavior When an Input Is Lost When an input becomes unavailable, you can configure how the output should behave. There are two available options: Keep generating: Continue generating segments using fallback content. Stop generating: Stop delivering segments, which will result in an HTTP 404 error. This setting is configured at the pool level in the Advanced section and applies to all inputs within the pool. ![](https://storage.crisp.chat/users/helpdesFew readers

Processing

• How to define your processing configurations

  Processing configurations are made of video, audio and subtitles sub-configurations. Video configuration Using presets Presets are pre-defined rendition ladders that should cover most of your needs. Use them if you are not sure what to do. A rule of thumb for using these presets is: If your content is fast-moving, such as sports, try to use 50p framerates. This is a rFew readers

• How do I map input components to output streams?

  You want to select specific tracks from your input? You want to make sure that some components are present in your stream? Follow the guide! Before one knows where to go, one needs to know where he is The first step is to understand the type of components carried in your input stream. When you ingest a SRT stream, the latter carries a Transport Stream (as per ISO/IEC 13818-1 MPEG2 Transport Stream (MPEG2-TS). As per wikipedia, TS is a packet-based media container format for transmitting videoFew readers

• How to use DRM encryption

  Quortex Play supports DRM (Digital Rights Management) encryption to secure your published streams and make sure they can only be watched by entitled viewers. In a nutshell, DRM ensures that video content is stored and transmitted in an encrypted form, to make sure only authorized users and devices can play it back. It is common to use multiple DRM schemes for better device compatibility. While there are multiple different schemes available, the three below mentioned are the most commonly used oFew readers

• How to use static DRM encryption (Legacy)

  This page describes the static DRM encryption only. For new projects, it is recommended to use the Dynamic as described here Quortex Play supports DRM (Digital Rights Management) encryption to secure your published streams and make sure they can only be watched by entitled viewers. In a nutshell, DRM ensures that video content is stored and transmitted in an encrypted form, to make sure only authorized users and devPopular

Delivery

• Block the streaming in some countries

  Quortex I/O offers several ways to prevent viewers coming from specific countries or regions to access your stream. Depending on whether you want to permanently block the stream or make it conditional to some other conditions, we got you covered. Let's find out! in any case, the detection is based on the user IP address. Do not hesitate to reach out to us in case you need more advanced detection schemes, or VPN blocking features. Method 1: Geoblocking Geoblocking is the most straightforwSome readers

• How to passthrough SCTE35 Messages

  Quortex I/O provides the ability to passthrough incoming SCTE35 Messages to be used for downstream Ad Insertion or content manipulation mechanisms. Like the rest of Quortex I/O configurations, this is pretty straight forward. Input Configuration First step is to confirm that SCTE Messages are received in the Input Stream and enable them. To do so, navigate to the Input Section, select your source and click on the settings button. After that navigate to the analysis tab. ![Analysis View onSome readers

• Monitoring the success of your streams

  Quortex I/O gives you the ability to measure the success of your streams, in terms of number of views or number of viewers. This does not require any player side integration: it truly works with any device used to watch your stream. Just publish your streams, we take care of everything else. Overview The overview panel is made of 4 different quadrants. This panel gives you a quick view of the pool audience, plus a view of the audience evolution over a given time period. | By default, the perFew readers

• What is the structure of a Quortex Play publishing point?

  Let's see how publishing points can help you customize endpoint URLs used by players!Few readers

• Adding a Custom Domain to Streaming URLs

  Quortex Play provides the ability to add a custom ( your own ) domain to your Publishing Points. The custom domain is set per pool and can be altered within a organization on different pools. Configuration The configuration is straight forward. After creating your pool, check the settings button on the top right. After Sliding the "add a custom domain name" button, you are required to add you domainFew readers

• Using Quortex as an Origin

  Quortex Play can be used either with its built-in CDN or as an Origin. In this article, you will learn how to configure your pool with the right settings to deliver your streams just the way you want! Using Quortex Play with the built-in CDN Using the built-in CDN is the default behavior. There is nothing to do in the platform, just create your pool and you can start delivering your streams throughout the world immediately! || You can create a CDN pool and use it as an Origin - it will jusFew readers

• Introducing OTT endpoints

  OTT endpoints are available in Quortex Play since June 26th 2024. This article describes this new configuration object and its benefits. What are OTT endpoints? OTT endpoints are an evolution of publishing points. They are used for the same purpose, which is configuring URLs that players can use to stream content. OTT endpoints have the same structure as publishing points, as described further in this article. However, OTT endpoints differ from publishing points in the way they are created.Few readers

Advanced Workflows

• Using Startover

  Startover is a built-in capability of Quortex Play. Before we go into the details of how to configure startover, let's make sure we use the same language ... Startover is the ability, for your end users, to go back in time in their live streams. The use case the platforms focuses on is when you want your users to come back to a specific point in time, typically the program start (in which case it can be API driven through integration with your EPG system), or the event start (in case you startedFew readers

• Premium Processing

  Quortex Play can support premium processing features and offer Low Latency, HEVC transcoding, and UHD output resolutions. These features rely on a specific pool type (Premium pool). This article introduces Premium Pool particularities. Premium Pool features Premium pool is used for premium processing which includes any of these features: Low Latency (as specified in LL-DASH and LL-HLS). Typically enables 3 to 8 seconds end-to-end latency. This requires a Low Latency player. HEVC transcodiFew readers

• Using Catch up (restricted availability)

  Catch up is a built-in capability of Quortex Play. Before we go into the details of how to configure Catch up, let's make sure we use the same language ... Catch up is the ability for your end users to replay a recorded program. The configuration of Catch up implies the creation of programs and the generation of VOD assets to stream recorded programs. This feature is available based on your use case analysis with Synamedia. Please contact us for more details! Activating the Catch up CatchFew readers

• Using FAST

  FAST stands for Free Ad-supported Streaming TV. Its implementation in Quortex enables the generation of a live stream from a list of video file assets, played according to a configured schedule. Advertising placeholders can be inserted between assets. The replacement of ads into these placeholders is performed by an external solution, which also allows for targeted advertising (ads selected by an ad server based on the user profile). ![](https://storage.crisp.chat/users/helpdesk/website/9845223dFew readers

• Using RTMP Output (Social Networks interface)

  Need to stream your live content to Social Network Platforms ? Quortex Play supports RTMP(S) as output protocol which allows to send your transcoded content to such platforms and expand your audience via Social Networks. This article describes how to configure Quortex to enable RTMP(S) outputs. Push endpoints The configuration of the Input, Processing, Targets is made as usual. RTMP(S) output are configured in a specific tab called "Push endpoints". Open the "Push endpoint" tab and add an enFew readers

• Assets Library

  The Asset Library is a space where slates can be uploaded and immediately reused in inputs configuration. This section describes how to list, upload assets in the library and use them in a service. Uploading an asset in the Library Assets are managed per pool. Select a pool, then open the Asset Library by clicking on the left menu. To upload an asset, click on "Add assets" and select your content as shown below. ![](https://storage.crisp.chat/users/helpdesk/website/-/9/8/4/5/9845223dbfb4eFew readers

• Using Time-shifting

  Time-shifting allows viewers to pause and resume an ongoing live stream. The implementation of this feature depends on the video player. It relies on a long playlist through which the player can browse to select and play the required segments. Quortex Play supports the generation of playlists up to 2 hours long, enabling users to pause a live stream for up to 2 hours. This article explains how to configure time-shifting in Quortex Play. Enabling long playlists The generation oFew readers