System Requirements

• Windows - Windows 7, 8, or 10 (all in 64-bit)
• Mac - macOS 10.14 ("Mojave") or above
• Linux - Ubuntu 18.04 or later
• a CPU capable of SSE 4.1

---

Changes in Bitwig Studio 4.0.1 [released 16 July 2021]

Fixes

• Some projects with missing files would crash when managing them
• With a demo song or template, selecting the master track as a track input would incorrectly show an error message

---

What's New in Bitwig Studio 4.0 [released 13 July 2021]

Audio Comping, Anywhere

Recording to the Arranger or Launcher

• To record on the Arranger timeline: new audio recordings are automatically added as comping take lanes when passing non-looping audio clips
  • For "cycle recording," just enable the Arranger loop
• To record into the Clip Launcher: from the Play menu, enable Record as Comping Takes, and set an appropriate Take Length
• Clips containing take lanes show the comping icon on their top right edge
• Since comping lives within the clip, comping clips can be freely dragged between the Launcher and Arranger
• Since comping lives within the clip, comping clips can be saved to your library, with take lanes intact and editable

Effortless Editing

• When a clip containing takes is selected, the Detail Editor Panel displays the Comping expression view for editing
• Each take lane is given its own color for visualizing the sources used, and each take can be renamed
• Take lanes can be reordered by dragging their headers
• Dragging over a portion of any take lane to create a comping region
• Clicking on any take lane uses that take for the nearest comping region and selects the region
  • Pressing [UP] or [DOWN] moves the comp region to the take above or below
  • Pressing [LEFT] or [RIGHT] selects the previous or next comp region
• Double-clicking a take lane selects it in its entirety as the current comp
• From the composite lane, dragging the top of any comping region up and down adjusts its gain
• From the composite lane, sliding the bottom of any comping region left and right adjusts its timing
• Sliding a boundary where two comping regions meet moves their fade point
  • Sliding a take boundary in the take lanes area also moves the transition point between comp regions
• Dragging near a boundary in the composite lane allows shortening a comp region to remove audio (including breaths, etc.)
  • Deleting a time selection within a comp similarly replaces the selection with silence
• [ALT]-dragging a take lane slides the time of that entire lane (and any comp regions pointing to it)
  • [SHIFT]-[ALT]-dragging a take lane slides the time of that all take lanes (and all comp regions referencing them)
• Comping expression editing keeps track of its own snapping setting, defaulting off
  • [SHIFT]-dragging temporarily inverts the snapping setting

Layered Comp Editing

• With multiple comping clips selected, layered editing mode of the Detail Editor Panel allows comp editing of multiple clips at once
• In the Comping expression view, the target layer shows all of its take lanes, and additional clips show only their composite lanes
• All comp editing gestures work as they do in regular (single) comp editing mode
• Using any of the comp editing gestures while holding [CTL] ([CMD] on Mac) applies that edit to only the single comp you are interacting with

Fold to Takes for Comping Any Source

• Wrap any audio clip into takes by right-clicking on it and choosing Fold to Takes
• Select either how many takes to create, or the length for each take
• Drag any audio file from the Browser Panel to the take lane area to add a new take lane
  • Right-click on any take lane header for Fold to Takes of that individual lane (in case a file is longer than the current comp, etc.)

---

Operators for any Note or Audio Event

Operators change when and how events are triggered. Devices have modulators; now notes and audio events have Operators. One or more modes can be used on each event.

Mode: Chance

• Sets the likelihood that any event will occur, adding probability to make any loop dynamic
• Is visualized on events like the face of dice
  • A higher die value represents a higher probability
• For notes, a Chance expression editor is available beside velocity

Mode: Repeats

• Causes retriggers within the original event, turning a single event into a ratchet, or polyrhythm, or…
• Repeat Value can be set two ways:
  • Values below 1 set the note rate for repeats (e.g., 1/2, 1/3, 1/12…)
  • Values above 1 set the number of slices the event is cut into
  • Right-clicking on this value provides a menu of common note rates
• Repeat Curve bends the repeats to either start closer together, or to speed up at the end
• For notes, Repeats End Velocity sets a relative target velocity for the end of the note repeat
  • This is also editable from the velocity expression lane
  • [ALT]-dragging on the end velocity point adjusts the velocity curve of the repeats
• Is visualized on events as slices where the repeats happen, just like the event restarts at each of those points
• Right-click on any event to Slice At Repeats, turning each repeat into an independent note or audio event

Mode: Occurrence

