Mouse configuration

Race review is a lot of play–pause–step–step–step. Doing that from the spare buttons of a many-buttoned mouse — one-handed, eyes on the video — is the point of this feature: map a Razer mouse’s extra buttons to transport actions.

Open it with the mouse button in the toolbar’s tool cluster.

Supported mice, and how they differ

Pick your model from the dropdown. What buttons are available to map depends on the model:

• Razer Viper V3 Pro / Viper V2 Pro / DeathAdder V3 Pro / Cobra Pro / Mamba Wireless — the standard set: two side buttons and the scroll wheel.
• Razer Basilisk V3 Pro — the standard set plus its multi-function paddle.
• Razer Naga V2 Pro — every input across its three swappable side plates: the 12-button grid, the XButton pair and the wheel. Which buttons actually work depends on the plate fitted — see The Naga’s swappable side plates below.
• Razer Naga 2014 — the fixed 12-button thumb grid and the scroll wheel. Unlike the Naga V2 Pro it has no separate back/forward side buttons — the grid fills the thumb area.

The dropdown lists the models alphabetically.

Selecting a model swaps the list of mappable buttons and shows a labelled outline of that mouse, so there’s no guessing which physical button is which. An assignment you made for a button that the current model doesn’t have is kept in the file — switch back to a mouse that has it and it’s still there.

The active mouse — telling the app which mouse this machine has

The dropdown only chooses which model you’re editing. Separately, the app needs to know which model is physically plugged into this machine — that’s the active mouse, and mappings do nothing until one is set.

Tick “Use this mouse on this machine” under the dropdown to make the selected model the active mouse. Exactly one model (or none) can be active at a time — marking one clears any other — and the line beneath always names the one in force, so you never have to click through models to find out. Both are visible in the screenshot above: the box is ticked and the line reads Active mouse on this machine: Razer Naga V2 Pro. The choice takes effect when you Save, immediately, no restart.

Why it exists: the mappings describe what the buttons should do; the active mouse describes what hardware is present. They’re deliberately separate, and the active mouse is stored per machine (in the machine’s local settings, not in the mappings file) — your desktop and laptop can each declare their own mouse.

What it means for playback:

• Only the active model’s buttons act. A button that exists only on some other model — say a Naga side-grid button while a Viper is active — has no effect.
• With no active mouse set, mouse button mappings are entirely inactive. The first time a mapped button would have fired, the status log explains why it didn’t (“No active mouse configured; mouse button mappings are inactive”) — so buttons never just silently stop working.

The Naga’s swappable side plates

The Naga V2 Pro ships with three magnetic side plates, and which one is fitted changes what buttons physically exist — and what Windows receives when you press them:

• 12-button plate — the MMO thumb grid. Windows has no native representation for these buttons: they only reach the app as keystrokes, and only after Razer Synapse is configured to send one per button (button 1 → F13, button 2 → F14, … button 12 → F24). This Synapse setup must be done first — until it is, the grid buttons do nothing anywhere, including in the app’s detection log. The next section walks through it.
• 6-button plate — six thumb buttons in two rows of three. The same story as the grid, just fewer of them: map them in Synapse to F13–F18 and the app sees them as Buttons 1–6.
• 2-button plate — a conventional back/forward pair, which Windows sees natively as XButton1 and XButton2. No Synapse setup needed.

That’s why the Naga V2 Pro’s mapping list offers all of these inputs — Buttons 1–12, the XButton pair and the wheel. It’s the union across the plates: mappings for buttons the fitted plate doesn’t have are kept but simply never fire, and swapping plates changes which mappings are live without touching the configuration.

Why F13–F24? They’re real keys that no physical keyboard sends, so nothing else competes for them — Synapse can fire them without ever colliding with ordinary typing or another application’s shortcuts.

This ties into the active mouse (above): marking the Naga V2 Pro as this machine’s active mouse tells the app to expect exactly this input encoding — grid buttons arriving as F13–F24 keystrokes, the 2-button plate’s pair as XButtons.

The Basilisk V3 Pro’s multi-function paddle is the same story as one grid button: Synapse must send F13 for it. On every model, the ordinary side buttons and the scroll wheel are seen natively and need no setup.

Setting up Synapse: mapping the grid to F13–F24

Before the app can use the 12-button grid, each grid button must be given a keystroke in Razer Synapse — the plate sends nothing Windows recognises as a mouse button, so until this is done the app’s mapping list is useless for the grid: nothing arrives to map. Configure Synapse first, then come back to the app. (The screenshot below shows the Naga Pro; the same flow applies to the Naga V2 Pro, and either one uses the app’s Razer Naga V2 Pro model entry.)

