Community Report 2025-09-21 - Per‑Note Pans, Plugin Pains, and Valhalla Gains
On the stable side, users traded practical tips: identifying CLAP plugins, per‑note panning in Hive, arranger clip-lock workarounds, and hardware sequencing/bounce strategies. Troubleshooting dominated with NI plugin ID migrations and a HW Instrument monitoring quirk. Power users
Bitwig Community Report 2025-09-21 #
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.
Identifying CLAP Plugins and Per‑Note Panning in u‑he Hive #
Users asked how to confirm CLAP usage and how to stereo‑spread chord notes. Tips: CLAP versions expose Bitwig note expressions like Pan; you can modulate Hive’s pan per voice and sequence note‑by‑note placement with Steps or ParSeq‑8 in Note Advance mode.
HW Instrument Monitoring vs Audio Tracks #
A report noted that monitoring couldn’t be disabled on a track routed via HW Instrument, while a plain audio track allowed disabling. The thread flagged this behavioral difference without a definitive workaround.
Migrating Old Projects with Kontakt/Reaktor ID Changes #
Opening older projects showed “missing” NI plugins due to device ID changes (Kontakt/Reaktor). Suggestions included checking with NI for migration tools or installing legacy versions to bridge the gap; otherwise, manual replacement may be necessary.
Locking Clips in the Arranger (Workarounds) #
Bitwig currently lacks a clip‑lock feature. A common workaround is consolidating the entire track from bar 1 so accidental moves are easier to correct; users noted alias clips in v6 may complicate this approach, but it still helps in many cases.
Hardware Sequencing Workflow and When to Bounce #
For hybrid hardware setups, users debated keeping MIDI “just in case” versus committing to audio. One viewpoint favored frequent bouncing to avoid second‑guessing and to enable comping/portable work, keeping MIDI only when truly needed.
Classic LFO vs LFO Device #
Classic LFO is a legacy device retained for backward compatibility. While functionally superseded by the modern LFO, it remains visible to ensure old projects load intact rather than auto‑converting parameters.
Browser‑Based Control via Web MIDI (Controllerism) #
A proof‑of‑concept allows controlling Bitwig from a web browser using Web MIDI SysEx and a custom controller extension. Dev notes recommended using a “dirty pattern” and updating state in flush to ensure properties are synced.
Quick Tip: Finding the Inspector #
Newer users asked where the Inspector is. It’s the side panel (toggle with the “i” key); on default layouts it’s on the left, and on small‑screen layouts it’s grouped with the right‑side panels.
Linux Tip: Installing Bitwig on openSUSE #
For openSUSE users, alien can convert Bitwig’s .deb to .rpm. Install via “sudo zypper in ./bitwig-
MOTU/Moto Control Experiences #
A user sought experiences integrating Moto/MOTU control with Bitwig to revamp their workflow. The thread did not yet yield concrete configurations or reports.
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.
Post‑Stop Editing Crash in Bitwig 6 Beta #
Multiple users reproduced a crash when stopping playback and immediately adding/deleting/moving an automation point or MIDI note. A theory suggested the engine mishandles changes to “active” automation values; users were encouraged to file detailed bug reports.
RAM Usage and Large Project Performance #
One producer on a ~500‑track project reported RAM spikes that dropped dramatically after using a memory cleaner, with Kontakt and Kirchhoff EQ implicated alongside Bitwig’s audio engine. Discussions covered sandboxing levels (higher isolation can increase RAM), Kontakt streaming/cache settings, bouncing to stems, Windows 10/11 LTSC flavors, and OS comparisons (macOS/Linux audio stacks vs Windows), with mixed experiences about Fabfilter/UI lag.
Valhalla VST3 Plugin Sleep CPU Spikes (b3) #
On Bitwig 6 beta 3, Valhalla Delay/Supermassive VST3 showed 100% CPU spikes when plugins were suspended/unsuspended; the issue didn’t occur in 5.3 or with sleep disabled, and was reproducible on Windows and Apple Silicon. Workarounds included disabling plugin sleep per device (Inspector > Suspend: Never, then save as default) or switching to VST2, with historical notes about Valhalla VST3 automation quirks and Bitwig logs showing misbehavior in some plugins; similar UI/parameter issues were cited for other VST3s (e.g., Softube Model 80).
Feature Requests: View‑Specific Visibility and Pinned Master #
Requests surfaced to hide FX tracks in the Arranger while keeping them visible in the Mixer, and to pin the Master channel in the Arranger alongside global automation. Users felt these would streamline mixing and global control.
Automation and Editing UX Notes #
Users praised tempo automation’s floor/ceiling scaling in v6 for better lane precision versus BW5. Others recommended using a “button” parameter for small, precise automations (e.g., ±1–2 dB, tempo nudges). A brief aside covered pen tool context behavior.
Miscellaneous Beta Chatter #
Keymaps were reported as getting wiped when switching between beta and stable. A question was raised about Minimmeters settings recall. The community shared new color palettes and discussed plugin sleep detection edge cases (e.g., long delays) and when to disable sleep per plugin.