System Requirements

• Windows - Windows 7, 8, 10, or 11 (all in 64-bit)
• Mac - macOS 10.14 ("Mojave") or above
• Linux - For installing the Flatpack file, any modern distribution with Flatpak 1.1.0 or later (more information here). For installing the DEB file, Ubuntu 20.04 or later.
• a CPU capable of SSE 4.1

---

Changes in Bitwig Studio 4.4.10 [released 5 April 2023]

Fixes

• Application may crash when clip launcher gets focus [31878]

Changes in Bitwig Studio 4.4.9 [released 28 March 2023]

Fixes

• Split (Mix) Grid module: Did not work in stereo if Interpolation mode was set to Nearest [31550]
• Slice At Repeats function could crash on notes containing only hidden expression points [30328]
• Scrolling the Arranger to time zero would sometimes become impossible in a project file
• Rearranging Arranger clips could destroy fade-ins in certain cases [25833]
• Moving a clip would sometime trigger automation thinning [28219]
• Rare crash after editing an audio event's gain expression [30508]
• Copy/paste or duplicating Grid modules could cause doubled modulation assignments, in some cases [31296]
• Duplicating Grid modules and then undoing/redoing could result in connections missing between modules, etc. [31817]
• In the Detail Editor Panel, note names could be visually truncated at different display Scaling settings [30469]
• Dual Display (Studio / Touch) display profile: Detail Editor Panel on second screen was not following Launcher clip selection [30656]
• Grid snapping to bars did not update correctly when transport time signature changed [31753]
• Arranger track focus was not changing in the Detail Editor Panel when clicking clips in Arranger view (while a group track was selected) [30984]
• Bouncing clips that ended before beat boundaries were producing wrong stretch markers [31557] [30858]
• Text editing of values in pop-ups (such as context menus, Historgrams, etc.) now works via [CTRL]-click ([CMD]-click on Mac) [28337] [26697]
• Pasting some characters into a multiline text field could sometimes crash [31484]
• Deactivating a track while recording was in progress would break the undo and prevent project from being saved unless the engine process was terminated [31478]
• Manual mappings (from a controller that uses the hardware API) would not work unless engine was reconnected to the project [31649]
• Controller-recorded automation (from a controller using the hardware API or manual mappings) would sometimes record the wrong automation [31556]
• During bouncing or offline exporting, automation playback was not visualized on the interface (visual issue only)
• Offline (non-realtime) exporting of large projects may crash the engine, after a long time
• macOS: Fixed crash when inserting beat markers via Trackpad "Force Touch" gesture [30450]
• Linux: Save Project dialog would sometimes open in the wrong folder
• MIDI files created by Audiocipher VST could not be imported [27874]

---

Changes in Bitwig Studio 4.4.8 [released 7 February 2023]

Fixes

• Fixed some plug-in scanning crashes and other errors (regression in v4.4.7)
  • If you loaded Bitwig Studio v4.4.7, plug-ins could have failed scanning or been indexed incorrectly. To rescan some or all plug-ins, go to Dashboard > Setting > Plug-ins, and click the button at the bottom of the page for Show plug-in errors. The window that appears will let you Rescan All of your plug-ins, etc.
• Mousing across the Detail Editor Panel was leaving GUI artifacts on top of the notes (regression in v4.4.7) [31364]
• Linux with ALSA: Fixed a rare crash

---

Changes in Bitwig Studio 4.4.7 [released 31 January 2023]

Improvements

• When program is set to Chinese, the Chinese language PDF manual is available from Dashboard > Help > Documentation (指示板 > 帮助 > 文档)

Fixes

• Sometimes short Arranger clips (with very short loop regions) would not playback [31179]
• Audio Out (I/O) Grid module: Loads a default Clip Level of +6 dB, which is better for pre-v4.2 content and often just nicer
• Sample stop marker in Clip view of Detail Editor Panel was sometimes shown at the wrong position (when the project had tempo automation) [31066]
• Bounce always had dither on, regardless of the dialog setting [30949]
• Increased the ti0meout for pack installation so that it succeeds on connections with low bandwidth
• Activation dialog now shows an error when the number of activations is maxed out
• Incorrect realtime ruler display in Detail Editor Panel for Arranger clips, when the project had tempo automation
• Windows: Rare engine crash when unplugging a MIDI device [29433]
• macOS: There was a several seconds lag between saving a clip to the user library and seeing it in the program [30184]
• MIDI Sysex buffers are now larger
• Notes to Tracks/plug-ins routing were not preserved with certain plug-ins [29433]
• Controller scripts: Touch automation mode now works correctly on controllers with touch-sensitive motorized faders (such as Mackie Control, and ICON QCon Pro X and G2)
• Controllers were sometimes having weird behavior or crashing when using Pop-up Browser to browse devices [30278]
• VST3 Plug-ins: Weren't saving the edit controller state if the edit controller isn't separated from the component
• VST3 Plug-ins: Fixed memory leaks when creating AttributeLists and Messages

