Testing of Bitwig Studio 5.2 or .3 or .4 ...

[Artie Fichelle]

I'm still sad because at the beginning I need Cubase, but once I have the chord progression and only need to tweak things, EZkeys 2 is good too in BWS. From that point on, Bitwig is amazing and very convenient to use.

It's worth it to learn to play a keyboard and some music theory. I can record whatever chord progression I want and it is faster than any of those chord helpers. It is also more expressive cause how I play a chord is recorded, not only the note pitch.

Don't need. There is an humanise button in scaler AND Bitwig.



(kidding).

Yes. Change one finger of a chord, then change the other and you have different chords.

[Jac459]

I'm still sad because at the beginning I need Cubase, but once I have the chord progression and only need to tweak things, EZkeys 2 is good too in BWS. From that point on, Bitwig is amazing and very convenient to use.

It's worth it to learn to play a keyboard and some music theory. I can record whatever chord progression I want and it is faster than any of those chord helpers. It is also more expressive cause how I play a chord is recorded, not only the note pitch.

Don't need. There is an humanise button in scaler AND Bitwig.



(kidding).

Yes. Change one finger of a chord, then change the other and you have different chords.

You can also use an harmonizer and sit on your keyboard. Or let your cat play in it.

[BBFG#]

Asking again. It's 5.2 still beta?
And is anyone else getting this weird high CPU usage that seems to be on my system to be related to Win 10 Defender?

[pdxindy]

Changes in Bitwig Studio 5.2, Beta 8 [released 21 June 2024]

NEW FEATURES

Bitwig Studio v5.1 User Guide is now available in ¡Spanish! [PDF here]
Bitwig Studio v5.1 User Guide is now available in Korean~^^ [PDF here]

IMPROVEMENTS

Automatic handling of audio stem import:
When multiple audio files are dragged into a project at once, files with identical lengths are grouped
Beat analysis will happen for those files together, giving all grouped files the identical Beat Markers (for stretching) and lengths
If non-matching files are dragging in as well, they will be analyzed individually
If analysis should be (re)done for any file individual, select those file(s) and use either Detect Event Tempo… (with parameter options) or Detect Event Tempo (which uses the default parameters)
Improved default stretch mode preferences (Dashboard > Settings > Behavior):
The Defaults section now includes:
Default Stretch Mode (replacing the previous Long and Short samples and file options)
Record / bounce stretch mode (was previously On record / bounce)
Files still import based on the Audio Preview/Import Mode setting, to either:
Play at Original Speed, or
Stretch to Project Tempo
Now when importing audio, holding the [ALT] key inverts the import mode
Various editing/selection improvements:
Added mappable function for Play from Left Edge of Current Editor
Compressor+ (Dynamics) device: Improved the device's reset behavior
Windows: Installer is now provided as an MSIX file
Installer distinguishes between 'beta' and 'release' versions, allowing one of each to be installed
macOS 14: Now support display refresh rates up to 144 Hz, and when multiple monitors are in use, each will use their own refresh rate
Earlier macOS versions max out at 60 Hz
VST3 plug-ins: Now includes note name support
Controller scripts for SSL UF1, iCON V1-M and iCON P1-M: Beat Display is now easier to read

FIXES

Sculpt and Focus (EQ) devices: Fixed clicks when switching Color mode
Touchscreen: Scrollbars now get less sticky [34872]
Fixed crashes related to Time Selection editing of start and end objects [36193, 35763]
Plug-in undo: Some plug-ins were writing an undo step upon opening project [36216]
It is now possible to deselect tracks after making a "global" time selection in the Arranger ruler (a regression) [36140]
Fixed Audio Quantize function, where Amount in the dialog now has the proper effect [36207]
Slice to Drum Machine dialog is now big enough to show all controls, all the time [36275]
When adjusting parameters from a controller, sometimes the value would not always be correctly adjusted [36219]
Particular WAV files are no longer garbled and distorted after import [36271]
Library index directory can no longer grow to an enormous size (if there are symbolic links that include the index storage location) [36153]
Plug-ins that reported an empty vendor now work when Plug-in Hosting Mode is by Vendor [36262]
Fixed an audio engine crash in some cases when a sandboxed plug-in crashed [35609]
Various graphics fixes:
Windows: General frame rate & latency improvements
White cursor line in Arranger no longer destroys clip names when mousing around [36264]
Group track headers (in both the Arranger Timeline Panel and the Mixer Panel) are less accidentally rounded
Browser Panel no longer loses the play (preview) button when long sample paths are shown [36062]
The About page (Dashboard > Help) shows the current graphics backend now
Windows: Fixed a crash when resizing windows on some backends [35690]
Windows: Fixed slow frame rate and missing graphics on some backends [36220]
Windows: Hardware that only supports feature-level 11_0 & 11_1 now uses Direct3D 12. Affected GPUS include:
NVIDIA: GTX 400-700 series
AMD: HD 7000, 8000, R7 200
Intel: HD/Iris Graphics 4000-6200
Windows & Linux: The OpenGL fallback for even older GPUs is now more performant
macOS: Maximizing a window now fills the entire screen, even with the system preference to Always Hide Menu Bar Automatically [35776]
Windows: A better fix for a previous fix [36119]
Fixed text appearance in Stretch Mode chooser for Japanese localization [32047]
Certain ALS file can now be imported [36139]
Windows: Fixed a crash when the MIDI output buffer was full [34198]
Controller script for SSL UF1: Track number is now shown correctly on the two-digit display

[xbitz]

it's a shame there won't be official theming support, but even with unofficial theming, we can steer the factory design in a pretty good direction.

[dlandis]

Asking again. It's 5.2 still beta?
And is anyone else getting this weird high CPU usage that seems to be on my system to be related to Win 10 Defender?

I'm guessing that you saw pdxindy's answer (yes, we're still in beta but it's now up to beta 10 with quite a number of issues apparently.)

CPU spikes have been mentioned by several. If you haven't already done so, please be sure to make a report.

[swilow11]

Curious if anyone is finding anything weird with the general search function in Bitwig. For example, I want to load a modulator eg. Macro. Open the browser, start typing Mac...normally the macro options appear. This just isn't happening. Happens when trying to load stuff in the grid too which is annoying as hell- there are so many modules, I can never remember which sub category they're in and search is just vital here.

[Zikax]

it's a shame there won't be official theming support, but even with unofficial theming, we can steer the factory design in a pretty good direction.

Is this possible with osx?

[xbitz]

^^^ yepp, just after the app security checksum validation, so should start the app at least once before

The descriptive JSON was definitely not meant to be tinkered with. Although it contains a lot of valuable data, some of them set several other parameters (color of edit cursor for ex, "Insert preview time"), and there is no dedicated section for the piano roll. The JSON shown in the image is there ... viewtopic.php?p=8927791#p8927791

howto


Of course, nothing guarantees that the entire thing won't change from one moment to the next.

[xbitz]

The UI in the latest beta version b11 has become very smooth(devs really managed to nail something). Those who came from FL and dropped it due to its lack should check it out when it's released, and the theming still works ... luckily

IMO this playhead "fx" is also an FL "feature"

[Sekops]

Theming is borked on Mac OS on 5.2 Beta 11 due to the playhead, recommended to use an older version prior to playhead support https://github.com/Berikai/bitwig-theme ... /issues/12

[xbitz]

Theming is borked on Mac OS on 5.2 Beta 11 due to the playhead, recommended to use an older version prior to playhead support https://github.com/Berikai/bitwig-theme ... /issues/12

have had to remove the advanced section from JSON

Code: Select all

  "advanced": {
    "Timeline Playhead": "#efefef"
  },
  

and works as before

[Valkasman]

I'm looking forward to the official release of 5.2

[xbitz]

magic theme has been finished meantime

I hope at least... If it hadn't been possible to recolor, I wouldn't have paid for another year in the Bitwig amusement park. But since it was, I had to recolor it, so at least you can benefit from it.

viewtopic.php?p=8935666#p8935666

[lb24569]

The UI in the latest beta version b11 has become very smooth(devs really managed to nail something). Those who came from FL and dropped it due to its lack should check it out when it's released, and the theming still works ... luckily

IMO this playhead "fx" is also an FL "feature"

That's becaused they switched Bitwigs graphics library to SKIA which is GPU acclerated. It's so smooth now