Pixel Power Gallium Parameter Controllable Device

Pixel Power Gallium Parameter Controllable Device

Minimum hi Version: v2.6.0

Overview

hi uses the Pixel Power Gallium^™ HTTP API to read and control supported core and playout parameters.

Network Requirements

• Connection Model: hi initiates HTTP requests to the Gallium API.

• Multicast / Unicast: Unicast only.

• VLAN / IGMP: No multicast configuration is required.

• Bandwidth: Control traffic only.

• IP Version: IPv4.

• Firewall: Allow outbound HTTP from hi to the Gallium REST Port. The Gallium REST web services use Port 9200 by default, and hi uses the same default.

Standards Conformance

Operator Workflow

• UI Surface in hi: Control Panel, Rule Engine, Parameter Control, and Inventory

• Resources Controlled: Core and playout parameters exposed by the Gallium API

• Parameter Semantics: Gallium > Core > System status contains IsMaster and IsFollower. Gallium > Playout > Channels contains Channel Names, and Channel contains Take Next, Take Next Break, and Take Next Program.

• Device Administration: Use Gallium tooling for graphics authoring, playlists, assets, and platform administration.

Connection Details

Required Configuration

Device-Side Setup

Follow Pixel Power Gallium Parameter Controllable Device Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Known Limitations

• Available controls depend on the Gallium services exposed by the connected system.

• If Parameters do not appear, confirm that the Gallium API is enabled and exposes the required core or playout service.

• hi connects to the Gallium API over plain HTTP and sends no credentials. Gallium offers optional Basic authentication and HTTPS for each REST service. hi cannot connect to a service that uses either option, so keep the Core and Playout services without authentication and HTTPS, and keep them on a trusted management network.

• Setting IsMaster or IsFollower changes only the Gallium that the Node connects to. Gallium does not change the other system of an A/B redundant pair. Add a Node for each Gallium and change both in an order that never leaves two masters at the same time.

• A Take command returns success when the request succeeds. Gallium continues through the channel list when one channel fails, so success does not confirm that every listed channel took the event.

• To send a Take command, set its Parameter to one or more Gallium channel short names separated by commas, for example CH1,CH3. The Parameter stays empty after hi sends the command. Gallium skips a listed channel that does not exist or fails, and sends one command to a channel that is listed twice.

• hi polls master/follower state and the channel list every 2.5 seconds with a 3-second request timeout. A failed poll marks the Node as disconnected. hi reports the Node as connected when the Gallium Core service answers an initial HTTP request. The first poll starts 5 seconds after hi creates the client.

What's Not Supported

• Playout commands other than Take Next, Take Next Break, and Take Next Program, and other Gallium services. hi does not use the Gallium Release, Hold, Pause, Join In Progress, Skip Next, backup channel assignment, Interactive Preview, or live schedule queries, such as channel timecode and break status.

• Timed Take commands. Gallium accepts an optional timecode that schedules a Take command. hi always sends the command for immediate execution.

• Can Take Next, Can Take Next Break, and Can Take Next Program checks before a Take command.

• Gallium component status, settings export and import, and the Asset, Data, Render, Report, Schedule, and Schedule Emitter web services.

• Template and scene design, asset upload, and font or license management.

• Firmware updates and device configuration backup.

Trademarks