LEDScreenCMS customer administrator handbook

Chapter 1

Your responsibility as customer administrator

Manage the users, content, desks and permitted screens of your own customer organisation. Customer admin is not the same as platform superadmin. Do not assume authority to transfer devices between customers, change platform licensing, delete another customer or install firmware simply because technical controls appear in an administrator screenshot.

Agree which changes you perform and which require the installer or platform administrator. Keep player identity, physical processor setup, network addresses, local eventserver route and approved mapping recorded for the installation. This handbook teaches customer operations and geometry; it does not replace a vendor-specific processor or wiring procedure.

End users need a route appropriate for their actual role. The companion end-user handbook distinguishes viewing, controlling and editing. Test that workflow with the intended permissions instead of using your administrator session as proof.

Chapter 2

Commissioning record before configuration

Record the customer, physical player model and serial number, number of physical HDMI outputs, installed autorun, actual output resolution and frame rate, LED processor input requirement, visible LED dimensions, logical face names and local control route. A model's decoding capacity is not automatically another physical HDMI connector.

Identify the device by serial number or hardware identity, not only by a similar name or shared public IP. Use the correct customer-bound startup profile. A new fixed HDMI preference may need a matching downloaded autorun, installation and restart; Save & apply alone is not proof that the hardware startup mode changed.

Use an agreed test period for calibration and visible changes. Record the pre-change mapping and display mode. Readiness, software feedback and browser simulations are useful but do not measure the physical wall's mapping, camera flicker or exact synchronisation.

Chapter 3

The geometry model you must verify

A Surface is a named logical visible face with a source rectangle. A slice is a source rectangle mapped into a destination rectangle in the HDMI raster. Its Surface selection associates the rule with a face but does not replace the numeric geometry. One face can use several slices. A physical cabinet grid is not automatically a list of separate faces.

A layout zone belongs to one design. It positions or organises layers and can define a supported source or blackout region. A playlist zone belongs to one zone playlist and has media per step. Neither is an automatic change to player slices.

The operational sequence is: create content in the design space; repack layout-local panorama surfaces if used; apply enabled player slices when CMS mapping is enabled; deliver the HDMI raster; let the processor route those pixels to the physical panels. Every link must be checked against the installation plan.

Chapter 4

Surfaces and slices from a verified plan

Define the real faces under Surfaces with names and Source X, Source Y, Width and Height. Use Add slice separately for each required sampling rule. Enter its Source and Output coordinates, association and Active state. Never rely on a matching name alone to make two different rectangles line up.

A source error can show the wrong design region on the correct physical face. An output error can put the correct region into the wrong HDMI area. Equal source and output dimensions avoid a size-changing scale step for that rectangle. Changed dimensions deliberately scale; changed aspect ratios can distort.

Keep rectangles within the agreed raster and inspect gaps, overlap and duplicated content. Import suggestions from supplier references are proposals. Confirm labelled measurements and distinguish a JPEG's image size from the actual HDMI raster. Tiny cabinet divisions inside a single face should not automatically become separate surfaces.

Chapter 5

Every Active and blackout control has a different scope

Apply CMS pixel mapping is the master mapping switch. When disabled, CMS mapping is bypassed and content continues to play. An active slice cannot override an inactive master switch. Disabling all slices is not a reliable general blackout: fallback content placement may still be used.

A surface's Active flag controls logical participation in surface-related editor tools and guides; it is not an independent physical power or blackout control. Check its associated slices separately. Use panel canvas is another setting for logical panel geometry and does not program the physical processor.

A layout zone's Blackout this zone covers a region when that layout is rendered. Layout output blackout is a layout adjustment in its selected context. Player-wide Black requests a black picture for the chosen player. Test pattern deliberately changes the calibration display state. Record which action was used and restore it through the matching workflow.

Chapter 6

Consequences for the layout editor

Choose Canvas reference screen to supply geometry for design. For a regular layout, a different reference can change the canvas size. Check existing layers, zones and aspect ratio afterwards. Show target is a separate set of recipients and must be reviewed independently.

When CMS mapping is enabled, the logical content bounds are derived from the active source slices; the editor can present named active surfaces within that space. When mapping is bypassed, the reference canvas can follow the output raster instead. A 252 × 336 visible source area and a 1920 × 1080 HDMI raster are therefore different valid dimensions with different meanings.

Surface focus is a view, not a new publish target. It can make one face convenient to edit while retaining the whole composition. Guides and snapping help align content; they do not fix an incorrect physical mapping. After any geometry change, open affected designs and inspect their references rather than assuming all layouts update safely.

A panorama stores its own logical surface arrangement and original packed positions. Changing the reference on an existing panorama does not automatically recalculate that composition for a different installation. Use a compatible reference or create a fresh approved panorama.

A valid enabled panel canvas can also supply reference dimensions. Confirm the approved Use panel canvas setting rather than assuming the panel canvas, active source bounds and HDMI raster are identical.

Chapter 7

A worked three-face installation

Take three faces, each 1920 × 256. Their packed source positions are Left at 0,0, Center at 0,256 and Right at 0,512. The packed source area is 1920 × 768 within a 1920 × 1080 HDMI raster. A panorama copy lays them out at X 0, 1920 and 3840 on a 5760 × 256 logical design canvas.

A point at panorama 2000,100 is on Center, 80 pixels from that face's left edge. Repacking takes it to source 80,356. If the Center slice is a one-to-one copy at output 0,256, the same point lands at HDMI 80,356. A different output rectangle or scale changes the final destination; the surface name does not override that transformation.

Confirm face labels with a test image. A supplier map may use a different packing than this example. Do not copy these numbers into a real installation without matching its verified plan. Check decoding capacity and installed player support for multi-surface video before a show.

Chapter 8

Teach users to draw and bind zones correctly

Give content creators an approved reference and explain that they edit design geometry rather than global mapping. Draw zone creates a layout rectangle. Enter exact X, Y, Width and Height after drawing. Make a two-column 1920 × 1080 layout with 960 × 1080 zones at X 0 and X 960 for a simple rehearsal.

In Layer, Zone chooses the association. Fill zone fits unlocked layers to the zone content box and follows normal geometry changes. Free placement keeps independent geometry. It does not guarantee clipping to the zone. Safe inset is a guide; overscan may enlarge fitted layer boxes. A layer lock can prevent fitting.

Duplicate copies the zone definition, not the assigned content layers. Mirror changes zone position, not image orientation. Spread evenly groups unlocked zones of the selected type horizontally. After these helpers, inspect or refit layer geometry deliberately.

Design, Output and Live zone are classifications. Source determines assigned layers or supported live content. The type name alone does not create a slice, physical output or input feed. Regional blackout is a layout rendering effect and should be taught separately from the player's Black action.

Chapter 9

Playlist geometry and automatic saves

Zone playlists use their own region and step model. Each step supplies content for the playlist zones. Full screen, Divide into and Draw zones build that arrangement; the layout-editor zone tools are separate.

Pixelmap import uses stored active slice source areas, normalised around their source bounds, and returns a playlist canvas. It does not import HDMI output placement as the design canvas, and it does not overwrite the player map. Stored slices can still be present while the master mapping switch is off, so review whether the imported arrangement matches the intended playback workflow.

Confirm replacement and inspect retained cells after importing. The playlist saves automatically; an active list may update without a new Show now click. Generated zone-playlist layouts must be edited in Zone playlists rather than as an ordinary layout. Use separate rehearsal copies and check dependencies before cleanup.

Chapter 10

Users roles modules and LightShell desks

Create customer accounts with the appropriate role. Viewer, Operator, Content editor and specialised event roles are not interchangeable. Follow actual account grants and application messages. Use administrator access for customer administration rather than as a shortcut for every daily task.

For LightShell, review four scopes: screens, content, available functions and allowed accounts. Task presets suggest features but do not replace the other selections. Include dependencies such as layout media, playlist files, sponsor assets and animation content when using a restricted library.

A LightShell-only account needs explicit desk assignment. Copy link does not grant access by itself. A customer-admin preview is not proof of an operator's permissions. Test with the intended role. Shared scoreboard edits can require access to all affected screens even if showing the scoreboard is allowed on a smaller desk scope.

Deliver credentials privately and keep password-reset results and MFA registration codes out of training material. Deactivating a desk prevents access but does not automatically stop its current screen picture; manage the desired display separately.

Chapter 11

Publishing scheduling and live show readiness

Use Content library for source files, Publish for immediate or timed publication, Screen storage for player copies and Show existing content for choosing already available content. Keep cloud, eventserver and player storage states separate. Selecting screens or browsing media does not itself constitute a show command.

For Events and Later publishing, check dates, time zones, overlap and the normal image after the block. For Sync, check exact participants, next content, preparation, READY, exclusions and GO. A changed cue needs new preparation. For Show lists, saving and arming are separate; stop or disarm automatic cues when operation ends.

Rehearse scoreboard goals, undo, clock periods, animation-only versus combined event recording, sponsor display and return. Check live HDMI source lock, fitting and audio on supported hardware. Keep Stream Deck trigger links private and verify their destination before giving the operator a button.

Chapter 12

Monitoring storage reporting and optional services

Use the most recent player contact, software state and HDMI information together. Activity helps connect an operator action with a time and screen. These are software reports, not physical camera observations. Avoid blindly repeating commands or restarting a healthy player as a routine repair.

Before migration or cleanup, review active content dependencies and local fallback needs. A cloud copy does not replace a required offline player copy. Recover through Recycle bin while retention allows it. Permanent purge is not the same as reversible removal.

Reports depend on received telemetry. Confirm range and UTC handling, grouping and selected screens. Ten seconds across three screens is thirty screen-seconds, not thirty seconds of unique audience attention. Compare sponsor delivery with the exact agreed media and destinations.

