Meyer Sound Documentation

An Apple iPad with iPadOS 14 or later.

Multiple iPads running Spacemap Go can be used with a system to:

iOS 15 Privacy Settings to Allow Discovery of GALAXY Processors

iOS 15 Privacy Settings to Allow Discovery of GALAXY Processors

The Spacemap Go iPad app is available from the Apple App Store at no cost. Visit the App Store from the iPad to install.

Galileo GALAXY processors are used in a Spacemap System. Each system supports up to 32 inputs and 256 outputs, depending on the number of processors and audio input format(s). Any of the GALAXY models can be used, except the GALAXY Bluehorn 816. Firmware that includes the Spacemap Mode boot option is required.

Galileo GALAXY Processor Models – Maximum Number of Inputs and Outputs by Model

Spacemap Go system inputs

The maximum number of Spacemap System inputs is 32, whether one or sixteen processors are used. The system inputs can be analog, AES3, or Milan AVB—usually transmitted by a mixing console, playback device, or an AVB source. See the Spacemap System Audio Signals section on the Operations page for further explanation.

Maximum number of inputs by processor model:

• GALAXY 408: 32 channels total, 4 channels can be AES3 or analog XLR inputs, reducing the maximum of 32 Milan AVB inputs

• GALAXY 816: 32 channels total, 8 channels can be AES3 or analog XLR inputs, reducing the maximum of 32 Milan AVB inputs

• GALAXY 816AES (legacy): 32 channels total, 8 channels can be AES3 or analog XLR inputs, reducing the maximum of 32 Milan AVB inputs

All GALAXY processor models support up to 32 Milan AVB inputs, with input processing available for inputs A-H (8 channels). Milan AVB inputs 9-32 are routed directly to the matrix inputs.

The GALAXY processors comply, and are certified by the Avnu Alliance as Milan compliant:

“Every device will connect with any other device using a variety of agreed-upon formats and market-required definitions in the protocol. Milan adds essential agreements about the implementation of AVB technology, including requirements for compatible and compliant media formats, media-clocking, redundancy, and controller software, while ensuring those requirements are implemented correctly through compliance testing and certification of end devices.”  -Avnu Alliance

The stream format GALAXY processors use is: AAF-PCM 24-bit in 32 integer, 8-channels of 12 samples at 96kHz or 48kHz.

AVB inputs from devices that are not Milan certified, may establish stream connections and transport audio successfully. However, these connections may not:

• Successfully re-establish after power cycling equipment (persistent connection)

• May not support the Milan network redundancy schemes

• May not maintain clocking between devices

For these reasons, we do not recommend using AVB input sources that are not Milan certified for show critical applications. Certification guarantees functionality, because all certified devices are rigorously tested for inter-connectivity and reliability. We cannot ensure the functionality of non-certified devices and we encourage users to contact the device manufacturer to inquire about their certification status, and how to make AVB connections to GALAXY processors.

Spacemap Go system outputs

The maximum total number of Spacemap System outputs is 256. The outputs are usually connected directly to self-powered loudspeakers, which typically have analog inputs. See the Spacemap System Audio Signals section on the Operations page for further explanation.

Milan AVB outputs are in parallel with the analog or AES3 outputs.

Maximum number of outputs by processor model:

• GALAXY 408: 8 analog XLR outputs, 16 Milan AVB outputs

• GALAXY 816: 16 analog XLR outputs, 16 Milan AVB outputs

• GALAXY 816AES (legacy): 16 AES3 channels / 8 XLR connectors , 8 analog XLR outputs (in parallel with output channels 9-16), 16 Milan AVB outputs

The current version of Compass software is needed. The GALAXY firmware included with this and future releases supports GALAXY Spacemap Mode. Compass also supports virtual GALAXY processors booted to Spacemap Mode, enabling off-line configuration and programing.

A network connection between the iPad(s) and the GALAXY processor(s) is needed for control. The connection can be wireless or wired. For control-only networks, Avnu Alliance certified network switches are not required. Currently, IPv6 is used for network connectivity between the Spacemap Go app on an iPad and GALAXY processors. Please ensure the wireless access point and the network switch are IPv6 enabled. The connection between a computer and a single Galileo GALAXY does not require a network switch.

If the system inputs are sent via Milan AVB, or if more than one GALAXY processor is used in a system, an Avnu-certified AVB network switch connects the GALAXY processors and optional AVB sources. For the latest list of Avnu-certified hardware, including switches, visit the Avnu Alliance website. Note that network switches certified as AVB compliant meet the Avnu Milan specification. No network switches are certified as Milan AVB compliant.

Avnu-certified Milan AVB devices are fully supported. For a list of devices, see Avnu's Certified Product Registry list.

Non-certified devices may successfully connect. These devices may require additional configuration and may not be capable of establishing or re-establishing a persistent, error-free connection during normal operation and/or power cycling. Meyer Sound is working with other manufactures to make interoperability advancements.

Source audio signals are connected to the Galileo GALAXY processor XLR inputs or via the RJ-45 connectors for Milan AVB audio streams.

Galileo GALAXY audio inputs

The iPad app Spacemap Go includes a connection wizard that configures the inputs and outputs of the GALAXY processors. For systems that include multiple processors, the wizard also configures the Milan AVB transport used to share input signals across the system processors. The configuration wizard assumes the first input is connected to input A and that additional inputs are contiguous.

• Analog: make connections starting with Input A, then Input B, C, D, E, and FAES3: make connections starting with Input A, then Input C, E, and G

• AES3: make connections starting with Input A, then Input C, E, and G

Milan AVB: Any processor input can be selected to receive a Milan AVB stream. Matrix Inputs 9–32 of the GALAXY 816 models and Matrix Inputs 5–32 of the GALAXY 408 model are only used for Milan AVB inputs.

The AVB input stream format GALAXY processors accept is: AAF-PCM 24-bit in 32 integer, 8-channels of 12 samples at 96kHz or 48kHz.

AVB inputs from devices that are not Milan certified, may establish stream connections and transport audio successfully. However, these connections may not:

• Successfully re-establish connection after power cycling equipment (persistent connection)

