AudionAudion

Audion TourBox Elite Map — Working Specification

Audion_TourBox_Elite_Apps_Map.md

Audion TourBox Elite Map — Working Specification

Status: planning / pre-Codex implementation Purpose: collect the applications, preset names, command sets, motor-memory rules, and unresolved items already discussed for the Audion TourBox Elite setup.

This document is intentionally a working specification, not a finished .tb pack.
Codex should use it together with the YongHee-Kim/tourbox-preset project, real TourBox Console exports, and live application testing.

1. Core design doctrine

The controller should not be filled with shortcuts merely because they exist. Prefer actions that benefit from a physical rotary, repeated stepping, or one-handed navigation.

Highest-value action classes

  1. Rotate / adjust
  1. Browse / cycle
  1. Repeat

Motor-memory vocabulary

ControlPreferred semantic role
ScrollScroll or zoom continuous content
DialHorizontal movement or cycling major peer objects
KnobLocal cycling / local parameter / markers
Knob PressCreate/confirm/toggle the thing controlled by Knob
D-padPrecise discrete navigation
C1 / C2Logical left/right pair, previous/next, or Undo/Redo
TallPrimary action / Play / Enter
ShortStop / Esc / Cancel
SideSecondary functional layer
TopView / Focus / Zoom-to-context
TourTourMenu for useful but less frequent commands

This is a guideline, not a hard rule. When two mappings are equally good, prefer the one consistent with this vocabulary.


2. Proposed preset naming and numbering

Core set

IDPreset
00Windows — Global
10Browser — General
11Browser — ChatGPT
20Office — Word
21Office — Excel
22Office — PowerPoint Show
23MapInfo — Map & Layout
30Dev — VS Code
31Dev — Notepad++
32Files — Total Commander
40Media — PotPlayer
41Media — foobar2000
50Audition — Waveform
51Audition — Multitrack
52REAPER — Edit
53REAPER — Mix (optional / only if useful)
60Premiere — Edit & Motion
61Premiere — Lumetri
70Lightroom — Develop
71Lightroom — Library
80Resolve — Color
81Resolve — Edit (optional)

Naming rule

Use:

Application — Mode

Avoid names such as:

Version the pack/repository, not the human-facing preset name.


3. Preset command maps


00 Windows — Global

Purpose: safe fallback when no application-specific preset is active.

Base layer

ControlAction
ScrollVertical scroll
D-padArrow keys
C1Undo
C2Redo
TallEnter
ShortEsc
TopFind

Candidate / not yet final

Windows TourMenu

Rule: Global must be conservative. No dangerous or surprising commands.


10 Browser — General

Purpose: Chrome / Edge / Firefox / generic browser navigation.

Base layer

ControlAction
ScrollScroll the control/area currently under the mouse pointer
Dial ← / →Previous / Next tab
Knob ← / →Back / Forward browser history
Knob PressFocus address bar
TallEnter
ShortEsc
TopFind
C1Reopen closed tab
C2Close current tab

Side layer

ControlAction
Side + ScrollHorizontal scroll
Other Side combosReserve for browser utilities after testing

Browser TourMenu

Design note

Do not spend the main Dial on ordinary scrolling. Scroll already naturally targets whatever scrollable web area is under the pointer.


11 Browser — ChatGPT

Purpose: preserve Browser motor memory but add ChatGPT-specific management.

Inherit from Browser — General

ChatGPT command set

Desired commands:

Preferred implementation

Avoid fixed screen-coordinate mouse macros.

Preferred architecture:

TourBox shortcut → browser userscript/extension → ChatGPT DOM action

Possible stable internal shortcuts:

These should be implemented only after Codex inspects the live ChatGPT UI and builds a resilient bridge.


20 Office — Word

Status: application selected, command map not yet deeply designed.

Already identified useful domains:

Codex task: observe actual Word usage before assigning valuable physical controls. Do not fill the preset with generic Ctrl+C / Ctrl+V / Ctrl+S unless there is a real ergonomic reason.


21 Office — Excel

Purpose: large-sheet navigation, especially horizontal work.

Current preferred design

ControlAction
ScrollVertical scroll
Dial ← / →Horizontal viewport movement
Knob ← / →Move active cell left/right across columns
Side + KnobZoom ±
D-padCell navigation
Side + D-pad ← / →Jump by data block (Ctrl+← / Ctrl+→ behavior)
Side + D-pad ↑ / ↓Jump by data block (Ctrl+↑ / Ctrl+↓ behavior)
C1Undo
C2Redo
TallEnter / confirm cell edit
ShortEsc
TopFind

Important decision

Do not spend Dial on Previous/Next Worksheet. Typical workbooks here are overwhelmingly single-sheet.

Excel TourMenu

A/B test candidate

Alternative:

Test with real wide office spreadsheets and keep whichever feels more natural.


22 Office — PowerPoint Show

Purpose: slideshow/presenter keyboard functions, not slide editing.

