Skip to content

Releases

Vexel 0.7.1 (beta)

Vexel 0.7.1 (beta) Pre-release
Pre-release

Choose a tag to compare

@Jallison154 Jallison154 released this 16 Nov 16:48

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.7.1

  • About Vexel (Options ▸ About Vexel…) now has a small link to support the project: ☕ Buy me a coffee. No changes to outputs, NDI or rendering since 0.7.0.

New in 0.7.0: NDI outputs

  • Send a display over NDI. Add one with + Display ▸ NDI Output… (source name and resolution), or pick NDI (network source) under Output to for an existing display. Map slices onto it as usual and press ▶ Start NDI. Receivers (NDI Studio Monitor, vMix, another OBS, LED processors that take NDI) see it as COMPUTER (name).
  • It is built exactly like an HDMI output: slices, per-output delay with crossfade, test pattern and slice outlines all apply. It runs at the OBS frame rate, and 1:1 slices are pixel-exact. Video only.
  • The dock shows Start / Stop NDI, the frames per second being sent, and how many receivers are connected (e.g. "30 fps · 2 receivers").
  • A running NDI output comes back after an OBS restart. Renaming it re-announces the source under the new name. Start All / Stop All include NDI displays.
  • Sending never slows OBS down: frames are read back from the GPU without waiting, and sent from a separate thread. If the network falls behind, Vexel skips to the newest frame instead of building up lag.
  • Needs the free NDI Runtime on the computer, installed with NDI Tools. Vexel finds it where NDI installs it; nothing NDI ships with Vexel. Without it, NDI displays say "NDI Runtime not installed" and everything else works as before.
  • New remote-control requests (obs-websocket, e.g. Stream Deck / Companion): StartNdi and RenameDisplay. Stop an NDI output with StopOutput.
  • Tested end to end on macOS against a stand-in NDI library that records every frame (32 checks), plus the full existing test (72 checks). Please check on Windows: add an NDI display, start it, and confirm an NDI receiver on another computer sees the source and the picture is right.

New in 0.6.4

  • Fixed: OBS could crash when a display disappeared (unplugged, powered off, or a video switcher dropping its signal), mainly on Windows. When an output's display goes away, the output now stops and hides straight away and is cleaned up safely a moment later. It still comes back by itself when the same display returns.
  • A quick burst of Windows display-change messages no longer makes Vexel give up on an output too early.
  • The test pattern now matches each slice. Every slice gets its own calibration pattern at its exact size and position on the output: red and white edge lines on the slice's outermost pixels, a grid and rulers counted from the slice's corner, corner markers in the slice's colour, and the slice's name, size and position. Areas no slice covers stay black. An output with no slices still shows one full-screen pattern. Output Placement shows the same image.
  • Please check on Windows: start your outputs, then unplug or power off one display, and plug it back in. OBS should keep running, and that output should come back by itself.

New in 0.6.3

  • Dock previews at full frame rate. The thumbnails in the Vexel dock now update on every OBS frame (30 or 60 fps), instead of about 10 times a second, so motion looks just like the outputs.
  • Accurate output frame rate. The fps reading in the dock is now measured against the real clock and smoothed. It no longer dips when the OBS interface is busy (e.g. while you drag slices) even though the output is smooth. If an output really falls behind, the reading turns amber and shows the target, e.g. "24 / 30 fps".
  • Measured on macOS: thumbnails 29.9 / 59.9 frames per second at 30 / 60 fps; the fps reading stays within 1 fps of the target while the interface is busy.

New in 0.6.2

  • Updated Vexel logo and banner from the final brand artwork: the V-tile mark (window icon, footer and About) now has eight tiles, cyan to purple. No changes to outputs, rendering or settings.

New in 0.6.1

  • The Vexel dock stays where you put it. It now comes back after an OBS restart exactly as you left it: shown or hidden, docked or floating, same place and size. Before, it could disappear after the first restart. If you closed it yourself, it stays closed (reopen it under Docks ▸ Vexel).
  • On first install, the dock is docked on the right side of the main OBS window instead of opening as a small floating window.

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.3-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.3 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.3-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Vexel 0.7.0 (beta)

Vexel 0.7.0 (beta) Pre-release
Pre-release

Choose a tag to compare