• May not support the Milan network redundancy schemes

• May not maintain clocking between devices

For these reasons, we do not recommend using AVB input sources that are not Milan certified for show critical applications. Certification guarantees functionality, as all certified devices are rigorously tested for inter-connectivity and reliability. We cannot ensure the functionality of non-certified devices and encourage users to contact those device manufacturers, inquire about their certification status and how to make stable, persistent AVB connections to GALAXY processors.

See the Galileo GALAXY User Guide for further information about inputs and outputs.

Galileo GALAXY audio outputs to loudspeakers

Analog and AES3: The outputs of Galileo GALAXY processors are analog, except for the 816AES model (legacy), which has 16 AES3 output channels available on XLR connectors 1–8, with analog copies of Outputs 9–16 available on XLR connectors 9–16. The outputs are typically connected directly to self-powered loudspeakers.

GALAXY 816 Audio Connections

Milan AVB: All GALAXY models have 16 outputs that are available as Milan AVB outputs. The output stream format is Milan compliant, AAF, 8-channel streams. Both 96 kHz and 48 kHz sample rate streams are available, Stream Output 0, 1, 4, and 5 below.

GALAXY Milan AVB Output Streams

See the Galileo GALAXY User Guide for further information about inputs and outputs.

Both the iPad and Galileo GALAXY processors must be connected to the same Ethernet network for control during system operation. iPad connections can be wireless. During processor configuration, a computer running Compass software is also connected to this network.

Ethernet

IPv6 is used for network connectivity between the Spacemap Go app on an iPad and GALAXY processors. Please ensure the wireless access point and the network switch are IPv6 enabled. The connection between a computer and a single Galileo GALAXY does not require a network switch.

Each GALAXY processor has two RJ-45 Ethernet connectors used for network connectivity and support a variety of redundant network schemes. Download the Galileo GALAXY User Guide for details.

When facing the rear of a processor, make primary network connections using Ethernet Port 1 (left connector) for standardization. Use Ethernet Port 2 (right connector) for connection to a redundant network. The ports are identical in function, sending and receiving different types of data. Compass, Compass GO, Spacemap Go, and devices that send and receive OSC commands are used to make changes to the processor settings. These ports also send and receive Milan AVB audio streams.

The two ports have different network speed capabilities:

• Port 1 (left) is capable of both 1000bT and 100bT connections

• Port 2 (right) is 1000bT, or Gigabit Ethernet only

Devices capable of 100bT connections can only be connected to Port 1 for proper functionality. Many older or less functional network switches and access points (WiFi) are capable of only 100bT connections.

When using more than one GALAXY processor in a Spacemap Go system or when the system input source format is Milan AVB, an Avnu Alliance certified network switch is needed. Avnu-certified network switches are specialized switches, capable of supporting the underlying Milan AVB protocols and that have been certified for interoperability. Extreme network switch configuration instructions are available here. Generic network switches do not support Milan AVB audio streams but can be used for “control only” networks.

When GALAXY processors are booted into Spacemap Mode, the inputs of the processors are shared with the other processors over the Ethernet network using the Milan AVB protocol.

System example: 1

• Analog or AES3 audio inputs are connected to the GALAXY input XLR connectors.

• A wireless access point (WiFi) is connected to GALAXY Ethernet Port 1.

• An iPad running Spacemap Go is connected via wireless Ethernet (Wi-Fi) to the wireless access point.

• GALAXY processor analog XLR outputs are connected to loudspeakers (not shown below).

Note

An Avnu-certified network switch is not needed for this system because the network is not transporting any AVB streams. It is only used for control.

Example System – Analog/AES3 Inputs, Galileo GALAXY Processor, Wi-Fi Access Point, and an iPad (Loudspeakers Not Shown)

System example: 2

This example uses Milan AVB signal inputs and requires an Avnu Alliance certified AVB network switch. The source audio is sent via Milan AVB to the Galileo GALAXY.

System Example Two: Milan AVB Audio Input and Analog Output

System example: 3

This example uses two GALAXY processors. The Milan AVB digital audio protocol is used to share the analog/AES3 inputs with the second processor. An Avnu Alliance-certified network switch is needed. The GALAXY XLR outputs or the Milan AVB output streams can be used to connect to loudspeakers or other Milan AVB devices connected to the network switch.

Example 3: Two Processors Used, Requires Avnu Certified Switch

AVB Milan network redundancy

A secondary/redundant network can be connected in case the primary network experiences an issue, which ensures continuous Milan AVB transport and system control connection.

AVB clock considerations

The connections of the AVB media clock will be automatically set when the Spacemap Go system configuration is completed.

Compass software manages the AVB connections of GALAXY processors in Normal Mode. Spacemap Go manages AVB connections of processors in Spacemap Mode.

Each AVB device has an Entity Name, a human-readable identification of a specific AVB device. Use unique Entity Names for each GALAXY processor and all other AVB devices.

Each AVB device also has a Group Name, a human-readable label that is used to group devices for control.

The following procedure updates the GALAXY processor firmware and boots the processor(s) to Spacemap Mode.

Follow these steps to save existing input/output processing settings, upload firmware and reboot Galileo GALAXY processors to Spacemap Mode. The saved processor settings will be recalled during the procedure.

If Galileo GALAXY hardware is not available, Compass can create virtual processors. All the functions of Spacemap Go are available without passing audio signals. Using virtual processors facilitates learning, testing, and programming off-line.

This quick start example configuration uses the Spacemap Go app to define the inputs and outputs of a Spacemap Go system, including:

From the GALAXY Configuration procedure, if a processor is part of a system that is in use, the optimization settings were stored as a Global Snapshot in Compass. This is the appropriate time to recall that Global Snapshot and save the settings to a Spacemap Go System Snapshot.

If sound is not being reproduced by the loudspeakers, please check:

At this point, if there is no sound coming from your loudspeakers, please contact us! Not only would we like to help you get things working, but we may also discover ways to make improvements to the app.

Tap PROJECT TITLE to edit or enter a new name.

