Bitwig 5 is up

[kpv]

It worked by moving vst3 file to vst2 folder... strange.

[BobDog]

I can not get Rewind to show up in Bitwig. All the usual locations are right in settings, shows up in Ableton. It is the only plugin have ever had an issue with showing up in Bitwig. Any clue?

Go to settings->plug-ins

At the bottom is a button "show plug-in errors", a window appears, is your plugin there?

If so click on it, and then copy the text at the bottom and send to the Bitwig email.

If it is not there then I would think it was a location problem.

[carlca]

Will do. Is it working for you? I am on Windows.

I’ve got it working on macOS. There is probably a small but diminishing number of plugins that don’t yet load and there may well be difference between the different OS’s. You’ll just have to wait, I guess.

[pdxindy]

Changes in Bitwig Studio 5, Beta 4 [released 21 April 2023]

NEW FEATURES

Segments modulator/module: Now includes a timebase option of minutes
When setting the rate–timebase to 1 minute, zooming out the Segments curve editor will cleanly shows minute divisions
Ø Split Grid module: Now has a Phase Shift Direction parameter, for whether the successive out ports add to the original phase (+ [Plus]) or subtract from it (− [Minus])
Phase Shift Direction can be set from the Inspector Panel, or by right-clicking on the module

IMPROVEMENTS

Browser: Location filter now includes your Collections & Smart Collections, so those are readily available again
Browser: The Location filter is now sorted better, including user locations filed under their type (Sound Content, Music, and Plug-ins)
Various Gain labels in devices have been clarified to better describe their position in the signal flow

FIXES

Bypassed devices were using too much CPU [32174]
Increased the size of Japanese, Chinese, and Korean fonts
Browser fixes / adjustments:
Use current selections (previously Remember selected filters) options now allow you to change the default Source and filters for various browsing contexts, available by right-clicking in the menu [32041]
Once you have changed a default, an option is also present to Restore defaults for current context
Having many collections didn't scale well in the interface [32098]
Wavetable browser now has the Import Wavetables… option again, available via right-click [32091]
Impulse browser now has the Import Impulses… option again, available via right-click [32091]
Creator settings weren't being recalled properly in defaults/snapshots/smart-collections
In some 'tree' views (Location, Device filters), the root node was collapsable but shouldn't be
No longer shows Tag filter columns when only Impulses are shown
Fixed an occasional crash when opening the Pop-up Browser to swap a device that was somehow not in the project anymore [32014]
Sort by Recent in package manager was not working correctly
The Grid: Pop-out Editor views now work when the Grid editor window is undocked / floating [32177]
Better auto-positioning of Pop-out Editors when used in track-level modulators
Segments (Envelope) modulator/module: Would crash when dragging in a curve file from the Browser Panel
Log (Math) Grid module, etc.: Was sometimes outputting invalid numbers, causing audio to break [32096]
Freq→Pitch (Pitch) Grid module, etc.: Was sometimes outputting invalid numbers, causing bad audio behavior [32094]
Ø Bend (Phase) Grid module: Was producing strange artifacts at the 100 % setting [32192]
Audio would stop when switching projects (without transport playing) [32089]
Edit File Metadata… function for curves (BWCURVE files) in the Browser Panel was not working [32160]
Dragging a clip from the Launcher to Arranger would not bring CC automation (regression) [32162]
Crash when swapping Grid modules that were modulated from a higher level [31240]
Was crashing when dragging globally modulated track to a new project [30786]
Fixed a crash when using JACK audio system [31962]
Fixed a crash when saving project [32049]
Fixed a crash when copying project or group modulator automation events to clipboard [32117]
You can now remove/restore the user defaults to the factory defaults
Adjusted the Poly Grid, FX Grid, and Polymer sleep threshold settings
When duplicating a device, track modulator were not being duplicated [32114]
Fixed some truncation issues that showed up in the Japanese localization
No longer shows an error when saving a project that contained a project modulator that was automated and then deleted [32176]
Wrong page scaling in Remote Controls editor
Manually mapping a hardware control to a device parameter was crashing [32002]

[SLiC]

Getting closer...

[BobDog]

Shame, Beta 4 didn't fix the bowser issues I am seeing (0 counts when I have any content locations set).

[BobDog]

The location changes are good though.

[nekavoq]

Is there a way to sort plugins the old way? Currently it looks to be Bitwig native plugins first on top, then third party plugins; I much preferred the previous sorting method where it's sorted alphabetically regardless of source.

That, or a way to use the interface of the old popup plugin browser? In the old browser, all I needed to do was scroll along and click on the location/category/creator I wanted to filter which is already visible and shown to me on the same screen.

Now I have to specifically click on location/category/vendor to view the list of the menu I selected, and I can only view one menu at a time? This feels like a significant UX downgrade to me, all for wider horizontal space for plugin names?

Please tell me I'm just being an idiot and I'm somehow missing the point or a toggle/option in the new browser that makes the new browser as efficient, if not more efficient in terms of sorting and finding the plugin you want.

(I'm aware it's currently in beta, I'm just afraid if this goes on unchanged into the actual non-beta version)

[pdxindy]

Is there a way to sort plugins the old way? Currently it looks to be Bitwig native plugins first on top, then third party plugins; I much preferred the previous sorting method where it's sorted alphabetically regardless of source.

Your search can now include anything... so a search order by file type makes sense so that devices/plugins end up above presets

[nekavoq]

Is there a way to sort plugins the old way? Currently it looks to be Bitwig native plugins first on top, then third party plugins; I much preferred the previous sorting method where it's sorted alphabetically regardless of source.

Your search can now include anything... so a search order by file type makes sense so that devices/plugins end up above presets

Hi, I apologise for my confusing wording. I did not mean to refer to the presets in any way, presets being sorted after devices is completely fine in my opinion; I meant to say that Bitwig devices are sorted first before third party devices like so (Addictive Drums being low on the list despite starting with A):



What I mean to say I prefer, is that devices are sorted alphabetically regardless if it's Bitwig native, or third party, like in previous versions (in this case, Addictive Drums is at the top because it begins with A):



Is there a way to sort it where it's sorted alphabetically regardless if it's Bitwig or third-party devices?

[pdxindy]

Is there a way to sort it where it's sorted alphabetically regardless if it's Bitwig or third-party devices?

No, it is always Bitwig devices first, then Plugins...

That would be a good feature suggestion (sort preferences)

What you can do is create a list of your preferred devices and set that as default.

[brightonob]

Changes in Bitwig Studio 5, Beta 5 [released 21 April 2023]
Fixes

Fixed application start-up issue for some users

[HBIII]

Well the top three things I wish bitwig had was midi comping, mseg, and chopping audio in the sampler. So one out of three ain't bad.

I'm surprised that midi comping still is not in there, seems like an easy addition.

[pdxindy]

I'm surprised that midi comping still is not in there, seems like an easy addition.

I would like to think that it is because they are creating a sophisticated hybrid comping

[Fannon]

I've now started trying the beta. Installed Beta 5 but it crashed immeadiately for me. Then tried Beta 4, same behavior.

Anyone else got this? Beta 5 changelog seems to be about a bug like that. I've sent crash report to beta@bitwig.com of course.