Optional Canva, Vision, AI and mobile notifications require customer configuration and the right account scope. Vision owns visitor registration and camera data; the CMS owns display scenes. AI commands need exact content and screen names, and accepted-command feedback is separate from confirmed rendering.

Chapter 13

Offline operation and hardware acceptance

Record which route is expected during WAN loss. A local eventserver has its own reachable address and must have the correct event, media and configuration prepared. An installed web-app icon does not automatically provide offline control.

Test separate scenarios: internet fails during playback; the eventserver fails; a player restarts without a network; an external livestream or HDMI input disappears. A file-readiness check does not prove all these cases, especially an offline cold start.

Ask the installer to verify physical pixel placement, signal lock, boot behaviour, panel orientation, camera use and practical video decoding capacity where relevant. Browser simulation, software readiness and automatic quality checks are useful evidence with limited scope; record the actual field result separately.

Chapter 14

Handover and change control

Retain the approved geometry record, installation contacts, normal standby image, role and desk matrix, known limitations and the intended local route. Provide the end-user handbook and practise the normal sequence with someone who did not configure the system.

Before changing mapping or a shared layout, check which content, schedules, playlists and screens use it. Keep the previous values and a known-good design available. Apply one understood change at a time and record what was checked; a saved setting alone is not an acceptance test.

After rehearsal, restore intended operation, end temporary blackouts or test patterns, disarm unwanted automatic cues and check the next schedule. Review account access when people leave or responsibilities change. Keep secrets in the appropriate private management process, not inside this guide.

• Approved hardware identity, HDMI mode, visible dimensions, surfaces, slices and master mapping state are recorded.
• The physical display and all required playback or offline scenarios have been checked by the responsible people.
• Users have suitable roles, explicit desks where required and the correct guide.
• Media dependencies and fallback content are available on the required route.
• The operator has rehearsed showing, temporary modes and return to normal operation.
• Support contact, unresolved limitations and change ownership are documented.

Chapter 15

Getting around Main

Open the correct customer workspace and find the tool you need.

Before you begin · Use your own account and confirm whether Main or an assigned LightShell desk is your normal workspace.

Procedure

1. Sign in

   Open the CMS address provided by your administrator. Use your own account and enter your authenticator code if requested.

2. Check the customer name

   Make sure you are working in the correct customer workspace.

3. Start with Overview

   Check the available screens and their most recent reported status.

4. Choose your task

   Use Publish to publish content, Content library for files, and Layout editor for designs.

Remember · A missing section may be caused by your account role or a disabled module. Ask your administrator if you need access.

What this changes · Navigation and inspection do not display new content.

Result check · You can identify the active customer and open the section for your task.

Practice · Find Overview, Publish and Content library. Open them without showing content on a screen.

Review questions

Open this as tutorial 01 →

Chapter 16

Understanding non-admin and customer-admin permissions

Choose the correct guide without assuming all non-admin accounts have the same capabilities.

Before you begin · Ask the customer administrator which role and workflow apply to you. The learning guides do not change those rights.

Common role differences

When a control is unavailable

A missing or disabled button can come from your role, a customer module, desk feature permissions, restricted content or target scope, no selection, an offline connection or unsupported hardware. Check the reason shown by the application instead of requesting unrestricted administrator access.

Procedure

1. Identify the account role

   Confirm it with the administrator and check whether LightShell only is enabled.

2. Identify the assigned workspace

   Use Main or the correct Control desk, not an unrelated shared link.

3. Match the task to access

   Read-only, showing, editing and configuration are separate responsibilities.

4. Check missing prerequisites

   Look for a selected screen, required module, desk content and supported hardware.

5. Request a precise change if needed

   Explain the task and screen instead of asking for every admin permission.

6. Choose the appropriate learning route

   Use the end-user guide for permitted daily tasks and the customer-admin guide for customer configuration.

Remember · Non-admin is an audience description, not one software role. A Viewer, Operator, Content editor and Event manager may have very different rights.

What this changes · Reading or selecting a guide changes no permissions. Actual access is enforced by the CMS.

Result check · You know which tasks your account supports and who handles the rest.

Practice · List three tasks you need, then ask your administrator to confirm the matching role and desk permissions.

Review questions

Open this as tutorial 02 →

Chapter 17

Customer admin setup and end-user handover

Hand over a configured installation with clear permissions and a usable daily workflow.

Before you begin · Complete installation verification with the installer. A customer administrator manages their own organisation; platform-wide customer ownership is a separate responsibility.

A practical handover record

Record customer and screen names, player identities, actual HDMI mode, visible LED dimensions, approved surface and slice geometry, mapping master state and intended content workflow. Keep credentials outside training screenshots.

Choose whether the end user works in Main or a limited LightShell desk. Grant the least access needed for their actual tasks. Do not assume a general Operator can edit layouts or that a Content editor can use every screen-control function. Check actual role grants, modules and desk permissions.

Test the end-user workflow as that role. An administrator's desk preview is useful for configuration but does not prove the operator has identical rights. Agree who can change mapping, who edits layouts and whom to contact for physical display faults.

Procedure

1. Confirm the installation baseline

   Check the real signal, approved surfaces and slices, saved state and normal standby content.

2. Create the intended user access

   Choose the correct role and desk assignment. Use private credential handover.

3. Review content and dependencies

   Include media required by layouts, playlists, animations and sponsors in restricted desks.

4. Run a role-based rehearsal

   Check sign-in, screen selection, prepare, show and return using the intended account permissions.

5. Provide the correct guide

   Give the end-user guide for daily work and retain this customer-admin guide for configuration.

6. Record acceptance and support

   Store approved geometry screenshots and a photo of the physical display, and document the support contact.

Remember · Documentation routes do not grant software permissions. Platform ownership changes, physical wiring and firmware installation still require the appropriate responsible person.

What this changes · This handover coordinates account and installation configuration. It is not itself a physical certification or an automatic permission change.

Result check · The end user can complete the approved daily tasks and knows which changes need an administrator or installer.

Practice · Rehearse the handover with one person who did not configure the installation.

Review questions

Open this as tutorial 03 →

Chapter 18

Identifying and linking a screen

Match the correct physical player to the correct customer and screen name.

Before you begin · Customer administration or delegated commissioning access is required. Coordinate physical installation and ownership assignment with the responsible installer or platform administrator.

Procedure

1. Record the installation details

   Collect the serial number, player model, LED pixel dimensions and required HDMI signal.

2. Open Screens & setup

   Check the customer workspace first. Ask a platform administrator to review hardware ownership under Device assignments.

3. Use the correct startup profile

   Have the installer install the autorun or startup link intended for this customer and player.

4. Check the name and identity

   Find the connected player by serial number. Use a clear screen name and check its assigned group.

5. Check the response

   Then continue to Output & Mapping for this one screen.

Remember · Each physical player needs its own identity. Do not reuse one device startup link for two different screens. Groups collect screens; profiles define settings.

What this changes · Commissioning links an actual device and its customer configuration. It is not simply creating a content design.

Result check · The real serial number, customer and screen name all match.

Practice · For an existing installation, identify the physical device represented by a screen card.

Review questions

Open this as tutorial 04 →

Chapter 19

Surfaces slices and zones explained

Recognise which object describes the screen, which maps pixels, and which organises content.

Before you begin · This is a read-only explanation for every role. Changing screen mapping requires separate permission.

Four different objects

How they work together

The designer arranges layers in a layout. Layout zones help position those layers. A panorama layout may arrange logical surfaces side by side for easier design, then repack them into their original source positions. The player applies the enabled slices to place selected source pixels in the HDMI output. The LED processor then takes the relevant HDMI pixels to the physical panels.

A surface can have more than one slice; naming a surface does not automatically create a slice. A layout zone does not become a slice. A cabinet grid inside one face does not automatically mean several surfaces.

Procedure

1. Identify the physical faces

   Use names such as Front and Back for separate intended faces, not for every cabinet.

2. Find the surfaces

   In the editor, review the available Surface names from the reference screen.

3. Identify the slices

   In Output & Mapping, compare each slice's Source and Output rectangles if you have viewing access.

4. Find design zones

   In Composition → Zones, inspect the regions that belong to this layout.

5. Use the correct tool

   Ask for a mapping correction if the physical placement is wrong. Edit a layout zone when the content arrangement is wrong.

Remember · One physical screen can contain many layout zones. A zone name or type does not rewire the processor or create an output slice.

What this changes · Reading this lesson changes nothing. Layout-zone edits affect a layout; mapping edits affect the configured player after application.

Result check · You can explain which object must change for a content-layout problem and which for a pixel-placement problem.

Practice · Describe an installation with two faces and one sponsor area inside each. Identify the surfaces, slices and layout zones separately.

Review questions

Open this as tutorial 05 →

Chapter 20

Defining surfaces for a customer screen

Describe the intended visible faces without confusing them with output placement.

Before you begin · Use a verified supplier plan and an agreed maintenance window. Confirm your customer's player and existing configuration before editing.

What a surface stores

A surface has a name, source X and Y, width, height and an Active state. These values describe the logical source area of that face. The linked slice separately determines where its source pixels land in the HDMI raster.

Use Add surface to describe a face. Use Add slice to create a mapping rule. Do not assume adding one automatically adds the other. Match their names and coordinates deliberately.

Example of stacked source faces

Procedure

1. Record the existing arrangement

   Note the player, HDMI raster, surface coordinates, active slices and saved preview.

2. Open the surface controls

   In Output settings, locate Surfaces and use Add surface where a real face is missing.

3. Enter the face name and source dimensions

   Use verified pixels. X increases to the right; Y increases downward.

4. Set Active deliberately

   Keep intended editor faces active. A surface's Active switch is not an independent physical blackout.

5. Review the linked slices

   Check their Surface selector and all Source and Output values.

