QUICK REFERENCE CHECKLIST

  1. Verify Art-Net Connectivity: Check that the Art-Net node is active and Arena is receiving DMX data from your console.
  2. Apply UI Layout: Configure the user interface according to the on-site instructions.
  3. Configure Layer 1 Effects: Set up Layer 1 with all required effects before creating any shortcuts.
  4. Duplicate Layers: Duplicate Layer 1 as many times as needed to create your full layer stack.
  5. Validate “By Position” Shortcuts: Ensure all “By Position” shortcuts are mapped only to the first Arena layer (not to Composition or Clip) to prevent erratic media server behavior.
  6. Validate “This Layer” Shortcuts: Ensure all “This Layer” shortcuts are mapped only to the first Arena layer and to the video opacity of duplicated layers (not to Composition or Clip) to prevent erratic behavior.
  7. Not working shortcut/Shortcuts: If some shortcuts of the Shortucts file won’t work despite the shortcuts lines, in the panel are white characters, and GUI fields look mapped, delete those and remap from begin. Because if, simply, you will remap those, you will add extra working shortcut in addition to the non-functioning ones, cheating the PROCESSING ENGINE shortcut count.
  8. Mind the Mode Context: Remember that “This Layer” shortcuts are composition-specific; they will not function in other compositions.
  9. Enforce Uniform Mapping Modes: Confirm that all initial shortcuts use either “This Layer” or “By Position” mode. Do not mix modes in the final file.xml to be processed.
  10. Calibrate Range Settings: Adjust the range of critical parameter shortcuts to match your output display.
  11. Define Bit Depth: Set the correct 8-bit or 16-bit parameters within each specific shortcut.
  12. Check 16-Bit Channel Mapping: Double-check which DMX channel maps to your console’s 16-bit parameters (usually the first of the two). Arena may accidentally map the wrong channel if both are active during shortcut assignment.
  13. Test Layer 1 Behavior: Verify that Layer 1 responds correctly to the console patch before running the Processing Engine. If issues arise, go to Shortcuts > Edit DMX to troubleshoot.
  14. Export the Source File: Copy the generated shortcuts file from C:\Users\User\Documents\Resolume Arena\Shortcuts\DMX and upload it to the online PROCESSING ENGINE.
  15. Cross-Check Console Personality: Verify that your shortcuts match the console fixture profile (personality).
  16. Verify DMX Footprint: Ensure the shortcuts and console fixture footprint align perfectly during the generation and processing of the start.xml file.
  17. Close the Software: Close Resolume Arena.
  18. Deploy the Processed File: Copy the output.xml file from the Processing Engine back into C:\Users\User\Documents\Resolume Arena\Shortcuts\DMX.
  19. Relaunch the Software: Restart Resolume Arena.
  20. Rename the shortcuts: Remember to change the shortcuts file name, only, from the Arena application panel, otherwise the file may become unreadable.
  21. Maximize Master Faders: Confirm that all master layer faders are set to 100% across all duplicated layers.
  22. Ready for Operation: Your system is now verified and ready to go.
  23. Layers Control Trouble shooting: Sometime may occur an uncertain multiple layers control at once, when you select from the first time a DMX Shortcut from the Panel within Arena. It happens due to the unknown and unlinked Shortcuts in the Composition. To fix select and manipulate by the console each layer of the project one at time, until you will have “touched” all shortcutted layers in the composition, to establish a strong link between the Layers and the assigned shortcut.