Bitwig 4.3 is out - Space & Tone (RELEASED)

[BobDog]

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.

Hi There,

This is nothing to do with the beta, here it is running in the release version of Bitwig:

Screenshot 2022-06-05 at 07.09.31.png

On the left is the vst3 version, on the right is the vst2 version.

You can see the empty bit at the bottom of the window.

OSX Uses a coordinate system where 0,0 is at the bottom left, here it looks like BW has it in the top left. There was a "bug" in the Juce sdk where this was happening but I'm pretty sure that BW do not use Juce?

I would contact BW over this, it is a hosting issue.

Or just use the VST2!

[lokanchung]

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!

Workflow is broad term. To be more precise, BItwig need more improvement on editing and navigation.

[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.

Hi There,

This is nothing to do with the beta, here it is running in the release version of Bitwig:

Screenshot 2022-06-05 at 07.09.31.png

On the left is the vst3 version, on the right is the vst2 version.

You can see the empty bit at the bottom of the window.

OSX Uses a coordinate system where 0,0 is at the bottom left, here it looks like BW has it in the top left. There was a "bug" in the Juce sdk where this was happening but I'm pretty sure that BW do not use Juce?

I would contact BW over this, it is a hosting issue.

Or just use the VST2!

Thanks for confirming @BobDog, and for digging a bit deeper. I've reported this to Bitwig as well.

As a side note, iZotope Relay vst3 window takes up my entire screen width when opening in Studio One. A bit weird both Bitwig and Studio One would have issues with Relay.

[dupont]

I have just had an audio interface crash with beta 4.
I put 2 bitwig filters after polymer, crash happens when I switch polymer filter type : no more sounds came out of the audio inferface until I reset it.

[aMUSEd]

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.

Hi There,

This is nothing to do with the beta, here it is running in the release version of Bitwig:

Screenshot 2022-06-05 at 07.09.31.png

On the left is the vst3 version, on the right is the vst2 version.

You can see the empty bit at the bottom of the window.

OSX Uses a coordinate system where 0,0 is at the bottom left, here it looks like BW has it in the top left. There was a "bug" in the Juce sdk where this was happening but I'm pretty sure that BW do not use Juce?

I would contact BW over this, it is a hosting issue.

Or just use the VST2!

Yeah same here with the VST3, can't be a JUCE bug as that would surely affect all plugins using JUCE and it doesn't even affect the other iZotope plugins as far as had a chance to test, only Relay

[ReleaseCandidate]

As a side note, iZotope Relay vst3 window takes up my entire screen width when opening in Studio One. A bit weird both Bitwig and Studio One would have issues with Relay.

No problems with the newest Relay in Live or Reaper on MacOS

[BobDog]

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.

Hi There,

This is nothing to do with the beta, here it is running in the release version of Bitwig:

Screenshot 2022-06-05 at 07.09.31.png

On the left is the vst3 version, on the right is the vst2 version.

You can see the empty bit at the bottom of the window.

OSX Uses a coordinate system where 0,0 is at the bottom left, here it looks like BW has it in the top left. There was a "bug" in the Juce sdk where this was happening but I'm pretty sure that BW do not use Juce?

I would contact BW over this, it is a hosting issue.

Or just use the VST2!

Yeah same here with the VST3, can't be a JUCE bug as that would surely affect all plugins using JUCE and it doesn't even affect the other iZotope plugins as far as had a chance to test, only Relay

It’s not a bug in the plug-in part of Juce but in the Hosting part of Juce, the host is in charge of the window not the plug-in. But as I said I wouldn’t think BW were using Juce.

[melime]

As a side note, iZotope Relay vst3 window takes up my entire screen width when opening in Studio One. A bit weird both Bitwig and Studio One would have issues with Relay.

No problems with the newest Relay in Live or Reaper on MacOS

you do know your posting your answer in a bitwig forum

[SLiC]

As a side note, iZotope Relay vst3 window takes up my entire screen width when opening in Studio One. A bit weird both Bitwig and Studio One would have issues with Relay.

No problems with the newest Relay in Live or Reaper on MacOS

you do know your posting your answer in a bitwig forum

Helps to know its a Bitwig bug and not a Relay bug surely?

[xbitz]

Changes in Bitwig Studio 4.3, Beta 5

IMPROVEMENTS

Delay+ device: Ducking action is nicer
MULTISAMPLE files containing FLAC files can now be saved and loaded
Re-organized Bitwig device categories:
New Distortion category (replacing Destruction, with all devices moving there)
New Modulation category (with Chorus+, Chorus, Flanger+, Flanger, Phaser+, Phaser, Rotary, and Tremolo moving there)
Comb is now in the Filter category
Plug-in categories work similarly for display
Actions that controlled transport playback state (such as pressing SPACEBAR) can now be invoked while adjusting a parameter via mouse or touch [28638]

FIXES

Delay+ device: FB FX chain was compensating latency for devices outside of it in the processing chain, limiting the minimum possible delay time when the chain was not empty
Delay+ device: Fixed an occasional error [28738]
Convolution device: Wet signal was not working when no impulse responses were installed and an impulse was dragged in manually [28729]
FX Layer device: Dragging a layer out onto an audio track was converting it to an instrument track and Instrument Layer [28410]
Tool device, etc.: Had a tiny gain boost (+0.0014 dB), now removed
FX tracks sending to other FX tracks could change sound when reordering the FX tracks [28805]
Dropping an audio time selection while holding ALT (to copy) could shorten existing events [28791]
Onsets weren't being analyzed for a sample dragged out of a multisample [28824]
When loading a sample file that results in an error, the loading task could appear hung, spinning indefinitely
Notification for engine audio thread hanging was missing localized text for terminating the audio engine
Recording of polyphonic pressure was not accurate [28346]
"Localization not found" button in Audio Device Notification [28820]
Inappropriately compressed multisample files (e.g. created by Moss conversion tool) weren't being loaded anymore [28818]
VST3: Now forwarding plug-in's output note expressions to the device chain
VST3: Was only showing the sidechain routing if the plug-in's only input bus is an auxiliary input
Controller API: Crash when zooming with no project open [28753]
Indexing could get stuck when encountered certain corrupt files [28829]
Strange situations could lead to an erroneous error ("At least two warp markers needed for warping") when previewing a file in the Browser Panel [28819]
192 kHz samplerate: Stretch modes lead to timing issues [28637]

have a good weekend for the dear devs ... too

[pdxindy]

CLAP support is just there now in Beta 5!

[SLiC]

CLAP support is just there now in Beta 5!

How can you tell? I was looking under driver (AISO, WASAPI etc) and I don't see anything obvious (but then I haven't really been following CLAP) I have MFM 2.5 which is supposed to be CLAP but I have no idea how things get selected- can you have some AISO and 1 CLAP for example...