Base layer

ControlAction
Dial ← / →Previous / Next slide or animation step
Dial PressAll Slides / slide navigator
ScrollScroll speaker notes in Presenter View
TallStart slideshow from current slide
TopStart/open Presenter View
ShortEsc / End Show
C1Black screen
C2White screen
D-pad ← / →Previous / Next
D-pad ↑First slide
D-pad ↓Last slide

Side / presenter utility layer

Philosophy

A normal presentation clicker still handles basic Next/Previous while standing away from the PC. TourBox should mainly replace the keyboard-only presentation commands when seated at the workstation.


23 MapInfo — Map & Layout

Purpose: map/layout navigation and frequently buried output commands.

Base layer

ControlAction
ScrollZoom In / Out
Dial ← / →Pan left/right
D-padPan ↑↓←→
TopContextual “show all”: View Entire Map / Fit Layout in Window
TallSelect
ShortEsc
C1Previous View
KnobCandidate: view/history cycling; verify in live use

Required special commands

MapInfo TourMenu

Close All

Required.

Preferred implementation:

TourBox → dedicated safe shortcut → MapBasic/MBX → Close All Interactive

Avoid accidental invocation. Use a protected combo such as Side + a secondary button or another deliberate combination.

Export Active Window

First try to expose the MapInfo internal command through Command Editor / custom shortcut / MapBasic. Use mouse-coordinate automation only as a last resort.


30 Dev — VS Code

Purpose: navigation and repeated IDE actions.

Base layer

ControlAction
ScrollScroll code
Dial ← / →Previous / Next editor tab
KnobZoom or local navigation; final choice after testing
Side + KnobPrevious / Next problem
D-pad ← / →Navigate Back / Forward
D-pad ↑ / ↓Previous / Next problem or symbol
TallCommand Palette
TopQuick Open
ShortToggle Terminal
C1Undo
C2Redo

Dev TourMenu

Philosophy

Prioritize tab/symbol/problem navigation over already-fast keyboard basics such as Copy/Paste.


31 Dev — Notepad++

Status: useful but lower priority than VS Code.

Candidate map

Useful commands


32 Files — Total Commander

Purpose: file/panel navigation and repeated file operations.

Base layer

ControlAction
ScrollScroll file list
Dial ← / →Previous / Next tab
KnobDirectory history or drive cycling; decide after testing
D-padMove selection through files
TallEnter
ShortUp one directory
C1Back history
C2Forward history

Utility commands

Philosophy

Do not waste the best buttons merely duplicating Total Commander’s already excellent F5/F6/F7/F8 keyboard workflow unless the physical controller proves faster in practice.


40 Media — PotPlayer

Status: key time-navigation hierarchy is approved.

Approved temporal hierarchy

ControlAction
Knob ← / →−1 / +1 frame
Dial ← / →−5 s / +5 s
Side + Dial ← / →−30 s / +30 s

This gives three scales:

frame → seconds → tens of seconds

Other approved / strong candidates

ControlAction
Knob PressPlay / Pause
ScrollPotPlayer volume
Side + ScrollWindows master volume
TopFullscreen
ShortMute or Esc from Fullscreen

Frame-step rule

PotPlayer QC TourMenu

Reserve

C1/C2 and D-pad should be assigned only after real usage shows whether audio/subtitle stream switching, file navigation, or another QC action is more valuable.


41 Media — foobar2000

Priority: optional / useful because Elite is already present, not a reason to buy Elite.

Candidate map

TourMenu


50 Audition — Waveform

Purpose: waveform navigation, markers, selections, range surgery.

This is the primary Audition preset.

Base layer

ControlAction
Dial ← / →Horizontal waveform pan
ScrollHorizontal Zoom
Knob ← / →Previous / Next Marker
Knob PressAdd Marker
D-pad ← / →Fine CTI/playhead movement
C1 / C2Left / Right selection-boundary operations
TallPlay / Stop
ShortClear / Deselect
TopZoom to Selection / Zoom Out Full
SideSelection/Range layer
TourWaveform command menu

Selection / Range layer

Desired operations:

Important verification

Codex must test the current Audition version for:

Do not assume old Adobe shortcuts are stable.

Range Marker alternative

Evaluate two workflows:

  1. Point markers + build selections on demand
  2. Range markers as first-class editable regions

Keep whichever is faster for real waveform editing.


51 Audition — Multitrack

Purpose: DAW/timeline mode, separate from Waveform.

Base layer

ControlAction
DialHorizontal timeline pan / scrub
ScrollHorizontal Zoom
KnobPrevious / Next track or marker
Knob PressAdd Marker
D-pad ← / →Nudge / playhead
D-pad ↑ / ↓Track up/down
TallPlay / Stop
TopRecord
C1 / C2Undo/Redo or Previous/Next Marker
SideClip-edit layer
TourMultitrack command menu

Side / clip layer