• Sets conditions for each event
• One Condition can be selected:
  • Always → Plays unconditionally
  • on First → Plays on first cycle
  • never First → Skips the first cycle
  • with Previous → Plays when last event did
  • without Previous → Plays when last event didn't
  • with Prev Key [note events only] → Plays when this key's last event did
  • without Prev Key [note events only] → Plays when this key's last event didn't
  • with Prev Chan. [note events only] - Plays when this channel's last note did
  • without Prev Chan. [note events only] - Plays when this channel's last note didn't
  • Fill on → Plays when Fill mode is on
  • Fill off → Plays when Fill mode is off
• The Fill button is a global performance control
  • It is available from the Play menu, and can be pinned beside the menus
  • It can be mapped to MIDI controller, or automated from the Master track under Transport > Fill
• Is visualized by displaying the condition icon on the event

Mode: Recurrence

• Gives each event its own looping timeline
• Recurrence Length sets the number of loops per cycle, from 2 to 8
• Toggles are then available for each loop
• So if the length is set to 4, four toggles are provided. And if only the first and last toggles are enabled, then this event will trigger on the first and fourth loops of this clip. (And then the fifth and eighth loops, etc. etc.)
• Is visualized on the event by a series of shaded (on) and empty (off) rectangles

General Workflow

• A new inspector section for Operators is available when note or audio events are selected
• All Operator settings are neutral by default, creating events that always sound
• When an Operator mode has active values, the mode is visualized on the note/audio event as described above
• Each mode icon represents a toggle that can be turned off and back on at any time

Take a chance on predictability with Expand

• Right-click on any Launcher clip and choose Expand to print any number of loops into a new clip
• Unlike Bounce options, Expand generates the type of clip you started with (so an audio clip will create audio clips, and a note clip will create note clips)
• Expand removes any Operator that can be calculated ahead of time (particularly good for "cycle-aware" options, like Recurrence, or the First conditions of Occurrence)
• Options are available to:
  • Preserve Chance values, instead of printing their result
  • Preserve expression Spread values, instead of printing their result
• This provides clips with predictable notes, and a visualization of how Operators are actually creating larger patterns within patterns
• When Chance settings are used, Expand a clip several times to glimpse into different possible timelines

---

Spread for any Expression Point

• Expression automation points each have a Spread value now, defining a range for the point that will be randomly selected each time the clip loops
• Notes have these per-note expressions that can use Spread:
  • Velocity (only defined at the beginning of each note)
  • Pitch
  • Timbre
  • Pressure
  • Gain
  • Pan
• Audio events have these expressions that can use Spread:
  • Gain
  • Pan
  • Pitch
  • Formant (used by some stretch modes)
• Random values will glide to and from their neighboring points, just as regular automation would
• [ALT]-drag on any expression point to define its Spread
  • When the clip is not playing, the Spread range will be visualized with a color gradient showing the bipolar range
  • When the clip is playing, the randomly selected values will be shown at the beginning of each loop cycle
• Spread values are also accessible in the Inspector by:
  • Selecting individual expression point(s), and using the Spread field in the automation Point section
  • Selecting a clip (or multiple note/audio events) and using the parameter's histogram, which now has a value for Spread of that parameter
• To grab a reproducible random sequence, each clip now has a Seed parameter
  • By default, the value is Random, producing different results each time the clip is triggered
  • By clicking this field, a particular Seed value is produced and saved (displayed as a shiny bit field)
  • To produce a new Seed value, just click the field again. Or click the die icon to return to total Random.
  • When recording a performance from the Clip Launcher to the Arranger, the Seed value used during recording will be preserved in the new Arranger clips, preserving the exact sequence playback as what you heard during performance.
  • This Seed functionality applies to all expression Spread values within a clip, as well as any Chance Operators used

---

New modulator: Globals (Interface)

• Provides modulator signals for three project-wide controls:
  • Fill - A modulator signal reflecting the current Fill mode state
  • A◆B - A bipolar modulator signal reflecting the current global crossfade value
  • Play - A modulator signal reflecting whether the transport is currently playing (1) or not (0)
• The Fill and A◆B sources can be used as global control sources, routing hardware controllers or automation (from Master > Transport) to any and all tracks

---

macOS: Native Apple Silicon Support

• Bitwig Studio now runs natively on Apple Silicon
• Thru Bitwig's unique plug-in hosting, Intel VSTs can still be used alongside ARM VSTs

Localization of Bitwig Studio

• The Bitwig Studio application is now localized in Chinese, Japanese, and German
• The language is set from the Dashboard under Settings > User Interface > Language, at the top of that page
• Device and parameter names are the same, but most functions, labels, and in-app documentation (for the 300+ devices and modules) are translated

Improved Export Options

• Export Audio function and dialog has been revamped
• You can now choose from various audio formats to export:
  • WAV
  • FLAC
  • Opus (information here)
  • OGG Vorbis
  • MP3
