# Welcome to Atlas Show Control Award Winning Show Control Software for Spatial Audio and more! ## Overview ### A new way of controlling Spatial Audio for Theatre, Live Events & Concerts {% hint style="info" %} This Manual is in Beta - Any obvious errors or omissions? Please let us know! {% endhint %} ## Get Started with Atlas We've put together some helpful guides for you to get setup with our product quickly and easily. {% content-ref url="/pages/P6CT32C6xdRXjnwmuOVS" %} [System Requirements](/installation-licensing-and-requirements/system-requirements) {% endcontent-ref %} {% content-ref url="/pages/zNBuFT1WabWuzdAHv1PX" %} [Key Atlas Concepts](/overview/key-atlas-concepts) {% endcontent-ref %} {% content-ref url="/pages/wR04QcO3QI2nhg22T8qM" %} [My First Atlas Session for DS100](/tutorials/my-first-atlas-session-for-ds100) {% endcontent-ref %} # What we do ## Video overview Got 2 minutes? Check out a video overview of our product: {% hint style="success" %} Coming soon! {% endhint %} # Our Features ## Show Control for Spatial Audio * Control object's positions & spreads and other attributes * Integrated with ZacTracks Trackers for ultimate control * Using Palette you remove the need to remember complex strings * Build OSC Templates and Palette to make programming even quicker * Automatically Park Objects out of the way when they aren't in the scene. * Control up to three OSC Devices on different interfaces for redundant Audio Control * Trigger External Devices, ie QLab, Mainstage, your Sound or Lighting consoles - with ability to quickly enable/disable their outputs * Use our shape generator to send objects around your space * Live Moves & Move in Mute for objects * Standby Selected, the quickest way to set back your devices in tech so you are never out of sequence. * Accepts MIDI & OSC for cue list control, along with OSC Wildcards for External devices * Filter Objects by Sets or by search * Lock objects to disable cue list control allowing only the Overview to move them * Custom background and rotation on a cue by cue basis. *** ## Palettes **Palettes are a powerful tool in Atlas, both Custom OSC and Position palettes are available.** 1. No more Strings! Use Atlas to build palettes with Objects 2. Define a position or palette properties once and reference throughout the cue list. 3. Custom Palettes appear as dropdowns within the cue list. 4. User friendly programming without all the OSC Strings # Key Atlas Concepts Atlas takes the programming of spatial audio show control concepts to a new level. Below are some key concepts that are intrinsic to Atlas's operation. ### What is tracking? ### Wildcards & Iterations # System Requirements Atlas is designed to be extremely efficient and therefore has modest hardware requirements. *** ### Base Requirement Apple Silicon Processor (M1 upwards) 8Gb RAM At least one hardware NIC Running MacOS 13 (Ventura) or Higher {% hint style="info" %} Did you know Mac OS supports VLAN implementation and allows for multiple networks to be presented on a single NIC to the platform. You can find out more about VLAN's and MAC OS here: [Tagging a VLAN on MAC OS. ](https://support.apple.com/en-gb/guide/mac-help/mh15134/13.0/mac/13.0) {% endhint %} {% hint style="danger" %} Atlas will run on Intel based installation of Mac OS. This compatibility mode may be suitable for programming offline but is not recommended for running in performance and no support is given to this implementation. {% endhint %} # Supported Integrations Atlas is constantly adding support for integrations with other manufacturers products. {% hint style="info" %} We're always looking to expand our support across further devices. If you have a project and don't see your preferred device listed get in touch. {% endhint %} ### Spatial Audio Devices * d\&b DS100 - Up to 6 devices in redundant / expanded configuration * L'Acoustics L-ISA * Spacemap Go * Yamaha AFC on DME7 and DME10 * Generic ADM support (Not bi-directional) * Timax SoundHub (Beta) * Adamson Fletcher Machine (Beta) * Amadeus (Beta) ### Trackers * Naostage Optical Tracking * TTA Stage Tracker * Timax Tracker D4 * ZakTracks Pro * ZakTracks SMART * ZakTracks Mini ### Network Devices * Digico SQ Series * Digico SD Series * Yamaha DM Series * Yamaha PM Series * ETS EOS Family * Reaper * Live Professor * QLab ### External Controllers with bi-directional support * Digico SD Series * Digico SQ Series * SSL L-Series Consoles * Yamaha PM Series ### External Devices with Templates installed * Yamaha DM Series * Yamaha PM Series * Digico SD Series * Digico SQ Series * Disguise * QLab * Reaper * ETC EOS ### Midi * Midi support for incoming triggers. * Midi support for program change, controller change and MSC. # Licensing Atlas is free to download and program offline. With a FREE basic license you can control 10 objects (ID's 1-10 only) You can rent full licenses to suit your needs when you go into production. To find out more about licensing Atlas for your production please visit our website: [www.atlas-control.app](https://www.atlas-control.app) # Version History Version 2 Find information about Atlas's Release History here. ## Atlas 2.2.1 (Current Release) ### Changed * Ignore behaviour for modules within a cue. If the cue is ignored but the modules aren't you will now be able to preview selected modules. ### Added * Adds file export to the Monitor & Logging window. * Adds OSC trigger for rotation of background image. * Incoming Tracking data can now have a global offset. * Dynamic Spread X-Mirror has a new variant that can limit the scaling in the y axis. * A new Duplicate Object Position button is now in the Overview toolbar. * A new Shortcuts Menu item. * The Cue Matrix has a Jump to Current Cue button and will now display the operators cue when you open it. * A new Device Editing Table for Outputs — allows for multi-edit and editing of output positions and angles. * External Triggers adds a profile for ScreenCover * User Alerts around Digico data failures or sync errors. ### Fixed 🛠: * An issue where Atlas was ignoring OSC on port 5000 * Adding a new Interface to a Network Device now starts with the correct port. * Issue where an online spatial device could set an objects z value to -inf causing a save to fail. * Quick Actions Live Data not always requesting FunctionGroup Information correctly. * External Controller Reverb Mapping not outputting control data to the spatial device. * Object Overview spread textfield now allowing editing when the object was playing back. * Fixes an issue with the cue list jumping to a cue number via keyboard import. * A Cue Colour of None is now an option in the context menu of the cue list. * Fixes and issue with cue number and name editing via double click. * OSC Output for Network Devices has been improved for a faster response time when cues are fired. * Network devices are now selected when created. * Fixed an ordering issue with the Cue Information view not always displaying network devices in the correct order. * Enabling Hubble Re-Transmit affecting incoming tag data. * Updates to Hubble Integrations * Issue where a position module enabling tracking on a limited axis would take from the live position if the module had a duration. * Issue with multi objects patched to the same tag but wanting different axis locks. *** ## Atlas 2.2.0 ### Added * Support for Devices E & F in Redundant only mode. * boundaries now have an optional z value which also apply to SmartAction triggers. * Adds a \`Remove Objects & References\` option in the Cue Matrix context menu. * You can now search in the Cue Matrix, this replaces the search from the cue list in the main workspace window. * Position modules that enable tracking and have a fixed axis value will now be outputted when the module starts. * Smart Actions no longer trigger when an object is parked. * New OSC for External Controller including updating /position for x,y and x,y,z * A new item in the Tools menu for enabling/disabling virtual tracking. ### Fixed 🛠: * Support for Hubble's default OSC style in the monitoring window. * When Hubble's output format is \`Hubble\` Atlas will allow it as valid OSC when virtual mode is enabled. * Network Device fixes for Yamaha PM. * Issue with keyboard shortcuts making Network Device Modules * Issues with newly created Controllers not responding to object based OSC control until the workspace has been reopened. * If a smart action enables dynamic spread and the dynamic is currently active it will no longer re-trigger. * UI Updates around fixed axis values for Position Modules when tracking. * Minor issues relating to External Controllers in specific OSC profiles using localhost. * Incoming monitor window for trackers now has UI updates round data coming from Hubble. * Issue with Position Modules moving from Live to a palette position where x/y didn't change from the objects live position. * Position modules that enable tracking that are also using a Position Palette will now use the position palette * Position module inspector will show the palette position in the textfields when its selected. * Position modules that enable tracking on a limited axis will now highlight the fields that will be locked by the module. *** ## Atlas 2.1.1 ### Fixed 🛠: * Fixes a issue with cue list selection OSC triggers. * Fixes and issue with modules not updating live values within the same cue if they had pre-waits. *** ## Atlas 2.1.0 ### Changed * The High priority queue has been rewritten, is now uses dynamic frame rates to try to avoid socket overloads when standing by for large amounts of data in less than ideal network situations. The OSC output stream can continue if the module has stopped playback for large quantities of data. The maximum output frame rate for high priority queue is now 350Hz per device. If you panic atlas while a standby is occurring it will stop the OSC output immediately. * Support for objects having x,y,z * Removal of \`height\` palette parameters ### Added * Spread modules now have an Update From button similar to Position Modules. * The context menu in the cue matrix allows you to set the selected cue in the main cue list or operator cue list. * OSC hooks for enabling Virtual Tracking. * A Reaper Network Device, which allows for creation of markers on cues being fired - markers are only created when the device is enabled and Reaper is recording. You need to install the Atlas/Reaper OSC Pattern config file to allow a connection, instructions on how to do this are within the Reaper Network Device. * Live Professor & Yamaha Rivage Network Device profile. * Yamaha AFC parameters for Zones and Outputting Alias Names. * Selecting an object header in the module list will now show the object name alongside the ID * When trying to standby for a cue if a spatial device is being throttled the standby will the canceled and a dialogue will appear. * Device Palettes can now have a folder structure in the editor window. * A new Sets Tab in Show Settings, allowing for more efficient creation/editing of sets. * The Tracker Monitor window now shows the objects that can be enabled on the tag. * Position and Shape Modules support a Z value. * Position Palettes, Object Parking & Default Locations support Z. * New Keyboard shortcuts for making modules, ⌘1 - Opens Object Picker, ⌘2- Adds a Palette. * Network Devices now have keyboard shortcuts for quickly adding to modules, they follow the order of the tool bar starting at ⌘3 * A new Smart Action Overlay now appears on the overview when a trigger occurs. * Actively tracking objects also now float with incoming data status on the overview. ### Fixed 🛠: * Smart actions now display all alias rather than just the first. * When copying a Palette Module cue only objects and output will now be pasted. * Inspector preWait and duration issues when entering a time with a \`:\` * Minor UI updates for palette inspectors * When changing palettes in the same module cue only objects will remain where appropriate. * UI updates for Ventura. * Deleting snapshots from a digico causing the incorrect cues to fire. * Cue matrix will now display Alias' for referenced objects. * Issue where MIM symbols didn't disappear when using Position Palettes, this could also lead to incorrect positions being outputted. * Memory leaks related to Tag and Network Devices. * Network device no longer output OSC when the global OSC Disable has been engaged * Issue where toggling the OSC Enable/Disable during output could cause Atlas to hang. * Creating a new modules from an Object Headers * Issues with the order of network devices not being consistent in the cue matrix. * Copy & Paste of shape modules not playing back the selected shape. * Function Group Display supports multi select * Patch sheet is resizable on macOS 15+ * Network Devices in the cue matrix now show the input field. * Memory Leaks & bug fixes relating to Network Devices initialising. * Duplicate modules controlling the same network device but with different actions will now output and show clashing module warnings as expected. * Palette folders not displaying correctly in Smart Actions. * Network Devices now apply custom formatting to batch module creation within the cue matrix. * Network Devices now display information correctly in the Cue description. * The Inspector can now show/jump to reference shape modules like the main workspace window. * Pasting Palettes into folders. * Alias are now saved correctly in Smart Actions. *** ## Atlas 2.0.5 ### Added * **Network Devices** – New device type with bi-directional support and current cue status displayed in the toolbar. Features include: * Support for DiGiCo, ETC Lighting Console, QLab, and Blackmagic Videohub. * Deletion and reordering of devices. * QLab enhancements: pause/resume status, workspace selection, display mode, passcode editing, TCP connection warnings, and automatic monitoring when a workspace is closed. * DiGiCo support, including firing snapshots via their number and point cue support. * Various display options in Atlas Preferences. * SpaceMap Go OSC profile is now available. * All External Controller profiles now listen for lock/locate OSC messages. * Palette parameters for Matrix Crosspoint gain and delay for Soundscape. * You can now update all devices at once when importing a new system file after the initial assignment. * Dynamic Spread now supports Y-Mirror. * LiveProfessor OSC template added as an External Trigger. * When selecting via Sets, the background will highlight when all members of the set are included in the selection. * Function Groups can now have a colour. * When using multiple objects on a Tag for tracking, the inspector will now show the first object alongside the Tag ID. * Only populated sets will appear in Palettes and QuickActions. * QuickActions for Matrix Crosspoints now show live data. * Output Sets now support a context menu for removing outputs. * Position Modules can now update selected modules to an object’s default location. * New MIDI trigger for *Go* to allow for footswitch triggers. * DiGiCo External Controller can now use a Control Group to control En-Space Trim. * Speaker display properties in the Space Editor now persist in the file. * Support for MSC Go and Stop. * Option to hide QuickAction values if needed. * Speakers can now be viewed per space in the Programmer. ### Fixed 🛠: * Selecting the object header in a cue now only highlights the relevant position modules. * Atlas External Controller profile now outputs separated strings. * Fixed: External Controllers in certain situations wouldn’t output OSC to the spatial device but would move the object on the overview. * When locking an object that’s actively being tracked, the module will remain tracking. Unlocking resumes tracking. * Colouring Sets now updates speaker colours in the overview. * A hard locate no longer stops tracking when unlocking the object. * Smart Actions using Dynamic Spreads now correctly reference the palette. * QuickActions: Selecting all Function Groups now only selects Function Groups enabled for display. * Fixed an issue where external MIDI devices could not control Atlas. * Layout issues fixed for Function Groups live data in QuickActions. * Fixed inconsistencies with Function Groups in QuickActions not always showing live data. * Minor updates for Matrix Crosspoints in QuickActions. * Standby Selected now correctly uses the selected cue when fired via MIDI. * When MIDI or the keyboard selects the previous cue, Atlas no longer deselects the cue list after the first cue. * Firing a Palette via OSC now requires an exact match of the first argument, rather than matching if the palette name contains the first argument. * Fixed a bug in Position Modules that could cause an object to return to its previous live location when triggering a module twice with *Go*. * Addressed an issue where cues could show a UI bug of looping after modules finished. * Fixed an issue where deleting multiple palettes could remove the wrong palette selection from a module. * Fixed a crash that could occur when standing by a palette with deleted objects. * Fixed issues with trackers locking the X/Y axis, causing incorrect behaviour. * UI update: In the Module Editor, only the selected cue will dim all modules. * Minor UI updates and bug fixes. *** ## Atlas 2.0.4 ### Added * Palette modules will now show a flag in the module list if no palette is selected. ### Fixed 🛠 * Issues caused when MIDI devices had intermittent connections while running timecode * Workspace timecode frame-rate can now be edited in the Show Settings or Monitor Window. *** ## Atlas 2.0.3 ### Added * TiMax Sound Hub V2 OSC Profile * Importing TiMax files for faster set up . * Scaling/repositioning of your show now happens simultaneously and allows for spaces to be dragged. * Objects are now drawn in the rescaling window allowing you to preview the new live positions. * Smart Actions - Smart Actions let you automate behaviour like adjusting spread or firing Palettes or External Triggers without relying on the cue stack. They stay active while enabled and react to triggers or boundary conditions in real time. * External Triggers now have an Object Patch allowing for integrations into Smart Actions. * You can now adjust resizing parameters by entering values. * A new Preview in Overview button allows for resizing to affect object positions in real time.
### Fixed 🛠 * OSC Triggers that start a cue will now scroll to the cue in the cue list. * Auto Creating output sets now only creates sets that have an output attached to them. * A bug where dragging a rescaling of the show off the screen would cause drawing issues. * Enable All Trackers from Show Settings could cause some Tags not to activate. * AutoScrolling the cue list when firing a cue. * OSC enable/disable for Timecode now correctly toggles chase enable. *** ## Atlas 2.0.2 ### Added * Holding Command while scrolling will now zoom. * You can now also Reposition as well as Rescale your Show by space . * More Live Data parameters for Yamaha AFC * Spatial Devices can now send to Atlas on port 5000 * When resizing or repositioning your show, the selected objects will also update the live object positions * The timecode display will now be read if the incoming MTC doesn't match the workspace settings. * More Live Data values for Outputs in Quick Selects for a DS100
### Fixed 🛠 * Performance updates related t o closing a file leading t o memory retention. * Custom OSC Server for AFC improving performance. * Standby Selected causing a crash in some profiles. * When creating a new parameter in a palette it's now automatically selected. * The Palette Picker for Parameters will now update for the OSC Device Profile without needing to close the window. * Palettes containing multiple device profiles could unintentionally output. *** ## Atlas 2.0.1 ### Added * Ability to Re-Scale your Show By Object. * The Programmer will now show a simulated output from the module during playback rather than the current positions of the object. ### Fixed 🛠 * Dynamic Palettes now auto-name correctly in the Spread module. * Editing multiple identical Position modules now updates all associated nodes as expected. * When editing multiple Position modules, the correct node is now highlighted during interaction. * Polar Space Listener adjustment now persists on save. * When editing unique Position modules simultaneously, the correct hover feedback now appears on each editable node. * Start and end text fields in the position module now individually update the x/y values when multi-selection editing. * General performance improvements. *** ## Atlas 2.0.0 #### Released 3rd June 2025 ### **🎉 Free Basic Plan** * New Licensing Model for Atlas – Allowing OSC output for 10 objects with a Basic Licence, which is **free** * Atlas now features new playback engines designed for improved performance and scalability, enabling greater object capacity with precise concurrent object control ### **🚀 Major New Integrations & Control** * Bi-Directional control for L-ISA & Yamaha AFC * Adds L-ISA as an external Controller Profile * Atlas can display DS100’s audio levels * Import from Yamaha Speaker Export File * Adds Spatial Device D in redundant mode ### **🎛️ Powerful New Creative Tools** * Palettes can now Fade 🙌 * Fading Palettes automatically transition from the current or last value to the new values * Quick Actions now support live data for all Palette properties * Cue Only Palette properties are now editable in the Inspector, enabling parameter adjustments and object/output assignment from the cue ### **🧭 New Space & Visual Features** * Atlas now has a Polar Space for all polar output * Listener position can now be viewed relative to every space * New tools for resizing and manipulating space * Views now have grids * Background images now exist independently of Spaces, allowing multiple overlays for better alignment across all Atlas Views ### **🎚️ Monitoring & Cue Enhancements** * The Monitoring window now shows all incoming OSC with validation * New "Incoming Triggers" tab logs all OSC triggers Atlas receives * OSC Trigger Publisher now sends start cue messages from external OSC * Cues with ongoing modules (e.g., Dynamic Spread or Trackers) now show as “Active” ### **🛠️ Workflow & Usability Improvements** * A new Object Patch Window for quickly editing names and spatial IDs * Patch Window now shows invalid conflicts and short names * You can now create multiple objects at once * Improved Standby Selected * Timecode can now auto-standby on sync lock (minimum 5 seconds) * Improved UI updates ### **⚙️ Preferences & Advanced Settings** * New preferences for Cue Number creation * Cues with number 0.0 can now be hidden * Cue Matrix can batch renumber to zero * Option to define Speaker Size in Atlas preferences * Function Groups now have a display option ### **🛠 Additional Improvements:** * When enabling an object for more than one Tag, the primary tag will be patched in the cue list * A Position module with a Tracker enabled will now remember the selected patch where appropriate if the tag has been disabled and the object isn't removed from the tag * If you have two modules with matching pre-waits controlling the same object parameter, Atlas will now playback both simultaneously * Background scale migrations from older files * Become active banner on first launch when it’s the only active workspace * AFC Heartbeat now follows the active workspace * CueOnly objects for spread palettes will now also show a clash # Atlas Version v1 (Archive) Atlas V1 is now retired. This information exists for archive purposes. If you have a V1 show file that you need translating to V2 please get in touch at support\@flamingosoftware.co.uk *** ## Atlas 1.4.7 #### Fixed 🛠: * Incoming OSC Triggers for Starting a Cue will now be debounced with the OSC Trigger Debounce Time. * External Controllers Reverb Mapping would attempt to output to Devices B & C when they were offline. #### Known Issues: * Selecting a specific interface for a Spatial Device can cause OSC to drop packets - (Recommend using Automatic) * If a you have two modules with matching pre-waits controlling the same object parameter Atlas will playback both simultaneously - (these will be shown in the module list as clashing) * Standby Selected in certain situations wont correct restart effects when mixing Groups & their children throughout the cue list. #### Previous Version History *** ## Atlas 1.4.6 #### Added: * Ability to Rotate incoming tracking data. * Support for Latest D\&B Soundscape Firmware allowing 128 objects and 32 function groups in device A. #### Fixed 🛠: * Issues with devices not automatically connecting on open when certain circumstances are met. ## Atlas 1.4.5 #### Added: •⁠ ⁠Naostage Tracker profile. #### Fixed: •⁠ ⁠Issues with the default boundary colour causing some files to save incorrectly. ## Atlas 1.4.4 #### Fixed 🛠: •⁠ ⁠Minor issues that could lead to some Atlas files not migrating correctly from older versions. ## Atlas 1.4.3 #### Added: •⁠ ⁠Effects! - In the Palette Editor you can create multiple effects for use throughout the cue list. •⁠ ⁠Ability to Stagger Pre Wait times for selected modules. •⁠ ⁠OSC Triggers for start a cue & standby will now publish on the Atlas Trigger Output #### Changed: •⁠ ⁠Anchoring a drawn path in a position module will now playback from the Objects live position. #### Fixed: •⁠ ⁠When creating an Alias it will now automatically be selected. •⁠ ⁠Performance when scrolling in the tracker list. •⁠ ⁠Overview Set Selection is now saved into the file. •⁠ ⁠Boundary Colours now persist. •⁠ ⁠Standby for sequence effects not allowing the correct offsets. •⁠ ⁠Multi edit plotted boundaries on objects within cues. #### Known Issues: •⁠ ⁠Selecting a specific interface for a Spatial Device can cause OSC to drop packets - (Recommend using Automatic) •⁠ ⁠If a you have two modules with matching pre-waits controlling the same object parameter Atlas will playback both simultaneously - (these will be shown in the module list as clashing) •⁠ ⁠Standby Selected in certain situations wont correctly restart effects when mixing Groups & their children throughout the cue list. ## Atlas 1.4.2 #### Added: •⁠ ⁠a new Atlas Preference window which allows for some control over the view. •⁠ ⁠The Overview can now follow the selected background including rotation. •⁠ ⁠When adding positions for objects into the cue you can now enable Tracking from the Object Picker. #### Fixed 🛠: •⁠ ⁠If you have a group enabled for Parking/MiM you now see a Parking Symbol next to all of the children. •⁠ ⁠Crashes that could occur in the CueMatrix when running macOS15 (Sequoia) •⁠ ⁠Updates to the Cue Description to allow to more detail ## Atlas 1.4.1 #### Added: •⁠ ⁠Functions within Palettes can now be duplicated. •⁠ ⁠Ignored Palettes will now be strikethrough in the Cue Matrix. •⁠ ⁠You can now create palettes for spatial engines that aren't the active profile. •⁠ ⁠Ability to copy a module to another object even if they aren't in the cue. #### Fixed 🛠: •⁠ ⁠A bug that could cause the ⁠ Another Workspace is Open ⁠ to not appear. •⁠ ⁠Improvements to how Atlas draws Speakers. •⁠ ⁠An issue in macOS Ventura that could stop function groups from being manually renamed. ## Atlas 1.4.0 **Released 4th October 2024** ### Added Support: * Profile added for L'Acoustics L-ISA. * Support added for TTA Trackers. * Support for 128 Objects across two DS100 devices. * Hubble Integration for Trackers. ### Changed: * Improved Midi implementation and efficiency. * Midi IO presentation to the system. * Shapes or Position modules that have an infinite repeat will now be started in Standby-Selected. ### New Features: * External devices will now take default port and icons when they are populated. * More Symbols for External Devices * Midi is now available for External Devices. * When changing OSC Profiles you'll need get an option to update all the TX ports to the devices default. * Palette Detail view will now show when a module in that cue is ignored. * Boundaries can now be applied to multiple tags at once. * You can now create Multiple Tracker Patches at once. * Objects are now drag and drop onto Tracker Tags. * Palettes now appear in the Cue Matrix. * Warning now appears when deleting objects. * Circles can now unlock axis making them into an Ellipse * A new Shape Reference is available for Shape Modules allowing more control over shapes that are currently running. * Spaces size and positioning can now be adjusted with drag handles in Show Settings. * Cue Matrix allows batch removal of External Devices. * External controllers now respond to Bundle OSC messages. * Right click on an object in a cue will now allow for selecting all objects. * A Timecode Frame Rate can now be set allowing for formatting and validation of Timecode values. * OSC can now set the Project Tempo to a known BPM. * OSC can now be used to assign the Overview background. * OSC can now be used to change Sets selection in the Overview. * Operator Cue list selected cue will now highlight even when the window doesn't have focus. * A new Clamp Timecode button that will clamp triggers to new frame rates. * More Control over removal of Cue Colours from the menu. * Palettes can now be deleted with multi selection * Palettes can now be copied and pasted across files. * Position Modules with a drawn path now have the option to repeat. * When adding a new image to a empty background, the background image will be auto named. * You can now duplicate backgrounds for spaces. * Loudspeakers now appear in the programmer view. ### Fixed 🛠: * Bug where seamless in random shapes wouldn't save. * OSC ADM will continue to listen when you change profiles. * Spread modules would show incorrect names when using a palette. * Bug that could cause a crash when editing a shape module in the cue matrix. * Tap Tempo now only displays to whole BPM Numbers. * Minor Bugs in shape References. * Other minor improvements When importing from a .dbpr file we will now show objects without names. * Windows not maintaining their title when being saved. * A bug that in certain situations not all workspace windows would close when the main workspace document was closed. * Bug in the timecode editor for the cue inspector. * Bug that could cause the Device A Network Interfaces to not be recalled correctly. * Bug in Standby Selected for external devices that could cause them not to output. * Live moves showing when you use a shape module with a type of reference * Shape Reference for a stop ignoring pre-waits. * When pasting a module with a pre-wait if the object doesn't exist in the new cue the pre-wait will be pasted. when standing by for a cue sometimes the move in mutes wouldn't be correct for shape modules. *** ## Atlas 1.3.6 **Released 2nd June 2024** ### Changed: * Minimum system requirements are now macOS 13 (Ventura) ### New Features: * Support for ADM as a Spatial Device. * An Operator cue list that responds to the midi inputs can be found under Window menu item. * A new "Show Selected" button in the editor window thats the equivalent of holding Control. * When holding Control or "Show Selected" is enabled in the editor reference objects will also now hide. ### Fixed 🛠: * Longer cue numbers truncating. * Palette Values updating now update live in the inspector. *** ## Atlas 1.3.5 ### Changed: * Only Trackpads or Apple Mouse can be used to pan around the views without holding CMD. * improvements to editing durations, cue names and numbers. ### New Features: * Spaces can be updated without the need for Array Calc. * Duplicate multiple cues from within the Cue Matrix. * Adds Cut/Copy/Paste to Cue Matrix. * Objects & Spaces can now have a height. * Speakers now appear in the boundary view. * Objects can have a boundary applied to plotted positions that can be overridden within a cue. * When opening a file that cant be decoded properly the document will close automatically and a warning will show. * Cue Matrix can now assign backgrounds to cues. * External Devices can now support multiple messages. * A greater level of control for background images in scale and position ### Fixed 🛠: * UI Updates for macOS Sonoma * Previewing a module in some cases would show the preview countdown. * Controller ADM Cartesian now outputs a height for the z value. * a bug that would show objects in the palette inspector if they weren't needed. * When making a new cue Atlas could create a cue with a matching number. * Issues with the Spread textfield in the overview when connected to a live device. *** ## Atlas 1.3.4 ### Changed: * The Module inspector now expands to under the Overview. * Drawing a single position will no longer set the module duration to 0. ### New Features: * Ability to Duplicate cues and modules. * Live data for Spread,EnSpace and Mode are shown in Quick Actions. * Visualiser mode allowing Atlas to display incoming OSC. * Output for Spatial Device now have the option to be scaled. * Modules can now be added when selected on the Object in a cue. * You can now edit & play a position module from clicking on the object if you only have one in the cue. * New styles available for the Object Overview * Dynamic Spread in X-Mirror now has a safe area where the spread will stay consistent. * Dynamic Spread Palettes * In the group configuration window you can now update the parent position from its absolute position. * Group colours can now be applied to children. * Adding a set into a palette, if the set contains a group the children will be added. * Arrows for fine adjustments of background images now available. * Groups will now how mixed status for children in the overview popover * Groups will show the child count for children that are currently under control in the overview popover * Speakers can now be viewed on the space configuration page ### Fixed 🛠: * Position textfields will now update all selected position modules in the inspector. * A bug that could allow return character in a pasted object name. * Views being able to zoom into negative space. * Bug that could cause new outputs to be added instead of updating names. * View & Performance updates. * When adding a module if the object isn't in set that is being filtered the viewing set will be changed to `all` * Static Spread view being able to pan/zoom. * A selection bug when holding shift in the object picker for groups. * Position Palettes now save the background image for configuration. * A bug that could cause groups with palettes to not set back their children correct with StandbySelected * A drawing bug for groups that wouldn't show children correctly if using palettes. * A bug where renumbering from the cue matrix wouldn't format to 2dp. * a bug where the Overview controls for Groups wouldn't apply to children. ## Atlas 1.3.3 ### Changed: * Auto-Reference will now only work for objects that have parking enabled. * Reverb Level faders are now logarithmic * Boundaries have moved into the Spaces Tab * Atlas Midi port will now just appear as \`Atlas\` ### New Features: * A new Palette detail view showing which cues are using the Palettes. * A new Palette \`Capture Live\` button that will take an objects spread, EnSpace send and Mode into a palette. * A new filter button that can quickly filter objects on the Overview. * Dynamic Spread now supports \`X\` and a \`X-Mirrored\` and Radial. * New \`Cue Only\` Button for palettes object and output assignment. * You can now update references based off previous cues in the cue matrix. * Palette view improvements. * Objects that don't have Parking enabled can now have a duration, if they do Atlas will move the object from its current location to the plotted. * A new TimeCode capture button in the cue inspector and the CueMatrix context menu. * A new Ignore option in the context menu for Cues. * Copy & Paste for Dynamic Spread * Ability to select objects for a \`Capture Live\` Palette * When running Dynamic Spread, live updates in the editor will take affect. * Cue Matrix can now batch renumber * Reverb Mapping for External Controller * ADM OSC Format for External Controllers * A Secondary Tracker Server is supported for ZacTracks * When configuring children in a group you can now click and drag on the child. * The ability to set the space for all groups. * A New Random Shape with ability for Tails * Random Shape has support for BPM either a manual tap, OSC or Midi trigger. * Cross Hairs now appear when dragging on the overview. * You can now import Cues that are Tab Separated, Number/Name - This allows for copying QLab cue Numbers/Names and importing into Atlas. * You can delete cues from the cue matrix * Cue Colours can be edited from the Cue Matrix. * Palette Detail view will now show markers. ### Fixes 🛠: * A reposition bug caused with a position module and a shape module in the same cue. * A bug causing a parent with parking enabled to not auto reference children when making a new cue. * when changing the palette in a cue the inspector will now select the new default preset rather than leaving the picker blank. * Minor UI updates * Bug causing spread module to not override dynamic spread if a position module was present. * A Small bug when trying to redraw shapes if they are running. * A bug that would cause dynamics to not apply if imported from array calc object. * small bugs in the Cue Matrix * Sleep All Tags will work when mode is Wake & Sleep on Park. * A bug in External Devices Populate dropdown that could cause Wildcards to have the same IDs. *** ## Atlas 1.3.2 ### Changed: * The default Yamaha PM Range Scene Recall OSC have changed to match newer firmware. * Objects with SpatialIDs that are greater than the profiles maximum number of objects wont output OSC. ### New Features: * Dynamic Spread can now be enabled on Spread Modules * Cue number that match and aren't 0.0 will display in orange. * Ability to handle scaled tracking data. * Speakers can be viewed on the Overview (Re-import of Array Calc is needed) * Output Sets can have colours that will be applied to the speaker overlay * A new relative offset for group configuration. * Undo support for group configuration * A new \`Force Offsets Live\` for quick manipulation of groups, found when editing groups. * A new Palette details view showing which cues are using the Palettes. * A new filter button that can quickly filter objects on the Overview. ### Fixes 🛠: * Bug causing Device C to not show as Online. * An issue where Spatial Devices wouldn't connect with the automatic interface. * Viewing multiple shapes will now dim non selected. * Adding new shape modules or changing shape types will now centre the shape in your selected space. * Changing the IP of Device C would temporality cause device B to go offline. * a bug where standby selected wouldn't set alias names. * a bug where deleting the last module for an object in a cue where the module is ignored wouldn't delete the object from the cue. * Small background improvements * Issue causing StandbySelected where ignored cues wouldn't be counted as ignored. * Overview and Programmer view improvements for toolbar controls. * small background bugs that could lead to a crash. * A reposition bug caused with a position module and a shape module in the same cue. *** ## Atlas 1.3.1 ### Added: * Atlas now has a \`Live\` view allowing you to see the Quick Select and Overview in the same window. ### Fixes 🛠: * Bug causing Device C to not show as Online. * An issue where Spatial Devices wouldn't connect with the automatic interface. * Viewing multiple shapes will now dim non selected. * Adding new shape modules or changing shape types will now centre the shape in your selected space. *** ## Atlas 1.3.0 **Released 19th January 2024** ### Changed: * Atlas no longer imports Rotated Array Calc Position Planes. * Atlas will communicate to all DS100 in Meters rather than scaled vectors, this means the only importance of the Mapping Plane relates to External Controllers if they require it. * This build will automatically migrate all positions and spaces, if you were working with space that contains a rotation that isn't 0,90,180,270 you wont see your previous space inside of Atlas. We will apply the rotations where possible then remove the rotation from your space. * The Move in Mute Colour on Objects is no longer red to avoid confusion with an objects being muted. * The Overview now has a purple border around it making it easier to distinguish between the programmer and the overview. * External Controllers Networking settings can now only be changed when the device isn't enabled. * What used to be called \`Assign Object References from previous cue\` is now called \`Assign Object References from previous cue\`, perviously Assign was only additive where as now update will remove objects references that shouldn't or cant be referenced in that cue. ### New Features: * You can now pan around views. * When drawing in a position module using Shift now repositions the drawing, CMD is used for panning around the view. * External Controllers in the Atlas Profile can now lock, locate & hard locate on the controller port * External Controllers using the Atlas Profile can now use Split x/y for Atlas Positional Strings * External Controllers can now control locked objects. * Shapes now support undo. * Editing a point in a position module will now register an undo. * You can now create module under the context menu of an object in a cue. * Spaces and Background can now be reordered. * External Devices can now name the value textfield by using \`#Name#\` where Name is the displayed parameter name. * External Device strings now support up to 3 wildcards \`#\` and up to two Iterations fields \`\[]\` * New OSC Trigger View in Settings * Tracker IP and Profile settings have move to a new \`device\` tab in Show Settings. * Duplicate Network Interfaces with different IP Addressed will now show as a single interface but show both addresses in the network interface pickers. * A new \`Automatic\` Network Interface option is available so you don't have to choose interfaces. * Outputs can now have belong to a set, these can be auto generated from your function groups. * Change logs can now be viewed from the \`about\` window offline. * Position Palettes can now be reordered. * Textfields for position modules start and end locations now have the option for scales or metered inputs. ### Fixes 🛠: * Selected a referenced object will keep the inspector spacing. * Children of Groups now work correctly in Auto Park Layouts. * When adding a new cue only objects that can be parked will be auto referenced into the cue. * Position Modules that have a path drawn can now have a duration of zero, you can now edit this time. * Position Modules with a time of zero will now go to their end location and not start. * A bug causing the modules to stay selected when selecting a cue. * Multiple messages to an external device will now playback for Standby. * All wildcard values are carried forward in a external device module copy and paste. * Bug causing textfield names not to show in a external device inspector if the OSC path has no arguments. * External Controllers that require multiple messages will now be sent as a bundle. * Catch radius not always drawing the in correct location * Overwriting Objects from an Array Calc Import will now update names correctly. * A bug caused rotation offset by selected multiple shape objects at once. *** ## 1.2.6 **Released 14th November 2023** ### Fixes 🛠: * A bug causing atlas to think it was closed when minimised * Tracker Improvements * Background improvements * Default Boundaries for Tags are now saved. * Removes comma separation from Tracker Patch *** ## 1.2.5 **Released 10th November 2023** ### New Features * Pressing Delete on an objects header will remove it from the cue. * Select all now works with external devices and Palette Modules. * You can now select all modules of the same type for that object. * Creating a Module from a Reference will now take the alias forward. * Atlas will stay open with no windows * Error messing around the ports has changed, you now get a yellow banner if multiple workspaces are open and you can quickly toggle between then. * If a workspace isn't active, it wont respond to OSC, or Midi and its outputs will be disabled. IE the workspace can be used for referencing and programming. * Secondary Patches for Tags * Ability to Sleep/Wake Tracker Tags on actions and via OSC. * By default when enabling a tracker its on completion will be \`Leave Active\` * Automatic Tag Refresh rate detection. * Groups now appear in the Object Overview. * Warning if you open an Atlas file in an older version that what it was previously saved in. * DiGiCo Quantum OSC Presets added. {% hint style="danger" %} V 1.2.5 changes the OSC strings for trackers. Please see relevant section for documentation. {% endhint %} ### Fixes * Ignored cues wont be triggered via OSC. * Improved context menu for single and multi selection. * Default short name will now show 4 characters * Tracking Objects Wrap in the patch view. * Bug that required a file to be reloaded in order to output External Controllers. * UI Updates around configuring Tags. * Context menu for the module list if running MacOS Monterey *** {% hint style="danger" %} As a general rule it is not advisable to open a file in a version older than the one in which it was created. {% endhint %} ## 1.2.4 ### New Features Pressing Delete on an objects header will remove it from the cue. Select all now works with external devices and Palette Modules. You can now select all modules of the same type for that object. Creating a Module from a Reference will now take the alias forward. Standby Selected and Force Selected now appear for OSC. ### Fixes Ignored cues wont be triggered via OSC. Improved context menu for single and multi selection. OSC Panic causing undesired issues Shape Modules not removing the Move in Mute Symbol. *** ## 1.2.3 ### New Features Rotation Offset View for wanting to spread multiple objects around a circle. Option to allow OSC Triggers to move the Playhead Option to allow TimeCode to move the Playhead Perform shows the Overview and the cue list. ### Fixes Issue where viewing Background Grids wouldn't always draw correctly. Issues were inspector selection wouldn't always show correct pre-waits and durations. Updating Position from Live now shows the Object at the top of the list. Duration Field is no longer disabled when multiple modules are selected. Deletion of modules for multi select. Deletion bugs around Position Palettes Performance Updates *** ## 1.2.2 ### New Features Group offsets now have a set from relative/absolute option. Alias' now appear in the Object Picker, clicking an alias will set the alias in the cue Alias' can now be searched in the Object Picker When opening the Object Picker alias for the cue will be displayed Alias' can now be reordered. Multi-Select Referenced objects will now allow you to add them to a cue/remove them. Reference objects can now be delete with backspace and the delete key Adds One Time Park for Objects that aren't in Atlas. Holding CMD and clicking in the Object Overview will remove all linked Objects. Object Overview button is now in the Overview Window ### Fixes Playback issue if you have a group and a referenced group member in the same cue. Shape Modules would Move in Mute to their end locations not their start. Spacing of points along a journey might not be as expected if not looking in the default space. Origin not showing when configuring backgrounds. *** ## 1.2.1 ### New Features Controller up to 3 External Controllers keeping them in sync with your spatial engine. Support for Undo/Redo when drawing boundaries. Palette Presets can now be targeted via OSC Atlas will open the most recent file on launch. Ability to turn off Stabilisation on Tags. Enable/Disable Tracker Tags can be done globally. Parking Layouts are now an option to auto generate grids for parked objects. Disclosure Groups in the Palette Editor are now saved. Presets for Palettes can now be rearranged. Group Offsets can now be updated from live information. En-Space Level send in the overview. Spread from palettes now gets passed to External Controllers. En-Space level can be used for groups. ### Fixed Boundaries adding points incorrectly when not in the default space. Forced Selected will now enable trackers. Setting boundaries to space size when not working in the default space. Performance Updates. A Clearer indication when adding objects that can be referenced into a cue and you've selected them. External Controller Port Field used to require Enter button before taking the port, no longer does. Dragging positions for long periods of time would cause the connection status to blink. Overview Overlay jumping/disappearing on click. Group Object config will remember your selected space for editing. Atlas will compress background images to a maximum of 5mb. A bug that caused larger file sizes with shape modules in certain circumstances. Improved Errors around Licence Activation Boundary views not filling when drawn outside of the space. *** ## 1.2.0 ### New Features Controller up to 3 External Controllers keeping them in sync with your spatial engine. Support for Undo/Redo when drawing boundaries. Palette Presets can now be targeted via OSC Atlas will open the most recent file on launch. Ability to turn off Stabilisation on Tags. Enable/Disable Tracker Tags can be done globally. Parking Layouts are now an option to auto generate grids for parked objects. Disclosure Groups in the Palette Editor are now saved. Presets for Palettes can now be rearranged. Group Offsets can now be updated from live information. En-Space Level send in the overview. Spread from palettes now gets passed to External Controllers. En-Space level can be used for groups. ### Fixed Boundaries adding points incorrectly when not in the default space. Forced Selected will now enable trackers. Setting boundaries to space size when not working in the default space. Performance Updates. A Clearer indication when adding objects that can be referenced into a cue and you've selected them. External Controller Port Field used to require Enter button before taking the port, no longer does. Dragging positions for long periods of time would cause the connection status to blink. Overview Overlay jumping/disappearing on click. Group Object config will remember your selected space for editing. Atlas will compress background images to a maximum of 5mb. A bug that caused larger file sizes with shape modules in certain circumstances. Improved Errors around Licence Activation Boundary views not filling when drawn outside of the space. # Objects Objects are the individual audio streams that are controlled within Atlas.

