Panduit Atlona OmniStream AT-OMNI-111 User guide

Atlona Manuals
Networked AV
AT-OMNI-111 / WP
AT-OMNI-121
Multiview Application Guide
OmniStream™

Multiview Application Guide 2
Version Information
Version Release Date Notes
1 May 2023 Initial release

Multiview Application Guide 3
Sales, Marketing, and Customer Support
Main Oce
Atlona Incorporated
70 Daggett Drive
San Jose, CA 95134
United States
Oce: +1.408.962.0515
Sales and Customer Service Hours
Monday - Friday: 6:00 a.m. - 4:30 p.m. (PST)
https://atlona.com/
International Headquarters
Atlona International AG
Tdistrasse 18
8002 Zrich
Switzerland
Oce: +41.43.508.4321
Sales and Customer Service Hours
Monday - Friday: 09:00 - 17:00 (UTC +1)

Multiview Application Guide 4
Introduction 5
About This Manual 5
Application: Overow Rooms 6
Overview 6
Planning 7
Conguration 10
Decoder Multiview Conguration 10
Encoder Conguration 13
Programming Recommendations 24
Switching Multiview Layouts 24
Background 24
Changing Multiview Layout 25
Using Velocity 25
Using JSON 30
Atlona Recommendations 34
Table of Contents

Multiview Application Guide 5
Introduction
About This Manual
Multiview functionality in OmniStream 2.0 allows integrators to design systems that display content from multiple
streams on a single display without requiring any additional equipment. Proper implementation of multiview systems
requires planning during the system design and programming phases to ensure the system operates as expected.
This manual takes readers through the design, conguration, and programming phases of a real-world multiview
application. This will introduce the reader to the techniques needed to properly implement a multiview system, which
can then be extended to other applications.
The second part of this guide provides programming recommendations for applications where multiview layouts
will be switched. Layout changes in OmniStream require several programming steps, and these recommendations
provide guidance on the best way to implement multiview layout switches.

Multiview Application Guide 6
The use of overow rooms is common in education and other presentation spaces to allow attendees to view a
presentation when there is insucient seating available in the primary space. In order to support overow, it is
necessary that sources in the primary space be available in the overow space. And, in practical applications where
overow will be supported, this needs to be done exibly since overow scheduling (i.e. determining which room is
primary and which is overow) will often be event-dependent.
Utilizing OmniStream is perfect for overow applications since content in one room can be exibly routed to one or
more overow spaces via a network. To illustrate how this works, Figure 1.1 shows three rooms where each room is
showing only its own content. For purposes of clarity, encoders and decoders are not shown.
Application: Overow Rooms
Overview
Laptop
3840 x 2160
Laptop
Camera
Laptop
3840 x 2160
Laptop
Camera
Laptop
3840 x 2160
Laptop
Camera
Laptop
3840 x 2160
Laptop
Camera
Laptop
3840 x 2160
Laptop
Camera
Laptop - Room 1
3840 x 2160
Laptop
Camera
Camera
Room 1
968 x 528
Figure 1.1 - Presentation spaces where each room is showing its own content.
Figure 1.2- Presentation spaces where Rooms 1 and 2 are showing their own content, and Room 3 is used
as an overow for Room 1.
If a presentation in Room 1 has more attendees than can t in that room, another room can be used as an overow
space and show both the content and camera from that room. In Figure 1.2, Room 3 is used as the overow space,
and shows the content and camera from Room 1 in a PiP format.