• Appropriate profiles are available for each format
• Multiple formats can be exported at once (in case you want a lossless version for your listening, and a lossy version to email, etc.)
• The Sample Rate for exports can also be set now
• If a time selection is made is the Arranger, that is used as the export Time Range

New Features

• Import of some data from FL Studio project files (FLP)
• Import of some data from Ableton Live project files (ALS)
• Auxy can now export a Bitwig Studio project file
• A top-level snap toggle is available in all timeline editors, to the right of the snap settings menu
• Waveforms are now shown in a Perceptual scale by default, for easier reading (setting is in the Dashboard under Settings > User Interface > View > Waveform display)
• Various container devices can now be converted, such as switching Layer devices to Selector devices, etc.
• Added track "lane heights" zoom functions for the Arranger and Detail Editor Panel (assignable via Dashboard > Settings > Shortcuts)
• Controller scripts added for Native Instruments A and M series
• Controller script added for iCON VCast
• Anonymized, optional usage data collection is now possible (details here), to help us improve Bitwig Studio

Improvements

• Track Monitoring: Sources from other tracks can now be monitored (as long as this would not create a feedback loop)
• Track Monitoring: Mode is now a tri-state switch (click to cycle from Auto to On to Off)
  • Or right-click the monitoring button for a menu with all modes and their descriptions
• The gain handle is now available at the top of any Arranger audio clip, and in the Detail Editor Panel (at the top of the waveform in the Audio Event and Comping expression editors)
• The slide gesture is now available at the bottom in the Detail Editor Panel (at the bottom of the the waveform in Audio Event or Comping modes)
• Time sliding handles are now available at the bottom of each audio event in the Detail Editor Panel
• Preview player (in Browser Panel and Pop-up Browser) provides temporary auditioning when you click on the note/audio visualization, now stopping audition on mouse release
• HW CV Instrument device: Now has a latency measurement option[24535]
• HW FX device: Better latency measurement algorithm [24032]
• Polymer/ Grid modules (Filters): Many filters now handle extreme resonance and modulation cases more smoothly
• Find All when looking for missing files is now faster when searching for multiple files
• Controller API: Added NoteStep.isMuted() and NoteStep.setIsMuted()

Fixes

• Sustain pedal problems with certain MIDI CC64 automation [26157]
• Meter of device chain was painted grey after unmuting [26149]
• Reordering automation lanes stops the updating of the knob onscreen
• In the Edit View, tool and snap settings are now shared between the Detail and Automation Editor Panels [25727, 26197]
• Smaller (read: better) sensitive area for boundary interactions with clips
• Showing piano roll micro-pitch expressions on a hybrid track could crash [25936]
• Clip selection in Detail Editor Panel did not always update correctly when selecting a clip on another track in the Arranger [21812]
• Note Editor: The "Draw Note Pattern" modifier would sometimes draw a double note with certain beat grid settings [25374]
• Automation editor was showing preview region over full editor width when drawing with pencil tool in some cases [25924]
• Snapping did not work for zero offsets via snap-to-relative-grid [26155]
• Various note and note name painting issues in Detail Editor Panel [26123]
• Crash when clip end was adjusted on mixed clip/meta-clip selection [26037]
• Clicking on an audio lane header in layered editing mode (for tracks) was changing the layers shown
• Drum Machine device: Weird CPU spikes could appear when playing one drum slot that is set to be choking another slot [25645]
• Drum Machine device: Internal return chains are no longer accessible to nested FX Layer devices (which could cause feedback loops) [25929]
• Delay 1, Delay 2 & Delay 4 devices: Might go to sleep before feedback is played, when delay times were long [25442]
• HW Instrument device: Did not preserve MIDI CC's channel [26102]
• Note FX Layer & Note FX Selector devices: Were causing note delay when first inserting them [23192]
• Note FX Selector device: Now correctly works with sustain pedal [25997]
• Mod Delay Grid module: Was sometime glitching at start/stop of transport when project had PDC latency [26363]
• Channel Map device: Was always lightning the channel 1 indicator
• Channel Map device: Did not work on MIDI CCs with HW Instrument device [26102]
• Crashes sometimes when undoing deletion of devices that were using samples [26166], [26065]
• Crash when triple-clicking inspector number field followed by drag at the right edge [25683]
• Possible to crash the application by calling some methods via controller API in some cases [26165]
• Zooming out in Grid editor could make knob graphics disappear [26039]
• macOS: Incorrect names were sometimes shown for certain files loaded from the OS (e.g Korean file names composed of Hangul Jamo characters) [25890]
• Linux: Rare crashes when using Wavetable module, in Polymer or The Grid [25958]
• Controller API: Tracks created via HW API were white [26126]
• Controller API: Added monitorMode() and isMonitoring() on Track object [deprecated monitor() and autoMonitor()]