System Snapshots include the System Level, the GALAXY input and output processing, and the delay matrix control points. Tap to reveal controls to create new, delete, and update System Snapshots.

To store a new System Snapshot, tap  and enter a name. Tap CAPTURE to finish.Tap the More icon (three-dots) to reveal controls to update the current System Snapshot with the current changes and display the System Snapshot details and External Recall ID number.

Spacemap Go – Project Settings, System Snapshot

Tap OPEN PROJECT to open the desired file. Use the iPadOS browser to locate and open a Spacemap Go Project file.

Tap SAVE PROJECT to save or share a Project. Name the Project and select whether to save the file on the iPad, the GALAXY hardware, or both. One Spacemap Go Project can be saved to the hardware of the GALAXY processor(s).

This Project can be recalled when the system is powered on and LOAD PROJECT FROM GALAXY ON RESTART is selected (System Settings, System Configuration).

Spacemap Go – Save Project to iPad Files and GALAXY Hardware

The overlay offers different ways to share the file (via AirDrop, mail, messages, etc.). To save the Project file on the iPad, tap SAVE TO FILES and select a folder.

iPadOS – File Save Dialog

The app creates a Spacemap Go folder for convenience. To change the default file name, tap the Project name.

iPadOS – Save Project to On My iPad/Spacemap Go/SMG Projects

Tap to select a Spacemap Project from which to import the Setlist and System Snapshots. The imported Snapshots are added to the Snapshots already in the Project.

Tap IMPORT SPACEMAP or IMPORT TRAJECTORY, then select the Spacemap or Trajectory file(s) to import. The imported Spacemaps or Trajectories are added to the Spacemap or Trajectory Library.

Tap RECALL USER DEFAULTS to recall the User System Defaults Snapshot.

Use the Setlist View controls to recall or update the Default Mix Snapshots. Tap the SHOW button in the Setlist View to reveal the Mix Default Snapshots. Tap the More menu (three-dots) to update the User Mix Defaults Snapshot.

Tap INITIALIZE SPACEMAP SYSTEM to restore the original state of the app. The Mix and System Snapshots, Spacemaps and Trajectories will be deleted and replaced with the defaults.

Spacemap Go – Project Settings, Initialize Spacemap System

The Mix View displays eight input channels per layer, up to four layers, 32 channels, as well as an Overview of all channels. The eight active channels are highlighted, Channels 1-8 below.

Tap the SELECT SPACEMAPS button to choose a Spacemap for a channel.

Spacemap Go – Mix View

Tap the ADD SPACEMAP button and select a Spacemap from the Choose Spacemap popover. Select APPLY TO ALL CHANNELS to assign the selected Spacemap(s) to all channels.

Spacemap Go – Select Spacemaps Window and Spacemap Library

Two Spacemaps can be selected for each channel. Tap the orange  ADD SPACEMAP button to add a second Spacemap.

When two Spacemaps are added, use the percentage slider to change the percentage of the input signal sent to each Spacemap. The slider changes color depending on which Spacemap has the higher percentage, although both are routing audio unless the percentage is 0% for one of them. For example, using two Spacemaps, one Spacemap for lateral Speaker Nodes and another for overhead Speaker Nodes, fading between the two Spacemaps pans the input vertically. See details on the Spacemaps page.

The second option for routing an input to outputs is to enter cross-point Matrix levels. From the Mix View, tap the name of a channel or tap the Channel View button to open the Channel View. Use the arrows on either side of the channel name in the channel navigator to switch to the previous or next channel. Tap the channel name to open the channel selector pop-over and select another channel. Tap a matrix level to enter the output level for the channel. Swipe the Matrix row for additional outputs.

Spacemap Go – Channel Matrix Levels

Trajectories are automated motion paths for the Spacemap Panner. When a Spacemap is assigned, the CHOOSE TRAJECTORY button is added below the Spacemap. Tap it to display the Trajectory Library. Tap a Trajectory to add it to the Spacemap.

Spacemap Go – Trajectory Templates

From the Mix View, two controls are displayed below the Spacemap: one to play the Trajectory and another to reset the Trajectory. Tap the Trajectory Name next to these controls to open the Trajectory Library and select a different Trajectory or none.

Mix View – Trajectory Controls

To remove a Spacemap or trajectory from a channel, follow the same steps to add a Spacemap or trajectory and select NO SPACEMAP or NO TRAJECTORY from the library.

Mix or Channel View – Select No Spacemap or No Trajectory

Each channel has the following controls:

Mix View – Channel Signal Meter and Level Fader

	Link: Tap this button to link the Fader Level, Solo, Mute, and Spread controls of odd/even channel pairs. Select a link mode for the Spacemap Panner – see options below. Select a Trajectory for the odd numbered channel of a linked pair. The Panner of the even numbered channel will follow the Trajectory of the odd channel depending on the link mode selected.
	SPRD: Regardless the Spacemap Panner position, the spread function routes an input signal to all of the Speaker Nodes in a Spacemap. Tap the SPRD button to open the percentage slider. At 0%, no additional signal is sent to Speaker Nodes. As Spread is increased, the surrounding nodes without signal start receiving the input signal. When Spread is set to 100%, all the Speaker Nodes receive the input signal at 0 dB, no attenuation.
	MUTE: When MUTE is selected, audio is no longer routed to outputs from the channel.
	SOLO: When SOLO is selected, only audio from the selected Channel is routed to outputs, commonly referred to as Solo In Place.

Mix View – Linked Channels

Tap-hold the channel label to change the name. A popover window opens; edit the name, and tap DONE.

Mix View – Rename Channel Pop-Over

For each channel, tap an output to manually enter a summing matrix cross-point level, routing the input signal of the channel to the selected processor output at the level entered. Swipe left/right to display additional outputs. Levels entered are overwritten if a Spacemap is added to a channel and the Panner is moved.

Tap Output to Enter Summing Matrix Cross-point Level

Channels do not have Spacemaps selected initially. Each channel can use two Spacemaps. To select Spacemaps for a channel, tap  in Mix View or Channel View. Then, tap either of the Add Spacemap buttons (below, left) to open the Spacemap library, which includes factory examples and user created Spacemaps (below, right). Swipe up/down to scroll the Spacemap library.