Multiview Application Guide 7
Application: Overow Rooms
This section will walk you through design and programming considerations for room overow using OmniStream.
Please note that this guide is also applicable for any spaces where users want to show two pieces of content.
DEFINITIONS
Content – Refers to presentation materials that are the primary content in the space. This
includes laptop, document cameras, and media players.
Camera – Refers to one of more cameras that show the presenter or attendees and is generally
considered secondary to the content.
Step 1: Decide what content is to be shown in each space.
Live presentations requiring overow support will often have content that is being displayed, which can include
a presentation, a document camera, or video content. Additionally, to provide optimal support for overow, the
presentation space should also have a camera. The rst step in system design is to consider what content you want
to make available in the overow and primary spaces and use this to determine what encoders are required.
Content sources include things like a presenter laptop or document camera. Depending on the design of the room,
there are two ways to make these sources part of an OmniStream system:
Planning
1. Connect each source to its own OmniStream encoder so that it can be switched to any OmniStream decoder
regardless of the state of any other source.
2. Connect each source to a switcher (such as an Atlona Omega switcher), and connect the output of the switcher
to an OmniStream encoder. This results in a lower cost room design, but it does mean that overow spaces will
only have access to the content currently switched to in the primary space.
Laptop
3840 x 2160
Laptop ENC
Document Camera
Media Player
ENC
ENC
Laptop
3840 x 2160
Laptop
Switch
Document Camera
Media Player
ENC
Figure 1.3 - Two ways to connect content sources to OmniStream. The room on the left has each source
connected to its own encoder. The room on the right connects its sources rst to a switch, and then the
output of that switch connects to an encoder.
Content Sources

Multiview Application Guide 8
Application: Overow Rooms
For the best overow experience there should be at least one camera in the room that is connected to an
OmniStream encoder. This allows viewers in the overow space to view the presenter.
Step 2: Decide how the content should be distributed in Overow Spaces
In the overow rooms, it’s always an option to show the content or camera full-screen, but this means that remote
viewers will only be able to see one or the other. With the multiview capabilities of OmniStream 2.0, it is possible to
composite the content and camera onto a single display so that overow viewers can see both at the same time.
As part of the system design and implementation, it’s important to rst consider how overow rooms will view the
content and camera. Some of the most common presentation layouts include:
• Picture-in-Picture (PiP) - In PiP applications, the content is shown full screen, and the camera is shown in
one of the corners. PiP has the advantage that the content will be shown at maximum size, but comes at the
disadvantage that the camera covers part of the content. For this reason, many PiP implementations will allow
the PiP content to be moved on the screen.
Figure 1.4 - Example PiP layout. The PiP window can be positioned in any corner to avoid covering critical
content.
Figure 1.5 - Example SbS layout. Note that the content and camera are identical size.
• Side-by-Side (SbS) - SbS views avoid the problem of the camera covering the content by placing the camera and
content side-by-side. In these applications, the content will be scaled down to a resolution less than full screen,
and the exact SbS layout will depend on the size expectations for both the content and the camera.
In Figure 1.5, both content and camera are shown at the same size. This greatly reduces the size of the content,
so this type of layout will typically only be used in overow applications where the screens are large and where
the camera view is determined to be of equal importance to the content.
Laptop - Room 1
3840 x 2160
Camera
Room 1
968 x 528
Content
1920 x 1080
Camera
1920 x 1080
Cameras

Multiview Application Guide 9
In those applications where the camera is secondary to the content, users can instead choose a SbS layout
where the content occupies most of the display and the camera is scaled down to a small size, much as you
would see in the PiP application.
The way the encoders and decoders are congured in a system will depend in large part on the multiview layout
or layouts that will be used in overow rooms. The instructions below are designed to allow users to have a mix of
single stream, PiP, and SbS layouts.
Application: Overow Rooms
Content
2880 x 1584
Camera
968 x 528
Figure 1.6 - Example SbS layout. Note that the content is given priority on this display and is shown at a
larger size
Step 3: Selecting the equipment for a Multiview System
Step 4: Conguring the Device
To successfully implement an OmniStream Multiview System, you will need the following:
• 1 x AT-OMNI-111 encoder per content source. This can be designed so that each content source, such as a
laptop, document camera, or media player is connected to the encoder. Or, the sources can all be connected to
a video switch, and the output of that switch can be connected to the encoder.
• 1 x AT-OMNI-121 decoder per display.
• Multicast-capable network, that connects all spaces that will have overow capability.
• Control System, such as Atlona Velocity™, that allows the user to make easy content and layout changes.

