Description:
Provide a single “Inspector” window that lists every mapping and action in a project—MIDI/Keyboard/OSC bindings, widget targets, follow actions, and related modifiers—in one searchable, filterable table with inline edit, jump-to, enable/disable, and delete.
Problem:
As projects grow, mappings are scattered across widgets, pages, and scenes. Debugging doubled triggers, stale bindings, or unexpected follow actions requires hunting through multiple editors. Orphaned/duplicate mappings are hard to spot, and bulk cleanup is slow and error-prone.
Proposed Solution:
Add a global Inspector panel with:
  • Unified table:
    Columns for Source (device/channel/CC/note/keystroke/OSC), Scope (global/page/widget), Target, Action, Conditions, Mode, Notes, and Last Trigger time.
  • Search & filters:
    By device, channel, CC/note range, action type, scope, page, or widget.
  • Inline operations:
    Edit target/action, toggle enable, duplicate, or delete (with undo).
  • Jump-to source/target:
    Select a row to focus the corresponding widget or page.
  • Conflict/orphan detection:
    Highlight duplicates and broken references; quick “Fix/Remove” tools.
  • Live monitor:
    Real-time event view to see which mapping fired and why.
  • Export/Import:
    Optional CSV/JSON export for documentation or sharing.
Benefits:
  • Rapid debugging of mappings and follow actions.
  • Safer refactoring with conflict and orphan warnings.
  • Faster setup via bulk edits and consistent oversight.
  • Greater transparency for complex performance templates.
Examples:
  • Find and delete a stray CC7 mapping causing double volume changes.
  • Filter to “Follow Actions” to audit what triggers after clip end.
  • Temporarily disable all keyboard bindings during rehearsal.
  • Export all mappings for a tech rider or for version control notes.
This summary was automatically generated by GPT-5 Thinking on 2025-08-20.
Original Post
An Ableton style window that shows all Midi bindings, followed actions etc for quick debugging / deleting.