Show Settings - Objects Overview showing named and coloured objects imported from R1 File.

### Adding Objects to the Workspace #### There are 3 ways in which it is possible to add objects to your workspace: {% hint style="info" %} By default Atlas will auto-increment the spatial ID with each additional object. {% endhint %} #### Import from DS100 When online Atlas will allow you to import objects as presented within the DS100. Any names will be preserved and imported from the live device. #### Import from File Please see [Import from File ](/show-settings/spaces/import-from-file-ds100-mode) #### Add Object Allows spatial audio objects to be manually added to the Atlas Workspace. By default these objects will be named "Spatial ID X". {% hint style="warning" %} Atlas w[ill warn the user when two objects share the same spatial ID with the following error message: ](#user-content-fn-1)[^1] {% endhint %} ### Deleting Objects from the workspace Select the required objects and select "Delete Object" from the menu. *** ### Functions Associated with Objects #### Name This is the long name of the object. #### Short Name This is a 4 character name that applies to the objects as viewed in the programmer and overview. Note: This can also include Emoji's. #### Spatial Object ID This is the ID that is presented to the spatial audio engine. These can be modified within the Atlas show file to allow for reassignment of objects without the need to reprogram within the space. #### Default Journey Duration This is the time in which an object will move by default when given a journey in the programmer. #### Live Move Duration When enabled: This is the time in which an object will move by default when presented with a live move in playback. #### Object Colour Allows for an object, or group, to be assigned a colour. [^1]: # Sets / Alias Sets and Alias's provide powerful programming and data filtering functionality within Atlas. ## Sets Sets allow for logical groupings of objects that a user may wish to view, program or control together. They form the basis of a programming tool and, unlike groups, have to direct effect over the objects contained within them.

