Skip to main content

Foot Pedal Setup

Foot pedal support helps reduce keyboard/mouse load for high-volume transcription and spotting workflows. Pedals use hold-to-play by default: press to start an action, release to stop or pause.

Supported pedal integrations​

Closed Caption Creator supports three pedal input sources. Pick the one that matches your hardware and OS.

SourceBest forRequirements
WebHID DeviceGeneric USB foot pedals that expose HID reportsChromium browser with WebHID; permission grant
vPedal (Browser API)vPedal owners who already use the tray appWindows; vPedal 2015API.exe running; window focused
Gamepad / JoystickPhilips Footcontrol USB, vPedal native mode, other game-controller pedalsPedal visible to the OS as a game controller

Prerequisites​

  • A compatible foot pedal is connected.
  • For WebHID: a Chromium-based browser (or host shell) that supports the WebHID API.
  • For vPedal Browser API: Windows, plus the vPedal 2015 API tray application running.
  • For Gamepad / Joystick: a pedal that appears as a game controller (including Philips Footcontrol and vPedal native joystick mode).
  • You have a target control scheme (play/pause, rewind, fast-forward).
  • Pedal configuration: Edit > Options > Foot Pedal Setup
  • Keyboard fallback configuration: Edit > Shortcut Keys

Workflow 1: Choose an input source​

  1. Open Edit > Options > Foot Pedal Setup.
  2. Enable foot pedal control.
  3. Select an Input Source:
    • WebHID Device — generic HID pedals (browser permission required).
    • vPedal (Browser API) — uses Ctrl+Alt+Shift+1–6 from the vPedal tray app.
    • Gamepad / Joystick — polls the Gamepad API (Philips independent pedals, or vPedal combined mode).
  4. Complete the source-specific setup below.

Foot Pedal Setup options

Validation checks​

  • Enable state and selected source persist after save/reopen.
  • Status errors (if any) are shown in the Options panel.

Workflow 2: WebHID device and mapping​

  1. Click Request Device and choose your pedal in the browser picker.
  2. Select the device from the list if more than one is available.
  3. Map report values to actions (value 0 is typically released / idle).
  4. Test each pedal: hold play, hold rewind, hold fast-forward, then release.

Validation checks​

  • Each pedal action triggers the expected playback behavior while held.
  • Releasing the pedal pauses or stops scrub modes.
  • No duplicate triggers after re-enabling control.

Workflow 3: vPedal Browser API​

  1. Install and run vPedal 2015API.exe (desktop shortcut) before opening Creator.
  2. In Foot Pedal Setup, choose vPedal (Browser API) and enable control.
  3. Keep the Creator window focused while using the pedal.
  4. Confirm play / rewind / fast-forward hold behavior.

Official chord map (from vPedal programmer notes):

ChordAction
Ctrl+Alt+Shift+1Play (down)
Ctrl+Alt+Shift+2Play (up / stop)
Ctrl+Alt+Shift+3Rewind (down)
Ctrl+Alt+Shift+4Rewind (up)
Ctrl+Alt+Shift+5Fast forward (down)
Ctrl+Alt+Shift+6Fast forward (up)

Workflow 4: Gamepad / joystick​

  1. Press a pedal once so the OS registers the controller.
  2. Choose Gamepad / Joystick, click Refresh, and select the device.
  3. Choose a Gamepad Mode:
    • Independent buttons (Philips Footcontrol) — each pedal is its own button; remap per button below.
    • Combined buttons (vPedal) — vPedal joystick layout: left = rewind, right = fast forward, center (both) = play.
  4. For Philips Footcontrol USB (0911:1844), defaults are:
ButtonAction
#0Fast Forward
#1Play
#2Rewind
  1. Test each pedal: hold to engage, release to stop.

Gamepad notes​

  • Philips Footcontrol USB (Vendor 0911, products such as 1844 / ACC2300 / ACC2330) is detected as an independent-button device and defaults to the mapping above.
  • If your pedal reports buttons in a different order, change the mapping in the Gamepad panel — no reload required.
  • Gamepad mode requires the browser window to stay focused / visible.

Workflow 5: Pair with keyboard shortcuts​

  1. Configure core keyboard shortcuts in Edit > Shortcut Keys.
  2. Reserve the pedal for transport controls; keep text-edit controls on the keyboard.
  3. Hotkey pedals (for example Philips ACC2310 / ACC2320) continue to work via Shortcut Keys — bind Toggle Playback / Fast Forward / Rewind as needed.

Validation checks​

  • Operators can sustain playback/edit workflow without frequent remapping.
  • Playback remains controllable while editing event text (vPedal Browser API chords are handled globally).

Troubleshooting​

Pedal device not listed (WebHID)​

  • Reconnect the device and click Request Device again.
  • Confirm the browser supports WebHID and that permission was granted.

vPedal chords do nothing​

  • Confirm vPedal 2015API.exe is running.
  • Confirm Creator is the focused window.
  • Confirm Input Source is set to vPedal (Browser API) and control is enabled.

Gamepad not detected​

  • Press a pedal button, then click Refresh.
  • Confirm the device appears in an online gamepad tester.
  • On Philips Footcontrol, verify it shows as Footcontrol USB under Windows Game Controller settings.

Wrong actions in Gamepad mode​

  • Switch Gamepad Mode between Independent buttons and Combined buttons.
  • If actions are still wrong, remap button indices in the mapping table.

Pedal works initially but not after restart​

  • Re-verify enabled state and source in Options.
  • For WebHID, accept the startup permission prompt when asked.