# FAQ ## What is the latest stable version? The latest stable release is 1.6x (1.69). Features labeled **BETA (v2)** in this chapter require a v2 beta build. ## Which features are BETA (v2)? Any feature marked **BETA (v2)** is only available in v2 beta builds. Examples include Nobe Connect and the new NDI audio options. ## Do I need an NDI license? NDI streaming features require an NDI license. Use **License > Upgrade to NDI...** to upgrade an existing license. See [Upgrading to NDI](/nobe-display/upgrading-to-ndi.md). ## Does Nobe Display support Apple Silicon? Yes. Native Apple Silicon support was added in 1.63. ## I didn't receive my license key after purchase The license key comes in a separate email from `timeinpixels.com` — not the Paddle receipt. Check your spam folder first. If it's still missing, visit [timeinpixels.com/lost-license](https://timeinpixels.com/lost-license/) and enter the email used at checkout. If no license is found, the checkout email may contain a typo — contact support with your purchase details so we can look up the order. ## My activation fails with "License not found" or a signature/SSL error Use the **Activation Code** method instead of email + key. It validates locally and bypasses firewalls, antivirus, and corporate proxies. 1. Check your key prefix first: Nobe Display keys start with `DDN1` (NDI) or `DDS1` (Studio). Keys starting with `NMTR` are OmniScope trial keys and won't activate Nobe Display. 2. Log in at [timeinpixels.com/my-license](https://timeinpixels.com/my-license/), click **Get Activation Code** next to your license. 3. In Nobe Display, open the **License** menu and paste the activation code. Full instructions: [License Activation → Activation Code](/nobe-display/license/license-activation.md#activation-code). ## I got "Exceeded number of activations" — how do I reset? This happens after a machine is wiped or replaced without deactivating Nobe Display first. 1. Log in at [timeinpixels.com/my-license](https://timeinpixels.com/my-license/). 2. Click **Reset** next to the machine you want to release. Reset requests are approved manually, usually within a few hours during business hours. 3. Once approved, activate on the new machine. One license activates on up to **3 machines simultaneously** for Nobe Display. If deactivation inside the app fails with a runtime error, open the logs folder, delete the `DDS1.dat` or `DDN1.dat` file, restart, and activate again. ## How do I change the email address on my license? Customers can't self-service this — contact support with your old email, new email, and (optionally) license key. After the change, deactivate and reactivate on your machines so the new address is stored locally. ## The Nobe Display plugin doesn't appear in DaVinci Resolve 1. **Launch the Nobe Display app first, before opening Resolve.** The first launch installs the OpenFX plugin on macOS. 2. Open Resolve — the plugin should appear in the Color page → Effects panel → OpenFX. 3. If it's still missing or shows "Failed to load", reset the OpenFX cache: see [OpenFX Plugin is Not Loading](/nobe-omniscope/troubleshooting/openfx-plugin-is-not-loading.md). 4. From inside the Nobe Display app, use **Options → Install Plugins → Install OpenFX Plugin** to force a reinstall. 5. If you're running Resolve from the Mac App Store, see [DaVinci Resolve from the App Store](/nobe-display/davinci-resolve-from-appstore.md) for the sandbox workaround. ## The Nobe Display window is black or plays back on its own The most common cause is DaVinci Resolve's **render cache** interfering with the OpenFX frame delivery. Disable it: * **Playback → Render Cache → None**, and turn off **Cache Frames in Background**. If you need smooth playback of heavy media, use **proxy media** instead of the render cache — proxies don't cause this. For a permanent fix, use a hardware capture card (DeckLink or UltraStudio) as the signal path: SDI output from Resolve is not affected by caching behavior. ## My color-managed timeline (DWG / ACES) looks flat or log in Nobe Display Place the Nobe Display node at the **end** of your node chain so the color transform is applied before the signal reaches the plugin. See [Color Managed Timeline](/nobe-display/color-managed-timeline.md) for the full setup. ## Can I use multiple Nobe Display nodes in one Resolve project? No. Nobe Display 1.x cannot differentiate frames from multiple OFX instances at once. Multi-instance support is planned for a future version — use a single Nobe Display node per timeline for now. ## What does the OpenFX plugin NOT pass through? The OpenFX architecture only delivers the composited frame. The following are **not** visible to Nobe Display via the OFX path — use a hardware capture card if you need them: * Power windows, qualifiers, and masks * Split view / image wipes * Gallery stills * Reference clips ## Nobe Display 1.x crashes when receiving NDI from an external source Known issue — Nobe Display 1.x ships with an older NDI SDK that can crash when connecting to NDI sources from other applications (e.g. OmniScope on another machine, VR headsets). The **Nobe Display 2.x beta** uses a newer NDI SDK that fixes this. Grab it from [timeinpixels.com/nobe-display-beta](https://timeinpixels.com/nobe-display-beta/). ## Why is there lag between Resolve and Nobe Display? OpenFX queuing in DaVinci Resolve adds latency that scales with timeline resolution and color pipeline complexity. There is no user-accessible control for this. For consistent low-latency output, use a hardware capture card (DeckLink or UltraStudio) instead — SDI output is unaffected. --- # 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-display/faq.md?ask= ``` 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.