6. Apply and verify

   Use Save & apply only after review. Then check the reference screen, layout view and the real display on the agreed setup.

Remember · A customer administrator works inside their organisation. Platform ownership transfers, firmware and physical processor configuration may need the platform administrator or installer.

What this changes · Saved surfaces influence reference geometry and available editor surface views. Surface changes alone do not install a new processor configuration.

Result check · Every intended face has a verified name and source rectangle, and its slices have been reviewed.

Practice · Reproduce the three-face example in an agreed test setup. Compare stacked source geometry with the side-by-side design view.

Review questions

Open this as tutorial 06 →

Chapter 21

Creating and linking mapping slices

Map a verified source area into the intended HDMI output area.

Before you begin · Get the actual source composition dimensions and the processor's required HDMI positions. Use one explicitly selected player.

One face can need several mapping rules

A slice contains a source rectangle, an output rectangle, an Active checkbox and a Surface selection. The Surface field provides an association; the actual source and output numbers still need to be correct.

For example, two 960 × 256 source halves can be placed into separate output rectangles. Both slices may belong to the same named Front surface. This is different from inventing two physical faces just because the processor uses two rectangles.

A simple one-to-one example

Procedure

1. Choose Add slice

   Give the new rule a clear name and select its intended Surface, or Complete canvas when appropriate.

2. Enter Source values

   Choose exactly the content rectangle to sample. Check that it contains the intended pixels.

3. Enter Output values

   Use the destination requested by the processor plan. Keep the rectangle within the HDMI raster.

4. Check aspect ratio

   Equal source and output sizes preserve native pixel dimensions. Different dimensions introduce scaling.

5. Check both Active controls

   The slice must be active and Apply CMS pixel mapping must also be enabled.

6. Apply and compare

   Review all slices, Save & apply and compare a labelled test image with the physical faces at an agreed time.

Remember · An incorrect source can show the wrong content on an otherwise correctly positioned face. An incorrect output can place correct content in the wrong HDMI region.

What this changes · Applying slice changes affects the player's mapping. It is not a layout-only edit and may change all content using that player mapping.

Result check · The intended source pixels reach the intended output rectangle with the intended scale.

Practice · Trace one labelled face from the source composition to its output rectangle and physical display.

Review questions

Open this as tutorial 07 →

Chapter 22

Understanding pixelmap Active and Not Active

Understand when the CMS applies pixel mapping and when it bypasses it.

Before you begin · Mapping access and an approved installation plan are required before changing any values. Other users should read the geometry concepts and report issues.

Consequences beyond a checkbox

Mapping belongs to the player. Switching the master off can change the reference canvas from mapped source bounds to the output raster. Recheck affected layouts and previews with the administrator; do not use this switch as an ordinary layout-edit tool. Surface Active and slice Active have different roles, described in the detailed geometry lessons.

Procedure

1. Open Output & Mapping

   Under Player being configured, choose exactly the player you intend to configure.

2. Find the master switch

   The current name is Apply CMS pixel mapping. Older screens use Pixel map active.

3. Choose the intended behaviour

   Active applies CMS mapping. Not Active bypasses CMS mapping; content continues playing.

4. Check the slices too

   A slice marked Active is only used when the master switch is also enabled.

5. Save deliberately

   Check all dimensions and use Save & apply when the configuration is ready to be applied.

Remember · Disabling all slices is not a reliable way to request a black picture. Use the separate Black control when black output is your goal.

What this changes · Save & apply changes the configured player mapping, potentially affecting all content using it.

Result check · You can distinguish the master switch from a slice's Active checkbox.

Practice · Find both settings and read their current states without changing the configuration.

Review questions

Open this as tutorial 08 →

Chapter 23

Positioning a slice correctly

Select the correct source area and position it correctly in the output.

Before you begin · Use verified source and output coordinates for one explicitly selected player. Changing a slice is a player configuration task.

Position and scale are independent

The Source rectangle chooses content pixels. The Output rectangle chooses where those pixels land and how large the result becomes. Matching names or assigning a surface does not automatically make these coordinates equal. Check both sets of dimensions and the master mapping state.

Procedure

1. Choose the player and slice

   Check the player name and select the slice to edit on the left.

2. Set the source

   Use Input Selection and Source X, Y, W and H to choose a rectangle from the composition.

3. Set the destination

   Use Output Transformation and Output X, Y, W and H for position and size within the HDMI raster.

4. Check the aspect ratio

   Preserve the aspect ratio when distortion is unwanted. Stretch may distort logos and circles.

5. Check and apply

   Review the simulation and compare the pixel values with the installation plan. Then use Save & apply.

Remember · X and Y define position; W and H define width and height. Values are in pixels. X 0 and Y 0 are at the top left.

What this changes · A slice edit affects source sampling and HDMI placement on the configured player after application.

Result check · The slice uses the correct source area and fits within the intended output area.

Practice · Identify Source and Output and explain why their dimensions might differ.

Review questions

Open this as tutorial 09 →

Chapter 24

Checking HDMI and the panel canvas

Distinguish the physical HDMI output from the logical panel canvas.

Before you begin · Have the installer provide the actual required HDMI signal, visible LED dimensions and approved panel topology.

Procedure

1. Check the actual HDMI signal

   Use player feedback and the installation plan. Record resolution and frame rate.

2. Choose the CMS output format

   Set Output format to the agreed raster. This field alone does not prove that the physical HDMI signal has changed.

3. Check the panel arrangement

   Enter verified panel dimensions, columns, rows and orientation where your installation uses a panel canvas.

4. Review Use panel canvas

   This option uses the logical panel arrangement. It does not program the LED processor.

5. Install hardware changes properly

   A changed fixed BrightSign HDMI mode also needs the matching saved autorun, installation and a restart.

Remember · A smaller visible LED area can sit within a larger HDMI raster. Canvas size, HDMI signal and processor mapping are separate settings.

What this changes · The logical canvas and actual HDMI mode have different installation paths. Verify both before accepting the result.

Result check · The reported HDMI mode and agreed LED pixel dimensions are recorded and match the installation plan.

Practice · Record the HDMI raster size and visible LED pixel size of one existing screen.

Review questions

Open this as tutorial 10 →

Chapter 25

Viewing and checking the pixelmap

Use zoom, references and previews while keeping viewing separate from applying settings.

Before you begin · View controls and configuration controls are different. Use mapping-edit permissions before applying geometry or uploading a reference.

Procedure

1. Choose the appropriate view

   Input Selection shows the source. Output Transformation shows placement. LED wall simulation shows a combined simulation.

2. Use Fit or 1:1 pixels

   Fit scales the diagram to the window. 1:1 pixels helps inspect precise details. These controls only change the editing view.

3. Use Pan to look around

   Pan moves your viewpoint. It does not move slices.

4. Check a reference

   Under Pixelmap reference, upload a supplier image if needed. Manually verify proposed dimensions and names against the real plan.

5. Compare the draft with the saved preview

   The diagram may show unsaved edits. Saved output uses saved settings. Save & apply applies your checked changes.

Remember · A supplier image is an editing guide. A simulation is not a capture of the real HDMI signal. Test pattern deliberately switches the physical display to a test image.

What this changes · Fit and Pan are view-only. Geometry application, reference upload and test-pattern commands have their own scopes.

Result check · You know which view shows a draft and which uses saved settings.

Practice · Use Fit, 1:1 pixels and Pan. Check that these actions do not change the configuration.

Review questions

Open this as tutorial 11 →

Chapter 26

Reference screen and surface focus in the editor

Understand why the selected reference screen changes the editor's geometry.

Before you begin · Ask the customer administrator for the approved reference screen and expected canvas dimensions.

Reference is not the publishing target

Canvas reference screen provides geometry for design. Show target selects which screens receive an action. They have different jobs. A reference choice is not permission to publish to all screens, and choosing destinations does not guarantee that every destination has matching mapping.

For a regular layout, changing the reference can update the canvas dimensions to the selected screen's logical content bounds. Use this early in design and review existing content afterwards; do not assume every layer has been safely rearranged for a new aspect ratio.

Surface focus shows one named logical source area as a convenient editing view. Complete canvas shows the overall source composition. Focusing a surface does not turn other physical faces off. Position fields may be presented relative to the focused view while the layout still contains the whole composition.

A panorama already stores its own logical arrangement. Changing its reference does not automatically rebuild that stored composition for another installation. Review compatibility or create a fresh approved panorama.

Panel canvas may also supply dimensions

An enabled, valid panel canvas can supply reference dimensions before the normal content bounds are used. Confirm the approved Use panel canvas choice with the administrator instead of assuming HDMI, source bounds and panel canvas always have the same size.

Procedure

1. Check the approved reference

   Choose it before adding detailed content.

2. Review the resulting dimensions

   Confirm the canvas ratio and known pixel dimensions.

3. Choose a Surface view

   Compare Complete canvas or All surfaces with one named surface.

4. Place content deliberately

   Keep important content inside the intended visible source area.

5. Check Show target separately

   Choose only screens whose geometry is suitable for this layout.

6. Preview and save

   Review all faces and use Save layout before preparing or showing.

Remember · A reference screen supplies geometry. Show target supplies destinations. Neither choice replaces a compatibility check.

What this changes · Reference selection can change layout dimensions. Surface focus changes the editing view; it does not independently change the physical output.

Result check · You can identify the reference, the current surface view and the actual show destinations.

Practice · Switch between the full composition and a named surface in an existing practice layout without publishing.

Review questions

Open this as tutorial 12 →

Chapter 27

From stacked surfaces to a panorama and back

Trace exact pixels from a panorama design back to the packed source and HDMI output.

Before you begin · Use a verified three-surface reference and a current compatible player renderer. Work in a new practice layout.

A complete numerical example

Where a point goes

