Community Report 2025-10-07 - Hot GPUs, Cold Meters: Piano Roll Gripes, Grid vs Loopers, and Controller Conundrums
Beta chatter focused on piano roll instability, grouped automation quirks, and unusually high GPU usage on macOS Tahoe, alongside crash fixes between betas. Users shared bug-report templates and tips like adjusting tempo automation ranges via dragging. Stable channels discussed c
Bitwig Community Report 2025-10-07 #
This page summarizes recent discussions in the Bitwig Community Forums and Beta forums, highlighting user questions, solutions, and workflow tips. This is updated periodically as new topics arise.
Audio/MIDI Device Issues and VCV Rack Plugin Host Errors #
- Push with a Bitwig extension: users struggled to record MIDI despite lights/sound, with ASIO driver selection and device presence warnings; switching to ASIO helped some, but MIDI still didn’t print until restarting.
- A Windows 11 user reported VCV Rack VST throwing “Plugin host died: Broken pipe” irrespective of Bitwig version, potentially pointing to audio driver/host issues with WASAPI post-upgrade.
Can the Grid Replace Buffer Loopers/Delays? #
- Consensus: while much is possible, working with audio buffers in Grid is currently clunky; Mod Delay covers part of the ground, but dedicated plugins (e.g., Sandman Pro) offer a better experience and sound for granular/looper tricks.
- UI/sonic critiques surfaced for a new looper plugin; broader plugin-sale nostalgia emerged around PA deals and coupon stacking.
Controller Mapping Portability and Scripts #
- Users want mappings to react to “any” controller rather than specific device ports; current behavior prefers specific scripts/ports for reliability.
- Suggestions: use Remote Controls, the Generic Keyboard/Controller scripts, rename controllers in Bitwig, or explore Flexi Extension for flexible mapping; be mindful that losing/renaming ports can break mappings due to IDs/names.
Live Vocals Latency: Buffer and Sample Rate #
- Lower buffer and higher sample rate reduce roundtrip latency but raise CPU/GPU demands; questions remain whether modern laptops can sustain 64-sample @ 96 kHz on moderate sets and how FFT-based tools scale with sample rate.
Feature Requests and Workarounds #
- Request: audition tool should temporarily solo the pointed track (possibly via toggle/modified key); on Windows, an AHK script can emulate an improved audition flow.
Grid Deep Dive: Boids/Swarm and Voice Interactions #
- Boids in Grid are conceptually possible but hampered by display/voice interaction limits; comparing values across voices is doable via voice-stack tools but becomes complex.
- Clarified behavior: Voice Toggle outputs only on the enabled voice; using Poly > Mono helps aggregate for cross-voice comparisons/metrics.
Mixer RMS Meter Fades When Devices Sleep #
- Report: on 5.3.13 (and also observed in v6 beta), RMS meters on instrument lanes blank immediately when devices sleep; when devices are kept visible/awake, meters fade out smoothly. Expectation: fade should persist even when sleeping if performance allows.
Transport Behavior from the Blue Triangle #
- To restart from the playhead with Space, bind Space to “Play or Stop Transport.” Users confirmed this restores the expected “return to blue triangle” behavior.
Production Feedback and Light Banter #
- A disco/house sketch received encouragement to finalize with subtle evolutions.
- Sound-design chat veered playful (balloons vs bass) and mused about using impulse responses for de-reverb.
Off-Topic: The State of the Web #
- Reflections on fragmented, algorithmic “dead internet” vibes; encouragement to build grassroots communities off social media, acknowledging effort but citing success stories.
Bitwig Beta Corner #
If there is a BETA version available, users are encouraged to test new features and report bugs in the Beta forum. Here are some recent topics.
Piano Roll View Resets and Multi‑Track Editing Pain #
- Multiple users reported the piano roll view unexpectedly resetting (e.g., after adding automation, device tweaks, or UI changes), making multi-track writing/large orchestrations cumbersome; belief that devs may not be stress-testing orchestral/multi-track workflows.
Tempo Automation Range Tip #
- Confusion over BPM automation limits (63–150) was resolved: you can extend the range by click‑dragging vertically on the scale to customize it.
Bug Reporting Template and Best Practices #
- Shared guidance: email beta@bitwig.com with steps to reproduce, expected vs observed, OS/hardware, and whether it’s new in 6.0; attach short screen captures and send crash reports with comments.
Crashes While Editing Automation (Beta 3 → 4) #
- Frequent crashes reported while editing automation in the piano roll (e.g., with Pianoteq 6). Several users said Beta 4 reduced or resolved crashes; advice was to upgrade to the latest beta rather than stay on older builds.
High GPU Usage and Hot Macs on Tahoe #
- Multiple Apple Silicon users on macOS 15 (Tahoe) observed elevated GPU usage and heat, sometimes hitting ~100% GPU even on empty projects; speculation about graphics redraw issues/regressions.
Grouped Track Automation Confusion #
- Users noted confusing automation behavior on grouped tracks; devs acknowledged the issue and are investigating.
Saving/Export Not Applying #
- One user experienced Save/Export silently failing after a while (progress lost after restart), while others couldn’t reproduce. Some noted “press save twice” moments and that saving can spike resources at unlucky times; recommendation to save often until fixed.
Scrollbar Flicker, Zoom Resets, and Crashes #
- Reports of editor scrollbar flashing and zoom level resetting seemingly on spurious events, occasionally leading to crashes.
Missing Global Plugin Window Toggle #
- Request to toggle all currently visible plugin windows on/off (like Logic); not currently available, with speculation it’s either nontrivial or encumbered.
Clip Overdub Still Not Working for Some #
- Users lamented that clip overdub remains broken/ignored in recent betas and that the backlog of unfixed bugs is long.
Project Tempo Automation Inconsistencies #
- Observed inconsistency: project tempo automation lacks curve editing found elsewhere; users found this odd even if musical utility is debatable.