Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| blocks:player-setup:aes67 [2026-10-15 09:50] – [System Requirements] mattias | blocks:player-setup:aes67 [2026-10-16 11:16] (current) – [System Requirements] mattias | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====PIXILAB Player AES67===== | + | =====PIXILAB Player AES67 Audio over IP ===== |
| This article describes how to set up AES67 Audio over IP in PIXILAB Player. | This article describes how to set up AES67 Audio over IP in PIXILAB Player. | ||
| - | ====System Requirements==== | + | ==== System Requirements ==== |
| - | AES67 is available in PIXILAB Player | + | AES67 is available in PIXILAB Player from version 8.0. |
| - | We recommend using players with Intel processors, this is because the implementations CPU task priority works (better) on Intel. | + | |
| - | For networks A/V hardware is recommended. | + | |
| - | We do not provide any support or documentation on how to configure networks optimised for AIOP as this is not product specific to Blocks. | + | |
| - | PIXILAB | + | **Player |
| - | PIXILAB Player can transmit 2-8 channels of 24 bit audio at 48 kHz with a packet | + | We recommend players with Intel processors, as these handle the real-time CPU task scheduling that AES67 depends on more reliably. |
| + | **Network** | ||
| + | * All network switches and cables must support gigabit speeds. | ||
| + | * PIXILAB Player AES67 is multicast only, so switches must support IGMP snooping, and an IGMP querier must be present on the network. | ||
| + | * We recommend network hardware designed for A/V use. For example, Netgear' | ||
| + | * PIXILAB does not provide support or documentation for configuring networks for AES67/AoIP, as this is not specific to Blocks. | ||
| + | **Audio format**\\ | ||
| + | PIXILAB Player transmits 2-8 channels of 24-bit audio at 48 kHz with a packet time of 1 ms. This format is fixed, so receivers must support it. | ||
| + | **Compatibility**\\ | ||
| + | PIXILAB Player AES67 has been tested with AES67-compatible Dante devices such as Audinate Dante AUIO receivers and Genelec speakers. Any device with modern Audinate chipset should be able to receive AES67. | ||
| + | |||
| + | **Clock synchronization**\\ | ||
| + | PIXILAB Player uses PTP (IEEE 1588) for clock synchronization. PTP is implemented in software, hence the player does not rely on hardware timestamping in the network adapter. In a AoIP network, the leader clock is normally selected automatically by the devices. All other devices synchronize their clocks to the elected leader. The current leader and synchronization status can be inspected in Dante Controller. | ||
| ====Getting Started==== | ====Getting Started==== | ||
| To enable AES67 in PIXILAB Player, the aes67_dest= configuration option must be set in the player configuration file. The aes67_dest= option must be set to a valid multicast address (e.g., 239.69.0.121) that is not in use by any other AES67 transmitter. The player configuration file can be edited from within the Display Spot settings as seen in the screenshot below: | To enable AES67 in PIXILAB Player, the aes67_dest= configuration option must be set in the player configuration file. The aes67_dest= option must be set to a valid multicast address (e.g., 239.69.0.121) that is not in use by any other AES67 transmitter. The player configuration file can be edited from within the Display Spot settings as seen in the screenshot below: | ||
| Line 23: | Line 32: | ||
| {{: | {{: | ||
| - | **IMPORTANT: | + | |
| After selecting the “AES67 Audio over IP” audio output, the AES67 stream from the player will appear in Dante Controller as shown below. | After selecting the “AES67 Audio over IP” audio output, the AES67 stream from the player will appear in Dante Controller as shown below. | ||
| {{: | {{: | ||
| + | **IMPORTANT: | ||