In this example the original packed content area is 1920 × 768, placed within a 1920 × 1080 HDMI raster. The panorama is 5760 × 256. A point 80 pixels from the left edge of Center has panorama X 2000. Repacking returns it to packed source X 80, Y 256 plus its local Y. A slice then determines its HDMI destination.

The panorama does not force HDMI to become 5760 pixels wide. It is an easier logical design canvas whose surface rectangles are packed back into the original arrangement before player mapping. General content preview, HDMI output preview and LED-wall simulation therefore show different coordinate spaces.

Conversion retains the existing layout and starts a new panorama draft. Layers or zones that ambiguously cross the old stacked surfaces may prevent safe conversion. Use an empty panorama or fix the ambiguous content first. Do not guess missing physical geometry from a drawing.

Procedure

1. Check the surface source rectangles

   The faces must be valid and non-overlapping.

2. Create or open a suitable draft

   A simple empty layout avoids ambiguous existing cross-surface layers.

3. Choose Surfaces side by side

   Confirm the new panorama name and canvas dimensions.

4. Design across or within surfaces

   Use All surfaces for a continuous design or select a single named face.

5. Save the new layout

   Keep the original packed layout as a separate reference.

6. Check packed output

   Compare panorama content, saved HDMI output and the real faces on the intended setup.

Remember · Panorama geometry belongs to the layout. It does not overwrite the player's physical mapping or guarantee that a different customer's screen will match.

What this changes · The layout stores a logical surface composition and is repacked by compatible player software. Existing global slice coordinates remain separately configured.

Result check · You can trace one labelled object from its panorama face to the correct packed and output position.

Practice · Put LEFT, CENTER and RIGHT into the matching faces and verify each view on an agreed test setup.

Review questions

Open this as tutorial 13 →

Chapter 28

Drawing zones in the layout editor

Draw a layout zone and give it exact pixel dimensions.

Before you begin · Create a practice layout. Use the correct canvas size or approved reference screen. Operators and Viewers need additional editing permission to use this workflow.

Drawing creates layout geometry

Open Composition and expand Zones. Draw zone arms a drawing tool; drag across the composition canvas to create a rectangle. Escape cancels the drawing tool. A new zone starts as a Design zone with Assigned layers as its source.

The drawn rectangle is an estimate until you check its numeric X, Y, Width and Height fields. A 1920 × 1080 canvas can be split exactly into Left content at 0,0,960,1080 and Right content at 960,0,960,1080. No player slice is created by this operation.

Procedure

1. Set the canvas first

   Confirm Width and Height before drawing. Choose the intended Surface view if working on one face.

2. Open Composition then Zones

   Select Draw zone. Drag from one corner to the opposite corner on the canvas.

3. Name the zone

   Use a meaningful name such as Left content or Sponsor strip.

4. Enter exact coordinates

   Check X, Y, Width and Height in pixels. Make the intended edges meet without accidental gaps.

5. Set the basic zone options

   Choose Design zone and Assigned layers for a normal content region. Review Safe inset and leave Overscan at zero unless you need it.

6. Save the layout

   Use Save layout when the design is ready. Prepare and Show are separate actions.

Remember · A zone outline is an editing aid. It does not automatically add a photo or video, and its border is not automatically printed into the displayed content.

What this changes · The zone is stored inside this layout. It does not change the player's global surfaces, slices, HDMI mode or physical processor.

Result check · The named zone has exact, deliberate coordinates and the layout has been saved.

Practice · Create the two 960 × 1080 regions shown in the example. Keep the layout off live screens while practising.

Review questions

Open this as tutorial 14 →

Chapter 29

Moving resizing and locking zones

Change zone geometry precisely and understand which layers follow it.

Before you begin · Check which layers are assigned to the zone before changing its geometry.

The effect on assigned layers

Choose a zone in the list or enable Move zones. Drag inside the rectangle to move it, or drag its corner to resize it. Exact pixel fields give a reproducible result. Arrow keys move a selected zone by one pixel; Shift plus an arrow uses ten pixels.

Unlocked layers assigned with Fill zone are repositioned and resized to the zone's content box. Layers set to Free placement do not follow this automatic fitting. Lock zone protects the zone from ordinary geometry changes; it is not access control for other users.

Removing a zone

Delete removes the selected zone and clears that zone association from its assigned layers; it does not delete those layers. Check their remaining positions. Redrawing a rectangle creates a new zone identity, so reassign layers deliberately.

Procedure

1. Select the zone

   Use the named entry in Composition → Zones. Check that you are editing zones rather than dragging a content layer.

2. Inspect its assigned layers

   Review their Zone and Inside zone settings in Layer.

3. Move or resize

   Use the rectangle or exact X, Y, Width and Height fields.

4. Check snapping

   Use Snap on or Snap to surfaces where available. Confirm exact numbers after a drag.

5. Review the result

   Check all filled layers and any free layers. Check safe edges and neighbouring regions.

6. Lock and save

   Use Lock zone if accidental geometry changes must be prevented, then Save layout.

Remember · A layer lock can prevent that layer from being automatically fitted. Check both the zone and the layer when a change does not behave as expected.

What this changes · The layout geometry changes. Filled, unlocked assigned layers can change along with it; physical screen mapping remains unchanged.

Result check · The zone and all intended following layers are correctly positioned.

Practice · Resize a practice zone with one filled layer and one freely positioned layer. Compare what follows and what stays in place.

Review questions

Open this as tutorial 15 →

Chapter 30

Fill zone versus Free placement

Choose whether a layer should follow zone geometry or keep its own box.

Before you begin · Create a zone and add a text, image or video layer. Select the layer before using the Layer inspector.

The important difference

Fitting is not the same as clipping

Zone assignment sets or maintains the layer's rectangle in the editor. It is not a universal clipping mask around all assigned layers. With Free placement, content may extend beyond the zone. Image or video fit settings separately determine whether the source is contained, cropped or stretched inside the layer box.

The Fit layers button can fit selected layers to the selected zone; if no layers are selected, it uses layers already assigned to that zone. This explicitly changes those layers to Fill zone. Check your selection before pressing it.

Recognise the clipping example

The second screenshot deliberately exposes an undersized free layer box: only part of WELCOME is visible. Free placement does not automatically make its box large enough for the current font and padding. Increase the box or reduce text size and check the whole word again. The first screenshot shows the complete word when the layer fills the zone.

Procedure

1. Select the layer

   Click it in the monitor or Layers list, then open Layer.

2. Choose Zone

   Select the named layout zone.

3. Choose Inside zone

   Use Fill zone for automatic fitting, or Free placement for a custom layer box.

4. Check the dimensions

   With Fill zone, review the zone box. With Free placement, enter the desired layer X, Y, Width and Height.

5. Check source fit separately

   For images or video, review how the actual picture fills that box.

6. Preview and save

   Move or resize the practice zone to confirm the chosen behaviour, then save the layout.

Remember · Assigning a zone does not add a second independent clipping boundary around a free layer. Keep essential content inside the actual visible source areas.

What this changes · This changes layer geometry and binding within the layout. It does not create or move a mapping slice.

Result check · You can predict whether the layer follows the next zone resize.

Practice · Compare the two screenshots, then switch a practice layer between Fill zone and Free placement.

Review questions

Open this as tutorial 16 →

Chapter 31

Safe inset overscan and visible edges

Keep important content readable without confusing guides with output cropping.

Before you begin · Use a known layout size and verify which pixels are actually visible on the LED installation.

Three separate ideas

Safe inset creates an inner safety guide in the editor. It helps you keep essential text and logos away from edges. It does not automatically crop media or shrink all layer boxes to that inset.

Overscan expands the content box used when layers are fitted to the zone, subject to canvas bounds. Zero is the precise starting point. Increasing it can push image edges or text outside the intended region.

The player's source slices decide which source pixels are sampled for output. A safe guide does not change those slice coordinates.

A practical example

For a 960 × 1080 zone, a 24-pixel safety guide leaves an inner area from X 24 to X 936 and Y 24 to Y 1056 relative to the zone. This is a design guideline, not a new physical 912 × 1032 screen. Place important content intentionally inside it.

Procedure

1. Select the zone

   Open its numeric settings in Composition → Zones.

2. Set a meaningful Safe inset

   Use a pixel margin appropriate for text and logos on this installation.

3. Start Overscan at zero

   Increase it only for an intentional bleed or installation requirement.

4. Check fitted layers

   Review the layer box after changes; overscan can enlarge it.

5. Review actual visibility

   Compare the layout, saved-output simulation and physical display before using the design in a show.

6. Save the tested layout

   Keep the chosen margin and overscan recorded with the design.

Remember · A dashed safe line is not a clipping boundary and is not automatically part of the displayed picture.

What this changes · Safe inset is a design guide. Overscan may change fitted-layer geometry. Neither rewrites physical LED processor mapping.

Result check · Essential text remains readable and no unintended edge is cropped.

Practice · Place a logo near a zone edge, add a 24-pixel safety guide and reposition the logo deliberately.

Review questions

Open this as tutorial 17 →

Chapter 32

Duplicating mirroring and distributing zones

Build repeatable zone arrangements and check the resulting layer positions.

Before you begin · Make a practice copy. Know which zones are locked and which layers are bound to them.

What the tools actually copy or move

Duplicate copies the selected zone with a new identity, a small position offset and an unlocked state. It does not duplicate the content layers assigned to the original zone. Name the copy and enter exact coordinates.

Mirror horizontally or vertically moves the zone rectangle to a reflected position around the full canvas. It does not mirror the media image. Spread evenly distributes unlocked zones of the selected zone's type horizontally, with equal outer and internal gaps. It is not an automatic vertical grid builder.

These helper actions should be followed by a layer review. Do not assume every existing layer binding has been repositioned simply because the zone outline moved. Check or reapply Fit layers where needed.

Procedure

1. Select the source zone

   Check its name, type, dimensions and source.