Show Settings - Object Overview showing Alias assignments

{% hint style="info" %} By default Atlas assigns all objects to a set named "all" that cannot be deleted. {% endhint %} #### Creating a New Set Clicking on the "+" sign creates a new set within the window. Sets can be renamed by right clicking on the name of the selected set and choosing "Rename". #### Deleting a Set Right clicking on a selected set and choosing "Delete "set name" will delete the set. #### Assigning Objects to a Set Assignments can be made by selecting an object and then selecting the required set. {% hint style="info" %} Objects can belong to multiple sets allowing for quick programming and views to be achieved. Multiple objects can be assigned to a chosen set(s) by holding CMD whilst selecting objects. Atlas will display "Mixed" in sets where not all selected objects are members of that set. {% endhint %} *** ## Alias's Alias's allow for objects and groups to take on different names within the cue structure. They can be used when an object or group may be used for multiple sources that are patched throughout a performance allowing for easy identification within a given scene.

Show Settings - Objects showing Alias assignments

#### Creating an Alias Clicking on the "+" sign creates a new Alias within the window. Alias's can be renamed by double clicking on them. #### Deleting an Alias Right clicking on the selected alias and choosing "Delete Alias" will delete the alias. {% hint style="info" %} Each object can have multiple Alias's. As the alias is unique to an object multi select will deactivate the ability to add an alias. {% endhint %} # Groups Groups allow objects to be logically joined together and programmed. ***