@Jallison154 Jallison154 released this 16 Nov 16:12

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.7.0: NDI outputs

  • Send a display over NDI. Add one with + Display ▸ NDI Output… (source name and resolution), or pick NDI (network source) under Output to for an existing display. Map slices onto it as usual and press ▶ Start NDI. Receivers (NDI Studio Monitor, vMix, another OBS, LED processors that take NDI) see it as COMPUTER (name).
  • It is built exactly like an HDMI output: slices, per-output delay with crossfade, test pattern and slice outlines all apply. It runs at the OBS frame rate, and 1:1 slices are pixel-exact. Video only.
  • The dock shows Start / Stop NDI, the frames per second being sent, and how many receivers are connected (e.g. "30 fps · 2 receivers").
  • A running NDI output comes back after an OBS restart. Renaming it re-announces the source under the new name. Start All / Stop All include NDI displays.
  • Sending never slows OBS down: frames are read back from the GPU without waiting, and sent from a separate thread. If the network falls behind, Vexel skips to the newest frame instead of building up lag.
  • Needs the free NDI Runtime on the computer, installed with NDI Tools. Vexel finds it where NDI installs it; nothing NDI ships with Vexel. Without it, NDI displays say "NDI Runtime not installed" and everything else works as before.
  • New remote-control requests (obs-websocket, e.g. Stream Deck / Companion): StartNdi and RenameDisplay. Stop an NDI output with StopOutput.
  • Tested end to end on macOS against a stand-in NDI library that records every frame (32 checks), plus the full existing test (72 checks). Please check on Windows: add an NDI display, start it, and confirm an NDI receiver on another computer sees the source and the picture is right.

New in 0.6.4

  • Fixed: OBS could crash when a display disappeared (unplugged, powered off, or a video switcher dropping its signal), mainly on Windows. When an output's display goes away, the output now stops and hides straight away and is cleaned up safely a moment later. It still comes back by itself when the same display returns.
  • A quick burst of Windows display-change messages no longer makes Vexel give up on an output too early.
  • The test pattern now matches each slice. Every slice gets its own calibration pattern at its exact size and position on the output: red and white edge lines on the slice's outermost pixels, a grid and rulers counted from the slice's corner, corner markers in the slice's colour, and the slice's name, size and position. Areas no slice covers stay black. An output with no slices still shows one full-screen pattern. Output Placement shows the same image.
  • Please check on Windows: start your outputs, then unplug or power off one display, and plug it back in. OBS should keep running, and that output should come back by itself.

New in 0.6.3

  • Dock previews at full frame rate. The thumbnails in the Vexel dock now update on every OBS frame (30 or 60 fps), instead of about 10 times a second, so motion looks just like the outputs.
  • Accurate output frame rate. The fps reading in the dock is now measured against the real clock and smoothed. It no longer dips when the OBS interface is busy (e.g. while you drag slices) even though the output is smooth. If an output really falls behind, the reading turns amber and shows the target, e.g. "24 / 30 fps".
  • Measured on macOS: thumbnails 29.9 / 59.9 frames per second at 30 / 60 fps; the fps reading stays within 1 fps of the target while the interface is busy.

New in 0.6.2

  • Updated Vexel logo and banner from the final brand artwork: the V-tile mark (window icon, footer and About) now has eight tiles, cyan to purple. No changes to outputs, rendering or settings.

New in 0.6.1

  • The Vexel dock stays where you put it. It now comes back after an OBS restart exactly as you left it: shown or hidden, docked or floating, same place and size. Before, it could disappear after the first restart. If you closed it yourself, it stays closed (reopen it under Docks ▸ Vexel).
  • On first install, the dock is docked on the right side of the main OBS window instead of opening as a small floating window.

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.3-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.3 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.3-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Vexel 0.6.4 (beta)

Vexel 0.6.4 (beta) Pre-release
Pre-release

Choose a tag to compare

@Jallison154 Jallison154 released this 15 Nov 06:24

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.6.4

  • Fixed: OBS could crash when a display disappeared (unplugged, powered off, or a video switcher dropping its signal), mainly on Windows. When an output's display goes away, the output now stops and hides straight away and is cleaned up safely a moment later. It still comes back by itself when the same display returns.
  • A quick burst of Windows display-change messages no longer makes Vexel give up on an output too early.
  • The test pattern now matches each slice. Every slice gets its own calibration pattern at its exact size and position on the output: red and white edge lines on the slice's outermost pixels, a grid and rulers counted from the slice's corner, corner markers in the slice's colour, and the slice's name, size and position. Areas no slice covers stay black. An output with no slices still shows one full-screen pattern. Output Placement shows the same image.
  • Please check on Windows: start your outputs, then unplug or power off one display, and plug it back in. OBS should keep running, and that output should come back by itself.

New in 0.6.3

  • Dock previews at full frame rate. The thumbnails in the Vexel dock now update on every OBS frame (30 or 60 fps), instead of about 10 times a second, so motion looks just like the outputs.
  • Accurate output frame rate. The fps reading in the dock is now measured against the real clock and smoothed. It no longer dips when the OBS interface is busy (e.g. while you drag slices) even though the output is smooth. If an output really falls behind, the reading turns amber and shows the target, e.g. "24 / 30 fps".
  • Measured on macOS: thumbnails 29.9 / 59.9 frames per second at 30 / 60 fps; the fps reading stays within 1 fps of the target while the interface is busy.