Map the twelve buttons to F13–F24, in order — button 1 → F13 through button 12 → F24. F13–F24 are real keys in the Windows keyboard model that no physical keyboard sends, so nothing else competes for them; Synapse’s default number keys, by contrast, collide with ordinary typing the moment you click into a text box.

Follow along against the screenshot:

1. Open Razer Synapse and select the device’s tab in the top bar — NAGA PRO in the screenshot, between LINKED GAMES and SETTINGS.
2. Make sure CUSTOMIZE is the selected sub-tab (highlighted green in the screenshot), and that the 12-button plate is the one selected in the plate selector along the bottom — the row of four mouse thumbnails; the grid plate is the right-most, shown ticked green. Leave the toggle beneath it on Standard, not Hypershift.
3. Click the grid button to remap — the numbered circles 1–12 flanking the mouse picture. Its editing panel opens on the left, headed with the button’s number (the screenshot has button 1’s panel open).
4. In the panel, choose the Keyboard Function category — the keyboard icon in the panel’s icon strip, as opposed to Mouse Function or Macro. The panel title confirms it: KEYBOARD FUNCTION.
5. Set the category dropdown to Function and the key dropdown below it to the target key — F13 for button 1, exactly as the screenshot shows. Leave Include Modifier(s) and Enable Turbo unticked.
6. Click Save, then repeat for the rest: button 2 → F14, through to button 12 → F24. Done right, the key names sit beside every grid button as in the screenshot — F13–F18 down the left column, F19–F24 down the right.

Your Synapse may not look exactly like this — Razer’s own instructions cover other Synapse versions and other models: https://mysupport.razer.com/app/answers/detail/a_id/5569/

If mapped keys don’t reach the app, check Synapse first: some Synapse versions have had reported issues where remapped buttons only work while Synapse is running, or behave differently on wireless versus wired connections. The app’s detection log (below) tells you immediately whether the keystrokes are arriving — if it sees nothing, the problem is upstream in Synapse, not in the app’s mapping.

Mapping buttons to actions

Each button has a dropdown of player actions:

Play / Pause • Step forward/back one frame • Step forward/back four frames • Forward 2× • Forward 4× • Rewind 2× • Rewind 4× • Set Zero Point • Toggle Lock Mode • Toggle Mute • Skip forward/back 4 seconds • Copy Timecode • Not used

Choose an action per button, then Save — mappings take effect immediately, no restart. They run the exact same code as the on-screen transport buttons. (Remember: they only act once the model is marked as this machine’s active mouse, above.)

The two Skip forward / Skip back 4 seconds actions are special: they exist only here. There is no transport button and no keyboard shortcut for them — a mapped mouse button is the one way to jump four seconds at a time. They behave like any other seek: frame-exact landing, the whole group in Lock Mode (each tile at its own offset) or just the selected tile in Unlock Mode, clamped at the start and end of the timeline, and the paused timecode goes to the clipboard as usual.

Copy Timecode maps the transport button of the same name (chapter 8): one press copies the timecode currently showing to the clipboard — the shared race timeline in Lock Mode, the selected tile’s own file time in Unlock Mode. Like the button, it copies whether or not the automatic clipboard writing is switched on, and doesn’t change that setting either way. With no video loaded it does nothing.

The middle (wheel) click is mappable; left and right are not

The middle button — pressing the scroll wheel — is in the assignable list on every model, alongside the side buttons and the wheel. It’s a handy one to use: it’s under your finger already, and it does nothing else in this application.

Left and right click stay reserved, and always will be. That isn’t an oversight — they’re how the app is operated. Left click selects a tile, Ctrl+left marks a tile for swapping, double-click maximises, and left-drag works the sliders and splitters; right-click opens the Clear-marks menu on Mark Split. Mapping a playback action onto either of those would fight the interface every time you used it. The middle button carries none of that, so there was nothing to conflict with — press it over a tile and it runs your mapped action without also selecting the tile, and over the transport without disturbing the slider.

Where each kind of input works while the app is running:

• Side-plate buttons (F13–F24) — anywhere, as long as the app (or its floating transport window) is the active window.
• The two ordinary side buttons — anywhere over the app window.
• Middle (wheel) click — anywhere over the app window.
• Scroll wheel — only while the pointer is over the video area (elsewhere the wheel does its normal job, such as nudging the volume slider).

Testing without guessing — and the emulator

The test pad on the right resolves inputs live: press a mapped button and the detection log (newest first) shows what was detected and what it’s mapped to — using your current, unsaved edits, so you can try a mapping before committing it.

No Razer mouse to hand? The Mouse Emulator (bottom row of the window) opens a panel of on-screen buttons matching the selected model. It’s for testing the mappings without the physical mouse: it sends real input through Windows, exercising exactly the same path the hardware would, so what you see in the emulator is what the real mouse will do. Its layout rebuilds to match whenever you change the selected model.