Show Settings - Object Overview - Showing "Drum" group creation

### Creating a Group Selecting two or more objects will cause the "Make Group" button illuminate. To group those objects click the button. {% hint style="info" %} When a group is created an additional tab will be created within the object setup called ["Group Config"](/show-settings/objects/groups/group-configuration) {% endhint %} {% hint style="info" %} An object can only belong to one group within a session. {% endhint %} ### Adding additional objects to a group Additional objects can be added to an existing group by right-clicking on an object and selecting the group from the drop-down list that appears. ### Removing objects from a group Objects can be removed from a group by right-clicking on an object(s) and selecting "Remove from Group" ### Deleting a Group If all objects are removed from a group Atlas will prompt that removal of the last object will delete the selected group. Selecting "Delete Group" will remove the group from the workspace.

Show Settings - Object Overview warning of group deletion.

*** ### Functions Associated with Groups #### Make a Group Creates a group from selected objects # Group Configuration The group configuration window allows the parameters of children with object groups to be determined.

Show Settings - Group Configuration

### Creating the Group Layout By selecting the parent object in the upper window it is possible to define the the origin of control for a group of objects. By subsequently selecting the children within the group it is then possible to position them as desired using either the mouse or by typing offset values within the relevant numerical fields box. #### Spread and En-Space Offsets Spread and En-Space sends can have offsets attributed to them within the group. Entering a numerical value in the relevant field box will activate this offset. Values can be either in the positive or negative. {% hint style="info" %} A groups layout and parameters are stored as an offset. The spaces and backgrounds are provided to allow the user to position objects relative to a real location. This does not define the groups location onstage. {% endhint %} *** ### Update from Live Update from live allows parameters of objects to be taken from their live positions and recorded into the group configuration. #### Absolute Positions The positional information of the group object(s) will be captured and stored in the group config. This can be for an individual child with the group or all children. #### Relative to Group - Position Only The positional information of the groups object(s) will be captured and stored in the group config. This can be for an individual child within the group or all children. #### Relative to Group - Spread Only The spread information of the groups object(s) will be captured and stored in the group config. This can be for an individual child within the group or all children. #### Relative to Group - Position & Spread Both the positional and spread information of the groups object(s) will be captured and stored in the group config. This can be for an individual child within the group or all children. *** ### Centre Group in View Centre group in view realigns the group of objects to the centre of the currently displayed view. *** ### Reposition Objects & Group When selected, objects can be repositioned to allow placement within the current view. {% hint style="info" %} Repositioning can be useful for aligning objects with ground plans. {% endhint %} *** ### Adjust All Offsets Allows objects to be relocated around the origin of the group. All objects will expand or contract in linear scaled manner. *** ### Force Offsets Live Forcing offsets live will send the created group positions to the device(s) and make them live. # Park, Move-in-Mute & Live Moves This functionality provides powerful programming tools that enables Atlas to intelligently assist with object data management.

Show Settings - Object overview showing objects selected for Parking, Move-in-Mutes and Live Moves.

### Allow Parking, Move-in-mute and Live Moves. #### Parking #### Move-in-Mute #### Live Moves # Network All settings related to network integrations live within this tab
### OSC Profile Select the required profile for the spatial engine(s) you are using. {% hint style="info" %} Atlas currently supports the d\&b Audiotechnik DS100 Engine but support for other engines is in development. {% endhint %} *** ### Spatial Devices Spatial devices are the designation of devices Atlas will control with regards to the manipulation of objects. 3 spatial devices are always shown within the Devices Tab. For configuration see [Spatial Devices.](/show-settings/network/spatial-devices) ### External Devices External devices are the designation of devices Atlas can control with regards to triggering external actions. Examples include sound consoles, lighting desks and video servers. For configuration see [External Devices](/show-settings/network/external-devices). ### External Controllers External controllers are the designation of devices Atlas can synchronise with in order to provide spatial audio object control within sound consoles and other devices. For configuration see [External Controllers. ](/show-settings/network/external-controllers) ### # Spatial Devices Atlas communicates with Spatial Engines.

Show Settings - Spatial audio device A active

### Selecting a Spatial Device Profile Select the required spatial audio renderer from the dropdown menu. {% hint style="success" %} Atlas supports the following devices: * d\&b Audiotechnnik DS100 (Enscene/Enspace) * L'Acoustics L-ISA * Generic ADM {% endhint %} ### Output Format Select the required output format for your spatial engine. By default Atlas outputs metered data based upon the origin of the workspace. The user can also select to output scaled data based upon their defined space within Atlas. {% hint style="info" %} The output format will need to be selected relevant to the output format. Each Spatial Signal Engine has a different implementation. Please see individual chapters relating to each engine. {% endhint %} ### Enabling a Device {% hint style="success" %} By default Atlas always has Device A as enabled within the workspace. {% endhint %} Selecting the required device from the menu and checking "enable device x" will enable additional spatial engines for use within Atlas. ### Choosing device mode Select the required device from the menu and choose between "Expanded Input", "Expanded Output" or "Redundant" within the menu. When choosing redundant you can choose which other device the selected device is to act as a redundant engine for. {% hint style="info" %} Atlas will automatically send OSC to the correct spatial engines based upon settings here. In redundant mode OSC will be sent to all relevant devices. In expanded only relevant messages will be sent to each engine depending on the actions being executed. {% endhint %} ### Assigning Output Sets Atlas allows outputs to be assigned by sets. This allows control of the output levels and functions through friendly naming conventions. #### Auto Create & Assign from Function Groups Selecting this option will allow Atlas to auto create output sets based on the function groups within the d\&b Audiotechnik DS100 signal engine. *** ### Functions associated with devices. #### Interface Defines the network interface that Atlas will use to communicate with the selected external device. #### Address Defines the IP address of the device that is required to be controlled by Atlas. This takes the IPV4 notation. #### TX Port Defines the port number that Atlas will transmit OSC on for the selected device. #### RX Port Defines the port number that Atlas will receive OSC on for the selected device. #### Outputs A list of output names for the chosen device are displayed here. #### Function Groups A list of function groups for the chosen device are displayed here. {% hint style="info" %} Atlas can output to up to 5 network interfaces, IP Addresses and ports for a given External Device. Select the "+" button next to the port text field to add additional network interfaces per device. {% endhint %} # External Devices External Devices allow Atlas to communicate with the world using the OSC protocol.

Show Settings - Adding an external device for control

### Adding an External Device Clicking on the "+' in the left hand menu next to "External Devices" will create a new External Device within Atlas ### Enabled Selecting this option will enable the external device for use within Atlas. {% hint style="info" %} Atlas supports Wildcards and Iterations when addressing external devices. See Wildcards & Iterations for more information. {% endhint %} *** ### Functions Associated with External Devices #### Icon Clicking on the icon allows the assignment of an icon to represent the external device within the programmer. #### Name Allows the device to be given a name. #### Display in Toolbar Selecting this option displays the selected external device within the [toolbar. ](/main-overview/toolbar/external-devices) #### Include in Standby Selected Selecting this option allows Atlas to include the external device in standby-selected. #### Interface Defines the network interface that Atlas will use to communicate with the selected external device. #### Address Defines the IP address of the device that is required to be controlled by Atlas. This takes the IPV4 notation. #### Port Defines the port number that Atlas will transmit OSC on for the selected device. {% hint style="info" %} Atlas can output to up to 5 network interfaces, IP Addresses and ports for a given External Device. Select the "+" button next to the port text field to add additional network interfaces per device. {% endhint %} #### Default String Defines the default string presented for an external device when first added to the cuestack. #### Panic Defines the OSC string that Atlas will send to the external device when the Atlas workspace is panicked. Leaving blank means Atlas will send no command upon panic. #### Templates Atlas holds a list of predefined OSC Templates for manufacturers OSC integration. Selecting one of these templates will populate the OSC string with appropriate strings for the selected manufacturers device. {% hint style="info" %} If the device you want to require is not listed it is very easy to add your own control strings for your chosen hardware. "New Template" will allow you to add your own commands to the device. If there is a common device you'd like to see added to the "templates" please email us with a reference to those commands on {% endhint %} # External Controllers External controllers allow Atlas to integrate with control devices such as sound consoles.

Show Settings - External Controllers tab showing Digico SQ7T configuration

### Adding an External Controller Clicking on the "+' in the left hand menu next to "External Controllers" will create a new External Controller within Atlas ### Deleting an External Controller Clicking on the "Dustbin" logo in the top right will delete an External Controller from within Atlas. ### Enable Selecting this option will enable the External Controller for use within Atlas. {% hint style="success" %} Atlas will keep multiple console integrations in synchronisation. {% endhint %} *** ### Functions Associated with External Devices #### Name Allows the device to be given a name. #### Interface Defines the network interface that Atlas will use to communicate with the selected external device. #### Address Defines the IP address of the device that is required to be controlled by Atlas. This takes the IPV4 notation. #### Port Defines the port number that Atlas will transmit OSC on for the selected device. {% hint style="info" %} Atlas can output to up to 5 network interfaces, IP Addresses and ports for a given External Device. Select the "+" button next to the port text field to add additional network interfaces per device. {% endhint %} #### OSC Format Allows the OSC format to be selected for the given External Controller. More information can be found within the [OSC Dictionary.](/glossary/atlas-controls) #### Position Format #### Space ### Controller Mode Determines the mode in which the External Controller will operate. #### Control Only Control allows Atlas based control data to be transmitted and received. #### Control & All Object Parameters Allows Atlas based control data to be transmitted and received as well as **all** object parameter data relating to the Spatial Engine. #### Control & Specific Objects Allows Atlas based control data to be transmitted and received as well as **selected** object parameter data relating to the Spatial Engine. # Other This section contains integrations with other devices that interact with Atlas through providing the software with control data. ## Trackers # Trackers Atlas allows the user to configure how tracker technology interfaces within the software.

Show Settings - Tracker Config window showing assigned and patched trackers with active boundaries.

### Creating a Tracker Patch By clicking on the "Add Tracker Patch" Atlas will create a blank tracker patch within the window. To assign an incoming tracker ID to that patch enter the numerical identifier as defined within your chosen tracking hardware within the primary patch window. To assign an object to that tracker patch; click on "Add Object" and select the desired object to be controlled under that tracker assignment. It is possible to assign multiple objects to a given tracker facilitating the use of sharing trackers between different performers. A default boundary can be selected if desired; this will automatically apply to the tracker when inserted into the cue list. The chosen boundary can be changed within each cue should a different boundary be required. {% hint style="danger" %} Atlas will not permit the use of duplicate incoming patch ID's and will display the error message "Patch already in use" {% endhint %} {% hint style="info" %} Multiple objects can be assigned to a single tracker patch allowing for dynamic assignment within the show file. {% endhint %} ### Modifying a Tracker Patch ### Deleting a Tracker Patch Ensure that the patch is disabled. Selecting the waste-bin symbol next the patch will delete it. *** ### Functions Associated with Trackers {% hint style="info" %} #### Global Settings The Global Settings menu facilitates the global enablement/disablement and stabilisation/pass-through settings of all tracker patches. {% endhint %} #### Type This menu allows the selection of the required hardware integration. Currently it is only possible to select one manufacturer within a show file. #### Range Bound / Metered Atlas will accept either range bound or metered tracking information. #### Add Tracker Patch Facilitates the addition of a tracker patch into the show file. #### Enable Enables a tracker patch for use within Atlas. Unselecting will disable the patch. #### Primary Patch This determines the numerical ID from the incoming tracking data that Atlas will use. Support for a redundant/secondary tracker patch is in development. #### Add Object Facilitates the addition of object(s) to the tracker patch. #### Default Boundary A default boundary can be selected for an object when it is enabled for use with a tracker within the cuelist. This boundary can be changed on a cue level basis if required. {% hint style="info" %} If no boundaries have been defined then the only option that will appear is "none". {% endhint %} #### Passthrough / Stabliise Defines whether Atlas is passing tracking data through or using its internal stabilisation algorithm. #### # TiMax Tracker D4 Atlas supports incoming tracking data from TiMax Tracker D4. {% hint style="success" %} The OSC string that Atlas is expecting from Zaktracks Server is: /atlas/timax/object/\* {% endhint %} {% hint style="info" %} Detailed Timax D4 Setup information coming soon! {% endhint %} # ZacTracks SMART Atlas supports incoming tracking data from ZakTracks SMART. {% hint style="success" %} The OSC string that Atlas is expecting from Zaktracks Server is: /atlas/zactrack/tag/\* The Tag ID Is Usually the Fixture\_ID {% endhint %} {% hint style="info" %} Detailed ZacTracks Setup information coming soon! - In the meantime if you need assistance we have a PDF Manual for setting up ZacTracks with Atlas we can share with you. {% endhint %} # NaoStage Atlas supports incoming tracking data from ZakTracks SMART. {% hint style="warning" %} BETA VERSION {% endhint %} {% hint style="success" %} The OSC string that Atlas is expecting from Naostage Server is: /atlas/naostage/id/\* {% endhint %} In Kratos it is necessary to patch Atlas. Navigate to the "actions tab" * Create a new module of type "OSC" and name your custom module. ("Atlas" is recommended) * Assign the IP of your Atlas machine as the "Output IP" * Assign the the "Output Port" as 5060
* Create a New Action Group and name "Atlas" * Create a New Action for your object of type: "Send a targets position using OSC" * Customise your action labelled: "Send position to Atlas" * Select the box "Send X & Y Co-Ordinates" and enter the Atlas string "/atlas/naostage/id/\*" * Repeat the above step for each ID replacing \* with the numerical ID of the object to be sent.
* Ensure Enable Action, Enable Action Group and Enable Module are all selected. # Spaces

Atlas Spaces Overview