Use the Create View to add user-created Spacemaps to the Snapshot Library.

Select Spacemaps Pop-Over – Tap Either ADD SPACEMAP Button (left), Spacemap Library, Select a Spacemap (right)

Choose Spacemap Pop-Over – Tap a Spacemap, SELECT ADDITIONAL CHANNELS or DONE to Add the Spacemap to the Channe

Tap a Spacemap to select it,  above, then tap SELECT ADDITIONAL CHANNELS  to add the Spacemap to multiple channels or tap DONE  to add the Spacemap to the channel.

Channel View, Two Spacemaps Assigned, No Trajectory

SPACEMAP NAME: Tap either to make a different selection, including none.

PERCENTAGE: When two Spacemaps are added, this slider adjusts the percentage of input signal routed to each Spacemap. The slider changes color and the Spacemap displayed changes depending on which Spacemap has the higher percentage, although both are receiving signal unless the percentage is zero for either one. There are advantages to using two Spacemaps; see details on the Spacemaps page.

POSITION MODE: Enables gesture control of the Spacemap Panner .

XY POSITION: Displays the X and Y coordinates of the Spacemap Panner. Tap values to enter coordinates

SPREAD: Controls how much of the input signal to routed to all of the speaker nodes in the Spacemap, regardless of the Spacemap Panner location. When set to 0%, no signal is “spread.” As the Spread percentage is increased, the level of the input signal routed to each Speaker Node is increased. When 100% is selected, the input signal is routed to all Speaker Nodes at 0 dB. This slider is logarithmic.

Use the Create View to add user-created Trajectories to the Trajectory Library.

A Trajectory is a defined movement path for the Spacemap Panner. When a trajectory is selected, a yellow line representing the movement path is overlaid on the Spacemap, and the Trajectory controls are displayed on the right side of the Channel View.

Channels do not have Trajectories selected initially. Each channel can be assigned one Trajectory. To select a Trajectory for a channel, tap in either Mix or Channel View to open the Trajectory library, which includes factory examples and user-created Trajectories. Swipe up/down to scroll the Trajectory Library.

Select Trajectory Pop-Over – Tap a Trajectory, SELECT ADDITIONAL CHANNELS, or DONE to Add the Trajectory to the Channel.

Tap a Trajectory to select it, then tap SELECT ADDITIONAL CHANNELS  to add the Trajectory to multiple channels, or tap DONE  to add the Trajectory to the channel.

Channel View – Trajectory Controls

PLAY: Starts the Spacemap Panner following the Trajectory.Restart: Stops the Trajectory, if playing, and resets the play head to the beginning of the Trajectory timeline.

TRAJECTORY: Tap to select another Trajectory or none.

RESET: Opens pop-over, select: Reset All, Rate, Scale, or Offset. CHOOSE ANOTHER: Tap to select another Trajectory or none.REMOVE: Removes the Trajectory from the channel.

REPETITIONS opens pop-over, enter number of times to repeat or infinity .

Tap the TRAJECTORY button to enable gestures to modify the Trajectory path overlaid on the Spacemap.

Use one-finger gestures to move the Trajectory, two-finger pinch/expand to scale, and two-finger twist to rotate.

Trajectory Movement

To switch between Rate and Tap Tempo controls, swipe left/right on the pane.

Channel View – Swipe Left/Right to Switch Between Rate and Tap Tempo Controls

RATE: Changes the speed the Trajectory is played. Tap-drag the encoder up/down to change the Rate.

REVERSE DIRECTION: Immediately reverses the direction the Panner travels along the Trajectory.

TEMPO & BPT: Change the Trajectory rate based on BPM or Beats/Trajectory. Tap to edit values.

TAP TEMPO: Tap repeatedly to set Tempo BPM manually – continue tapping until the Tempo BPM updates.

Channel View, Trajectory – Timeline and Rotation, Scale, and Offset Controls

TIMELINE: All changes are reflected on the Trajectory Timeline. The graphic consists of three horizontal axes; the middle represents the time of the trajectory. The other two depict the X and Y coordinates of the Panner.

ROTATION: To rotate the Trajectory, use the encoder, the plus/minus buttons, or tap a preset value.

SCALE: To change the Trajectory size, use the Scale X and Scale Y controls. Tap the Lock icon to link the Scale X and Y values absolutely.

NOTE: If the Spacemap area is exceeded by the Trajectory, it will change shape, respecting the boundary.

Channel View, Duplicate Controls Available in Mix View

CAPTURE SNAPSHOT: Creates a new Channel Snapshot, which includes: Channel Name, Link, Spread, Mute, Level, Matrix levels, Spacemap, Spacemap Pan, Trajectory and Spacemap modifiers.

RECALL SAFE: Prevents overwriting of the channel settings when either type of Snapshot is recalled. The Recall Safe state is not stored when Channel Snapshots, Mix Snapshots, or Projects are created or saved.

LINK, MUTE, SOLO: Are duplicate controls, also available in Mix View.

LEVEL and INPUT METER: Are duplicate controls, also available in Mix View.

A Mix Snapshot stores the parameters for all Channels plus the Mix Level and Mute.

A Channel Snapshot stores the parameters of an individual Channel.

Saving Hierarchy – Channel and Mix Snapshots

The Setlist View displays the Mix and Channel Snapshots in two panels. If the Mix Snapshot panel is hidden, tap button  below to reveal.

Setlist View – Mix and Channel Snapshot Panels

Recall this Mix Snapshot with confirmation

Mix Snapshot name and comment

Most recent Mix Snapshot Recalled. Tap  to recall the Mix Snapshot again.

Default Mix Snapshots show/hide

Number of Channels with Recall Safe Enabled

Capture new Mix Snapshot

Opens popover to update or display Mix Snapshot details, view external recall ID#

Collapse/Expand Channel Snapshot panel

Channel Snapshot name, included Channels, and comment

Most recently recalled Channel Snapshot indicated by grey background. Tap again to recall.

Selected Channel Snapshot. Tap PLAY button or Recall Selected Snapshot button  to recall.