2. Duplicate when another region is needed

   Rename the new zone and set its exact X and Y.

3. Use Mirror deliberately

   Choose the required axis and confirm the resulting rectangle; this is a position operation.

4. Use Spread evenly for a row

   Select the desired zone type, leave enough total empty width and review unlocked participants.

5. Add or review content layers

   Create separate content where required. Check each layer's Zone and Inside zone settings.

6. Preview and save

   Check every region and save the finished layout.

Remember · Duplicating a zone does not clone its assigned media layers. Mirroring a zone does not flip the picture inside it.

What this changes · These tools organise layout-zone rectangles. They do not duplicate hardware, slices or physical surfaces.

Result check · The arrangement is deliberate, with matching content in each intended region.

Practice · Duplicate a left region to make a right region, then assign a separate logo layer to the copy.

Review questions

Open this as tutorial 18 →

Chapter 33

Zone types sources and blackout

Understand which zone options affect the rendered content.

Before you begin · Use a draft layout and identify whether your player supports the live source you intend to use.

Type is not a physical output mapping

Design zone, Output zone and Live zone classify a layout region and help organise the editor. Selecting Output zone does not create a player slice or assign an HDMI connector. Selecting Live zone alone does not create a live source.

Source determines whether the zone uses assigned layers, the supported live HDMI input or a livestream URL. Assigned layers does not automatically insert media: create and assign actual layers. A valid supported stream and working network are needed for livestream playback.

Blackout this zone adds a black covering region when this layout is rendered. This differs from the player-wide Black action and from merely disabling a mapping slice. Lock zone only prevents ordinary editing of zone geometry.

Live HDMI restrictions

A supported player has a limited hardware input plane. Do not expect multiple independent HDMI sources from one connector or combine conflicting HDMI zones and layers. Keep the live region free of opaque covering layers and check the actual device. Panorama use of live hardware input needs particular caution; use an approved regular layout for that workflow.

Procedure

1. Choose the zone Type

   Use a meaningful classification without assuming it changes physical routing.

2. Choose Source

   Use Assigned layers for ordinary content, or the supported live source you actually need.

3. Supply a stream address if required

   Use a supported HTTP or HTTPS stream and verify compatibility on the intended player.

4. Review blackout and locks

   Use Blackout this zone deliberately; distinguish it from Lock zone.

5. Check overlay order

   Confirm that opaque layers do not hide the intended live picture.

6. Test and save

   Check the physical device on an agreed test setup before showing the layout in a live event.

Remember · Changing a layout zone source or blackout can alter the picture when that layout is displayed. A zone type label alone does not establish a live feed.

What this changes · Source and zone blackout affect this layout's playback. They do not reprogram the global pixelmap or LED processor.

Result check · You can explain which source produces the zone's pixels and how temporary blackout is removed.

Practice · In a draft, compare Assigned layers and the live-source fields. Toggle zone blackout in the draft and inspect the preview without publishing.

Review questions

Open this as tutorial 19 →

Chapter 34

What saving previewing and showing actually change

Choose the correct action and understand its scope before affecting a display.

Before you begin · Know whether you are editing a layout, an active playlist or a player's mapping. Their save actions have different scopes.

Action and scope

Draft versus saved-output simulation

The mapping diagram can show an unsaved draft while Saved output still follows saved settings. A layout monitor shows the design being edited. Neither is a physical HDMI camera capture. Compare the appropriate views and use a real screen check for installation acceptance.

Procedure

1. Name the object you are changing

   Is it one layout, one playlist or a player's mapping?

2. Read the action label

   Do not substitute Save & apply for Save layout or assume Preview is a publication.

3. Check current use

   An existing active object may already be referenced by playback or a schedule.

4. Confirm destination before a display action

   Read all selected screen names, not just the previewed screen.

5. Read the result

   Check save state, accepted commands, readiness and excluded screens as appropriate.

6. Verify the visible outcome

   Use the physical display when the action affects output.

Remember · A stored design, an accepted CMS command, a rendered player picture and the physical LED result are different stages.

What this changes · The scope depends on the action. This comparison helps prevent a player-wide mapping change while intending to edit only a layout.

Result check · You can describe exactly what your next click will change and which check follows it.

Practice · For three actions on your current page, explain their scope before clicking anything.

Review questions

Open this as tutorial 20 →

Chapter 35

Creating a simple layout

Create a saved design with the correct canvas dimensions.

Before you begin · Layout editing must be available to your role. Choose an approved canvas or reference screen before designing.

Procedure

1. Open Layout editor

   Start a new design and give it a clear name.

2. Choose the correct canvas size

   Use the agreed screen dimensions or an appropriate Canvas reference screen. Check Width and Height.

3. Add content

   Use Media for an image or video, and Text for a text layer.

4. Review the design

   Check the composition monitor for readability, margins and the correct aspect ratio.

5. Use Save layout

   Use Prepare and Show separately when the design may appear on a selected screen.

Remember · Save layout saves your design. Show displays it on the chosen screen. Check Show target before showing anything. When editing an existing layout, check whether it is already used by a live screen or schedule.

What this changes · Save layout stores the design. Check active uses of an existing layout; Prepare and Show are separate actions.

Result check · The design has the correct name and canvas size, and has been saved.

Practice · Create a practice layout with one image and the text Welcome. Save it without showing it.

Review questions

Open this as tutorial 21 →

Chapter 36

Editing text and layers

Change the intended text or image without editing another layer by mistake.

Before you begin · Use a practice layout or an approved version. Select the intended layer and check whether the layout is already in use.

Procedure

1. Select the correct layer

   Click the item in the monitor or select its name in Layers.

2. Open Layer

   Adjust the available text, media, position or style settings for the selected layer.

3. Check the layer order

   A higher layer in the list may cover a lower one. Give layers clear names.

4. Check the picture

   Read the text at the real design proportions. Keep logos and important text away from unintended cropping.

5. Save the change

   Use Save layout and check the save status.

Remember · Workspace rotation rotates your editing view. It is separate from the rotation of the content itself.

What this changes · Layer content and geometry change inside the layout. Player-wide surfaces and slices are not edited here.

Result check · Only the intended layer has changed and the composition remains readable.

Practice · Change one text layer in a practice layout and give the layer a clear name.

Review questions

Open this as tutorial 22 →

Chapter 37

Designing across multiple surfaces

Use a panorama or focus on one named surface within a layout.

Before you begin · Use verified, non-overlapping surfaces from an approved reference and compatible player software. See the full geometry lessons for the conversion limits.

Procedure

1. Choose a suitable reference screen

   Use an existing, verified surface arrangement.

2. Create a panorama if needed

   Surfaces side by side creates a new design draft. The existing design is retained.

3. Choose Surface

   Use All surfaces for the panorama, or select a named surface to work on it individually.

4. Align the content

   Use Snap to surfaces to align layers with surface edges.

5. Check and save

   Check canvas dimensions and the supported player route. Test the complete layout on the intended installation before using it in a show.

Remember · The panorama is a logical design space. The player must support packing the layout into the intended output positions; this does not reconfigure the physical processor.

What this changes · A new panorama draft stores layout-local surface geometry. Global player mapping remains separately configured.

Result check · Content is on the intended surfaces and the saved layout uses the correct arrangement.

Practice · Switch between All surfaces and one named surface and compare the views.

Review questions

Open this as tutorial 23 →

Chapter 38

Using the timeline

Control when layers appear within your layout.

Before you begin · You need layout-editing rights and at least one layer. Use local Play for rehearsal, keeping display actions separate.

Procedure

1. Open the timeline

   If only the Timeline bar is visible, choose Show timeline.

2. Select a layer

   Find the same layer name in the layer list and on the timeline.

3. Adjust the timing

   Move the clip or its start and end points using the available controls.

4. Review the sequence

   Use Play for the local preview. Check when each layer appears and disappears.

5. Make room and save

   Drag the divider or use Expand timeline. Save the design or sequence with the appropriate save action.

Remember · Expand timeline and Collapse change your workspace. They do not publish the design. Play in the editor is a local check; Save & play sequence is a separate save-and-play action.

What this changes · Layer timing is stored with the layout. Timeline view controls alone do not publish it.

Result check · Layers appear in the intended order and their timing has been saved.

Practice · Make two text layers appear one after another in a practice layout, then check them with local Play.

Review questions

Open this as tutorial 24 →

Chapter 39

Layout quality checks and output adjustments

Improve readability while keeping software adjustments separate from hardware calibration.

Before you begin · Use the approved canvas and display setup. Establish an acceptable picture with the installer before applying design-level adjustments.

What the editor can and cannot guarantee

LED Quality Control flags potential issues such as small text, thin lines, low contrast or aggressive motion. Pixel pitch preview, camera-related presets and gamma preview help assess a design; they do not physically change the panel pitch, processor refresh or camera shutter.

Output adjustment is stored with the layout and the selected layout target context. Review its label before changing brightness or blackout. It is separate from physical LED processor calibration, player-wide Black and per-zone Blackout this zone. A strong software brightness change can alter the design without correcting uneven physical panels.

Procedure

1. Review all visible faces

   Use surface focus and the complete view to check text size and important edges.

2. Read LED Quality Control

   Resolve specific warnings by changing the actual design where appropriate.

3. Keep motion readable

   Check the timeline, frame-rate suitability and repeated movement.

4. Review the output-adjustment scope

   Read the target label before using Day, Night, calibrated values or layout blackout.

5. Preview on the intended device

   Check actual readability and any camera use with the installer or show team.

6. Save the approved design

   Record what was tested and retain a normal fallback.

Remember · Software preflight is useful guidance, not a measurement of physical LED output or camera performance.

What this changes · Design and layout-level adjustments can change this layout's rendered picture. They do not reprogram the processor or certify the hardware.

Result check · The design is readable on the intended surfaces and the adjustment scope is understood.