---

Changes in Bitwig Studio 4.4.6 [released 14 December 2022]

Fixes

• Sampler device: Release Velocity Mode setting of On (to use each original note-on velocity for the corresponding release trigger) was broken and acting the same as Off (use the release velocities, such as they are). On now works properly.
• Fixed an intermittent crash when renaming a file that is in a collection (regression from v4.4.4)

---

Changes in Bitwig Studio 4.4.5 [released 08 December 2022]

Fixes

• Recording a Launcher audio clip did not use the transport time signature [30853]
• Big meters (in the Mixer Panel) now adjust correctly to different scaling settings [30819]
• Deactivating a device would show the device sleep indicator instead of device off (regression in 4.4.4) [30855]
• JACK and PipeWire audio systems: Stereo port pairs could be incorrectly identified [30479]
• Controller API: Fixed a case where a script could lock up the engine

---

Changes in Bitwig Studio 4.4.4 [released 02 December 2022]

Fixes

• Fixed a crash when dragging an automation time selection onto an empty Launcher slot [30022]
• Renaming a file in Bitwig Studio wasn't updating any user collections with the new file name [30558]
• Renaming a collection in the Browser was allowing invalid filenames [30679]
• The Mixer Panel context menu will no longer show up in Remote Controls Editor
• Selecting a clip or sample in the Browser Panel would add an empty scene — when the project had no scenes [30032]
• Audio clip was showing an incomplete waveform overview in a particular project [30690]
• Fix some rare and random application crashes [30332]
• Controller API: fixed note interactions through Clip objects
• Plug-ins: Changing a plug-in parameter via Bitwig Studio's GUI would not cause the plug-in to wake up
• Plug-ins: At the top-level of a track, plug-ins could show as active, even when suspended
• Plug-ins: Some modal dialogs (for activation) were causing weird issues and crashes in the plug-ins (e.g., Reason Racks) [30615]
• Plug-ins: States may not have been correctly saved in some circumstances
• macOS Ventura: Some plug-in context menus were not showing when Bitwig Studio was in fullscreen mode [30570]

---

Changes in Bitwig Studio 4.4.3 [released 08 November 2022]

Fixes

• Fix a regression where exporting and bouncing in Non-realtime mode sometimes caused the audio engine to hang [30501]
• Linux: Fixed engine crash when using a high number of plug-in instances
• Controller API: fixed note interactions through Clip objects

---

Changes in Bitwig Studio 4.4.2 [released 27 October 2022]

New Features

• Controller script added for Novation Launchkey MK3 Series

Fixes

• Application GUI scaling affects the Device Panel scroll bar proportionally higher than other GUI elements [30282]
• Extension API: device.createChainSelector() wasn't working with Note FX Selector device [30360]
• Overdubbing an Arranger clip could set its loop length to zero, leading to various issues (regression) [30391]
• Generic Controller script couldn't be used anymore (regression) [30309]

---

Changes in Bitwig Studio 4.4.1 [released 21 October 2022]

New Features

• Controller script added for Arturia MiniLab3
• Controller script added for Arturia BeatStep Pro

Improvements

