Velum Studio
All guides

Guides › Make it yours

Automations and hotkeys

Let Studio do things for you when a scene goes on air, or when you press a key.

Automations are things Velum Studio does by itself: when a scene goes on air, when your game shows a certain screen, when your category changes, or when you press a key. A hotkey always belongs to an automation, so this is also where you set up hotkeys.

Make an automation

  1. In the Automations panel, click New automation and give it a name.
  2. Choose When:
    • When this scene goes on air or When this scene goes off air
    • While a detector sees its picture (see Screen Detect)
    • When the category changes to
    • Only when I press Run or its hotkey
  3. Set a Hotkey if you want one. It works from any app, and the app in front still gets the keys.
  4. Add a step for each thing it does, in order.

What it can do

  • Move a layer to a framing (a saved spot; see Framings)
  • Show a layer or Hide a layer
  • Turn a filter on, Turn a filter off, or Fade a filter setting over a few seconds
  • Show a source in a mirror
  • Switch to a scene
  • Change a text layer's words, at once or typed out over a few seconds
  • Wait
  • Take a screenshot or Save a replay

When it stops, put everything back the way it was undoes its changes when it ends: a layer it moved goes back, a filter it turned on goes off. If it's still running when it fires again chooses whether it starts over, finishes first, ignores the new trigger, or runs both.

Each automation has a switch to turn it on or off and a Run button, and shows when it last ran.

Screen Detect

A detector watches a source, like your game capture, for a picture (a results screen, a logo) or words on screen (Victory, SELECT CAR), in the part of the screen you choose. In Screen Detect, click New detector. Choose how steady it should be: Snappy reacts within a few frames, Steady waits longer and never flickers. Then make an automation While a detector sees its picture.

On Linux, reading words needs Tesseract: install the tesseract-ocr package.

Hotkeys on each computer

  • macOS asks you to allow Input Monitoring once (the gear › Permissions… › Hotkeys from any app). Studio only watches for your hotkeys.
  • Windows needs nothing extra.
  • Linux: hotkeys from other apps work in an X11 session; on Wayland they aren't built yet.