Practice · Find one quality warning in a practice design and correct its cause rather than only dismissing it.

Review questions

Open this as tutorial 25 →

Chapter 40

Creating a zone playlist

Create a sequence with one full-screen image or several simultaneous zones.

Before you begin · Playlist-editing controls must be available. Start a separate practice list because editing an active list can affect live playback.

Steps and zones

A step is one simultaneous combination of media across playlist zones. The next step changes that combination after its duration. A playlist region is not a layout-editor design zone, and neither is the same as the player's output slice. See the dedicated playlist-geometry lesson before importing or redrawing zones.

Procedure

1. Open Zone playlists

   Choose New zone playlist and give the playlist a clear name.

2. Set the canvas

   Check Width and Height. Choose Full screen or divide the canvas into the desired zones.

3. Add a step

   Choose the media for each zone in that step and set its duration.

4. Check all steps

   Review the preview, content, duration and fit or crop settings in each zone.

5. Save and prepare

   Wait for the save status. Then choose the screens, use Prepare screens and press Show now only when everything is correct.

Remember · A step describes what all zones show together. Editing a zone playlist that is already playing may affect the active display. Generated playlist layouts should be edited in Zone playlists, not as ordinary layouts.

What this changes · Playlist edits autosave and can update an active list. The player mapping is not rewritten.

Result check · Each step has the correct media and duration, and the intended zones are filled.

Practice · Create a new practice playlist with two steps. Do not use it to replace an active show playlist.

Review questions

Open this as tutorial 26 →

Chapter 41

Drawing dividing and importing playlist zones

Build playlist regions without changing screen mapping.

Before you begin · Create a separate practice playlist. Zone playlists save automatically; editing a currently displayed list may affect live screens.

Playlist zones are a different object

A playlist zone belongs to the playlist. Each step chooses media for its zones and lasts for the step duration. These are not the Design, Output and Live zones in the layout editor, even when the rectangles look identical.

Use Full screen for a single region. Divide into creates equal regions along the chosen direction. Draw zones enables dragging on the playlist canvas and adjusting region geometry. Confirm the final pixel values in the available zone controls.

Import from a screen's pixelmap uses the server-provided zone geometry and canvas. It replaces the playlist's zone arrangement after confirmation. Check retained media assignments carefully: cells for removed zone identities can be dropped. The import does not write the player's pixelmap.

Source geometry is not HDMI placement

Pixelmap import uses the stored active slices' Source rectangles, translated around their combined source bounds. It is not a copy of their HDMI Output positions. Stored slice definitions may still be present when the master mapping switch is off, so review whether that imported source arrangement suits the intended playback.

Procedure

1. Start a new practice playlist

   Confirm its name and canvas dimensions.

2. Choose one construction method

   Use Full screen, Divide into, Draw zones or the pixelmap import.

3. Review all rectangles

   Check names, coordinates, dimensions and the chosen split direction.

4. Fill every step

   Assign media to the intended zone in each step and choose step durations.

5. Check automatic save status

   Wait for Saved and resolve any errors before leaving.

6. Prepare and show deliberately

   Choose explicit screens, prepare their files and show only after reviewing the complete sequence.

Remember · Changing an active playlist can be operationally significant even without another Show now click. Use a copy for rehearsal.

What this changes · The playlist arrangement and its saved steps change. The player's surfaces and slices do not change.

Result check · The playlist zones have the intended geometry and every step has correct content.

Practice · Create a new two-zone playlist and compare two steps. Then inspect import on a separate practice copy.

Review questions

Open this as tutorial 27 →

Chapter 42

Preparing different screen formats

Group landscape and portrait versions of the same campaign.

Before you begin · Use content-set editing and publication controls only where permitted, and obtain the expected screen formats first.

Procedure

1. Open Content sets

   Use the available content task in CMS navigation.

2. Check the screen profiles

   Identify the format required by each screen.

3. Create the content set

   Enter a name and use Add variant to add the correct files and dimensions.

4. Save the set

   Use Save content set.

5. Review the publication

   Under Review and publish, check which variant each screen will receive. Publish only when those matches are correct.

Remember · A content set contains format variants. A playlist contains successive steps. A landscape design does not automatically become readable on a narrow totem.

What this changes · A content set groups variants. Applying or publishing it chooses content for screens without defining their physical wiring.

Result check · Each selected screen receives the correct variant or a fallback you have deliberately reviewed.

Practice · Create a practice campaign with one landscape and one portrait variant, then review the result.

Review questions

Open this as tutorial 28 →

Chapter 43

Choosing the correct screen

Choose exactly where your content will appear.

Before you begin · You need access to view the intended screens. Knowing a screen name does not grant control permission.

Procedure

1. Open Action target

   Click the screen selector at the top of the page.

2. Choose a familiar screen name

   Select one screen or the intended screens. Use a named group only when you know which screens belong to it.

3. Review your selection

   Read every selected screen name before continuing.

4. Check the status

   Check whether the screens are online. When you send an action, also read which screens are skipped.

Remember · Selecting a screen does not show new content. Looking at a preview does not automatically change the action target.

What this changes · Screen selection sets an action destination; it does not itself issue a display command.

Result check · All intended screens are selected, with no unintended screens included.

Practice · Select one practice screen. Reopen the selector and check its name.

Review questions

Open this as tutorial 29 →

Chapter 44

Adding a photo or video

Add a usable file to the content library.

Before you begin · You need media-upload permission or an explicitly allowed LightShell upload feature. A normal Viewer cannot follow upload steps.

Procedure

1. Open Content library

   In older screens, this section is called Content.

2. Choose your file

   Use the upload option and select a photo or video from your computer. A clear filename makes it easier to find later.

3. Wait for the upload

   Stay on the page until the file and its status are visible.

4. Check the result

   Find the uploaded file. Review the image or video and check its size and orientation.

Remember · Uploading adds a file to the library. It does not automatically show the file on a screen.

What this changes · A library file is added. Display requires a separate show, publish or schedule action.

Result check · Your file is easy to recognise in the library and the upload has finished.

Practice · Upload a practice image with a clear name, then find it again.

Review questions

Open this as tutorial 30 →

Chapter 45

Importing from a cloud source or Canva

Bring a design or file into the CMS library.

Before you begin · The customer connection must be configured and your account must allow the chosen import source.

Procedure

1. Choose the import source

   Open Cloud sources or Import from Canva through the available content task.

2. Connect if needed

   Follow the sign-in steps. If One-time setup required appears, an administrator must configure the connection first.

3. Choose the correct design

   Check the page, dimensions and export option before importing.

4. Check the import

   Wait for the result and find the file in the library. Publishing it is a separate action.

Remember · A successful import does not automatically show content on a screen. Resume import can continue an interrupted Canva import.

What this changes · The import creates library content. Publishing remains a separate decision.

Result check · The correct imported file is available in the library.

Practice · Import one simple image from a source that is already configured, then check its dimensions.

Review questions

Open this as tutorial 31 →

Chapter 46

Publishing content now

Show a photo or video on the screens you have deliberately selected.

Before you begin · Use the publishing controls only if your account is permitted to show this content on these screens.

Procedure

1. Open Publish

   Choose an existing file or upload the content you want to show.

2. Choose the screens

   Select the exact destination and read the selected screen names.

3. Choose Now

   Check the content and the current timing option.

4. Publish once

   Press Publish. Read the response, then check the player status and the physical screen.

Remember · A CMS confirmation means the command has been processed. Also check whether the intended picture actually appears.

What this changes · Publish Now changes the selected display destination immediately through the supported playback route.

Result check · The correct content appears on the correct screens.

Practice · Publish a clearly recognisable image on an agreed practice screen.

Review questions

Open this as tutorial 32 →

Chapter 47

Scheduling content for later

Show content during a specific time window.

Before you begin · Scheduling requires the appropriate scheduling rights. A general Operator is not automatically an event planner.

Procedure

1. Choose content and screens

   Open Publish and select the file and intended destination.

2. Choose Later

   Enter Start and End. The end time must be after the start time.

3. Check the date and time zone

   Read the time zone displayed on the page. Pay extra attention to dates and daylight-saving changes.

4. Publish and review

   Press Publish, then check the scheduled block under Events.

Remember · Normal CMS content may return after the scheduled block ends. Make sure that content is suitable too.

What this changes · A future schedule is created. Review conflicts, time zone and what resumes after it.

Result check · The scheduled block has the correct content, screens, date and times.

Practice · Create a short future time block on a practice screen and review all its details.

Review questions

Open this as tutorial 33 →

Chapter 48

Using Control room and screen storage

See which content is already prepared for your selected screens.

Before you begin · Storage inspection and preparation or display actions can have different permissions. Follow only the controls offered to your account.

Procedure

1. Open Control room

   Choose Screen storage to inspect files stored on players.

2. Choose the screens

   Use the screen selector within this workspace. Change screens adjusts the destination.

3. Check each player's storage

   Check the selected SSD or SD storage and read ready, waiting, transferring or failed.

4. Choose the next task

   Use the available preparation action for missing files. Use Show existing content to show saved content, and Sync for a coordinated change.

Remember · Content library contains source files. Screen storage shows copies on selected players. Upload & show is an immediate display action.

What this changes · Reading storage changes nothing. Preparation creates usable copies; show and return actions affect the selected displays.

Result check · You know which screens actually have the required files ready.

Practice · Open storage for one practice screen and identify the selected storage and status.

Review questions

Open this as tutorial 34 →

Chapter 49

Creating an event and schedule

Organise an event and check its scheduled time blocks.

Before you begin · Event creation and schedule editing require the relevant permissions. Prepare a separate practice event for rehearsal.

Procedure

1. Create or choose the event

   Open Events. Use Create event if it does not exist yet.

