Skip to content
Close
SEARCH
Contact
Sign In
Contact
Sign In
Multiview
True personalized multiview at scale

Let viewers build and watch personalized multiview experiences without the cost and complexity of traditional approaches. Quortex makes personalized multiview scalable, while helping ensure the clean, crisp video quality viewers expect.

Talk to an expert
Quortex Multiview_04
Image frame_white-

Why multiview is hard to scale

The promise of personalized multiview is compelling, but traditional approaches struggle to support it at scale.

Icon_Outlin_yellow_Complexity-
Viewer choice increases complexity

When viewers can choose their own four-channel layout (or more), the number of possible arrangements rises quickly.

For example: Selecting 4 channels from 30 feeds creates 657,720 possible combinations.

Icon_Outlin_yellow_multiple views-
Client-side approaches are difficult to deploy

Client-side multiview often relies on proprietary players, multiple integrations, multiple decodes, and stream synchronization, making rollout across devices harder.

Icon_Outlin_yellow_server-
Mass Headend Encoding

Mass Headend Encoding architectures reduce player complexity, but require transcoding for each arrangement, which increases cost and limits scalability.

Q_blue
A more scalable approach to personalized multiview with quality built in

Quortex’s multiview solution assembles requested channels at the packager layer using HEVC or VVC tile remixing, avoiding full transcoding for every arrangement and minimizing impact on existing workflows. And because scalable multiview also needs to look right on screen, Quortex applies deep video compression expertise to help ensure clean, crisp tiled output.

  • No player replacement
  • Minimal client changes
  • No full transcoding per layout
  • Compression-optimized tiled output
  • On-prem or cloud deployment
Request a demo
Quortex Multiview_05

Core capabilities

Icon_Outlin_blue_multiview layout-
Packager-layer multiview assembly

Assemble requested multiview layouts dynamically at the packager layer instead of creating and storing every permutation in advance.

Icon_Outlin_blue_flexible_1-
Flexible deployment options

Support both component-based deployment and end-to-end workflow options, on-prem or in cloud environments.

Icon_Outlin_blue_compression-
Compression-optimized HEVC/VVC tile remixing

Use HEVC/VVC tile remixing to compose multiview streams efficiently while applying advanced video compression expertise to help maintain clean, crisp output.

Icon_Outlin_blue_flexible-
Minimal client impact

No player replacement required. Client changes are limited mainly to request handling and API interaction.

Icon_Outlin_blue_controls-
Back-office control and API integration

Support a simple API-based model for defining channel selections, arrangements, and business logic.

PAttern_Black_01

Ready to scale
personalized multiview?

See how we can help you deliver flexible multiview experiences with lower complexity and a more economical architecture.

Talk to an expert
MULTIVIEW FAQ

Frequently Asked Questions

What is Multiview?

Multiview enables viewers to watch multiple live channels in a single screen experience, with support for personalized channel selection. It is designed to help operators deliver flexible multiview experiences without relying on traditional architectures that become costly or difficult to scale.
How is Multiview different from client-side multiview?

Client-side multiview often depends on proprietary players, multiple integrations, multiple decodes, and stream synchronization. Multiview reduces that burden by assembling requested channel combinations at the packager layer, which minimizes impact on the player and simplifies rollout across devices.
How is Multiview different from server-side transcoding-based approaches?

Traditional server-side approaches typically require transcoding for each multiview arrangement, which increases cost and makes scale harder to achieve. Quortex Multiview avoids full transcoding for every possible layout by using lightweight HEVC tile remixing at the packager layer, creating a more economical and scalable architecture.
Does Multiview require player replacement?

No. Multiview is designed to avoid player replacement. Client-side changes are kept minimal and are primarily limited to requests and API interaction, reducing disruption to existing deployments.
Can Multiview support subscriber-selected channel layouts?

Yes. Multiview is built to support subscriber-driven multiview experiences, allowing viewers to choose their own channel combinations instead of being limited to a fixed set of predefined layouts.
How does Multiview handle scale?

Scale is one of the main design goals. When viewers can choose their own four-channel layouts, the number of possible combinations grows rapidly. For example, selecting 4 channels from 30 feeds creates 657,720 possible combinations. Quortex Multiview addresses this by assembling requested arrangements dynamically at the packager layer rather than pre-building every option.
Does HEVC tiling alone guarantee high-quality multiview output?

No. HEVC tiling provides a scalable and standards-based foundation for multiview, but the final viewing experience also depends on how the tiled video is encoded and optimized. Quortex combines efficient multiview assembly with deep video compression expertise to help ensure clean, crisp output.
Can multiview channels support multiple language tracks?

Yes. In our solution, each tile within a multiview channel can support multiple language tracks, helping operators deliver a more flexible viewer experience.
Can multiview channels support closed captions?

Yes. In our implementation, each tile within a multiview channel can support closed captions, helping preserve important accessibility features within the multiview experience.
Can Multiview be deployed on-prem or in the cloud?

Yes. Multiview supports both on-prem and cloud deployment models, giving operators flexibility to integrate it into existing environments with less impact on legacy workflows.