Preset switching

Waveform and Multitrack should be two distinct presets with similar motor semantics.

Do not cram Multitrack into modifiers of the Waveform preset.


52 REAPER — Edit

Status: useful candidate, less finalized than Audition.

Candidate base

Buttons

Utility layers


53 REAPER — Mix

Optional.

Create only if real use justifies a separate mix-mode preset.

Potential domains:

Do not create it merely to fill the preset list.


60 Premiere — Edit & Motion

Purpose: effects-heavy Premiere workflow, Motion, keyframes, timeline navigation.

High-priority Motion parameters

Keyframe command set

Editing/navigation commands

Implementation note

Premiere exposes some keyframe operations poorly through normal shortcuts.

Preferred implementation order:

  1. native Premiere shortcuts
  2. TourBox macro
  3. stable AHK/UI automation
  4. fixed coordinate click only as last resort

61 Premiere — Lumetri

Purpose: Curves + Wheels, Luma-centric, fine adjustment by default.

User workflow assumptions

Precision hierarchy

Curves mode

ControlAction
DialFine mouse Y movement
KnobFine mouse X movement
ScrollLumetri panel scroll
Dedicated Drag buttonLMB hold while moving selected curve point

Useful buttons:

Wheels mode

ControlAction
DialFine puck movement X
KnobFine puck movement Y
Dedicated Drag buttonLMB hold
ScrollLumetri panel scroll

Principle

Do not create hard-coded “S-curve” buttons. Preserve manual, fine Luma shaping.


70 / 71 Lightroom — Develop / Library

TourBox supports workspace-aware grouped presets for Lightroom; prefer the official .tbg group model where practical.

Develop

Candidate main controls:

Buttons:

Secondary parameters:

Utility:

Library

Priorities:


80 Resolve — Color

Purpose: minimal “survival” preset. Resolve is necessary, not the preferred environment.

Base layer

Buttons

Utility

Precision

Prefer fine control; keep the profile intentionally small.


81 Resolve — Edit

Optional.

Create only if actual use justifies it.

Do not build a large Resolve ecosystem by default.


4. Cross-application patterns already worth standardizing

Local vs system volume

Where applicable:

Candidate applications:


Horizontal workspace rule

When the application is fundamentally a horizontal workspace:

Browser is the main exception because Dial is more valuable for tab cycling.


“Show me everything” rule

Prefer Top for context-wide view commands:


5. TourBox preset implementation notes

Existing reverse-engineering project

Use:

YongHee-Kim/tourbox-preset

Purpose:

CLI:

tbtool

The project already understands:

Known gaps

Our calibration contribution already discovered

From controlled TourBox exports:

These should be independently verified against the project tests before use.


6. Codex implementation rules

Codex should not immediately generate the whole pack.

Recommended sequence:

  1. Clone/install YongHee-Kim/tourbox-preset.
  2. Decode the supplied Audion test .tb files.
  3. Confirm encode → decode/round-trip with TourBox Console.
  4. Build a readable source directory for presets.
  5. Implement one application at a time.
  6. Import into Console.
  7. Test on the actual Elite.
  8. Record subjective feedback.
  9. Revise the JSON source.
  10. Generate final .tb files only after each profile stabilizes.

Source-of-truth idea

Keep human-readable mappings in Git, e.g.:

Audion-TourBox-Elite/
├── presets/
│   ├── 00-windows-global.json
│   ├── 10-browser-general.json
│   ├── 11-browser-chatgpt.json
│   ├── 21-office-excel.json
│   ├── 23-mapinfo-map-layout.json
│   ├── 40-media-potplayer.json
│   ├── 50-audition-waveform.json
│   ├── 51-audition-multitrack.json
│   ├── 60-premiere-edit-motion.json
│   └── 61-premiere-lumetri.json
├── generated/
│   └── *.tb
├── Docs/
│   └── Audion_TourBox_Elite_Map.md
└── tools/

The JSON is the editable source. The .tb is a generated artifact.


7. First implementation priority

Recommended first wave:

  1. 40 Media — PotPlayer
  2. 50 Audition — Waveform
  3. 21 Office — Excel
  4. 23 MapInfo — Map & Layout
  5. 10 Browser — General
  6. 11 Browser — ChatGPT
  7. 60 Premiere — Edit & Motion
  8. 61 Premiere — Lumetri
  9. 30 Dev — VS Code
  10. 51 Audition — Multitrack

These profiles already have the clearest real-world requirements and should teach us most of the remaining TourBox implementation details.


8. Current “approved” mappings

These should not be changed casually.

PotPlayer

Audition Waveform

Excel

Browser

Premiere Lumetri


9. Items intentionally left unresolved

These need real-device or real-application testing:


Working project name: Audion TourBox Elite Map

Suggested generated pack name: Audion_TourBox_Elite_Presets

Suggested source document name: Audion_TourBox_Elite_Map.md

Alle Projekte