{% hint style="info" %} Use the slider at the bottom of the Spaces tab to adjust the viewing size of your space. {% endhint %} ### Adding a Space See ["Import from File"](/show-settings/spaces/import-from-file-ds100-mode) ### Deleting a Space Highlight the required space and select "Delete Space" Alternatively right-click on the required space and select "Delete Space" from the pop-up menu. {% hint style="danger" %} The default space has to exist within Atlas and cannot be deleted. {% endhint %} *** ### Functions associated with spaces #### Default Space When first opening Atlas the user is presented with a "Default Space". This cannot be deleted by can be updated with relevant data to reflect the users mapping plane. #### Units Allows for the user to switch between metric and imperial measurements. #### Colour Allows for the boundaries of the mapping plane to have a colour applied. #### New Background Clicking on the image icon allows for background images to be assigned to spaces. Each space can have multiple images. These are recallable on a cue by cue basis and selectable independently in the overview. #### Name Allows the background image to be named. #### Grids Images can be overlaid with 1m and 5m grids, a crosshair and quad divisions to aid alignment of images. #### Invert Colour Inverts the colour of the selected image. This can be useful for modifying an image between dark and light modes when responding to the environment. (ie: in daylight or inside a dark room) #### Image Scale Allows selected image to be scaled to match the mapping planes parameters. #### Opacity Allows selected images opacity to be varied. # Import from File - DS100 Mode Atlas has the ability to import objects, spaces and function group information from within your completed d\&b R1 File. ## Spaces {% hint style="info" %} Atlas will show the given co-ordinate points for the spaces as shown in your R1 file. {% endhint %} ### Import from File Atlas allows the user to import the positioning plane information from the d\&b R1 file.

Import from File Overview

### Assign Space Allows the user to assign the default mapping plane from the d\&b R1 File. The user can select between either "Points Only", "Name & Points" or "All" ### New Space Allows the user to add spaces to the Atlas workspace. *** ## Objects ### Importing Objects Click on the required objects will select them for import into Atlas. Cmd-Click will allow for multiple objects to be selected or import. Cmd-A will select all objects for import. Once selection is made click on "Import x Objects" to bring those into the Atlas workspace. {% hint style="info" %} Only objects that are selected for En-Scene mode within the R1 file will show as available objects to import into Atlas. {% endhint %} *** ## Outputs & Function Groups ### Assigning Spatial Engines Atlas will display all available spatial engines presented within the R1 file. By selecting from the dropdown each spatial engine in the R1 file can be mapped to an available device within Atlas. # Background Images Background images allow users to view their workspaces in a friendly and relatable manner. {% hint style="info" %} The yellow cross hair denotes the origin of the workspace for assistance when aligning images. {% endhint %} ### Importing a New Background Image It is permissible to select multiple background images for use within the programmer and overview screens. To insert a new background image within a space click on the photo icon next to the space and a new background will appear. It is then possible to drag an image file onto the space. {% hint style="info" %} Use the slider at the bottom of the Spaces tab to change the zoom within your space. {% endhint %}

Show Settings - Spaces showing assignment of an image into Atlas

### Deleting a Background Image Highlight the required background image and right-click. Choose "Delete Background". ### Replacing Background Images Highlight the required background image and right-click. Choose "Use background for all cues associated with this Space" {% hint style="success" %} Images have a maximum size of 5mb. Images larger than 5mb will be automatically compressed by Atlas. {% endhint %} *** ### Functions associated with Background Images #### New Background Clicking on the image icon allows for background images to be assigned to spaces. Each space can have multiple images. These are recallable on a cue by cue basis and selectable independently in the overview. #### Name Allows the background image to be named. #### Grids Images can be overlaid with 1m and 5m grids, a crosshair and quad divisions to aid alignment of images. #### Invert Colour Inverts the colour of the selected image. This can be useful for modifying an image between dark and light modes when responding to the environment. (ie: in daylight or inside a dark room) #### Image Scale Allows selected image to be scaled to match the mapping planes parameters. #### Opacity Allows selected images opacity to be varied. #### Show Speakers Shows and hides the loudspeakers if imported. #### Fill Speakers Adds a solid fill to the loudspeaker icons. # Boundaries Atlas allows the user to define boundaries when using performance tracking technologies. These can be used to bind objects within defined spaces in performance.

Show Settings - User defined boundary drawn.

### Creating a Boundary By clicking on the + button in the top left of the window Atlas will create a new boundary. Clicking within the spaces view will allow the creation of points to define the perimeter of the boundary. As points are selected the interior of the boundary will be shown with the default opacity level. As points are created they are shown at the bottom of this window. Individual points can be deleted by clicking on the "x" next to the relevant point. "Remove All" will delete all the given points for the chosen boundary but will not delete the boundary itself. {% hint style="info" %} Whilst there is no limitation on the shape or number of points determining a boundary it is advisable to consider the effect of a given boundary on a tracked object. Regular shapes defining playing spaces may offer better results depending on the spatial audio processors operational mode. {% endhint %} ### Deleting a Boundary Selecting a boundary within the boundary list and right clicking on the boundary will present the "Delete Boundary" option to the user. *** ### Functions associated with Boundaries #### Boundary Name Boundaries can be assigned a name for the purposes of identification within the programmer. #### Space The space selector can be used to determine the space and background image within which a boundary is to be drawn. #### Set to size of space By selecting this option Atlas will draw a boundary that conforms to the size of the space. This can be useful if wishing to bind trackers to a stage area as defined within the overall project. #### Background Opacity This slider allows the opacity of the boundaries fill to be adjusted. Moving the slider to the right will reduce the opacity and provide a solid fill colour. #### Colour Each boundary can be defined by a chosen colour. This choice effects both the boundary line and fill colour. # Triggers The triggers tab allows the user to specify the external triggers to be used with Atlas. ### # Keyboard Atlas supports a number of standard keyboard shortcuts. #### Assigning a Keyboard Shortcut Clicking on "x" within a given shortcut will allow a new defined keyboard shortcut to be selected. Atlas will accept the next keyboard input as the accepted shortcut. #### Removing a Keyboard Shortcut Click on the "x" within a given shortcut and then clicking outside of the text field will leave the message "record shortcut". The given keyboard shortcut will then be made inactive whilst in this state. #### Resetting to Defaults Clicking on "Reset to Defaults" will reassign all keyboard shortcuts to Atlas's default shortcuts. {% hint style="warning" %} Keyboard shortcuts are only applied when the "Show Settings" window is closed. {% endhint %}

Show Settings - Triggers showing default keyboard assignments

# OSC Atlas has an extensive OSC library allowing its integration into many workflows. {% hint style="success" %} You can find a full list of Atlas's OSC library in the [OSC Glossary.](/glossary/atlas-controls/osc-library) {% endhint %} {% hint style="info" %} Atlas is fixed to listening to incoming OSC on port 5050. {% endhint %} #### Assigning a Debounce Time Atlas has the ability to ignore OSC commands that occur within a given timeframe. By entering a time in this window Atlas will not respond to the same command within that time. By default this setting is 0.20 seconds. #### Allow OSC to move playhead Selecting this option will allow external OSC commands to move the playhead within the workspace. #### Custom OSC Trigger Atlas can be triggered via a custom OSC Trigger message. To assign a custom string to trigger Atlas's cuestack enter the necessary string within this window. {% hint style="info" %} An example where the custom OSC Trigger can be used includes the triggering of Atlas scene for scene alongside a sound console. By creating matching scene numbers in Atlas to coincide with the console Atlas will seamlessly mirror the console scene structure. {% endhint %} ### Atlas Trigger Output Atlas can output a specific OSC command when it is triggered. You can sepecify the IP address and port here.

Show Settings - Triggers showing OSC settings within Atlas

# Midi Atlas supports midi for the purposes of triggering the cuelist only. Atlas will display a list of all available midi interfaces at the top of the window. #### Allow External Midi Control Selecting this box allows Atlas to respond to incoming midi for the purposes of cuestack control. #### Assigning a Midi Command to a Trigger Selecting "Capture" will place Atlas in a listening state. The next incoming midi command received by the computer will be assigned to the trigger. #### Removing a Midi Command from a Trigger Selecting "Remove" will delete the command associated with the selected trigger.

Show Settings - Triggers - Midi

# Timecode Atlas supports MTC as a method of triggering the cuestack. {% hint style="info" %} To assign cues to a timecode selection please see: [cuelist](/main-overview/cuelist) {% endhint %}

Show Settings - Timecode window showing options

### Enable Timecode Selecting this option will allow Atlas to be triggered via incoming Midi Timecode. Atlas supports these timecode standards. ### Allow Timecode to move playhead Selecting this option will allow incoming timecode to progress the playhead within the cue list. {% hint style="info" %} This option can be useful for shows using both operator and musically fired cues. The operator can progress the playhead locally for cues outside of timecode. {% endhint %} ### Timecode Frame Rate Select the desired timecode frame rate from the dropdown menu. Common formats are listed in the initial menu; a full list is available on the sub menu. {% hint style="danger" %} If opening an existing show file or switching between timecode formats Atlas may display the error: "Malformed Timecode". This error informs the user that the programmed format needs attention in order to preserve the show. {% endhint %} ### Clamp all cues to a valid Timecode Selecting this button will clamp all invalid timecode cues to the nearest value for the selected frame rate. # d\&b Audiotechnik DS100(M) Signal Engine The following details the settings required to enable Atlas to communicate with d\&b DS100 and DS100M. It is not considered to be an instruction manual on how to use DS100. ## Single Engine / Redundant Application ## Expanded Output (64 input / 128 output) ## Expanded Input (128 input / 64 output) # L'Acoustics L-ISA The following details the settings required to enable Atlas to communicate with L'Acoustics L-ISA controller. It is not considered to be an instruction manual on how to use L-ISA. {% hint style="info" %} The following instructions were written with L-ISA Controller version 3.2.0.12417 {% endhint %} ## Atlas Settings ### Assigning Atlas to work with L'Acoustics L-ISA Controller Follow the device assignment procedure as defined within [network/device settings](/show-settings/network) to assign Atlas to control L-ISA (Polar). ### Assigning the Co-Ordinate Space {% hint style="info" %} By enabling L-ISA mode within Atlas a Polar Co-Ordinate space will be visible over your Atlas Space. {% endhint %} Atlas can output the co-ordinate space into a defined polar space in order to translate Cartesian values into Polar ones. In "system settings/spaces" create the mapping space in which you wish to output within. {% hint style="info" %} If your space incorporates 360 degrees of movement your polar space will need to encapsulate the listener and the entire Cartesian playing space. {% endhint %}

Atlas - System Settings - Spaces - L-ISA Polar View

{% hint style="success" %} In the example above we can see that our existing example stage and the entire room are encapsulated within our L-ISA view. {% endhint %}

System Settings - Devices - L-ISA - L-ISA Output Space Selected

## L-ISA OSC Settings The following settings are required to be implemented in order for Atlas to connect to L'Acoustics L-ISA Controller.

L-ISA OSC Settings Window

# Generic ADM The following details show how Atlas integrates into the generic ADM protocol. {% hint style="info" %} You can find out all about generic ADM on the [GitBook Page.](https://immersive-audio-live.github.io/ADM-OSC/) {% endhint %} # Yamaha AFC (Beta) The following details the settings required to enable Atlas to communicate with Yamaha AFC on DME7 and DME10. It is not considered to be an instruction manual on how to use AFC Controller. Coming soon.... # Timax SoundHub The following details the settings required to enable Atlas to communicate with Timax SoundHub. It is not considered to be an instruction manual on how to use Timax SoundHub. Coming soon... # Cuelist The Cuelist allows programmed actions to be replayed within Atlas. These can be triggered locally, via timecode or OSC.

Atlas Window showing cuelist active on the far left.

### New Cue To create a new cue in Atlas select the new cue button or use (shortcut 0) Cue numbers, titles and cue durations can be edited by double clicking on the relevant text and entering the desired value. When enabled for timecode Atlas will display the timecode trigger time for the cue in the format: xx:xx:xx:xx {% hint style="warning" %} Atlas will allow multiple cues to adopt the same cue number. If triggered locally from the cuestack each cue will run independently. If triggered remotely via OSC any cues with the same identifying number will trigger simultaneously. {% endhint %} ### Changing Cue Duration (Global) Changing the cue duration will affect the duration of all modules within the programmer for that selected cue. Atlas will produce the following warning in this scenario:
### New Marker To create a new marker click on the "New Marker" button. Atlas will insert a marker below the selected cue. {% hint style="info" %} Markers do not interrupt the flow of the cuestack and serve to provide information to the programmer/operator only. {% endhint %} ### Search Search allows users to locate external device values within the cuelist as well as showing all executable triggers within one window.

Atlas Window - Showing the cuelist search function

*** ### Cuelist Inspector #### Cue Enables the cue to be given a name. #### Notes Each cue has a free text field where notes relating to the cue can be typed. These are displayed at the top of the window next to the cue number. #### No Defines the number of the cue. #### Duration Defines the global duration of the cue. #### Timecode Defines the time of the timecode tigger (if enabled). {% hint style="info" %} The currently selected timecode format will be displayed next to this window. {% endhint %} #### Trigger Selecting this option will enabled MTC triggers for the selected cue. #### Space Selects the space/image for the given cue allowing the user to program within that given view. #### Colour A colour can be assigned to the cue within the cuelist. #### Ignore Allows the cue to be ignored from the cuelist. *** ### Right-Click on cue

Cuelist - Rightclick on cue.

#### Delete Cue with "x" modules Selecting this action will delete the selected cue. Atlas will warn how many programming modules are inside that cue and therefore about to be deleted. #### Fold All Modules Selecting this action will cause all object modules within the programmer to close showing just the headers for the programmed actions. #### Unfold All Modules Selecting this action will cause all object modules within the programmer to open showing all programming actions. {% hint style="info" %} Individual modules can be opened and closed using the downwards arrow icon on the object header. {% endhint %} #### Set [Operators Cuelist](/main-overview/operators-cuelist) to this cue Selecting this assigns the playhead on the Operators Cuelist to the currently selected cue. #### Ignore Cue Ignoring a cue in Atlas causes the software to behave as if the cue doesn't exist. All warnings associated with ["Park, Move-in-mute & Live Moves"](/show-settings/objects/park-move-in-mute-and-live-moves) will be reassigned to cues either side of the ignored cue. The playhead will progress directly over the ignored cue and proceed as though the cue does not exist within the cuelist. #### Update Object References from Previous Cue When using ["Park, Move-in-Mute & Live Moves"](/show-settings/objects/park-move-in-mute-and-live-moves) selecting this option will assign referenced objects from the previous cue to the selected cue. #### Check for Errors Selecting this will refresh all cue references within the cuelist looking for errors relating to ["Park, Move-in-Mute & Live Moves"](/show-settings/objects/park-move-in-mute-and-live-moves) *** ### Functions associated with Cuelist #### Cue Number Atlas allows users to allocate a cue number to a cue for identification purposes. #### Cue Title Cues can be assigned a title for identification purposes #### Cue Duration Atlas will display the cue duration as the longest module action active within it. #### Markers Markers allow users to insert instructions and identifiers without distrupting the flow of the playhead. #### Timecode Trigger Time If enabled, timecode trigger times will be displayed within the cuelist. # Programmer The Programmer allows users to choreograph their sequences for playback within Atlas. ### Programmer Actions ### Adding an object(s) or group of objects to the programmer [See Module Selector](/main-overview/programmer/module-selector) ### Adding a Palette to the programmer [See Palettes](/main-overview/programmer/palettes) ### Adding External Control for a device to the programmer [See External Devices. ](/show-settings/network/external-devices) #### *** ### Object Module Right-Click