2. Choose the time block

   Open a date or the scheduling form. Enter the title, start and end.

3. Choose content and destination

   Select the event, exact screens, content type and content.

4. Save the schedule

   Use Save schedule and review Upcoming schedules.

5. Check readiness

   Prepare event content in advance. Use the available offline showtest and review missing files for each player.

Remember · Creating an event does not display content. A successful file check also does not prove that a player will restart without a network after power loss.

What this changes · Events and schedules organise or trigger content. A file-readiness check is not a physical offline-start test.

Result check · The correct content is scheduled for the correct date and destination.

Practice · Create a practice event and check one future scheduled block.

Review questions

Open this as tutorial 35 →

Chapter 50

Starting together with Prepare and GO

Prepare a coordinated content change and start the screens that are ready.

Before you begin · Your account needs the Sync module and permitted screen control. Agree whether a partially ready set is acceptable for this show.

Procedure

1. Open Sync Show Control

   Select the explicit participants and check their names.

2. Choose the next content

   Check Next after GO for each screen. No change leaves that screen untouched.

3. Prepare the cue

   Choose the available transition and storage route. Press Prepare.

4. Read READY and exclusions

   Decide whether the ready subset is sufficient for the show.

5. Start with GO

   Use GO when the change should begin. Check the response and the physical screens.

Remember · After changing media, targets, transition or route, prepare again. An excluded screen retains its previous content and does not simply join the same transition later.

What this changes · Prepare establishes cue readiness; GO starts the ready participants. Excluded participants retain previous content.

Result check · The intended READY screens start the prepared cue, and any excluded screens are known.

Practice · On an agreed test setup, check Prepare and READY before testing a coordinated GO.

Review questions

Open this as tutorial 36 →

Chapter 51

Preparing a show with Show lists

Prepare the order of a show and control each cue deliberately.

Before you begin · Show-list access and the required module must be enabled. Review automatic timing before arming anything.

Procedure

1. Open Show lists

   Create a clearly named list or open the intended existing list.

2. Fill in the cues

   Choose supported images or videos and exact screens for each cue.

3. Save the list

   Check the order and any timing or follow rules.

4. Prepare the cue

   Use Prepare and read readiness and excluded screens for that cue.

5. Start or arm deliberately

   Use GO for a manual start. Arm enables the available automatic cues; check their conditions and validity.

Remember · Saving a list does not start it. Arm may allow automatic starts. Stop or disarm automation when the show ends.

What this changes · Saving stores a show list; arming permits automatic cues; starting can change displays.

Result check · Cue order, destinations and automatic starts have been checked.

Practice · Create a practice list with two manual cues. Review the order before starting anything.

Review questions

Open this as tutorial 37 →

Chapter 52

Preparing the scoreboard

Prepare the correct teams and a readable scoreboard.

Before you begin · Confirm scoreboard editing access and the complete affected screen scope before changing shared match details.

Procedure

1. Open Scoreboard and Setup

   Do this before the match.

2. Choose the number of matches

   Select one, two or four matches where available.

3. Enter teams and logos

   Check home and away teams, short names, competition and round.

4. Choose visible elements

   Set teams, score and clock. Check position, size and background.

5. Save and review

   Use Save matches & layout. Show and check it on the agreed screen.

Remember · Several screens may use the same scoreboard. Check the affected screens before changing shared match information.

What this changes · Shared scoreboard settings can affect multiple screens using the same match data.

Result check · Teams, logos and visible elements are correct and readable.

Practice · Check a practice match for swapped teams and text outside the visible area.

Review questions

Open this as tutorial 38 →

Chapter 53

Controlling score clock and animations

Control the correct match without recording a goal twice.

Before you begin · Choose a practice match for rehearsal and confirm the match and screen scope before a real score action.

Procedure

1. Choose Match to control

   Check which match you are operating.

2. Control the score and clock

   Use the intended goal or undo action. Start or pause the clock and check the period.

3. Choose a prepared animation

   Play animation shows the animation. Record event & play may also record the match event.

4. Avoid a duplicate goal

   After a combined goal-registration action, do not also use a separate goal action for the same goal.

5. Stop temporary displays

   Use Stop animation or Sponsors off when needed. Check that the normal scoreboard returns.

Remember · Playing an animation does not automatically increase the score. If feedback is unclear, check the score and event list first.

What this changes · Score and clock actions update match state. Animation and sponsor actions temporarily alter the visible display.

Result check · The visible score, clock and period match the real match.

Practice · On a practice match, compare playing an animation with recording a goal.

Review questions

Open this as tutorial 39 →

Chapter 54

Switching to live HDMI

Switch deliberately between CMS content and a connected live source.

Before you begin · A compatible physical HDMI input and connected source are required. Browser previews alone do not prove input lock.

Procedure

1. Check the source and player

   The player needs a suitable physical HDMI input. Have the source and cable connection checked.

2. Open Live switch

   Choose the correct screens and check input status.

3. Check picture and audio

   Review the available picture-fit and audio options.

4. Switch to live HDMI

   Use the available live action when the live picture should appear.

5. Return to CMS

   Use the return action and check the normal picture.

Remember · A software preview does not prove that the physical HDMI signal is locked. Check the real screen and input status.

What this changes · Live switching changes the selected player's source mode. It does not give unsupported hardware an HDMI input.

Result check · The correct live picture appears and returning to CMS works.

Practice · Practise switching to live and back on an agreed test setup.

Review questions

Open this as tutorial 40 →

Chapter 55

Preparing a Stream Deck button

Connect a clearly labelled button to one intended action.

Before you begin · Button configuration requires the corresponding permissions. Never expose private trigger links in public instructions.

Procedure

1. Open Stream Deck

   Review the existing buttons first.

2. Give the button a clear name

   Use a label that identifies its action, such as Welcome foyer.

3. Choose action and destination

   Check the content and exact screens the button may control.

4. Save the mapping

   Follow the displayed setup for your Stream Deck or Companion installation.

5. Test the intended action

   Use an agreed practice screen and check the result and return behaviour.

Remember · A trigger link is a control key. Keep it private and do not include it in general training material.

What this changes · A stored button defines a trigger action. Executing it can change its permitted screens.

Result check · The button performs exactly the intended action on the intended screens.

Practice · Review an existing button's label, action and destination without triggering it.

Review questions

Open this as tutorial 41 →

Chapter 56

Checking screen status and faults

Read the latest player feedback and choose a suitable next step.

Before you begin · Use Monitor only if your account exposes it. Otherwise report the status available through Overview or your assigned desk.

Procedure

1. Open Monitor player settings

   Choose the player by name and check its identity.

2. Read the last contact time

   Old feedback is not a new observation. Consider online, offline and warnings together.

3. Check the signal chain

   Read the available HDMI and player status. Compare it with the physical display.

4. Review recent actions

   Use Activity to see which commands were issued around the time of the problem.

5. Record precise details

   Record the time, screen name, action and error message. Ask a technician for targeted help if the cause remains unclear.

Remember · Hardware contact, player rendering and the visible LED picture are different signals. A restart may interrupt the picture; do not use it without considering the effect.

What this changes · Status inspection does not fix or restart hardware. Separate maintenance controls can interrupt playback.

Result check · You can identify the screen, the reported problem and when it started.

Practice · Find a player's last contact time and describe exactly what it does and does not confirm.

Review questions

Open this as tutorial 42 →

Chapter 57

Managing storage and restoring files

Understand where media are stored and clean up deliberately.

Before you begin · Storage administration can affect required copies and recovery. Check show dependencies and offline needs before cleanup.

Procedure

1. Open Storage management

   Review server, object-storage, eventserver and player copies where available.

2. Check which copies are needed

   Identify the files required for a show or offline playback.

3. Check before migrating

   Start with the available check action and read the result before starting a migration.

4. Restore where possible

   Find a deleted file in Recycle bin and use Restore while recovery is still available.

5. Check after the action

   Find the file again and check the library and affected content.

Remember · A server copy and a player copy are separate files. Permanent deletion or expired retention may make recovery impossible.

What this changes · Migration, removal or recovery changes stored copies. Confirm dependencies before acting.

Result check · You know which copies are needed, and a restored file is usable again.

Practice · Review the storage overview and identify which storage belongs to the player and which to the server.

Review questions

Open this as tutorial 43 →

Chapter 58

Viewing a playback report

Find the correct report and understand its figures.

Before you begin · Your role must allow reports. Choose the exact date range and grouping before interpreting figures.

Procedure

1. Open Reports

   Choose Group by Content item or Sponsor.

2. Choose the period

   Use Last 7 days or Custom dates, for example. Read the displayed date range.

3. Read duration and counts

   Check which content has been reported and how much playback time was received.

4. Review agreements if used

   Under Agreed vs delivered, compare the correct media, screens and agreed targets.

5. Export if needed

   Use Export CSV for the selected report range.

Remember · Reports use player feedback. Screen-seconds add time across screens; they are not unique visitors or guaranteed viewing time.

What this changes · Reports read received playback data; they do not count physical viewers or modify displayed content.

Result check · The report has the correct period and grouping, and you can explain the figures accurately.

Practice · Compare one file across two different reporting periods.

Review questions

Open this as tutorial 44 →

Chapter 59

Creating a Vision welcome scene

Prepare an appropriate welcome scene for the Vision connection.

Before you begin · Vision reception must be configured and allowed for this customer. Visitor and camera operations belong in the separate Vision setup.

Procedure

1. Open Vision reception

   Check the event and intended customer workspace.

2. Create the scene

   Choose an image, video or suitable welcome layout and give the scene a clear name.

3. Choose destination and duration

   Select explicit screens and check duration and return options.

4. Save and prepare

   Use the available Prepare action and check readiness.

5. Link through Vision

   Have the scene linked to the correct visitor in the separate Vision setup.

