Community Report 2025-10-05 - Waveform Ghosts, Scale-Degree Dreams, and GNOME Keyboard Gremlins — Meanwhile, Betas Battle Stuck Notes and Step Input
In stable channels, users debated strange waveform rectangles that look like DC offset ghosts and how best to report them. Folks shared workflows for slicing audio into separate files, asked about missing Layers in the editor, and noted velocity curves feeling non‑linear. Linux u
Bitwig Community Report 2025-10-05 #
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.
Waveform Rectangle/DC Offset Display Artifacts #
Several users saw bold rectangular blocks in otherwise silent regions of audio and automation, with meters showing nothing. A spectrum analyzer was suggested to rule out true DC offset, but the consensus leaned toward a rendering bug from pre‑6.0 builds. Participants reminded each other this is a community server and official bug reports should go by email.
Note Velocity Perception Feels Non‑Linear #
One user reported 50% velocity being nearly inaudible and needing ~90% to sound like half volume. No definitive solution emerged; it likely depends on the instrument’s velocity curve and patch dynamics rather than a global setting.
Strumming Notes in the Piano Roll (Manual Workflow) #
To manually strum chords, users recommended holding Shift to temporarily disable the snap grid while nudging notes. A side suggestion proposed enhancing the eraser tool with modifier functions for smarter trimming; others urged filing feature requests via email.
Where Did Layers Go in the Piano Roll? #
A user asked how to view notes from multiple instruments at once (“Layers”). In the stable channels, no clear step‑by‑step answer surfaced; participants hinted at changes tied to the large editor and encouraged checking the bigger editor views and menus.
Slicing to Separate WAVs (Workflow) #
For turning an audio file into individual slice WAVs: slice in place, bounce, then locate the bounced pieces in the right‑side file browser and drag them into Drum Machine pads. This approach creates separate files per slice you can reuse.
MIDI Clock Slave Tightness (Question) #
A user asked about experiences slaving Bitwig via MIDI for tight sync, referencing older KVR threads with promising results. No detailed setup steps or confirmations were provided in the day’s stable chat.
Grouped MIDI Tracks with No Sound (Routing Issue) #
One poster added instruments to two grouped MIDI tracks but heard no audio. The thread didn’t reach a confirmed cause; likely a routing or group device chain configuration issue needing project‑specific inspection.
GNOME Keyboard Input Stops Working (Linux) #
On GNOME, some reported Bitwig occasionally stops receiving keyboard input. A practical workaround is running “ibus exit” (some automate this at login). IBUS is an input method framework primarily for complex/non‑Latin languages; users discussed whether it’s needed on their systems.
Production Idea: Stereo Arps, S&H Modulation, and FX Chain #
A user shared a creative patch: large chords into an arpeggiator with rate modulated via Curves sampled by Sample & Hold every two beats, then duplicated and hard‑panned with differing modulation speeds for evolving stereo motion. The group track ran through a chain (e.g., morphing EQ, tape coloration, limiters/EQs), and the poster favored LFO+S&H over Random for predictable, transport‑synced results.
Operator/Control Sensitivity Feels Off (General Observation) #
Some noted fine‑tuning certain parameters (like recurrence patterns or arpeggiator transpose) felt unusually stiff or slow to adjust. One hypothesis mentioned mouse polling rate as a factor; others experienced it on standard 125 Hz mice as well, suggesting a broader UI sensitivity concern.
Creative Sidechain with Math #
A quick tip celebrated using “Math” to duck a low shelf EQ only when two separate triggers overlap (e.g., kick AND bass), providing conditional ducking beyond simple single‑source sidechains.
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.
Hardware Requirements and CPU Support Changes #
Users discussed hardware requirement shifts between beta versions, including dropped support for some older CPUs. Experiences varied, with some seeing changes as early as b1.
Automation and Clipboard/Editing Bugs During Playback #
Multiple reports noted glitches: automating an effect on/off crackled or glitched, and duplicating/moving/pasting MIDI clips during playback caused stuck notes that only stop after retriggering or power‑cycling the instrument device. The stuck‑note issue has been present since early betas; reducing live edits during playback helps.
Long‑Press UI Paradigm Debate #
A vigorous debate centered on Bitwig’s small long‑press button revealing editor tools. Some found it undiscoverable and slow, preferring always‑visible tools or right‑click menus. Others defended it as a legacy interaction (from pre‑right‑click Mac days), emphasizing that right‑click also works; the main pain point was discoverability rather than capability.
Step Input Tool: Discovery and How‑To #
Beta 4 introduced the Step Input Tool in the Detail Editor for rapid note entry by grid step. Tips included placing the insertion line with a click, using Right Arrow to commit/advance and lengthen notes, Left Arrow to shorten/delete, and resetting shortcut mappings to defaults if arrows don’t respond. Some mused about mapping footswitches to arrow keys for hands‑on keyboard workflows.
Slice Tool and Editor Behavior Quirks #
Several UI inconsistencies emerged: the Slice Tool only worked in the large editor for some, not the compact panel; pasting notes didn’t appear in “track view” but worked in “clip view”; lasso selection felt buggy; the large editor’s track list toggle sometimes did nothing or flipped views unexpectedly. Users on Windows 10 noted the Layers list wouldn’t appear unless selecting multiple clips; pinning was removed; and the editor could revert to Launcher view even with Arranger clips.
Note Audition Crackles in Step Recorder #
Note auditioning while using the step recorder produced crackles for some users. People asked whether it had been officially reported yet.
General Beta Stability Notes #
Overall, participants agreed the betas are “very beta.” Some issues were less frequent if avoiding edits during playback, but several bugs persisted across b1–b4.