Multiview Application Guide 10
Application: Overow Rooms
Based on the desired multiview layout (as described above), each decoder will need to be congured to display that
layout. OmniStream has numerous multiview preset layouts, which can be customized if needed.
Creating a new layout on a decoder is as simple as going to the Multiview tab on the decoder web page and clicking
on the ADD MULTIVIEW button.
Conguration
Decoder Multiview Conguration
A pop-up will appear, allowing the user to dene a new multiview. Give the multiview a name, select a canvas
resolution (for most applications, this will be the default of 3840x2160), and select a layout.
Figure 1.7 - OmniStream decoder web page showing the Multiview tab before any Multiviews have been
created.
Figure 1.8 - Multiview creation pane showing the various built-in layouts.

Multiview Application Guide 11
Application: Overow Rooms
For PiP applications, OmniStream decoders include four dierent presets, depending on the position of the PiP
window. This is just a starting point, since the PiP window can be moved anywhere on the screen using the API.
Users should pick the layout they think will most likely be used as a starting point.
For SbS applications, OmniStream decoders make a side-by-side layout available, where each of the two pieces of
content is the same size. If customers desire to have the content window much larger, they should select the 4-split
layout and delete the two subframes that will not be used.
When conguring the decoder multiview, you will need to assign ip_inputs to subframes. For maximum exibility, this
guide assumes ip_inputs will be used as follows:
• ip_input1: native resolution source content or scaled content for large SbS.
• ip_input12: scaled content for SbS.
• ip_input13: scaled camera for PiP and SbS.
Figure 1.9 - Multiview creation pane with one of the PiP layouts selected.
Figure 1.10 - Multiview creation pane showing two dierent options for SbS layouts. The layout on the left
has both content and camera the same size. The layout on the right allows the content to occupy most of
the screen. Note that only 1 of the three panes on the right is needed for the camera.

Multiview Application Guide 12
Application: Overow Rooms
These ip_inputs can be assigned when setting up a new multiview according to the following table:
Decoder Layout Type Default Layout Options ip_input Assignments
PiP pip-top-left
pip-top-right
pip-bottom-left
pip-bottom-right
1: ip_input1
2: ip_input13
SbS
(content and camera same size)
side-by-side 1: ip_input12
2: ip_input13
SbS
(content larger than camera)
4-split 1: ip_input1
2: ip_input13
3: None
4: None

Multiview Application Guide 13
Encoder Conguration
Application: Overow Rooms
When conguring encoders for multiview applications, the Encoding and Session conguration will depend on
the selected layout. This section will describe those settings; the reader should reference the AT-OMNI-111
documentation for information about other encoder conguration options.
Encoders that are connected to content sources will be assumed to be the primary content shown in the multiview.
If this content will ever be secondary, you can congure this encoder in the same manner as a camera encoder.
In the Encoding tab of the AT-OMNI-111, there will be two encoders that can be congured, including scalers for
each encoder. The recommended settings are shown in the table below:
*Because the content resolution in the 4-split layout is greater than supported by the Encoder 2 scaler, Encoder 1 will
be used. This means that 4K sources will be scaled down in the encoder, which could result in some loss of delity
in rooms that are not using multiview. In cases where the content is not being used in overow scenarios, the scaler
can be reprogrammed to 3840x2160, but it will need to be changed to 2880x1584 when an overow room is used.
Setting PiP SbS
Using side-by-side
template in decoder
SbS*
Using 4-split template in
decoder
Encoder 1 Input: hdmi_input1
Max bit rate: 750 Mb/s
Scaler: 3840x2160
Input: hdmi_input1
Max bit rate: 700 Mb/s
Scaler: 3840x2160
Input: hdmi_input1
Max bit rate: 700 Mb/s
Scaler: 2880x1584
Encoder 2 Input: Not used
Max bit rate: 150 Mb/s
Scaler: 1920x1080
Input: hdmi_input1
Max bit rate: 200 Mb/s
Scaler: 1920x1080
Input: Not used
Max bit rate: 200 Mb/s
Scaler: 1920x1080
Content Encoder
Figure 1.11 - Encoding tab on the AT-OMNI-111 with the elds highlighted that need to be changed based
on the target overow application.

