Community Report 2025-10-03 - Clips Start in the Middle, Inflators Are Just Waveshapers, and SRT Saves Your Stream

Users flagged unreliable automation playback unless an anchor point exists, and puzzling export differences between Bitwig and external players. Everyday workflow chat focused on audio slicing/quantization limits, FX tracks turning into audio tracks when rearranged in groups, and

Bitwig Community Report 2025-10-03 #

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.

Automation Lanes Sometimes Ignored Without Anchor Points #

• A user observed automation not consistently honored unless an automation point is placed, suggesting intermittent automation-state recognition. Another acknowledged the clarification.

Export Sounds Clean in Bitwig but Noisy in External Players #

• One report claimed clean levels in Bitwig (and with additional metering) yet transient "noise" or clipping in external players (WMP, VLC, KMPlayer). A reply asked to confirm the export is WAV/FLAC and not MP3, noting lossy codecs can smear transients; if it’s a lossless export, the cause remains unclear.

Audio Slicing and Quantization Limitations #

• Discussion highlighted Bitwig’s rhythmic shuffling being rudimentary compared to other DAWs. Split at onsets is fine for percussive material, but connected audio edits are laborious; audio quantization sometimes helps. Users hope for future improvements, including adjustable fade curves akin to Ableton’s Beats mode.

FX Tracks Converting to Audio Tracks Inside Groups #

• Moving an FX track inside a group sometimes resulted in it becoming an audio track (not merely group-local FX). Multiple tests showed that on a second reposition within the group it converts to audio. Some suspected this may be intended behavior (a quick bounce-like feature), though it surprised users.

How to Record a Microphone on Windows (ASIO Setup) #

• Advice: install a universal ASIO driver (e.g., ASIO4ALL) or use VB-Audio’s virtual ASIO device. Select the ASIO device in Bitwig and route the mic within the ASIO control panel. ASIO4ALL may offer lower latency and simpler setup.

Hardware and Controller Chatter #

• General gear talk: enthusiasm for LinnStrument and SP-404MK2’s playability, plus a user seeking tips for Nano Cortex stability on Linux (intermittent “frying” and sample-rate mismatch issues).

Python MIDI App Instability on Windows 11 #

• A developer sought help for a Textual TUI app using mido/python-rtmidi that crashes on first run(s) under Windows 11 (Python 3.12.7), suspecting a MIDI initialization/timing quirk. macOS runs fine.

Production Tips and Questions #

• Quick tip: manually stretch audio to grid (align start, then Alt/Option-drag end). Bitwig’s tempo detection struggles without clear transients. A question about exporting audio with slice markers was raised without a definitive solution in-thread.

Supercollider Sending OSC to Bitwig #

• Users discussed getting parameter names via OSC. Remote Controls pages work, but a direct, reliable way to obtain names beyond that remains unclear.

Streaming/OBS Capture: Mac Mini to MacBook #

• NDI over a wired network proved CPU heavy; switching to an SRT server solved it. A single good Ethernet cable was enough to stabilize 4K capture from the Mac mini to an M1 MacBook.

Plugin Talk: Inflator vs Waveshaper, Alternatives, and Linux Formats #

• Debate over Oxford Inflator’s value and frequent sales; free JS Inflator clones and budget options like KClip were suggested (Linux-native, no iLok). Guidance for Linux-native plugin identification: .so for VST3 bundles on Linux, .clap for CLAP (not cross-OS compatible), while Windows uses .dll/.vst3. Installers differ (scripts on Linux vs .exe on Windows).

Theming and Presets Shared #

• A BlackWig theme update (new format) and a multiband saturator in FX Grid (Saturn-like) were shared, with pointers to tutorial videos included in the device description.

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.

Beta Talk: Editing Ergonomics, Duplicate Behavior, UI Long-Clicks, and Polling-Rate Glitches #

• Pencil/automation workflow wishes (override alt-click create-clip when a time selection exists), and desire for streamlined time selection within the pencil tool.
• Zooming the right edge of audio clips tanks framerate (left edge fine). Browser sound packs panel scroll feels sluggish for some.
• Duplicate behavior in Bitwig 6 beta: users found inconsistencies between Clip vs Track modes and between time vs note selections; debates over whether duplication should overwrite or append. Many want a clear, consistent option.
• Pitch/Formant automation access moved behind a long-click/right-click button; many dislike long-press UX on desktop, though right-click and Ctrl-click also work.
• Sliders "fight" the mouse at high polling rates (1 kHz); switching to 125 Hz helps, suggesting event-queue issues. Trackpads (lower Hz) fare better; some devices show lagging meters when moving the mouse.
• Other quirks: Undo intermittency for one user, Operator/Over device pops on playback (likely unsmoothed gain resets), Time Shift and Arp feel sluggish, looped time-signature automation disrupting metronome/timeline, and default pointer behavior hiding time selection (though re-enablable in preferences). Users stressed the power of pointer+time-selection for stretching and duplication workflows.

Clips Desync / Clips Start in Middle #

• Reproduced bug: after retriggering clips in the Launcher, stopping/restarting transport can start clips offset (quantized but wrong). Scene launch can sometimes reset, but not reliably across disparate tracks. Users expect a global reset (e.g., double stop) and visual indication of any "invisible" start position. LFO/Curves modulators also sometimes start with phase offsets; occasionally recording arms/stops reset state.

Piano Roll Focus Consistency #

• In b4, clicking with a stationary pointer now updates the editor consistently. If the pointer moves during the click (e.g., trackpads), it may select the clip in the arranger but not update the editor.

Multi-Track Editing: Cmd+A on Aliased/Shared Clips #

• Confirmed bug: selecting notes across aliased clips and using arrow keys moves notes multiple steps (one per selected alias instance). Lasso selection doesn’t trigger the same multiplication; likely a selection-state handling issue.

New Multitrack Piano Roll: Regressions vs v5? #

• Strong feedback that b4’s layered editing is a step backward for large multitrack workflows: unpredictable flat layer list ordering (based on selection), no persistent locked/ unlocked layer sets, no state bookmarks, and selection across distant track branches is error-prone. Some would stick with v5 if unchanged.

Regression: Bounce-in-Place of Time Selections #

• BiP of time selections in empty regions no longer works; the prior workaround (hybrid track + empty MIDI clip) also stopped working in b4.

Redraw Artifacts in Automation #

• b4 on Windows shows straight vertical white streaks in automation when moving the mouse right-to-left; likely a classic redraw issue.

Linux Early Access Packaging #

• Arch users asked for an updated bitwig-studio-earlyaccess package for 6.0b4 to start testing.