Recall selected Channel Snapshot

Tap EDIT to group/ungroup, move, or delete Channel Snapshot;  to create new Channel Snapshot.

Update Channel Snapshot, update group, ungroup, edit details, or view external recall ID#

To capture a new Mix Snapshot, tap the plus button , to open the popover. Enter a name for the snapshot and tap CAPTURE. The new snapshot will be added to the Mix Snapshots list.

Setlist View – Capture Mix Snapshot Popover

If changes are made to one or many channels, and the settings stored in a Mix Snapshot need to be updated, tap the three-dot icon  next to the Snapshot Name, then UPDATE MIX SNAPSHOT. Any Mix Snapshot can be updated with the current settings of all the channels.

The Mix Snapshot column also lists the Default Mix Snapshots , which are hidden by default. Tap the SHOW/HIDE button to toggle the User and Factory Defaults display. There are two types of Mix Defaults:

Setlist View – Default Mix Snapshots

The total number of channels that are set to Recall Safe is displayed . Tap EDIT to select channels to recall safe.

Tap the Play Button  to overwrite all the channels with the parameters stored in the Mix Snapshot. Tap RECALL to accept, CANCEL to decline. When a Mix Snapshot is recalled, the Play Button changes to a circle with an arrow at the end ; tap to recall the Mix Snapshot again.

Tap the three-dot icon to open the More pop-over  to view these options:

Tap UPDATE MIX SNAPSHOT to overwrite the settings currently stored in the snapshot.

To exclude a channel, tap NONE (below) and select channels from the list to exclude them when the Mix Snapshot is recalled.

Setlist View – Mix Snapshot Details

Tap INCLUDED CHANNEL SNAPSHOTS to preview the Channel Snapshots without recalling the Mix Snapshot.

Setlist View – List Channel Snapshots in Mix Snapshot

Setlist View: To store a Channel Snapshot, tap the ADD button . The Capture Channel Snapshot popover opens. Add a name and comment. Then tap CHANNEL to select the channels to include. Enter Wait and Transition Times if an immediate change is not desired. Tap CAPTURE to save a Channel Snapshot.

Channel View – Add Channel Snapshot

Channel View: Channel Snapshots are also saved/captured in Channel View. Tap the CAPTURE SNAPSHOT button (below). The Capture Channel Snapshot popover opens. Make the same entries and selections as above and select the Mix Snapshot with which to associate the Channel Snapshot.

Channel View – Capture Snapshot Button

Group, move, and delete Snapshots

Tap the EDIT button  and select Channel Snapshots to group/ungroup, move, or delete. Tap the desired action at the bottom of the pop-over. When GROUP is selected, a popover opens to name the Channel Snapshot Group. Groups are identified by a folder icon (FX 1 below) instead of displaying the channel number (Movement 1-3 below).

Setlist View – Group/Ungroup, Move, and Delete Channel Snapshots

To move/copy a Channel Snapshot to another Mix Snapshot, tap EDIT , select the channels to be moved, and tap MOVE. The popover that opens lists the possible destination Mix Snapshots.

Setlist View – Channel Snapshot Group Indicated by Folder Icon

Mix Snapshot Selection

Delete mix or channel Snapshots

To delete a Mix or Channel Snapshot, swipe left on the Snapshot.

Important

This action cannot be undone. Channel Snapshots included in the Mix Snapshot are also deleted.

To delete many Channel Snapshots at the same time, tap EDIT , select the Channel Snapshots, and tap DELETE.

To create a Spacemap, select SPACEMAP at the top of the view and tap CREATE NEW SPACEMAP (above) to open the Spacemap editor.

Tap the ADD button on the right (below). Select one of the four node types on the left, then tap inside the Spacemap to add nodes. Use two-finger pinch and open gestures to zoom the Spacemap.

Tap More (three-dot icon) next to the Spacemap name to edit the name, save a Spacemap file, and add tags.

Create View – Add Spacemap

Nodes types

For more information about nodes and their uses in a Spacemap, please see the Spacemaps page.

	Speaker Nodes Speaker Nodes represent the physical outputs of a Spacemap System as blue squares. Positions of Speaker Nodes in a Spacemap can represent the loudspeaker layout logically, randomly, or abstractly. Abstract layouts are usually used to facilitate specific panning scenarios that would be difficult or impossible to create with a logical speaker node layout.
	Virtual Nodes Virtual Nodes simulate a physical output for panning purposes and can be used in conjunction with Silent Nodes. Virtual Nodes are linked to Speaker Nodes and/or Silent Nodes. The links are indicated graphically by a translucent line, wider at the Virtual Node, narrower at the linked Speaker Node. When the Spacemap Panner is moved to a Virtual Node, the input signal is equally distributed to the linked Speaker Nodes by default. Each linked Speaker Node has a Link Weight that is adjustable (0–100%).
	Silent Nodes Silent Nodes are included in Trisets, just like Speaker Nodes, but they are not associated with an output. When the Spacemap Panner is moved closer to a Silent Node, all output levels of the channel are reduced. When the Spacemap Panner is on a Silent Node, all output levels of the channel are -∞ (-infinity) dB. Moving the Panner closer or further away from a Silent Node is an easy way to fade-in or fade-out a channel using the Spacemap Panner instead of the channel level control. In a Spacemap, when the Spacemap Panner is moved to a location that does not include a Triset, all of the output levels of the channel drop to -∞ dB. As the Panner is moved on and off of Trisets it will sound like the mute for the channel is being toggled. If this is not the desired effect, Silent Nodes can be added at the extents of a Spacemap with Trisets that include them. When Trisets fill the entirety of a Spacemap and the Spacemap Panner approaches the edge of the Spacemap, the output levels will not suddenly drop to -∞ dB. Instead, the output levels are gradually reduced as the Panner is moved closer to a Silent Node.
	Derived Nodes Derived Nodes link to one or more Speaker Nodes and receive the sum of the signals from the linked Speaker nodes. They are represented as hexagons in a Spacemap. Dashed lines indicate the Speaker Nodes to which they are linked. Derived Nodes are used as a method to send input signal to additional outputs, relative to the linked Speaker Nodes. They are commonly used for subwoofer sends, fill mixes, sends to balconies, and other cases where a secondary mix-down of a multichannel mix is required.
	Trisets At least one Triset is required in each Spacemap. Trisets are triangular panning surfaces created between three nodes that define the panning area between them. In conjunction with the relative location of the Spacemap Panner, Trisets are used by the app to determine the output levels for each node. The size of the Triset is not critical because the power-preserving panning law is proportional rather than absolute. The output levels are calculated based on the relative distance between the Spacemap Panner and each of the nodes that make up a Triset, rather than the actual physical distance within the grid of the Spacemap. If an area of a Spacemap does not have a Triset and the Spacemap Panner is moved there, the output levels will drop to -∞ dB (the input signal will not be sent to any output). Trisets can be generated automatically or added manually when creating or editing Spacemaps in Create View.