Multiview Application Guide 14
Application: Overow Rooms
The Session tab contains the stream settings for each encoder. PiP only requires the use of Session 1 on Content
Encoders, whereas SbS requires the use of both Sessions. The conguration of the two sessions will be virtually
identical, but the reader is encouraged to adhere to the following guidelines:
• The scrambling key should be enabled (to support HDCP content) and set to the same streaming key as all other
encoders that will be used in the overow application.
• Session 1 Video should use encoder1 and Session 2 Video should use encoder2.
• The Destination IP address and UDP port for each Session should be assigned based on a scheme dened by
the end user. One recommendation is to pick a range of multicast addresses for the encoders, and assign odd
multicast addresses to Session 1 and even multicast addresses to Session 2. It is critical that no two encoders in
a system have the same multicast addresses.
• Only Session 1 needs to have Audio enabled and a unique multicast address assigned to it, since that one
stream can be used in overow rooms regardless of overow conguration.
Figure 1.12 - Session tab on the AT-OMNI-111 with the elds highlighted that need to be changed based on
the target overow application.

Multiview Application Guide 15
Encoders that are connected to camera sources will be assumed to be the secondary content shown in the
multiview. If this content will ever be primary, you can congure this encoder in the same manner as a content
encoder.
In the Encoding tab of the AT-OMNI-111, there will be two encoders that can be congured, including scalers for
each encoder. The recommended settings are shown in the table below:
*This will determine the size of the PiP window and can be made larger or smaller depending on the target PiP size.
The Session tab contains the stream settings for each encoder. The conguration of the two sessions will be virtually
identical, but the reader is encouraged to adhere to the following guidelines:
• The scrambling key should be enabled (to support HDCP content) and set to the same streaming key as all other
encoders that will be used in the overow application.
• Session 1 Video should use encoder1 and Session 2 Video should use encoder2.
• The Destination IP address and UDP port for each Session should be assigned based on a scheme dened by
the end user. One recommendation is to pick a range of multicast addresses for the encoders, and assign odd
multicast addresses to Session 1 and even multicast addresses to Session 2. It is critical that no two encoders in
a system have the same multicast addresses.
• Only Session 1 needs to have Audio enabled and a unique multicast address assigned to it, since that one
stream can be used in overow rooms regardless of overow conguration.
Setting PiP SbS
Using side-by-side
template in decoder
SbS
Using 4-split template in
decoder
Encoder 1 Input: hdmi_input1
Max bit rate: 750 Mb/s
Scaler: disable
Input: hdmi_input1
Max bit rate: 650 Mb/s
Scaler: disable
Input: hdmi_input1
Max bit rate: 750 Mb/s
Scaler: disable
Encoder 2 Input: hdmi_input1
Max bit rate: 150 Mb/s
Scaler: 960x528*
Input: hdmi_input1
Max bit rate: 250 Mb/s
Scaler: 1920x1080
Input: hdmi_input1
Max bit rate: 150 Mb/s
Scaler: 960x528
Camera Encoder
Application: Overow Rooms

Multiview Application Guide 16
Application: Overow Rooms
Now that the encoders and decoders have been congured, the one remaining step will be to assign the correct
multicast address and port numbers to the ip_inputs used within the multiview. Depending on the layout selected,
the multicast address and port number for the desired stream should be entered into the ip_inputs assigned to the
multiview.
Decoder Stream Conguration
Figure 1.13 - Decoder tab on the AT-OMNI-121 where multicast addresses will be assigned to ip_inputs.

Multiview Application Guide 17
In the case where content will be shown full screen, regardless of whether the content comes from within the room or
from another room, the programming will command the decoder to show ip_input1 and not a multiview.
Steps in programming:
1. Set the desired multicast address and port in ip_input1 on the decoder.
2. Switch the HDMI output on the decoder to ip_input1.
Using Velocity
In any of the rooms, you will want to give the user the ability to select what content is shown in that room. This could
be full-screen content from within the room, full-screen content from another room, or a multiview layout where the
content within the layout can also be changed.
Most of the time, the user will select the content that is shown using a touch panel. This section provides examples
of the programming required to change the content on the decoder. Examples are provided both using Atlona
Velocity macros and JSON.
Step 5: Programming the System
Showing Content Full-Screen
Application: Overow Rooms
Left Display to BluRay
Command 1 Custom Value:
Device: Left Display Decoder (10.1.0.19)
IP Input Set All
1
225.0.0.1
Hide In: Drawer
Device
Command
IP Input:
Multicast IP
Address:
Repeat: Interval: 10
00ms
Delay
ms
(After):
Preset Page
1000
Multicast Port:
off
Enabled:
Command 2 Custom Value:
Device: Left Display Decoder (10.1.0.19)
HDMI Output - Video Input
1
Device
Command
IP Input Start
Or Multi View
Name
Repeat: Interval: 10
00ms
Delay
ms
(After):