[pdxindy]

CLAP support is just there now in Beta 5!

How can you tell? I was looking under driver (AISO, WASAPI etc) and I don't see anything obvious (but then I haven't really been following CLAP) I have MFM 2.5 which is supposed to be CLAP but I have no idea how things get selected- can you have some AISO and 1 CLAP for example...

On the Mac, it just works... CLAP is enabled by default now, so nothing to do. The public beta of MFM 2.5 is out of date and will not work!

There are internal betas of ACE, Diva and Hive that work with Beta 5 (also a newer MFM 2.5). The per voice modulation using Bitwig modulators is fantastic!

Next week there will be public betas and the official announcement of CLAP 1.0

[SLiC]

CLAP support is just there now in Beta 5!

How can you tell? I was looking under driver (AISO, WASAPI etc) and I don't see anything obvious (but then I haven't really been following CLAP) I have MFM 2.5 which is supposed to be CLAP but I have no idea how things get selected- can you have some AISO and 1 CLAP for example...

On the Mac, it just works... CLAP is enabled by default now, so nothing to do. The public beta of MFM 2.5 is out of date and will not work!

There are internal betas of ACE, Diva and Hive that work with Beta 5 (also a newer MFM 2.5). The per voice modulation using Bitwig modulators is fantastic!

Next week there will be public betas and the official announcement of CLAP 1.0

Ah, I am on PC so that may also be an issue I guess....but it all sounds promising.
is it almost like the UHE devices are now operating like Bitwig native devices?

[pdxindy]

CLAP support is just there now in Beta 5!

How can you tell? I was looking under driver (AISO, WASAPI etc) and I don't see anything obvious (but then I haven't really been following CLAP) I have MFM 2.5 which is supposed to be CLAP but I have no idea how things get selected- can you have some AISO and 1 CLAP for example...

On the Mac, it just works... CLAP is enabled by default now, so nothing to do. The public beta of MFM 2.5 is out of date and will not work!

There are internal betas of ACE, Diva and Hive that work with Beta 5 (also a newer MFM 2.5). The per voice modulation using Bitwig modulators is fantastic!

Next week there will be public betas and the official announcement of CLAP 1.0

Ah, I am on PC so that may also be an issue I guess....but it all sounds promising.
is it almost like the UHE devices are now operating like Bitwig native devices?

Works for PC also...

Yeah, the u-he synths work similar to Bitwig instruments. Workflow is a bit different obviously as plugins don't have device panel GUI's like Bitwig instruments. Also, voice stacking is not yet there and who knows when it will be. Apparently it is planned though.

Suddenly there are a lot more modulation options for Diva!