Toolbar

Tap the tools to the right of the canvas to add, select, or delete nodes in the Spacemap.

Toolbar	ADD: Tap in the Spacemap to add the selected node type.
	SELECT: Tap a Node or Triset to edit or move it.
	DELETE: Tap to delete the selected Nodes or Trisets.
	UNDO: Tap to undo the last change.
	REDO: Tap to redo the last undo.
	VIEW: Opens Spacemap view option popover for Spacemap (see below).
	CENTER: Zoom to extents.

View options

The View popover has several options that facilitate Spacemap creation:

• SHOW SPACEMAP: A Spacemap can be selected as reference for node locations.

• SHOW GRID: Toggles display of grid lines.

• SNAP TO GRID: When enabled, nodes are only added at grid intersections.

• BLOCK GRID SIZE: The grid size is adjusted in four increments.

• SHOW CIRCULAR GUIDE: Overlays a circle with a number of snap points equally spaced. Use sliders to adjust size and number of points (Spacemap only).

Create View, View Options – New Trajectory (left), New Spacemap (middle), New Spacemap with Show Circular Guide On (right)

Test Spacemap

Tap the TEST button next to the Spacemap name in the upper-left corner to open the Spacemap Test View.

Create View – Spacemap Test Button

Move the Spacemap Panner, observe the output levels and confirm desired behavior.

Create View – Spacemap Test Mode

To create a Trajectory, tap TRAJECTORY at the top of the Create View. Tap  CREATE NEW TRAJECTORY to open the Trajectory editing controls. Tap START RECORDING and draw inside the Spacemap to create a path. Tap FINISH RECORDING to end. Use two-finger pinch and open gestures to zoom the Spacemap.

A trajectory is a series of points that can be edited. Tap TIME and POINTS to edit values. Two times are listed for each point. The first is the wait time, the second is the time between consecutive points. The total time can be edited—modifying the individual wait and next-point times proportionally.

Tap the three-dot icon next to the name in the upper-left to edit the name, save as a Trajectory file, and add tags.

Create View, Trajectory Editor – Edit Wait Time for Point 4

Tap-hold and move a Trajectory Point to modify the trajectory shape. The POINTS option lists the X,Y coordinates (-1000 to 1000) for each point. Tap to edit values. Tap DONE to add the Trajectory to the library.

Create View – Edit Trajectory Points

System Settings includes controls and functions not related to mixing or appearance. Tap the buttons on the left to reveal the associated details and settings.

Galaxy processor status

Tap the name of a Spacemap System to display details about each connected GALAXY processor.

Three colors differentiate the state of each processor (below).

• GREEN: The processor is online and operating normally.

• YELLOW: Indicates the module is connected but is not part of a Spacemap System.

• RED: Indicates the processor is defined as part of a system but is not connected.

Settings View – System Status, Reported Processor States

Inputs

Outputs

External device connection

System configuration

System log

Speaker nodes represent the GALAXY processor outputs of a Spacemap System and are represented in the app as blue squares. Positions of Speaker Nodes in a Spacemap can represent the loudspeaker layout logically, randomly, or abstractly. Abstract layouts are usually used to facilitate specific panning scenarios that would be difficult or impossible to create with a logical speaker node layout. Each Speaker Node is associated with only one output. However, multiple Speaker Nodes can be associated with the same output. These outputs can be connected to loudspeakers, effects processors, or any other audio device.

Spacemap Go – Speaker Node Arrangement Examples

Assign each Speaker Node to an output. Tap the More icon next to a Speaker Node and tap SET OUTPUT to open the pop-over and select an output. Multiple Speaker Nodes can be assigned to the same output.

Spacemap Go – Create View: Speaker Node Parameters

Virtual Nodes simulate a physical output for panning purposes and can be used in conjunction with Silent Nodes. Virtual Nodes are linked to Speaker Nodes and/or Silent Nodes. The links are indicated graphically by a translucent line, wider at the Virtual Node, narrower at the linked Speaker or Silent Node. When the Spacemap Panner is moved to a Virtual Node, the input signal is equally distributed to the linked Speaker Nodes by default. Each linked Speaker Node has a Link Weight that is adjustable (0-100%), see below.

Spacemap Go – Create View, Four Speaker Nodes, One Virtual Node, Output 1 Link Weight

Virtual Nodes are commonly used to complete a Triset, while not being linked to an output. Below, the left Triset uses an un-linked Virtual Node. As the Spacemap Panner moves closer to the Virtual Node that is not linked, the level for Outputs 1 and 2 decreases to -∞ dB. The right Triset uses a linked Virtual Node. As the Spacemap Panner moves closer to this node, because it is linked to both Speaker Nodes, the level for Outputs 1 and 2 increases to a maximum of -3 dB.

Spacemap Go, Spacemap Test Mode – Upper Virtual Node Un-Assigned, Lower Virtual Node Assigned to Outputs

Virtual Nodes can be used in a Triset with one or two Silent Nodes. Adjust the Link Weights of the Virtual Node to alter the panning results.

Silent Nodes are included in Trisets, just like a Speaker Node, but they are not associated with an output. As the Spacemap Panner is moved closer to a Silent Node, all output levels are reduced. When the Spacemap Panner is on a Silent Node, all output levels are reduced to -∞ dB. This is an easy way to create fade-in and fade-out effects based on the Panner location rather than using the level fader of the channel.