Atlas Programmer - Showing right-click on a position module for a chosen object.

#### Solo "Object" Solo allows the user to highlight a given object or object group for easy identification within the overview. Clicking on the solo icon a second time will release the solo function. {% hint style="warning" %} This is a visual functionality and does not effect audio output. {% endhint %} #### Anchor Start to Last Location Anchoring allows the user to acknowledge and accept the presence of situations where a live move would occur under normal programming. By anchoring the object any flags associated with programming errors will be removed. {% hint style="info" %} Anchoring is only applicable to objects that are enabled for[ Park, Move-in-Mute & Live Moves. ](/show-settings/objects/park-move-in-mute-and-live-moves) {% endhint %} #### Ignore Ignoring a cue in Atlas causes the software to behave as if the cue doesn't exist. All warnings associated with ["Park, Move-in-mute & Live Moves"](/show-settings/objects/park-move-in-mute-and-live-moves) will be reassigned to modules either side of the ignored module(s). #### Rename Enables the selected module to be renamed for the purposes of identification within a sequence. #### Fold All Selecting this action will cause all object modules within the programmer to close showing just the headers for the programmed actions. #### Unfold All Selecting this action will cause all object modules within the programmer to open showing all programming actions. {% hint style="info" %} Individual modules can be opened and closed using the (downwards arrow icon) on the object header. {% endhint %} #### Select All "Module Type" Selecting this action will select and highlight all modules of the selected type within the selected cue. #### Select All "Module Type" for Selected Object Selecting this action will select and highlight all modules of the selected type for the chosen object within the selected cue. #### Remove Module Selecting this action will delete the selected module. {% hint style="warning" %} By removing the last module associated with an object Atlas will automatically remove that object from the selected cue. {% endhint %} *** ### Object Header Right-Click

Atlas Programmer - Showing right-click on a header for a chosen object.

#### Solo "Object" Solo allows the user to highlight a given object or object group for easy identification within the overview. Clicking on the solo icon a second time will release the solo function. {% hint style="warning" %} This is a visual functionality and does not effect audio output. {% endhint %} #### Anchor Start to Last Location Anchoring allows the user to acknowledge and accept the presence of situations where a live move would occur under normal programming. By anchoring the object any flags associated with programming errors will be removed. {% hint style="info" %} Anchoring is only applicable to objects that are enabled for[ Park, Move-in-Mute & Live Moves. ](/show-settings/objects/park-move-in-mute-and-live-moves) {% endhint %} #### Ignore Ignoring a cue in Atlas causes the software to behave as if the cue doesn't exist. All warnings associated with ["Park, Move-in-mute & Live Moves"](/show-settings/objects/park-move-in-mute-and-live-moves) will be reassigned to modules either side of the ignored module(s). #### Fold "Chosen Object" #### Fold All Selecting this action will cause all object modules within the programmer to close showing just the headers for the programmed actions. #### Unfold All Selecting this action will cause all object modules within the programmer to open showing all programming actions. {% hint style="info" %} Individual modules can be opened and closed using the (downwards arrow icon) on the object header. {% endhint %} #### Select All "Module Type" Selecting this action will select and highlight all modules of the selected type within the selected cue. #### Select All "Module Type" for Selected Object Selecting this action will select and highlight all modules of the selected type for the chosen object within the selected cue. #### Remove Module Selecting this action will delete the selected module. {% hint style="warning" %} By removing the last module associated with an object Atlas will automatically remove that object from the selected cue. {% endhint %} # Module Selector The module selector allows users to quickly select objects for programming actions.

Programmer - Module Selector open showing objects to be inserted into the cue

### Accessing the module selector The module selector is access by clicking on the + symbol at the top of the programmer. {% hint style="success" %} Objects can be filtered by sets or by a given search term to allow easy selection. {% endhint %} ### Selecting objects to create a programming action. Clicking on an object will select it for insertion into the programmer. Multiple items can be selected in this way and inserted at the same time. {% hint style="info" %} To deselect an item simply click on it again. {% endhint %} Select whether you wish to take default values or live values for the chosen function. Click on the required function module to insert relevant programming actions. *** ### Functions Associated with module Inspector #### Journey Module The journey module allows an object to be assigned a movement action within the programmer. Variables that can be assigned are chosen within the Object Properties Inspector. #### Spread Module The spread module allows an objects spread value to be modified within the programmer. #### Shape Module The shape generator allows an object to be moved within given parameters as defined within [the shape generator.](broken://pages/3fKjkLisNypxQ1AcWK2d) #### Reference Module The reference module allows an object to be assigned as onstage when using ["Park, Move-in-Mute & ](/show-settings/objects/park-move-in-mute-and-live-moves)[Live Moves. ](/show-settings/objects/park-move-in-mute-and-live-moves) # Palettes Actions associated with palettes within the programming inspector. {% hint style="info" %} For more information on external devices and their usage please see [Palettes. ](/main-overview/atlas-button/palette-editor) {% endhint %}

Programmer - Palette module showing the addition of a palette into a cue with menu open.

### Adding a palette to a cue Clicking on the palette icon in the programmer will insert a palette cue. ### Choosing a palette Within the inspector a drop down menu displays all available palettes created by the user. ### Choosing a palette preset Within the inspector a drop down menu displays all presets associated with the selected palette. {% hint style="info" %} Palettes are referenced throughout the cue list. Changing a preset at show settings level will then reflect throughout the show file. {% endhint %} *** ### Functions Associated with Palettes #### Prewait Prewait defines the amount of time the given module will wait before starting. {% hint style="success" %} Atlas will automatically assign a pre-wait time equal to the total duration time of all previous modules of the same type associated with an object. {% endhint %} #### Duration Duration defines the amount of time over which the selected action will occur. #### Ignore Allows the selected programming action to be ignored within the programmer. # External Devices Actions associated with external devices within the programming inspector.

Progammer - Showing inserted External Device module for EOS.

{% hint style="success" %} To assign multiple external device triggers in a sequence this can be accomplished using the [cue-matrix. ](/main-overview/atlas-button/cue-matrix) {% endhint %} {% hint style="info" %} For information on the setup of external devices and their usage please see E[xternal Devices](/show-settings/network/external-devices) {% endhint %} ### Adding a palette to a cue Clicking on the palette icon in the programmer will insert a palette cue. ### Choosing a palette Within the inspector a drop down menu displays all available palettes created by the user. ### Choosing a palette preset Within the inspector a drop down menu displays all presets associated with the selected palette. {% hint style="info" %} Palettes are referenced throughout the cue list. Changing a preset at show settings level will then reflect throughout the show file. {% endhint %} *** ### Functions associated with External Devices #### Prewait Prewait defines the amount of time the given module will wait before starting. {% hint style="success" %} Atlas will automatically assign a pre-wait time equal to the total duration time of all previous modules of the same type associated with an object. {% endhint %} #### Duration Duration defines the amount of time over which the selected action will occur. #### Ignore Allows the selected programming action to be ignored within the programmer. # Object Properties Inspector Displays the currently selected programming modules parameters. {% hint style="warning" %} The Object Properties Inspector changes depending on the module selected. If no module is selected within the cuelist then the [Cuelist Inspector ](/main-overview/cuelist#cuelist-inspector)will be shown. {% endhint %} ### Position Module The [Position Module](/main-overview/programmer/object-properties-inspector/position-module) allows objects positions to change ### Spread Module The [Spread Module](/main-overview/programmer/object-properties-inspector/spread-module) allows an objects spread to change ### Shape Module The [Shape Module ](/main-overview/programmer/object-properties-inspector/shape-module)allows objects to be controlled by Atlas's Shape Generator ### Reference Module The [Reference Module](/main-overview/programmer/object-properties-inspector/reference-module) allows Atlas to maintain an objects relevance to being onstage when using [Park, Move-in-Mute and Live Moves. ](/show-settings/objects/park-move-in-mute-and-live-moves) # Position Module This module allows objects to be moved within the programmer. Single points, custom journeys and trackers are all available options.

Atlas Window - Showing an object module with static positon.

### Creating an action for an object Using the [Module Selector](/main-overview/programmer/module-selector) - Select an object, objects or group for which you wish to create a positional change. Clicking at a single location will create a single point movement without an associated journey. By clicking and holding the left mouse button it is possible to draw a custom journey for the given object.

Programmer - Position module showing custom journey.

{% hint style="info" %} The slower the user draws the journey the more editable points that will be created along the pathway. {% endhint %} {% hint style="info" %} Holding down Option whilst drawing will create a straight line between two points. {% endhint %} {% hint style="info" %} Holding down Cmd and clicking inside the programmer window will allow an existing journey to be relcoated within the workspace without the need to redraw. {% endhint %} *** ### Use Tracker Selecting this option activates a tracker for the given object. {% hint style="info" %} For full tracker implementation see [Trackers.](/show-settings/network/other/trackers) {% endhint %} #### Patch Allows the allocation of a tracker patch to an object within the cue. Available options are shown within the dropdown menu. {% hint style="warning" %} This option will only show when an object is patched to more than one tracker within the show settings. This allows for objects to change their tracker allocation within the show. {% endhint %} #### Axis Allows the selection of the active tracking axis. Tracking can be allowed within the XY, X-Only and Y-Only axis. To assign a manual value to either X or Y select an object position within the overview prior to selecting the chosen restriction. #### Boundary Allows the selection of a tracking boundary to be activated within the given cue. #### Completion Allows for the action of the tracker to be defined once the cue has completed over its duration. Disable Tracker This option turns the tracker off at the end of the duration of the selected cue. Leave Active This option leaves the tracker active and tracking based upon the parameters selected within the cue. Disable and Move-in-Mute This option will turn off the tracker and allow Atlas to move the object automatically as part of Move-In-Mute. Catch This option allows Atlas to catch the selected tracker and then turn off the tracking. When selected a green boundary is activated that can be adjusted in width with the slider. When the tracked object enters this area Atlas will perform the catch. *** ### Functions associated with Position Modules #### Prewait Prewait defines the amount of time the given module will wait before starting. {% hint style="success" %} Atlas will automatically assign a pre-wait time equal to the total duration time of all previous modules of the same type associated with an object. {% endhint %} #### Duration Duration defines the amount of time over which the selected action will occur. #### Ignore Allows the selected programming action to be ignored within the programmer. #### Palette Allows the selected object to reference a location palette to take its position from. {% hint style="info" %} By using a position palette you can easily update the position across multiple objects and cues by editing the [palette position. ](/main-overview/atlas-button/palette-editor#palettes) {% endhint %} #### From From allows the user to update the position within the programmer from another objects position within the programmer or from a live position within the overview window. # Spread Module This module allows an objects spread/width to be adjusted within the programmer.

Programmer - Spead module inserted into the programmer for Character 1

*** ### Functions associated with Spread Module #### Prewait Prewait defines the amount of time the given module will wait before starting. {% hint style="success" %} Atlas will automatically assign a pre-wait time equal to the total duration time of all previous modules of the same type associated with an object. {% endhint %} #### Duration Duration defines the amount of time over which the selected action will occur. #### Ignore Allows the selected programming action to be ignored within the programmer. #### Spread Allows the spread value of the object to be changed within the programmer. Permissible options are: * Entering a single value * Entering an fade from one absolute value to another absolute value. * Entering a fade from the current live value to another absolute value. # Shape Module This module allows objects to be moved within predefined shape patterns within the programmer.

Programmer - Shape Module showing offset object allignment

*** ### Functions associated with Shape Module\` #### Prewait Prewait defines the amount of time the given module will wait before starting. {% hint style="success" %} Atlas will automatically assign a pre-wait time equal to the total duration time of all previous modules of the same type associated with an object. {% endhint %} #### Duration Duration defines the amount of time over which the selected action will occur. #### Ignore Allows the selected programming action to be ignored within the programmer. #### Shape Allows the user to select the required shape action for the object. As of 1.2.2 a circle and straight line are currently available. #### Repeat Allows the shape to repeat forever or a custom number of times before stopping. #### Autoreverese Allows the shape to autoreverse from its start point to end point within the repeat duration. #### Offset (circle only) Allows the start/end point of the circular shape to be defined within degrees. # Reference Module This module allows objects to be referenced as still onstage within the programmer and allows Atlas to know that it is still relevant to the show.

Programmer - Objects referenced within the programmer displayed.

There are no editable functions associated with the reference module. {% hint style="danger" %} Referencing is a core concept of Atlas when using Park, Move-in-Mute and Live Moves. It allows the software to maintain objects within the playing space when no absolute action is associated with them within the given cue. Objects that are not correctly programmed will exhibit undesirable behaviour when not referenced. {% endhint %} # Overview Window The overview window(s) shows the position and parameters of objects within the system.
{% hint style="info" %} Users can view the overview window inside the main workspace by clicking on the folded map symbol at the top right of the programmer. {% endhint %} #### Space Within this drop down users can select which "space" and any background images associated with it as setup within the ["spaces settings"](/show-settings/spaces) #### Overview - Simulated When working offline Atlas will display "Overview - Simulated" when looking at the overview window. In this mode Atlas can be used to program your spatial audio show without the necessity to connect to a device. #### Overview - Live When connected to a spatial audio engine the overview window will display "Overview - Live". In this mode Atlas will display realtime data returned from the spatial audio engine confirming the accuracy of the data and ensuring synchronisation for the user. It is possible to select which spatial audio engine you are receiving data from by clicking on the relevant button within the [toolbar. ](/main-overview/toolbar#spatial-audio-engine-indicator) ### External Overview Window

Atlas Exploded Overview Window

# Overview Actions The overview window in Atlas provides the user with useful realtime functionality. These actions exist in both the captive overview and external overview window.

Overview Window - External window showing action buttons top right.

