Feature Requests: 9 possible Enhancements for ANTICATER VK-01

VK-01
1

Hi everyone,

After a deep dive into the current software and hardware capabilities, I’ve compiled a comprehensive list of features that i think are missing.

1. Advanced Input Triggers: Double Click & Long Press

  • Feature: Dedicated assignments for Double-Click and Long-Hold (e.g., 3 seconds) of the encoder button.
  • Why: This adds two additional layers of functionality without needing extra buttons.
  • Use Case: Single click for ‘Play/Pause’, Double click for ‘Next Track’, Long-press (e.g., 3 seconds) for ‘Previous Track’.

2. Profile Management & Visual Feedback (LED Integration)

  • 2.1. Multiple Onboard Profiles: Ability to save 3-5 distinct profiles directly to the device memory.
  • 2.2. LED Color Coding: Assign a specific LED color to each profile.
  • 2.3. Portable Switching: Use for example a Long-Press (3s) to cycle through profiles. The LED changes color to indicate the active mode (e.g., Red = Gaming, Blue = VideoEditing, Green = Coding).
  • Why: This makes the device truly portable and functional on systems where the configuration software is not installed.

2.5. Automatic Context Awareness (App-Specific Profiles)

  • Feature: The software should detect the active window (e.g., VSCode or DaVinci Resolve) and auto-load the corresponding layout.
  • Why: Eliminates the friction of manual switching during a multitasking workflow.

3. Dynamic “Speed Sensitivity” (Acceleration Curve)

  • Feature: Implementation of velocity-based input for the rotation.
  • Logic: Slow rotation = frame-by-frame precision. Fast rotation = large jumps (e.g., 10-second seeks or scrolling hundreds of lines).
  • Why: Linear scrolling is often too slow for long-distance navigation and too imprecise for detail work.

4. Advanced Macro Logic: “Release” Events & Virtual Holds

  • Feature: Ability to trigger commands upon releasing the button (Key-Up events).
  • Use Case: “Hold-to-Action” functions like Push-to-Talk or “Hold-to-Zoom” where the action stops as soon as the physical button is released.

5. Debounce Settings (Click-Through Prevention)

  • Feature: Adjustable “Debounce Time” in milliseconds for both the rotation and the click.
  • Why: Mechanical encoders can sometimes suffer from ghost-clicks or jitter. This ensures high-end precision and hardware longevity.

6. Professional “J-Shuttle” Seek Logic

  • Feature: Native “Seek +/- 5 seconds” or “Seek +/- 10 frames” commands.
  • Why: Essential for video editing and daily content consumption (YouTube/Podcasts).

7. Multi-Step Macro Chains with Delays

  • Feature: Sequence multiple commands with millisecond delays (e.g., Ctrl+S → 100ms Delay → F13).
  • Use Case: A single click to “Save Project & Open Render Queue.”

8. Radial Menu & API Support

  • Feature: Trigger a circular UI menu around the mouse cursor. Rotate to select, click to confirm.
  • Developer Shortcut: If a native Radial Menu is too complex to build, maybe provide a Websocket or API output so third-party tools (like AutoHotkey or Steam Deck software) can listen to the encoder’s position and handle the UI. Or add direct support for a multiplatform radial tool like the Open Source tool “Kando”.

9. Incremental vs. Absolute Input Mode

  • Feature: Toggle between relative scrolling (like a mouse wheel) and absolute value mapping (0-100%).
  • Why: Crucial for precise slider control in Color Grading or System Volume where you want a defined start and end point within one full rotation.

Suggested Presets & Default Shortcuts

  • Panic Button: Native command for “Show Desktop” (Win + D) combined with “Mute All”.
  • Window Snap Management: Commands for Win + Arrow Keys to nudge windows or “Press + Rotate” to move windows between monitors.
  • Creative Suite Logic: Global “+/- 1%, 5%, 10%” logic. Useful for Font-Size in VSCode or Clip Gain in Resolve.
  • Terminal Precision: Presets for line-by-line scrolling and code folding.

The hardware feels great, but these software enhancements would unlock its true potential! Looking forward to hearing the community’s and developer’s thoughts.

2

Thank you very much for your suggestions and support. I have compiled my responses to the questions you raised and will address the requirements you mentioned.

  1. Advanced Input Trigger: Double-click and Long-press.

Our default function includes press-to-rotate, which conflicts with long-press, and double-click and press-to-mute.

Adding these two functions would require a dual encoder.

2.1 Configuration File Management.

I think this can be understood as layers. Layering requires additional recognition, and adding layers requires additional screens to improve the experience. Otherwise, it’s not very meaningful.

2.2 LED Color: This corresponds to each button. A knob cannot address this issue specifically. A keyboard would be easier to implement.

2.3; 2.5; 3; 4.5; 6.7 represent significant challenges in implementing on a knob with higher hardware and software requirements.

8.9 Regarding this feature requirement, I understand that we have a partner development team that has released a separate driver version for this feature. You can follow up on its later improvements, which I will release later. It has been adapted for our Anticard product.