When the Spacemap Panner is moved to an area of a Spacemap that does not have a Triset, the outputs will suddenly drop to -∞ dB. To avoid this, add Silent nodes at the extents of a Spacemap and build Trisets that include them. The Panner will no longer be able to “fall off” of a Triset because the entire Spacemap is “covered” by Trisets.

Derived Nodes link to one or more Speaker Nodes and receive the sum of the signals from the linked Speaker nodes. They are represented as hexagons in a Spacemap. Dashed lines indicate the Speaker Nodes they are linked to.

Derived Nodes send the input signal to additional outputs, relative to the linked Speaker Nodes. They are commonly used for subwoofer sends, fill mixes, sends to balconies, and other cases where a secondary mix-down is needed.

When a Derived Node is added, it is assigned to the next available output, which can be changed, see below. Each link level of the associated Speaker nodes can be adjusted, see below.

Spacemap Go – Create View: Derived Node Options and Speaker Node Link Level Adjustment

In the example below, the Derived Node output is connected to a subwoofer. The Derived Node is linked to the left and right Speaker Nodes, outputs 1 and 2. The subwoofer receives a constant signal as the Spacemap Panner is panned between the Speaker Nodes. When the Panner is centered between outputs 1 and 2, they each receive -3 dB level, while the Derived Node (output 5) receives 0 dB. When the Panner is moved to the right, the levels change for outputs 1 and 2, while the level of output 5 remains unchanged.

Test Spacemap – Spacemap Panner Moved from Center to Right, Derived Node Level Remains the Same

Three-dimensional movement of a sound source can be accomplished using one of these methods:

This design method utilizes wide (horizontal) coverage loudspeakers. The family of 110° wide loudspeakers is preferred (current products): LYON-W, LEOPARD, ULTRA‑X40, ULTRA‑X20/23, UP‑4slim, UP‑4XP, HMS‑12, Ashby‑5C/8C, MM‑4XP, MM‑4XPD. The family of 80° to 90° wide loudspeakers may require slightly higher density (current products): LYON‑M, UPQ‑D1/D3, UPJ‑1P, HMS‑5/10/15/15AC.

Before designing a Spacemap Go system, it is important to understand what the artistic and aesthetic goals of the system are, and what content is intended to be reproduced. If a system will be used to continuously pan a sound horizontally around a space, a Lateral, 360° Granular design is needed (example on the left, below). To smoothly pan above the audience’s heads, an Overhead, 360° Granular design is needed (center, below). To pan a sound from one corner to overhead to the opposite corner, an 360° Fully Granular design is needed (right, below).

For the examples below, the design goals are:

System Design Goals – Lateral Panning (left), Overhead Panning (center), Lateral to Overhead to Lateral Panning (right)

There are many room shapes. To describe the design steps, we will use a room that is square with a high ceiling (22 m x 22 m, 12 m high).

Perimeter: The distance between the wall and the mounting locations of the main and lateral loudspeaker (1 m).

Coverage Area: The area of the room within the Loudspeaker Perimeter (20 m x 20 m).

Example Room – Dimensions and Loudspeaker Perimeter (left), Coverage Area (right)

Go Distance: 1/4 the distance of the narrow side of the Coverage Area (20 m x 0.25 = 5 m).

Go Zone: Subtract 1x “Go Distance” (5 m) from all sides and elevate to ear height of the listeners (1.5 m). The narrow side of the Go Zone is 2x the Go Distance (10 m). In this square room, the Go Zone is 2x the Go Distance square (10m x 10 m).

Example Room – Dimensions and Loudspeaker Perimeter (left), Coverage Area (right)

To meet the design goals for this example, the Main loudspeakers should have a narrower vertical and wider horizontal coverage. Beyond directivity, bandwidth and SPL needs to reproduce the desired signals versus the loudspeaker capabilities should be considered.

Main System Horizontal Spacing:

Spread the loudspeakers to fill a length of 2x the Go Distance (10 m).

Example 1: Three Mains Scenario – Spread the mains horizontally to fill a length of 2x Go Distance (10 m), horizontal spacing of 5 m. The outer mains are in line with the edges of the Go Zone.

Example 2: Five Mains Scenario – Spread the mains horizontally to fill a length of 2x Go Distance (10 m), horizontal spacing of 2.5 m

Main System – Three and Five Loudspeakers

Example 3: If using higher SPL models as primary Left/Right anchors, with lower SPL models used in secondary positions: spread the loudspeakers horizontally to fill a length of 2x Go Distance (10 m). Use the outer positions or the second and forth positions for the Left/Right anchors.

Main System Height:

Maximum: One Go Distance above the Go Zone (5 m), less than 45° downtilt to closest edge of Go Zone.

Minimum: 1/2 Go Distance above the Go Zone (2.5 m).

Usually, maximum height yields the most uniform coverage.

Main System – Maximum and Minimum Height

Mains Coverage Verification

One way to simplify verification of loudspeaker coverage, is to adjust the SPL preferences in MAPP 3D:

• To make coverage easier to identify, change the preferences in FILE > PROJECT SETTINGS, SPL Tab to be ATTENUATION mode, Range = 12 dB, 6 dB/color.

• Set the Prediction Parameters to 1 Octave, 4kHz. This frequency range is representative of the high-frequency coverage of most loudspeaker models.

• The prediction data in red represents 0 dB to -6 dB of attenuation and we will call that “in coverage.” The Go Zone should be completely red or very close to it.

  Note

  All MAPP 3D predictions below use these settings unless otherwise stated.

  

  MAPP 3D Project Settings, SPL Tab, Attenuation Settings

Ideally, each loudspeaker provides the same coverage for each audience location. Because that is not realistic, we work towards that goal. Spill outside the Go Zone is great! But, if the walls above listener height are in coverage, consider a loudspeaker model with a narrower pattern. If a loudspeaker model provides less than 75% coverage in the Go Zone (relative, 0 dB to -6 dB), use a loudspeaker with different directivity or change the height and aim.