#### ![](https://4121747729-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmSmRU0BtlSOhG2HtpJOR%2Fuploads%2F75riTq8lZnswZ6mUpPfh%2FSolo.jpeg?alt=media\&token=076c209e-8df6-4487-815e-e60cb877b8cf) Solo Solo allows the user to highlight a given object or object group for easy identification within the overview. Clicking on the solo icon a second time will release the solo function. {% hint style="warning" %} This is a visual functionality and does not effect audio output. {% endhint %} #### Disable Trackers Disable Trackers allows the user to disable all, or a selected object, that is currently under tracker control within the cuelist. #### ![](https://4121747729-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmSmRU0BtlSOhG2HtpJOR%2Fuploads%2FKb9jgAm1Fjj0Q9XLmou2%2FBoundaries.jpeg?alt=media\&token=1b2d025e-d2b5-4560-b73e-070596142e49) Show / Hide Active Boundaries This function toggles between showing any active tracking boundaries on the overview within the current cue #### ![](https://4121747729-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmSmRU0BtlSOhG2HtpJOR%2Fuploads%2FlCQmWiSv43mV9IsIitKs%2FResync.jpeg?alt=media\&token=be280197-6a38-431d-9619-91515330fc1c) Re-Sync from Device Re-Sync requests all the current data from the spatial audio processor. When connecting external controllers and devices to Atlas it is recommended to perform this action to sync all devices within the control network. #### ![](https://4121747729-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmSmRU0BtlSOhG2HtpJOR%2Fuploads%2FpWN1RNci4Q1pZZJmNRIb%2FLayers.jpeg?alt=media\&token=23db80e0-ec93-486f-8c49-76aec708b5a1) Bring to Front Bring to front will locate the chosen object to the top layer of the overview. When objects overlap this function can be used to allow control of the chosen object in the overview. #### [Object Overview](/main-overview/overview-window/object-overview) By clicking on an object or object group icon within the overview window a menu will appear at the bottom of the window. Within this window the user can change realtime parameters of the selected object. Available parameters include object spread, mode, en-space send and the ability to "Lock" an object. #### Object Lock In the overview window the action of locking an object will prevent any cuelist action or external controller from moving or changing parameters related to that object. Manipulation of parameters are still permissible directly from the overview window only. A locked object will display a padlock symbol next to the object in the overview. # Object Overview The Object Overview allows users to determine the realtime values of objects alongside making quick realtime changes to objects parameters.
{% hint style="warning" %} All actions within this window are affecting the realtime parameters of the selected objects. {% endhint %} ### Activating Object Overview in Overview Window Clicking on an object in the overview window will activate the Object Overview display to appear. ### Functions associated with the Object Overview #### Locked Selecting this box will lock the selected object or object group. The cue list and external controllers will not allow any changes to be made to the selected object whilst the object is locked. Manual changes are permissible from the overview window (such as repositioning or changing spread) Unselecting this box will allow the controllers and cue list to take control over the object and resume programmed actions. {% hint style="info" %} Objects can be locked via OSC control allowing macros and other controllers such as Streamdeck to provide easy user control. {% endhint %} *** {% hint style="success" %} #### Other functions All other functions are covered elsewhere within the documentation and relate to object parameters as outlined. {% endhint %} # Toolbar
#### OSC Output Indicator #### Spatial Audio Engine Indicator #### Global OSC Input / Output Controls #### Incoming Timecode Display #### Global Timecode Control #### # Spatial Audio Devices Spatial audio engines are at the heart of Atlas's show control.

Atlas Window - Showing Spatial Engine A online and Spatial Engine B offline

#### OSC Transmit Indicator This indicator will flash green when Atlas is transmitting OSC to the Spatial Engines. {% hint style="danger" %} Atlas requires a [license](/installation-licensing-and-requirements/licensing) to output OSC {% endhint %} #### Device Status The status of Spatial Audio Devices is displayed within the bottom toolbar. {% hint style="warning" %} Devices will only display within the toolbar if they are enabled within [devices.](/show-settings/network/spatial-devices) {% endhint %} #### Yellow Boundary When Atlas is connected and online with a spatial audio device the yellow boundary around a devices' status indicator determines which device Atlas is communicating with to display its "live overview" in online mode. Each device present can be selected to confirm communication from the device. #### Disconnected When working offline the status of these will display as "Disconnected" and display the background colour of the device as red. #### Connected When a valid spatial audio devices is present the relevant window will display "Connected" and display the background colour of the device as green. Currently a maximum of 3 devices is supported. #### Disabled When OSC output is disabled for a spatial audio device a banner "disabled" is displayed across the device. No OSC output will be present. This function can also be controlled via OSC [(OSC Library)](/glossary/atlas-controls) {% hint style="danger" %} Atlas will not output OSC if it is not connected to at least one device. {% endhint %} # External Devices

Atlas Window - Showing 2 external devices with ETC EOS being temporarily disabled from outputting OSC

