# Action Editor

The Action Editor provides a centralized interface for configuring keyboard shortcuts and StreamDeck panel mappings. It is designed for professionals in demanding workflows where quick, efficient actions are essential.

<figure><img src="/files/BZEriXIWfi0YLSyaUNIl" alt=""><figcaption><p>Action Editor</p></figcaption></figure>

## Action Categories

The Action Editor organizes actions into intuitive categories:

* **General Actions** — Straightforward actions that don't require additional parameters, ideal for quick and routine tasks.
* **Input Device Actions** — Assign specific devices to desired input slots, essential in multi-device environments.
* **Layout Actions** — The **Load Layout** action accepts two parameters: layout index or name, making it easy to switch between different layouts.
* **Input Slot Actions** — Assign actions to specific input slots, ensuring accurate responses from the intended device. Particularly useful in complex multi-input setups.
* **Scope Actions** — Each action is linked to a unique scope identifier, visible in the Action Editor. This allows precise control over multiple scopes.
* **Timeline Navigation Actions** — Direct actions for **Go to Frame** and **Go to Time**, enabling precise timeline jumps from shortcuts, Stream Deck, and integrations.
* **Input Settings Actions** — Expose source settings directly through the Action Editor and integrations.

## User-Friendly Features

* **Preview of Scope Index** — View the scope index by pressing **Alt+Shift** (or **Opt+Shift** on macOS), even when the Action Editor is closed. This aids in fast scope identification.
* **Action Filtering** — Narrow down actions for a specific scope using the search box. For example, typing **`idx:3`** filters actions exclusively for scope index 3.

<figure><img src="/files/MBhgsqDVUQbXVpvqHi98" alt=""><figcaption><p>Filtering actions by scope index</p></figcaption></figure>

* **Clearing the mappings** — Use the "3 dots" menu to reset existing mappings and start from scratch:

<figure><img src="/files/6ZSS0AOBxYyTmSniZsb4" alt=""><figcaption><p>Reset mappings menu</p></figcaption></figure>

## Assigning Keyboard Shortcuts and StreamDeck Actions

* **Keyboard Shortcuts** — Click the action name to record a new shortcut. OmniScope will notify you if the chosen shortcut is already in use, preventing conflicts.

<figure><img src="/files/RmKYY9N9BJFEdvDBqlj1" alt=""><figcaption><p>Recording a keyboard shortcut</p></figcaption></figure>

* **StreamDeck Actions** — Two columns in the editor, **StreamDeck** and **Per Layout**, provide flexibility in mapping. Global mappings apply across all layouts, while Per Layout mappings are specific to the current layout and override global mappings when active.

<figure><img src="/files/dNvyqhXhmYYejApT5SRg" alt=""><figcaption><p>StreamDeck global and per-layout mappings</p></figcaption></figure>

* **Keyboard shortcuts** are automatically displayed in the macOS menus:

<figure><img src="/files/FTPxq839MEV960Lo4JH9" alt=""><figcaption><p>Shortcuts in macOS menus</p></figcaption></figure>

## Application Protocol

OmniScope supports invoking actions programmatically using the custom URI scheme **`omniscope://`**. This enables workflow automation and integration with scripts, macros, or third-party applications.

Format: **`omniscope://action?id=ActionID&param=ActionParam`**

The **ActionID** can be found by hovering over the action in the editor:

<figure><img src="/files/ts7ZbzrGAcbnzIyq93hf" alt=""><figcaption><p>Action ID tooltip</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.timeinpixels.com/nobe-omniscope/action-editor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.