Remember · The CMS manages the screen scene. Visitor registration and camera management belong in Vision. Use a generic standby image as fallback, without previous visitors' personal details.

What this changes · Scene preparation and a deliberate show or visitor trigger have different effects. Verify duration and return content.

Result check · The intended scene is ready and the return display has been checked.

Practice · Create a generic practice welcome scene without personal information.

Review questions

Open this as tutorial 45 →

Chapter 60

Giving the AI assistant a clear command

Use exact names and check the execution result.

Before you begin · The AI module and customer service configuration must be enabled. Know whether fast execution can immediately show content.

Procedure

1. Check AI availability

   Open AI assistant. If the module is disabled, an administrator must configure it first.

2. Name content and screen precisely

   For example, use Show Welcome on Foyer left, using the actual names in your CMS.

3. Check the recognised choices

   Answer a clarification question if several names match.

4. Read the execution feedback

   Check which command was accepted and what player feedback is available.

5. Check the screen

   Confirm that the intended content appears on the intended destination.

Remember · Fast operator mode may immediately execute a clear, permitted show command. During a show, do not send exploratory display commands that must not run.

What this changes · A permitted AI command may issue a real display action. Accepted feedback is separate from rendering evidence.

Result check · The assistant uses the intended content and screen, and you have checked the result.

Practice · Start with a normal CMS help question. Practise show commands only on an agreed practice screen.

Review questions

Open this as tutorial 46 →

Chapter 61

Managing users and access

Give a user the appropriate role and access.

Before you begin · This is a customer-administrator workflow. Use the actual role and explicit desk assignment needed for each person.

Procedure

1. Open Settings and Users and roles

   Check the customer workspace.

2. Enter the user details

   Use a clear username and display name.

3. Choose the appropriate role

   A Viewer looks; an Operator controls permitted content. Grant administrator access only for administration tasks.

4. Set LightShell only deliberately

   For a restricted desk user, choose the appropriate role and explicitly assign the user in Manage LightShells afterwards.

5. Save and share privately

   Deliver the one-time login details through the agreed private channel. Have the user follow their own MFA setup where available.

Remember · A LightShell-only account without an assigned desk cannot control anything. Do not put passwords or MFA registration codes in screenshots.

What this changes · Account creation or role changes alter access, not physical screen geometry.

Result check · The user can open exactly the intended workspace and tasks.

Practice · Compare the intended tasks with the selected role and desk assignment together with your administrator.

Review questions

Open this as tutorial 47 →

Chapter 62

Creating a LightShell desk for your team

Give a team exactly the screens, content and features it needs.

Before you begin · A customer administrator configures desk scope. Test the intended end-user role after saving.

Test what the end user actually gets

Review the account role, enabled customer modules, desk screen scope, content dependencies and feature switches together. An administrator preview is not a substitute for checking the intended user role. Give content creators layout tools only where needed; give installers mapping tools only where approved.

Procedure

1. Open Manage LightShells

   Check Customer and use New LightShell or Configure.

2. Set the name and screens

   Keep Enabled on for a usable desk. Choose the intended screen selection.

3. Choose the content library

   Use all eligible customer content or a deliberate selection. Include media required by layouts and playlists.

4. Choose features and users

   Start with a suitable task preset and review every checkbox. Select the intended accounts.

5. Save and check access

   Use Save LightShell and View this desk. Also check the intended user role before sharing the link.

Remember · A task preset suggests features; it does not replace your screen, content or account selections. LightShell-only accounts need explicit desk assignment.

What this changes · Desk changes alter access to tools, media and screens. Disabling a desk does not itself stop an existing picture.

Result check · The team sees the intended screens and content and receives only the actions it needs.

Practice · Review an existing desk's screens, content, features and users.

Review questions

Open this as tutorial 48 →

Chapter 63

Showing content in LightShell

Show existing content through the simple desk controls.

Before you begin · Use your assigned desk and an account with permitted show actions. A Viewer remains read-only.

Procedure

1. Open the desk link

   Sign in and check the customer name and Control desk.

2. Choose Action target

   Select the intended permitted screens.

3. Select the content

   Search by name and click the correct tile. Review Selected and the destination in the bottom bar.

4. Prepare where available

   Use Prepare screens for the selected image or video and read the status.

5. Show the selection

   Use the Show button for your chosen screens. Check the response and the physical picture.

Remember · Selecting a tile alone does not show anything. Your role, desk, content selection and screen selection together determine what is possible.

What this changes · Showing changes permitted selected displays. Merely selecting a tile or preview does not.

Result check · The selected content appears on the intended desk screens.

Practice · Select one image in a practice desk and read the content and screen selection in the bottom bar.

Review questions

Open this as tutorial 49 →

Chapter 64

Uploading and adding movement in LightShell

Add a file and choose suitable movement for an image.

Before you begin · Upload and image movement must be enabled for your desk and account. Use approved media and a practice target for rehearsal.

Procedure

1. Check the upload feature

   If the desk allows uploads, Add images or videos is available.

2. Choose and upload the file

   Use Choose images or videos and Upload selected files. Wait for the upload status.

3. Select an image

   Find the correct tile in the library.

4. Choose movement

   Use Still, Cinema zoom, Horizontal drift or Vertical drift. Check that edges and text remain readable.

5. Check and show

   Review the content and destination in the bottom bar, then use Show.

Remember · Image movement presets apply to images. Videos and layouts use their own animations. Uploading alone does not display anything.

What this changes · Upload adds media; choosing movement sets the intended image presentation. Show applies the selected content to screens.

Result check · The correct image is in the library and the selected movement suits the content.

Practice · Compare Still and Cinema zoom on a practice image without important text near the edge.

Review questions

Open this as tutorial 50 →

Chapter 65

Using extra LightShell tools and returning to schedule

Use the tools your administrator has made available for your desk.

Before you begin · Tools depend on customer modules, account permissions, desk features, eligible content and allowed screens.

Procedure

1. Review Control desk tools

   Only features enabled by your administrator are shown.

2. Choose an existing task

   Start an allowed playlist or open the appropriate scoreboard controls.

3. Check the destination again

   Available Stream Deck or HDMI tools remain restricted to permitted screens.

4. Use Return or Black deliberately

   Return to schedule restores normal CMS mode. Black requests a black picture if the action is allowed.

5. Check the result

   Read the response, especially skipped screens, and check the physical display.

Remember · Calibration and test patterns require separate desk permissions. Showing a test pattern is a real screen change; a preview is a simulation.

What this changes · Available tools may issue real actions, including black, return and test-pattern changes. Check their target and scope.

Result check · You know which tools are available and how to end a temporary display action.

Practice · Identify the permitted tools and find the return action without trying it during a live show.

Review questions

Open this as tutorial 51 →

Chapter 66

Using the LightShell scoreboard on a phone

Open mobile match controls within the correct desk.

Before you begin · Showing the scoreboard and changing shared match data may require different screen scopes. Follow the permissions shown.

Procedure

1. Open the scoreboard tool

   Choose Match setup & live controls in LightShell.

2. Check desk and screen

   The link belongs to the selected desk. Check Show on screen.

3. Use Setup before the match

   Enter teams and layout and use Save matches & layout where your permissions allow it.

4. Control the correct match

   Choose Match to control and use the appropriate score and clock actions.

5. Check every important action

   Avoid duplicate registration when using a combined goal animation. Stop temporary animations when needed.

Remember · Shared scoreboard changes may require broader screen permissions than merely showing the scoreboard. Missing editing controls may therefore be caused by desk access.

What this changes · Mobile controls can alter shared match state and permitted displays. They are not an independent local score copy.

Result check · You are operating the correct match from the intended desk.

Practice · Open the mobile page and find Setup, Live controls and Animations without changing the score.

Review questions

Open this as tutorial 52 →

Chapter 67

Opening CMS controls on your phone

Open the correct web controls and optionally install them as an app.

Before you begin · Use your own CMS account. Installing a browser app does not provide additional rights or automatic offline operation.

Procedure

1. Open Apps and LightShell

   Choose the appropriate controls, such as LightShell or Monitor.

2. Sign in

   Use your own customer account.

3. Install if desired

   On Android, use Install app. On iPhone, use the Share button and Add to Home Screen.

4. Check customer and desk

   Open the app and check that you are in the intended workspace.

5. Use the agreed local route during an outage

   A local eventserver has its own address. Have the administrator prepare and test that route beforehand.

Remember · An installed app icon does not automatically make control available offline. The app uses the same account permissions as the web page.

What this changes · A browser installation adds a shortcut or web app. Account scope and network requirements remain.

Result check · You can open the correct controls on your device and see the intended customer or desk.

Practice · Add the appropriate control page to your home screen and open it again.

Review questions

Open this as tutorial 53 →

Chapter 68

Troubleshooting a missing or incorrect picture

Check methodically where a display action or mapping may have gone wrong.

Before you begin · Start with the information you may view. Leave mapping, hardware and account changes to the responsible authorised person.

Procedure

1. Check your selection

   Read the customer name, content name and screen destination again.

2. Read the response

   Check online status, last contact time, errors and excluded screens.

3. Check the content route

   Are the required files ready on the chosen storage? Is the player in the intended CMS or live mode?

4. Check incorrect cropping

   Review the master switch, active slices, Source and Output. Compare them with the verified installation plan.

5. Report precise details

   Record the screen name, time, action and error message. Include a screenshot and, where needed, a photo of the physical wall.

Remember · Do not repeat an unclear show command endlessly. If software feedback looks correct but the physical picture remains wrong, have HDMI, the processor and cabling checked.

What this changes · Inspection narrows the cause. Do not apply a random player-wide configuration change to solve an unknown layout issue.

Result check · You can describe the problem precisely and identify which check is still needed.

Practice · Describe a fictional fault using the screen name, time, action and visible result.

Review questions

Open this as tutorial 54 →