#### External Devices External devices can be enabled / disabled per device in the toolbar. A red boundary around a device indicates the device is disabled. This function can also be controlled via OSC [(OSC Library)](/glossary/atlas-controls) {% hint style="danger" %} Atlas requires a [license](/installation-licensing-and-requirements/licensing) to output OSC {% endhint %} # External Controllers When enabled the status of external controllers are displayed here.
External devices will appear automatically in the toolbar when added within the ["Network Settings"](/show-settings/network#external-controllers) #### OSC Receive/Transmit Indicator These indicators will flash green when Atlas is receiving and transmitting OSC. {% hint style="danger" %} Atlas requires a [license](/installation-licensing-and-requirements/licensing) to output OSC {% endhint %} # Timecode Devices

Atlas Window - Incoming timecode displayed and enabled

#### Timecode Display Displays incoming timecode in the format --:--:--:-- #### Timecode Enable/Disable Allows for incoming timecode to be globally enabled/disabled as a trigger within the Atlas workspace. This function can also be controlled via OSC [(OSC Library)](/glossary/atlas-controls) # Edit / Perform Perform mode changes Atlas window to display playback functions only.

Atlas Window - Showing Perform mode with cue list and overview on display.

#### Edit Mode Allows users to edit the performance space and make changes to all attributes within the workspace. #### Perform Mode Removes the module editor from the main workspace and prevents changes being made within the programmer. {% hint style="success" %} In performance mode it is still possible to have the [cue-matrix](/main-overview/atlas-button/cue-matrix) and [palette](/main-overview/atlas-button/palette-editor/palettes) window open allowing for editing in performance away from the operators view. {% endhint %} # Atlas Button The Atlas button houses powerful editing functionality for the programmer. ### Atlas Button Functions #### [Palette Editor](/main-overview/atlas-button/palette-editor) #### [Cue-Matrix](/main-overview/atlas-button/cue-matrix) {% hint style="info" %} Additional functions will be added here as support expands. {% endhint %} # Palette Editor Palettes are powerful programming tools allowing multiple spatial audio functions to be grouped together and then referenced throughout the cue list and during live performance. {% hint style="success" %} Atlas makes use of priorities to ensure that all data arrives at the spatial engine and will guarantee data delivery. {% endhint %} ### Palettes [Palettes ](/main-overview/atlas-button/palette-editor#palettes)allow for common functions relating to the spatial audio engine. ### User Defined Palettes [User Defined Palettes](/main-overview/atlas-button/palette-editor/user-defined-palettes) allow users to create their own actions for functions not included within the Atlas software. ### Position Palettes [Position Palettes](/main-overview/atlas-button/palette-editor/position-palettes) allow referenced positions to be created that can then be updated to reflect changes across the cue list. {% hint style="info" %} When using palettes multiple object assignments and parameters can be targeted using wildcards and iterations. For more information on these terms please see: Wildcards and Iterations {% endhint %} # Palettes Palettes allow for referenced parameters to be accessed within Atlas both throughout the cue list and in realtime mode.

Atlas Key - Palette Editor showing object input parameters.

### Creating a New Palette Clicking on the "+' in the left hand menu next to "Palettes" will create a new Palette within Atlas. ### Deleting a Palette Selecting a palette and then clicking on the "-' in the left hand menu next to "palettes" will delete the selected palette within Atlas. ### Assigning Functions to a Palette Select the required palette for editing from the main palette list. From the dropdown menu it is possible to select from the available palette actions for the given spatial engine. Objects, outputs and function groups are all selectable depending upon the action chosen. Clicking on the required tiles will add them into the palette command and move them into the "chosen objects". {% hint style="info" %} Objects can be searched for and/or selected by set to assist programming. {% endhint %}

Atlas Key - Palette Editor showing function group editing

Clicking on the "+" next to the default preset on the menu will allow for the addition of selectable presets for the given command. These can be manually assigned or by [populating](#populate) from known parameters. {% hint style="warning" %} Currently palettes cannot be assigned a duration for their action to occur. A workaround is possible using [user defined palettes.](/main-overview/atlas-button/palette-editor/user-defined-palettes) {% endhint %} {% hint style="info" %} If using more than one spatial engine in an extended mode Atlas will automatically work out which commands needs to be sent to which engine to achieve the desired result. {% endhint %} *** ### Functions Associated with Palettes #### Palette Name Allows the palette to be assigned a name for identification. #### Standby in Cues When selected Atlas will execute the palette within the cuelist when using Standby Selected and Forced Selected. #### Recall Palette Will immediately recall the selected palette. #### Default Preset / Add Preset Allows for presets to be allocated to a palette allowing parameters to be recalled against the chosen action. #### Populate When using certain functions Atlas can auto populate the palette with known values from the manufacturers implementation. {% hint style="info" %} When using d\&b DS100 there are automatic populations for the following functions: * Delay Mode * Reverb Send Level * Spread * Reverb Room Selector {% endhint %} #### Add Command to Palette Allows additional parameters to be added to a given palette. # User Defined Palettes These allow users to create palettes for functions that are not presented within Atlas

Atlas Key - Custom palette showing values for fading output levels up and down.

### Creating a Custom Palette Click on the + in the custom palette menu. ### Deleting a Custom Palette Selecting the required custom Palette and clicking on the - will delete the selected palette. *** ### Functions Associated with User Defined Palettes #### Palette Name Allows the palette to be assigned a name for identification. #### Standby in Cues When selected Atlas will execute the palette within the cuelist when using Standby Selected and Forced Selected. #### Show/Hide OSC Dictionary Clicking this button will show/hide an OSC dictionary of common OSC strings. #### Standby in Cues When selected Atlas will execute the palette within the cuelist when using Standby Selected and Forced Selected. #### Wildcard Values User defined palettes can have wildcards attributed to them. #### Add Values Allows the addition of values that can be assigned for selection within cues. #### Duration Duration defines the amount of time over which the selected action will occur. {% hint style="info" %} User Defined Palettes can have a duration attributed to them allowing values to fade. {% endhint %} # Position Palettes Position palettes allow a positions object to be stored and then recalled relatively within the cue stack.

Atlas Key - Position palette showing referenced location.

### Creating a Position Palette Click on the + in the position palette menu. Select from the required space for reference and then click inside the space at the desired location. ### Deleting a Position Palette Selecting the required Position Palette and clicking on the - will delete the selected palette. *** ### Functions Associated with Position Palettes #### Description Allows the user to attribute a description to the palette. #### Space Allows the user to select a space in which to align the objects position within the palette. #### Update from Overview Position Allows the user to take a current live position and store within the selected position palette. {% hint style="info" %} Position palettes are helpful when a given position may change as a result of a one time change. For example assigning downstage centre as a position palette would allow this to be updated in a different venue and have that location track across an entire show. {% endhint %} # Cue Matrix The cue matrix provides a powerful batch editing function allowing for multiple cue editing alongside real-time updates to an active show.

Atlas Key - Cue-matrix showing pop up editor for object.

{% hint style="danger" %} The Cue-Matrix view requires Mac OS 13.0 or above. {% endhint %} *** ### Functions Associated with the Cue-Matrix #### Add Object(s) Clicking on the + button in the objects column will allow for object actions to be assigned within a given cue. #### Editing an Object Clicking on a given object will bring up the cue-matrix editor for the selected object. Most functions found within the respective modules [Object Properties Inspector](/main-overview/programmer/object-properties-inspector) can be edited from here. {% hint style="warning" %} Changes made within the cue-matrix are made in realtime to the cuelist and may affect playback. Edits can be made during the performance to modify upcoming cues and their behaviour as well as updates made in previously executed cues. {% endhint %} #### Add External Device Trigger(s) Clicking on the + button in the external triggers column will allow for external triggers to be assigned. {% hint style="info" %} Using the ESC key will close the window without any action being applied. {% endhint %} ***

Atlas Key - Cue-Matrix showing incremental addition of external trigger cues

{% hint style="success" %} By selecting multiple cues the in the cue-matrix it is possible to assign external triggers across a range of cues attributing a custom start number and custom incrementation. {% endhint %} *** #### Headers Visible within the Cue-Matrix #### No. Displays the cue number. #### Timecode Displays the timecode trigger time. #### Cue Name Displays the name of the cue. #### Objects Shows the objects and actions assigned within the selected cue. #### External Triggers Shows the external triggers associated with the selected cue. # Object Overview The Object Overview window allows the user to see and control an objects parameters both whilst programming and online.

Object Overview Window

### Offline Mode When Atlas is working offline the parameters displayed in the overview are related to the programming within the cuelist. Any values entered into the Object Overview will not be actively reflected as changes within the programmer. {% hint style="danger" %} Any object whose parameters haven't been actively modified will display default values when working offline! {% endhint %} *** ### Online Mode When Atlas is working online the parameters displayed in the overview are realtime values being received from the device. {% hint style="danger" %} Any changes made will affect the live output but will not be recorded in the programmer unless specific actions for those parameters are entered! {% endhint %} *** ### Selecting Objects By default Atlas will provide additive selection when clicking on objects. Multiple objects can be edited in this way. {% hint style="info" %} On the left hand menu objects can be sorted by [Sets ](/show-settings/objects/sets-alias)to enable specific selections of objects to be made visible together. {% endhint %} ### Relative/Absolute Editing When multi-selected moving a fader relating to a Reverb Send Level will maintain relative levels between the selected send level When multi-selected typing a value into the Reverb Send Level will cause all selected objects to move to the entered value. *** ### Functions associated with Object Overview #### Clear Selection Clears all currently selected objects. #### Add All Selects all objects currently visible within the Object Viewer. # Monitor Monitor Incoming Tracking Data The monitor window allows you to see incoming tracking data to confirm its validity. It is accessed from "windows/monitor". *** ### Patch With the presence of a valid data stream the relevant indicator will change to green. ### Incoming Co-Ordinates Displays the currently received data co-ordinates from the tracking system {% hint style="info" %} This is usefu {% endhint %} ### Last Received Data *** ### Functions Associated with Monitor None # Operators Cuelist # My First Atlas Session for DS100 Getting started with Atlas is easy. In this tutorial we create our first workspace. {% hint style="success" %} Coming Soon {% endhint %} # Importing Space Information Setting up our workspace and importing our objects ### Prerequisites Atlas saves the user time by using your d\&b Audiotechnik R1/Arraycalc file to determine its spaces and, should the user wish, its object names and assignments. Atlas requires a configured R1 file with active positioning planes to define the spaces in which Atlas will work. {% hint style="info" %} The R1/ArrayCalc file can be modified and completed as the production develops. It is advisable to start with an R1 positioning plane that approximates the stage area when starting programming. {% endhint %} ## Creating a New File When opening Atlas for the first time it will create a blank file. To manually create a blank file select "New" from the menu or ⌘-N {% hint style="success" %} Subsequently opening Atlas will cause the software to reopen the last saved file. {% endhint %} ### Importing Arraycalc File To import an Arraycalc file navigate to the "Atlas Menu-Show Settings" or ⌘-, Navigate to the "Spaces" tab and select "Import File" from the menu. In the pop up that opens navigate to the R1/Arraycalc file that you wish to import. {% hint style="warning" %} Ensure the file is not open within R1/Arraycalc or a duplicate access error will occur causing R1/Arraycalc to need to reopen or resave the file. {% endhint %}

New Atlas workspace with R1 file opened showing the available data.

Next we need to assign our mapping planes to relate to spaces within Atlas. From the dropdown menu select mapping plane 1 (called stage in our example) and assign to the Default Space. We are also going to create an additional space providing us with a wider view of the room. Click on "New Space" and then in the pop up that appears assign mapping plane 2 (called Venue in our example) to this new space. {% hint style="info" %} Selecting "Points Only" will keep the default naming convention in Atlas should you not wish to use the name imported from the R1 File. We can rename our spaces in Atlas later. {% endhint %}

New Atlas workspace with R1 file mapping planes assigned to spaces within Atlas

When we have completed the above we can click "Done" and return to the Spaces window. {% hint style="info" %} It is also possible to import our Objects and assign our spatial engines from within this step and as you get familiar with Atlas you may wish to complete these steps at this time. For the purposes of this tutorial we will return to this step at a little later. {% endhint %} In the Spaces window we can now see the mapping planes we have imported into Atlas. At this time we can now rename the spaces if we wish to do so.

Show Settings - Spaces after our R1 import.

#### Images *Now that we have assigned our spaces within Atlas it is usually desirable to assign some images that relate to the groundplan of the space in which we are working.* Click on the symbol and Atlas will create a new background image. We can select the New Background and give this a name. Next we can drop an image file onto the Space and using the scaling tools we can adjust the image to be relevantly scaled to the Mapping Plane. We can use the mouse pointer to click and drag to manipulate the image. {% hint style="info" %} There are a number of tools and options to assist us with our images. More details can be found in the manual section: [Background Images](/show-settings/spaces/background-images) {% endhint %} The yellow dot denotes the centre or 0,0 co-ordinate of the R1/Arraycalc file.

Show Settings - Spaces showing an image file dropped in as a background image.

We can now repeat this step for each space in which we are working. {% hint style="info" %} Atlas supports an unlimited number of image backgrounds for each space. These can be recalled dynamically within the programmer. {% endhint %} {% hint style="success" %} Multiple background images for each space can be used for different scene settings etc. {% endhint %}

Show Settings - Spaces showing an image file dropped in as a background image.

*** Having created our spaces in which we are going to work we can now turn our attention onto the sound objects we wish to control within Atlas. ### [Importing Object Information](#importing-object-information) ### # Importing Object Information Setting up our workspace and importing our objects ## Objects Having created our spaces in which we are going to work we can now turn our attention onto the sound objects we wish to control within Atlas. Select the "Object" tab within the "Show Settings". There are 3 different ways in which to add Sound Objects into our workspace. Descriptions of how to do this for each method are outlined below. * [Manually Add Object](#manually-adding-objects) * [Import from DS100](#importing-objects-from-ds100) * [Import from R1/Arraycalc File](#importing-objects) ### Manually Adding Objects To manually add objects; click on the "add object" button. Atlas will add objects to the workspace in a numerically sequential manner starting with the lowest unused object ID. (Usually 1 within a new workspace) ### Importing Objects from DS100 {% hint style="warning" %} This option relies upon completing a number of other processes and having the DS100 onsite at the time of setup/intial programming. The method is included here for completeness but is usually attributed to onsite usage. {% endhint %} Click on the "Import from DS100" button. A complete list of available objects within the DS100(s) will be shown. Select the objects you wish to bring under control with Atlas and then click "select objects to import" Atlas will now import the selected objects into the workspace along with their spatial ID's from the DS100. Click on the "close" button to close the window. {% hint style="info" %} Where more than one DS100 is present within the system the object names and ID's of all available units will be shown. {% endhint %} ### Importing Objects from File Click on the "Import from File" button to open the import window. Select the required R1/Arraycalc file that you used in[ importing the space information. ](/tutorials/my-first-atlas-session-for-ds100/importing-space-information) Select the "Objects Tab" from the window that appears.
For the purposes of this tutorial we will import all the available objects from within the R1/Arraycalc file. We can do this by manually clicking on each object or selecting one object and then using the shortcut ⌘-A. {% hint style="info" %} If the object ID is already in use and assigned Atlas will display the message (overwrite) next to the spatial ID within the import window. {% endhint %} Once selection is made click on to bring those into the Atlas workspace. Click on the "close" button to close the import window. {% hint style="info" %} Only objects that are selected for En-Scene mode within the R1 file will show as available objects to import into Atlas. {% endhint %} Once we have our objects imported into the workspace we can now proceed to [Organise our Audio Objects. ](/tutorials/my-first-atlas-session-for-ds100/organising-our-audio-objects) ### # Organising Our Audio Objects In this chapter we organise our objects to assist us with our programming ### Assigning Colours & Names One of the simplest things we can do to assist us to recognise objects within the workspace is to assign them colours and short form names. {% hint style="success" %} If we imported from our DS100 or R1/Arraycalc file we will already have the names imported from the file/device. In terms of workflow this is the least labour intensive as it allows the naming of the object once within the initial R1/Arraycalc file and then using them throughout our workflow. {% endhint %} Atlas allows us to assign a short 4 character name to each object or group. These will then be displayed in the programmer and overview to aid identification. ### Changing Object Name - Applicable if we did NOT import our names from the R1/Arraycalc File. To change the short form name of within our workspace; Select the "Objects" tab within the show settings and select "Spatial ID1" Select the text field box and type the name by which we wish to identify "Spatial ID 1" Repeat this step for all objects. ### Changing Short Form Name To change the short form name of within our workspace; Select the "Objects" tab within the show settings and select "Character 1" {% hint style="success" %} By default Atlas will have assigned the first 4 characters of the long name to be the short name and be displaying this greyed out below the long name. {% endhint %} To rename "Character 1"; Click in the greyed out box and type the new short form name "Ch-1" {% hint style="info" %} The icon will change to show you how the short form name will display. {% endhint %}

Show Settings - Object showing changed short form name replaced with Ch-1

Repeat this step for all the objects with appropriate short form names. *** ### Changing Colours Select "Character 1" thru "Character 4" by clicking on the objects whilst holding down the ⌘ key. We can now change the colour of these 4 selected objects by clicking on the "Object Colour" selector and choosing a colour from the colour selector that has appeared.

Show Settings - Objects showing multiple objects selected and colour identifier changed.

Repeat this step for each object. Colours can be chosen for individual objects or for collections of objects based upon user preference. Close the colour picker by selecting the close window icon. *** ### Creating Sets We can also arrange collections of objects into [sets. ](/show-settings/objects/sets-alias) Select the objects named "Character 1", "Character 2", "Character 3" & "Character 4" using the multi select method from the last step. In the "Sets" window click on the "+" icon to create a new set. Click on the newly created set labelled "New Set". This has now assigned those objects to that set. To rename the set; Right-Click on the set - "New Set" and select "Rename" from the pop-up menu that appears. Rename the set "Main Cast" and hit enter to commit the change. {% hint style="success" %} Sets provide a great way of selecting a collection of objects when programming as well as allowing us to view only the objects we want within the programmer and overview windows. {% endhint %} Repeat this step for all the objects by creating and assigning sets using the following titles: * Main Cast * Chorus * Band * Playback * Reverb {% hint style="info" %} Objects can belong to multiple sets so users can arrange by any selection they require. (For example: By type of sound source or by cast members in a given scene(s)). {% endhint %}

Show Settings - Objects showing objects coloured and assigned to sets.

*** ### Groups Collections of objects that we wish to move as one can be assigned to "Groups". Unlike sets groups are programmed collectively with position offsets. {% hint style="info" %} Any child of a group can be programmed independently so assignment to a group doesn't limit the individual object within programming or overview. {% endhint %} ### Creating Our Groups {% hint style="success" %} Sometime it is desirable to be above to move multi format audio sources. A group will allow us to move the stereo playback objects as one. {% endhint %} Select both of the objects associated with playback Left and Right using the multi select method from above. At the bottom of the window select the button "Make Group" button. This will now make a [group](/show-settings/objects/groups) of objects within our workspace. The newly created group will appear at the top of the Object List. Name the newly created group "Playback" and assign a short form name. Select the newly created group and, following the same procedures as above, assign the group a full name, short form name, colour and assign it to the set "Playback".

Show Settings - Objects assigned to a group, named, coloured and placed in the "Playback" set.

Next click on the "Group Config" tab; this will now allow us to configure our group. {% hint style="info" %} By default our Stage Close space will be selected as the default space. We can select a different space to view and layout our groups from the dropdown menu at the top. {% endhint %} Highlight the group icon called "Playback" and select a position in the centre of the stage to determine the centre point of our stereo group. Next highlight the object "Playback Left" and position this where our nominal left source would sit within a stereo system. Repeat this procedure for the object "Playback Right".

Show Settings - Object groups configured in a stereo configuration.

{% hint style="success" %} Groups are not limited to two objects and can be used to group components of instruments, chorus's and other objects that are used together. {% endhint %} Lets repeat the steps above but this time for the drum objects within our workspace. Select all of the objects associated with our drums using the multi select method from above. At the bottom of the window select the button "Make Group" button. This will now make a [group](/show-settings/objects/groups) of objects within our workspace. The newly created group will appear at the top of the Object List. Name the newly created group "Drums" and assign a short form name. Select the newly created group and, following the same procedures as above, assign the group a full name, short form name, colour and assign it to the set "Band".

Show Settings - Objects assigned to a group, named, coloured and placed in the "Band" set.

Next click on the "Group Config" tab; this will now allow us to configure our group. Highlight the group icon called "Drums" and select a position to determine the centre of the drum group. Sequentially highlight the objects associated with the group "Drums" and position accordingly.

Show Settings - Objects associated with drum group positioned within the stage picture.

{% hint style="info" %} Object positions within groups can be taken from live positions. Spreads can be offset and changed relatively to each other. More information can be found in [Group](/show-settings/objects/groups/group-configuration)[ Configuration. ](/show-settings/objects/groups/group-configuration) {% endhint %} Close the "Show Settings. Go to "File" and select "Save As" Title your file and save following standard OS X procedures. *** Now we have organised our objects we can move onto [Creating Our First Cue. ](/tutorials/my-first-atlas-session-for-ds100/creating-our-first-cue-s) # Creating Our First Cue(s) Cues allow the creation of actions and sequences of actions to be performed within performance. ### Creating a New Cue ### Inserting Objects & Creating a Journey ### Creating a Sequence # Going Online {% hint style="danger" %} Atlas needs a license to output OSC. {% endhint %} ### Configuring our DS100 Settings # Advanced Atlas Programming {% hint style="success" %} Coming Soon {% endhint %} # Creating a Shape # Using Groups # Using Aliases # Introduction to Palettes {% hint style="success" %} Coming Soon {% endhint %} # Creating a Palette # Multiple Function Palettes # Uses for Palettes & Examples # Park, Move-in-Mute & Live Moves {% hint style="success" %} Coming Soon {% endhint %} # Setting up Objects to Use # Live Moves & Move-in-Mute # Defining Parking Locations # Using Trackers {% hint style="success" %} Coming Soon {% endhint %} # Patching Trackers & Objects # Using Trackers in the Cuelist # Boundaries # Using External Controllers {% hint style="success" %} Coming Soon {% endhint %} # Applications using Controllers # Controllers - Digico SD/Q Series # Controllers - SSL L-Series # Using External Devices {% hint style="success" %} Coming Soon {% endhint %} # Adding an External Device # Wildcards & Iterations # Terminology # Atlas Glossary A-Z ### Range Bound / Metered ### Stabilisation # Atlas Controls # Keyboard Shortcuts Atlas supports keyboard shortcuts for both operation and programming. ### Atlas Shortcuts By default Atlas has the following keyboard shortcut mappings. | Command | Key | | ---------------- | :---: | | Go | SPACE | | Panic Workspace | | | Panic All | | | Preview Selected | V | | Stop Selected | S | | Standby Selected | | | Force Selected | F | | Solo Object | H | ### Atlas Keyboard Shortcuts Atlas supports most conventional Mac OS X keyboard shortcuts with respect to software operation. # OSC Library Atlas has an extensive OSC library to allow user control. ### Functions associated with cue playback
NameMessageNotes
Go/atlas/go
Start a Cue/atlas/cue/*/start
Stop a Cue/atlas/cue/*/stop
Panic Workspace/atlas/panic
Panic All/atlas/panic/all
Select Previous Cue/atlas/previous
Select Next Cue/atlas/next
### Functions associated with locating objects
NameMessageNotes
Send an object to its Default Location/atlas/locate/*
Send a range of Objects to their Default Locations/atlas/locate//thru/
Send a group to its default location/atlas/group/*/locate
Hard locate an object/atlas/hard/locate/*
Hard locate a range of objects/atlas/hard/locate//thru/
Hard locate a group/atlas/hard/locate/group/*
### Functions associated with locking objects
NameMessageNotes
Lock an object/atlas/object/*/lock
Lock a range of objects/atlas/object//thru//lock
Lock a group of objects/atlas/group/*/lock
Unlock an object/atlas/object/*/unlock
Unlock a range of objects/atlas/object//thru//unlock
Unlock a group of objects/atlas/group/*/unlock
### Functions associated with soloing objects
NameMessageNotes
Solo an object/atlas/solo/*
Solo a group of objects/atlas/solo/group/*
Clear solo command/atlas/solo/clear
### Functions associated with palettes
NameMessageNotes
Recall a palette/atlas/palette/start
Move an object to a position palette/atlas/locate/*/to/palette
Move a range of objects to a position palette/atlas/locate//thru//to/palette
### Functions associated with OSC control
NameMessageNotes
Enabling incoming OSC/atlas/overrides/oscinput/enable
Disable incoming OSC/atlas/overrides/oscinput/disable
Enable outgoing OSC/atlas/overrides/oscoutput/enable
Disable outgoing OSC/atlas/overrides/oscoutput/disable
Enable incoming MTC Timecode/atlas/overrides/timecode/enable
Disable incoming MTC Timecode/atlas/overrides/timecode/disable
Enable incoming tracking data/atlas/overrides/tracking/enable
Disable incoming tracking data/atlas/overrides/tracking/disable
### Functions associated with OSC control to external devices
Enable outgoing OSC to external device/atlas/control/externaldevice/*/enable
Disable outgoing OSC to external device/atlas/control/externaldevice/*/disable
Toggle outgoing OSC to external device/atlas/control/externaldevice/*/toggle
# Midi / Midi Timecode Atlas accepts midi for the purposes of triggering the cue list from an external source or following Midi Timecode (MTC) *** ### Midi Triggers Any standard midi command can be captured to use as a trigger. *** ### Midi TimeCode Atlas supports the following MTC Formats #### Film/ATSC/HD 23.976, 24, 24.98, 47.952, 48, 95.904 and 96 #### PAL/SECAM/DVB/ATSC 25, 50 and 100 #### NTSC/ATSC/PAL-M 29.97, 29.97-DF, 59.94, 59.94-DF, 119.88 and 119.98-DF #### NTSC Non Standard 30-DF, 60-DF and 120-DF #### ATSC 30,60 and 120 --- [Next Page](/llms-full.txt/1)