Multiview Application Guide 18
Application: Overow Rooms
Using JSON
The following two commands need to be sent to the decoder where the items in orange need to be changed for the
specic stream that will be viewed.
Changing the HDMI output to ip_input1:
{
"id": "ip_input-set",
"username": "admin",
"password": "Atlona",
 "cong_set":{
"name": "ip_input",
  "cong":[{
"multicast": {
"address": "225.0.0.1"
},
"name": "ip_input1",
"port": 1000
}]
}
}
{
"id": "ip_input-set",
"username": "admin",
"password": "Atlona",
 "cong_set":{
"name": "hdmi_output",
  "cong":[{
"name": "hdmi_output1",
"video": {
"input": "ip_input1"
},
"number": 1
}]
}
}

Multiview Application Guide 19
Application: Overow Rooms
Showing multiview in overow rooms is a matter of assigning which content and camera will be shown by setting
the correct ip_inputs on the decoder and then switching to that multiview. As described in a previous section, if the
content will be shown in a PiP layout or in a SbS layout with large content, the content will be assigned to ip_input1,
and if the content will be shown in a SbS layout, the content will be assigned to ip_input12.
Steps in programming:
1. Assign the content multicast address and port number to ip_input1 (PiP or large SbS) or ip_input12 (SbS).
2. Assign the camera multicast address and port number to ip_input13.
3. Switch the decoder to the desired multiview layout.
Showing Multiview in Overow Rooms
Using Velocity
Left Display to BluRay PiP
Command 1 Custom Value:
Device: Left Display Decoder (10.1.0.19)
IP Input Set All
1
225.0.0.1
Hide In: Drawer
Device
Command
IP Input:
Multicast IP
Address:
Repeat: Interval: 10
00ms
Delay
ms
(After):
Preset Page
1000
Multicast Port:
on
Enabled:
Command 2 Custom Value:
Device: Left Display Decoder (10.1.0.19)
IP Input Set All
13
225.0.0.11
Device
Command
IP Input:
Multicast IP
Address:
Repeat: Interval: 10
00ms
Delay
ms
(After):
1000
Multicast Port:
on
Enabled:
Command 3 Custom Value:
Device: Left Display Decoder (10.1.0.19)
HDMI Output - Video Input
None
multiviewPiP
Device
Command
IP Input Start
Or Multi View
Name
Repeat: Interval: 10
00ms
Delay
ms
(After):

Multiview Application Guide 20
Using JSON
Application: Overow Rooms
The following three commands need to be sent to the decoder where the items in orange need to be changed for the
specic streams and multiview that will be used.
Changing the ip_input1 multicast address and port:
Changing the ip_input13 multicast address and port:
Changing the HDMI output to the PiP multiview:
{
"id": "ip_input-set",
"username": "admin",
"password": "Atlona",
 "cong_set":{
"name": "ip_input",
  "cong":[{
"multicast": {
"address": "225.0.0.1"
},
"name": "ip_input1",
"port": 1000
}]
}
}
{
"id": "ip_input-set",
"username": "admin",
"password": "Atlona",
 "cong_set":{
"name": "ip_input",
  "cong":[{
"multicast": {
"address": "225.0.0.11"
},
"name": "ip_input1",
"port": 1000
}]
}
}
{
"id": "ip_input-set",
"username": "admin",
"password": "Atlona",
 "cong_set":{
"name": "hdmi_output",
  "cong":[{
"name": "hdmi_output1",
"video": {
"input": "multiviewPiP"
},
"number": 1
}]
}
}