New in 0.6.2

  • Updated Vexel logo and banner from the final brand artwork: the V-tile mark (window icon, footer and About) now has eight tiles, cyan to purple. No changes to outputs, rendering or settings.

New in 0.6.1

  • The Vexel dock stays where you put it. It now comes back after an OBS restart exactly as you left it: shown or hidden, docked or floating, same place and size. Before, it could disappear after the first restart. If you closed it yourself, it stays closed (reopen it under Docks ▸ Vexel).
  • On first install, the dock is docked on the right side of the main OBS window instead of opening as a small floating window.

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.3-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.3 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.3-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Vexel 0.6.3 beta: full-rate dock previews, accurate fps

Choose a tag to compare

@Jallison154 Jallison154 released this 15 Nov 01:34

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.6.3

  • Dock previews at full frame rate. The thumbnails in the Vexel dock now update on every OBS frame (30 or 60 fps), instead of about 10 times a second, so motion looks just like the outputs.
  • Accurate output frame rate. The fps reading in the dock is now measured against the real clock and smoothed. It no longer dips when the OBS interface is busy (e.g. while you drag slices) even though the output is smooth. If an output really falls behind, the reading turns amber and shows the target, e.g. "24 / 30 fps".
  • Measured on macOS: thumbnails 29.9 / 59.9 frames per second at 30 / 60 fps; the fps reading stays within 1 fps of the target while the interface is busy.

New in 0.6.2

  • Updated Vexel logo and banner from the final brand artwork: the V-tile mark (window icon, footer and About) now has eight tiles, cyan to purple. No changes to outputs, rendering or settings.

New in 0.6.1

  • The Vexel dock stays where you put it. It now comes back after an OBS restart exactly as you left it: shown or hidden, docked or floating, same place and size. Before, it could disappear after the first restart. If you closed it yourself, it stays closed (reopen it under Docks ▸ Vexel).
  • On first install, the dock is docked on the right side of the main OBS window instead of opening as a small floating window.

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.3-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.3 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.3-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Vexel 0.6.2 beta: updated logo and banner

Choose a tag to compare

@Jallison154 Jallison154 released this 14 Nov 03:30

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.6.2

  • Updated Vexel logo and banner from the final brand artwork: the V-tile mark (window icon, footer and About) now has eight tiles, cyan to purple. No changes to outputs, rendering or settings.

New in 0.6.1

  • The Vexel dock stays where you put it. It now comes back after an OBS restart exactly as you left it: shown or hidden, docked or floating, same place and size. Before, it could disappear after the first restart. If you closed it yourself, it stays closed (reopen it under Docks ▸ Vexel).
  • On first install, the dock is docked on the right side of the main OBS window instead of opening as a small floating window.

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.2-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.2 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.2-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Vexel 0.6.1 beta: dock stays put across restarts

Choose a tag to compare

@Jallison154 Jallison154 released this 14 Nov 03:17

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.6.1

  • The Vexel dock stays where you put it. It now comes back after an OBS restart exactly as you left it: shown or hidden, docked or floating, same place and size. Before, it could disappear after the first restart. If you closed it yourself, it stays closed (reopen it under Docks ▸ Vexel).
  • On first install, the dock is docked on the right side of the main OBS window instead of opening as a small floating window.

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.1-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.1 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.1-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Vexel 0.6.0 beta: OBS output mapping (formerly Output Mapping)

Choose a tag to compare

@Jallison154 Jallison154 released this 14 Nov 03:02

Vexel: OBS output mapping

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.6.0: Output Mapping is now Vexel

  • New name and look. The plugin is now Vexel: OBS output mapping by Okami Designs. It appears in OBS as Tools ▸ Vexel Output Mapping…, the Vexel dock and Vexel: … hotkeys. The editor has the Vexel style: deep navy, cyan accent, cyan-to-purple buttons, and the V-tile logo (window icon, footer and About).
  • Nothing to set up again. The install folder (output-mapping), your saved mappings and presets, hotkey bindings and the remote-control vendor name are unchanged. Update by replacing the folder as before. The download files keep the output-mapping-… name for the same reason.
  • No changes to video output or rendering since 0.5.3.

New in 0.5.3

  • Changing an output's delay no longer flickers: the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second.

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.6.0-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Vexel 0.6.0 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.6.0-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Output Mapping 0.5.3 beta (Windows + macOS) — smooth delay crossfade

Choose a tag to compare