• With a modulator selected, you can now open/close its detail pane with the [ENTER] key
• In the Dashboard's Recent Projects page (where Bitwig probably opens), the [TAB] key now moves keyboard focus to the project list
• Various controller extension improvements
• CLAP: Bitwig Studio now forwards choke events to plug-ins [Interop #39]

Fixes

• Splice activation could cause crashes [30118]
• Bitwig now opens in the Quick Start page only if you don't have any recent projects
• Freq Split device: Gain was off by 1.2 dB
• Fixed delay compensation error involving individual parallel chains (Delay-4, Freq Split, etc.) within certain sidechain configurations
• Exporting audio files with multiple periods in filename is possible again [27897]
• Display of polyphonic modulation was adding up all voices [Interop #36]
• Editor did not repaint immediately when locking a clip in layered note editor [29659]
• Generic Controller extension was filtering out program change messages [29886]
• Some controller scripts could randomly crash the application [28504]
• Threshold for showing group track metaclip content differed from regular Arranger clips when zoomed out [29597]
• It was not possible to shift-select multiple group track metaclips when master track content is shown on the group track [19584]
• Rare crash when disconnecting a display while the display prefs were being edited [22661]
• Plug-ins hosted in the engine were always in offline mode instead of real-time mode
• When adjusting a plug-in parameter, the modulated value sometimes wouldn't change until the plug-in starts processing [29689]
• Overlapping plugin state saves could trigger timeout a dialog (with Elektron overbridge plug-ins, for example)
• CLAP: Fix inverted check when floating plug-in windows were closed by the plug-in [Interop #41]
• CLAP: Bitwig wasn't forwarding some changes made in its parameter list to the plug-in [Interop #14]
• Controller API: Launch option continue\_immediately did not work for clips in groups. [29835]
• Controller API: Binding a hardware button to some kind of bank scroll action would not cause the GUI to follow, even when that option was enabled for the controller [29912]

---

What's New in Bitwig Studio 4.4 [released 05 October 2022]

New Spectral devices, for all Bitwig Studio customers

• Spectral Suite, four new audio FX and a package of sound content, is now part of Bitwig Studio
• There is a new Spectral device category, where the four new audio FX can be found
• How do these "spectral" devices work?…
  • These audio FX are frequency-domain devices, which separate the incoming sound into hundreds of pieces for analysis
  • In the frequency domain, each moment of a sound isn't simply loud or quiet (for example); there are always frequencies that are loud and those that are quiet
  • So Bitwig does the math and then, based on the device's orientation, related signals are grouped into "channels" for easy mixing and plug-in-friendly control
• These devices are "containers" at heart, reconstructing the original sound… until you move one of the channel controls (Gain or Panning) or insert a plug-in
  • The sooner you adjust an audio parameter, the more obvious the devices become
• All four devices have an identical structure for each channel:
  • Gain control, in standard volume range
  • Panning control, for stereo placement
  • An On (or "active") switch, shown with a speaker icon beneath the Gain knob, in case you want to disable a channel
  • A Solo control, shown as an S button to the left of the Gain knob, for auditioning one channel at a time
  • A device chain, for processing this channel of audio with any Bitwig device or VST/CLAP plug-in
    • Like all nested device chains on these devices, notes reaching the device are available here, for envelope triggers, phase resets, or anything else you deem appropriate
• All four devices also share an identical Output Section:
  • A Pre FX chain, for processing incoming audio before it goes to the spectral analysis, perhaps for a Compressor or Dynamics to tighten the signal, or anything else
  • A Post FX chain, for processing the sum of the audio channels, maybe for an EQ+ to balance the full output, or your favorite plug-in, or…
  • A Mix control, that blends the dry incoming signal with the final processed signal (coming from the channels and Post FX chain)
• Freq Split, Loud Split, and Harmonic Split all use similar visualizations and share a Spectrum Display Inspector parameter, with two modes:
  • Pre shows the analysis data (and no audio processing from the channel controls, such as Gain or audio plug-ins), good for tweaking the splits
  • Post shows each channel's output audio, post-processing

New Spectral Suite device: Freq Split (Spectral)

• Divides signal into frequency groups and sorts them into one of four channels, for individual mixing and processing
• Frequency Splits sets the number of splits across the frequency spectrum, which works with two nearby parameters:
  • Split Insertion Direction sets whether additional splits are added from the right/high edge of the spectrum (←), from the left/low edge of the spectrum (→), or around the relative middle (↔︎)
  • Crossfade Amount determines the overlap between splits
  • So with the device's default settings, 16 Splits with an Insertion Direction putting new splits on the right (←) means:
    • The 1st, 5th, 9th, and 13th splits land in channel 1 (red)
    • The 2nd, 6th, 10th, and 14th splits land in channel 2 (blue)
    • The 3rd, 7th, 11th, and 15th splits land in channel 3 (yellow)
    • The 4th, 8th, 12th, and 16th splits land in channel 4 (magenta)
    • And if the Crossfade Amount was increased from 0.00 % (full isolation between bands) to 50.0 %, then each split would spend its first 25 % crossfading with the previous split, and its last quarter crossfading with the next split
• Split Nudge slides the frequency splits by an offset value, so a setting of +2.00 pushes the contents of channel 1 into channel 2, channel 4 into channel 2, and so on
• Split Spin also slides the frequency splits but relative to the entire spectrum; so a setting of -10.0 % slides all the splits a tenth lower in the entire spectrum
  • Whether being subtle (Split Nudge) or extreme (Split Spin), modulating either of these parameters shows the "filter bank" quality of this device, creating new phasers and more when each channel is loaded with different audio FX
• Split Bend curves the frequency split pattern around a new midpoint, either moving the midpoint downward and putting splits closer together in the lower frequencies (negative values) or moving the midpoint higher and having splits closer together in the upper frequencies (positive values)
• Split Pinch kinks the frequency split pattern, either bunching more splits around the midpoint (positive values) or putting more splits into the sides (negative values)
  • In the device's display, the interactive white dot controls Split Bend when dragged left to right, and Split Pinch when dragged up and down; it's fun
• The Spectral Limiter option sets a maximum Threshold level for each individual frequency bin
  • In the device's display, the Threshold is shown with a horizontal orange bar that can be dragged up or down

New Spectral Suite device: Harmonic Split (Spectral)

• Tracks the fundamental frequency of the incoming sound, for splitting Nonharmonics (gray) to one channel and dividing harmonics between Harmonics A (orange) and Harmonics B (turquoise) channels, for individual mixing and processing
• Harmonics Pattern decides how harmonics are distributed between the A and B channels
  • The default setting of 2 places every 2nd harmonic in A channel, so the A channel will be odd harmonics (1st, 3rd, 5th, etc.), and the B channel receives all even harmonics (2nd, 4th, 6th, etc.)
  • A setting of 4, for example, would place the 1st, 5th, 9th, etc. harmonics in channel A, and all other harmonics (2nd, 3rd, 4th; 6th, 7th…) into channel B
  • Higher values lead to narrower results in the A channel — and the potential for more extreme processing without "getting into trouble"
  • A setting of 1 is special, routing only the fundamental to channel A and all other harmonics to channel B
• Nonharmonic Sensitivity is a relative control for how picky the harmonic vs. non-harmonic split is, where a higher Sensitivity value allows less audio into the Nonharmonic channel — and more audio into the two Harmonics channels
• The Maximum Harmonics Inspector parameter allows you to limit the number of harmonics being tracked, acting as a "ceiling" when you want fewer frequencies in the Harmonics A and B channels
• Fundamental tracking can be adjusted with several analysis parameters:
  • Tilt favors the high frequencies (when positive) or low frequencies (when negative), useful when the desired fundamental is filtered in the sound, etc.
  • The Low-cut Frequency and High-cut Frequency parameters narrow the frequency tracking area
  • An amplitude Detection Threshold can be set, keeping moments that stay below that level in the Nonharmonics channel
  • In the device's display, the Detection Threshold and Cut Frequencies are interactive lines that can be dragged
  • The device display also illustrates the currently-detected fundamental with a white dot and moving crosshairs

New Spectral Suite device: Loud Split (Spectral)

• Uses two thresholds to separate the Quiet (green), Mid (yellow), and Loud (red) portions of the incoming sound, for individual mixing and processing
• A Higher Threshold (red) sets the level where stronger signals are considered Loud
• A Lower Threshold (green) sets the level where weaker signals are considered Quiet
  • In the device's display, both thresholds are visualized as horizontal lines, which can be dragged up and down
  • When clicking a line's dot handle on the right, only the outer band of that threshold will be heard while the mouse is held
• Any signal falling between the two thresholds is considered Mid
• Relative Loudness Mode follows the level of the incoming sound, treating 0.0 dB as the strongest band at any given moment
  • Relative Loudness Mode uses separate Relative Higher Threshold and Relative Lower Threshold parameters
• Each threshold has its own Knee value, for setting the transition (and effective crossfade) between adjacent channels
  • In the device's display, ALT-dragging on either threshold adjusts its Knee parameter
• Rise Time sets the number of blocks before a softer signal fully transitions up into a louder band, like a "resistance" parameter
• Fall Time sets the number of blocks before a louder signal fully falls down into a quieter band, like a "decay" parameter
• Tilt is an analysis parameter, favoring the high frequencies (when positive) or low frequencies (when negative) before the channel splitting is applied

New Spectral Suite device: Transient Split (Spectral)

• Separates the Transients (short, unstable sounds; colored yellow) and Tones (periodic or pitched sounds; colored blue), for individual mixing and processing
• Analysis Bias either skews the detection to favor Transients (positive values) or Tones (negative values)
• The Transient Type Inspector parameter switches between two different algorithms for which type of Transient is being looked for:
  • Percussive searches for typical impact transients, good for drums or other things that "click" and "smack"
  • Noise looks for noisy smears, or even reverb residue
• Transients Decay sets a time (in blocks) for extending detected Transients, allowing them to release
• Tones Smoothing sets a time (in blocks) for extending detected Tones, allowing them to decay
• Tilt Amount is an analysis parameter that is colored yellow as it is oriented to how it affects the Transients channel; its effect is the opposite for the Tones channel
  • The Tilt Mode Inspector parameter changes the method of Tilt applied, between a Standard model that favors the Transient channel's high frequencies (when positive) or its low frequencies (when negative), or a Contour approach that subtly adjusts the mid frequencies vs. the highs & lows
• Transient/Tones Blend is the audio balance at the output of the spectral section, before each signal reaches its channel
• The Display Style of this device is unique, with two modes:
  • Waveform shows a split amplitude domain representation of the two groups
  • Sonogram offers the recent frequency-domain history for each group

New Features

• There is now a Japanese translation of the Bitwig Studio v4.3.0 manual
• Device context menus have be reorganized so that device-specific entries come near the top of the list (for example, the Spectrum Displays setting for three of the Spectral devices)