Bitwig 4.3 is out - Space & Tone (RELEASED)

[Trancit]

I also asked about the amount of index and cache files Bitwig keeps, seems they are never...I have over 7000 folders in my Bitwig Index Folder (in User/App data) and more than that in the Cache folder...not sure if this is related to the duration and frequency of scanning or if it can be tidied up (I have had Bitwig since V1 so maybe it just makes a new file very time you boot up!)...

I asked them as well if it is really necessary to put 80.000+ tiny files and only god knows how many folders on my system drive...

By the way I don´t know if you are aware of this but here is an answer from Bitiwg how to clean up the cache and index folder...
https://www.bitwig.com/support/technica ... anguage=en

It´s more related to plugins but I guess deleting the index folder cleans up all the file indexing too...

[SLiC]

I also asked about the amount of index and cache files Bitwig keeps, seems they are never...I have over 7000 folders in my Bitwig Index Folder (in User/App data) and more than that in the Cache folder...not sure if this is related to the duration and frequency of scanning or if it can be tidied up (I have had Bitwig since V1 so maybe it just makes a new file very time you boot up!)...

I asked them as well if it is really necessary to put 80.000+ tiny files and only god knows how many folders on my system drive...

By the way I don´t know if you are aware of this but here is an answer from Bitiwg how to clean up the cache and index folder...
https://www.bitwig.com/support/technica ... anguage=en

It´s more related to plugins but I guess deleting the index folder cleans up all the file indexing too...

Cheers- I did but it was Bitwig Pre-sets were duplicated however I have just traced this to user error as I had my 'library' file in 2 locations nested in folders

Must have happened when I moved Bigwig stuff of my SSD to a different drive when the content went up which may also explain some excessive indexing! Anyway- Fixed

[SmajjL]

I read at the yabridge site that robbert say that we can get Bitwig-flatpak/wine/yabridge to work if we start Bitwig through /var/lib/flatpak/app/com.bitwig.BitwigStudio/current/active/files/bitwig-studio
And it looks like it
https://github.com/robbert-vdh/yabridge

[Vladislav_Gronk]

I cannot wait for a big update that focuses on workflow improvements instead of pleasing the tinkerer crowd with new, fancy devices.

[SLiC]

Changes in Bitwig Studio 4.3, Beta 4

IMPROVEMENTS
When mousing over a modulator source that is assigned to only one destination, the window footer now tells you the one destination it is assigned to
Support for 64-bit floating point WAV files

FIXES
Launcher Clip Loop button would perform inconsistently when switched during playback [28676]
First kick in looping clip launcher clip louder than other clips if there's a note following behind the loop [28066]
8-bit WAV files had an incorrect DC offset
8-bit WAV files (that did not contain an even number of samples) could click
Linux: When using PipeWire, switching projects would leave a hanging buffer [28686]
Linux: Occasional audio engine crashes when switching to Jack API from PipeWire [28018]

REGRESSION FIXES (SINCE BETA 3)
Painting of Arranger and Detail Editor Panels was much slower in beta 3 than previous versions [28707]
Clip functions — such as Stretch, Scale, Reverse, etc. — were broken [28705]
Note Grid device: The default patch was producing silence, due to an unfortunate chain of circumstances
On duplicated tracks, FX Sends were all getting enabled [28688]
New Rename dialog for audio events was missing its title, etc. [28689]

[billcarroll]

My favorite fix explanation:

"Note Grid device: The default patch was producing silence, due to an unfortunate chain of circumstances"

Like, I can use this ... "due to an unfortunate chain of circumstances"

[SLiC]

A Series of Unfortunate Events....

[billcarroll]

A Series of Unfortunate Events....

Great title, for almost anything in our day and age

[nsq]

8-bit WAV files had an incorrect DC offset
8-bit WAV files (that did not contain an even number of samples) could click

They finally fixed it ... after 8 years.

[billcarroll]

Anyone else having issues with iZotope Relay in Bitwig 4.3 beta 4? I'm on a Mac, and when inserting and opening iZotope Relay on a track, the top of the plugin is not displayed properly and I'm unable to grab and move the plugin using the title bar.



Not sure if this was happening pre beta. Also, this is a new version of relay that came out a few days ago with some of the recent iZotope updates.

[BobDog]

Is there an empty area at the bottom of the same size as the missing top bit?

[billcarroll]

Is there an empty area at the bottom of the same size as the missing top bit?

No, just the top part is missing.

[_leras]

I cannot wait for a big update that focuses on workflow improvements instead of pleasing the tinkerer crowd with new, fancy devices.

I totally agree with this. A bit of catch up on the basic functionality would be great.

I love working in Bitwig, but I definitely think it can be made a bit smoother.

I think one step back, break a few small things, and two steps forwards would be huge and would set Bitwig up for years.

[SLiC]

To be fair, there have been 100's of little workflow improvements and core device improvements with the last few 'fx' based updates...and a decent reverb was really needed. The core FX are now excellent (and Polymer is now pretty powerful) , so I don't thein k we will see 'devises' as the main part of the next update.

It may well be that whilst they have been designing the new FX (and they have come out pretty fast) they have been working on other things in parallel...we still have 'networking' to come built in since v1!

[BobDog]

Is there an empty area at the bottom of the same size as the missing top bit?

No, just the top part is missing.

Weird, so that means window is too small. I’ll have a look tomorrow if they have a trial version and I will test it as well...