Back to corpus
research notebacklog referencescore 30

Mapping System Update - Complete Guide

The Rekordbox voice control system has been updated with comprehensive command mappings from the full Rekordbox keyboard shortcut catalog. This update includes **450 commands** covering all major DJ operations across both decks.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

The Rekordbox voice control system has been updated with comprehensive command mappings from the full Rekordbox keyboard shortcut catalog. This update includes **450 commands** covering all major DJ operations across both decks. **Before:** - ~60 commands manually curated - Basic transport, loop, and hotcue operations - Limited coverage of Rekordbox features **After:** - **450 commands** from full Rekordbox mapping - **227 Deck 1 commands** (30xx command IDs) - **223 Deck 2 commands** (31xx command IDs) - Complete coverage of: - Transport (play, pause, cue, slip reverse) - Loops (1/2, 1, 2, 4, 8 beat loops + manual loop controls) - Hot Cues (A, B, C, D + clear operations) - Sync & Tempo (beat sync, master tempo, pitch bend, tempo adjust) - Effects (FX slots, parameters) - Mixer (crossfader, EQ, filters) - Library (load tracks, search, playlists) - Sampler (12 slots, playback, pause, sequences) - Grid & Beat (memory cues, beatgrid editing) - Layout (zoom, panels, views) - Recording (start/stop/pause) **Updated Files:** - `gemini_listener.py` - Original Gemini Live listener - `gemini_listener_enhanced.py` - Enhanced listener with Tier 1 optimizations **New Instruction Features:** - Organized by category (Transport, Loop, Hot Cue, Sync/Tempo, etc.) - Comprehensive examples for each category - Clear deck specification (left/right) - Voice-friendly command phrasing - Batch command support (enhanced version only) - Confirmation/cancellation keywords

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.