Example 1: The ULTRA‑X40 (110° vertical x 50° horizontal ) at the maximum height (6.5 m, 1.5 m listener height + 5 m Go Distance), provides uniform coverage from each main position for this space (below).

Main System Coverage Verification – Good Go Zone Coverage Achieved (ULTRA‑X40, 110° Horizontal)

Example 2: With the ULTRA‑X40’s in the same location and the horns rotated (50° horizontal x 110° vertical), the coverage is insufficient, below.

Main System – Insufficient Coverage, ULTRA‑X40 Horns Rotated to 50° Horizontal

Example 3: As the height of the center loudspeaker is changed, the coverage is affected. The downtilt is adjusted for each height, always at the opposite edge of the coverage area. The coverage area decreases as loudspeaker height is lowered from 1x Go Distance (5 m) to 1/2x Go Distance (2.5 m).

Main System – Maximum, Middle, and Minimum Height Effects Coverage

Like the mains, select models with wide horizontal coverage and more narrow vertical coverage.

Lateral System – Power Scaling

 The maximum SPL output of a loudspeaker in the Go Zone is dependent on your relative power needs. It is a decision based on creative needs – what sound needs to be reproduced at what maximum level? If the surrounds must reproduce signals at the same level as the mains – then they require an equal power scale. If the surrounds need to only supplement the mains, they can be 6 to 12 dB less in power scale or more, depending on the desired SPL.

Example 1: Leopard Mains – equal power = ULTRA‑X40 surrounds, reduced power = ULTRA‑X20

Example 2: ULTRA‑X40 mains – equal power = ULTRA‑X20 surrounds, reduced power = UPJ‑1P

Lateral System – Height (same as main system)

Maximum: One Go Distance (5 m) above Go Zone (1.5 m), less than 45° downtilt to closest edge of Go Zone.

Minimum: 1/2 Go Distance (2.5 m) above Go Zone (1.5m).

Lateral System, Sides – Horizontal Spacing

Locate first and last Side Surround 1/2 Go Distance beyond the Go Zone (5 m / 2 = 2.5 m).

Nominal spacing for the Side Surrounds is the Go-Distance (5 m). Fill between first and last Side Surround at evenly spaced intervals, not exceeding 1x Go Distance.

Lateral System, Side Locations – First and Last 1/2 Go Distance Outside Go Zone (left), Fill Between (right)

Lateral System – Aiming: (same as Main System)

Pan (horizontal) to middle of Go Zone

Tilt (vertical) to opposite Loudspeaker Perimeter.

Note

The center lines of the Meyer Sound HMS models from the CINE-STUDIO Series differ slightly from the center of the acoustic output: HMS‑15 and HMS‑10 aim 2°‑low, HMS‑5 aim 2°‑higher.

Lateral System, Sides – Pan to Center of Go Zone, Downtilt to Opposite Loudspeaker Perimeter

Lateral System, Rears – Pan to Center of Go Zone, Downtilt to Opposite Loudspeaker Perimeter

Lateral Coverage Verification

Use the same verification method for the side and rear laterals as was used for the mains: target the Go Zone and cover as much of the entire space as possible without covering the walls above listening height. If coverage is not sufficient, adjust the height and downtilt and/or try another loudspeaker model.

Example 1: The ULTRA‑X20 (110° vertical x 50° horizontal ) at the maximum height (6.5 m, 1.5 m listener height + 5 m Go Distance), provides uniform coverage of the Go Zone from each Lateral Side position for this space.

Lateral System, Sides – Coverage Verification, Good Go Zone Coverage Achieved (ULTRA‑X20, 110° Horizontal)

These positions will benefit from a model selection that has both a wide horizontal and vertical coverage pattern.

Overhead System – Power Scaling

The maximum SPL output of a loudspeaker in the Go Zone is dependent on your relative power needs. If the overheads must reproduce signal at the same level as the mains – then they must have equal power scale. If the overheads need only supplement the mains, then they can be 6 to 12 dB down in power scale.

Example 1: Leopard Mains – equal power = ULTRA‑X40 surrounds, reduced power = ULTRA‑X20

Example 2: ULTRA‑X40 mains – equal power = ULTRA‑X20 surrounds, reduced power = UPJ‑1P

Overhead System – Height

Maximum: 2x Go Distance (10 m) above the Go Zone (1.5 m)

Minimum: 1x Go Distance (5 m) above the Go Zone (1.5 m)

Tip

Maximum height usually provides more coverage area.

Overhead System – Horizontal Spacing

Locate loudspeakers above the corners of the Go Zone. On the long side of a rectangular room, if the distance between the Go Zone corners is between 1x and 2x Go Distances, consider adding a loudspeaker between the corners. If the distance is 2x Go Distances or more, add evenly spaced loudspeaker positions at 1x Go Distance spacing.

Overhead System – Locate above Go Zone Corners, Height Between 1x and 2x Go Distance

Overhead System – Aiming

Pan (horizontal) through middle of the Go Zone

Tilt (vertical) to 1/2 Go Distance past the center of the Go Zone.

Overhead System Aiming – Pan Through the Go Zone Center, Tilt to 1/2 Go Zone Corners

Overhead Coverage Verification

Again, target the Go Zone and cover as much of the entire space as possible without covering the walls above listening height. Adjust the height or select another loudspeaker model if coverage is not sufficient.

Example 1: The ULTRA‑X23 (110° vertical x 110° horizontal) at the maximum height of 2x Go Distance (11.5 m, 1.5 m listener height + 2x Go Distance, 10 m), provides uniform coverage of the Go Zone from each Overhead position for this space.

Overhead System – Coverage Verification, Good Go Zone Coverage Achieved (ULTRA‑X23, 110° x 110°)

For maximum panning control, each GALAXY processor output is connected to an individual loudspeaker or an array of loudspeakers. When one processor output is connected to multiple loudspeakers, panning between the loudspeakers is not possible. If panning within an array is not needed, a single Spacemap Go processor output can be used as an input, routed to several outputs connected to an array, and/or used for inner-array optimization.