@Jallison154 Jallison154 released this 14 Nov 02:06

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.5.3

  • Changing an output's delay no longer flickers. It used to play in slow motion (adding delay) or fast-forward (reducing it) until it caught up. Now the output keeps playing at normal speed while the new delay buffers, then crossfades over half a second from the old picture to the delayed one. Turning delay on fades from live; turning it off fades back to live. Safe to adjust during a show.
  • Verified on macOS: blended frames during the change, never a black frame, and the output is pixel-exact afterwards (acceptance test 73/73).

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.5.3-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Output Mapping 0.5.3 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.5.3-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Output Mapping 0.5.2 beta (Windows + macOS) — output health diagnostics

Choose a tag to compare

@Jallison154 Jallison154 released this 13 Nov 07:26

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

New in 0.5.2 (diagnostic build)

  • Output health: each running output's real frame rate is shown in the Output Mapping dock (e.g. "30 fps"). If an output stops drawing for 3 seconds, the dock shows a red ⚠ NOT RENDERING, and the OBS log records it.
  • The OBS log now records when each output's video surface is created (and its size) or fails to be created.
  • If outputs don't appear on Windows: start them, wait 5 seconds, then send the log (Help ▸ Log Files ▸ Upload Current Log File) and say what the dock shows for each display.

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.5.2-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Output Mapping 0.5.2 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.5.2-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later

Output Mapping 0.5.1 beta (Windows + macOS) — dock resize fix

Choose a tag to compare

@Jallison154 Jallison154 released this 13 Nov 07:10

Beta. Built for OBS Studio 33.0.1: Windows 10 (2004+) / 11 x64, and macOS 13+ (Apple Silicon and Intel).

Fixed in 0.5.1

  • Resizing the Output Mapping dock could make it flicker and crash OBS on Windows. The dock's thumbnails no longer use native video windows: they are drawn from GPU-rendered images (~10 fps, same rendering as the real outputs), with a stable layout, so resizing, docking or floating the dock can't disturb OBS. All remaining video-surface resizes (editor previews, outputs) are coalesced and never sized below 2×2 pixels.
  • Please check on Windows: drag the dock's edges around quickly, float it and re-dock it (step E10 in docs/windows-test-plan.md).

New in 0.5.0

  • Output Mapping dock in the main OBS window (Docks ▸ Output Mapping, shown automatically the first time): a live thumbnail of exactly what each display receives (including delay and test patterns), status, and per-display Fullscreen / Window / Clear Pattern buttons, plus Start All, Stop All, Test Pattern All and Editor.
  • Test Pattern and Slice Outlines on the real output (display panel ▸ Identify): a calibration pattern with red + white edge lines (spots overscan/cropping), grid with pixel rulers, corners, centre, display name and slice outlines; or each slice's outline and name over the live video. Per display or on all displays at once. Asks first before taking over a live screen; red ON OUTPUT badges; never saved (always off when OBS starts); also shown in Output Placement so you can fit slices against it.
  • Keyboard commands: Copy / Cut / Paste slices (Ctrl/⌘+C/X/V), Paste Position Only (Ctrl/⌘+Shift+V), Paste Crop Only (Ctrl/⌘+Alt+V), Tab / Shift+Tab, ] / [, H, F2, Esc. Full list under Options ▸ Keyboard Shortcuts.
  • Stop All asks first when outputs are live.

Show-readiness

Verified on macOS with a 30-minute soak at 60 fps (3 outputs; scene changes, delay changes, preset recalls, test patterns and slice edits throughout): 661/661 pixel-exact checks, no crashes, no memory growth, 0.03 % skipped frames, 4.95 ms average render time. Run tools/soak_test.py on your show PC before an event (see README).

To update, replace the existing plugin (Windows: the output-mapping folder; macOS: run the new installer). Your mappings and presets are kept.

Install on Windows

  1. Quit OBS.
  2. Download output-mapping-0.5.1-windows-x64.zip below and extract it (right-click ▸ Extract All…).
  3. Paste C:\ProgramData\obs-studio\plugins into File Explorer's address bar (create plugins if needed) and move the output-mapping folder in, replacing the old one.
  4. Start OBS. The editor footer should read Output Mapping 0.5.1 · © 2026 Okami Designs.

Install on macOS

  1. Quit OBS.
  2. Download output-mapping-0.5.1-macos-universal.pkg below and double-click it.
  3. If macOS says it can't be opened (the installer isn't signed with an Apple Developer ID yet): click Done, then System Settings ▸ Privacy & Security ▸ Open Anyway.
  4. Click through the installer (installs for your user only, no admin password), then start OBS.

Copyright © 2026 Okami Designs · GPL-2.0-or-later