I apologize for the chaos I’ve created in the discussion, but since I’m probably the only one with the problem, I’m constantly moving to new information and older information is no longer valid. And in order not to unnecessarily stir up unnecessary information, I’ve deleted some of the previous messages.
Distillation:
Bitwig 5/6
Scaler 3.2.1
Windows 11
After activating, deactivating, and then reactivating a plugin in a chain on an instrumental track, Scaler 3 will forget its custom settings for Global Motion and Bind Zone.
The problem is really critical because if the project is saved to disk after a failure, it is saved in a broken state.
Hi @tomasmark79 We can’t replicate this. Are you activating the Performance and BIND within Scaler 3 or via automation. Please try in standalone or another DAW. This seems related to Bitwig and its automation recall?
Enabling the TOGGLE FLYING AUTOMATION LANE feature in Bitwig 6 causes the loaded Scaler 3 to seem to be uninitialized.
I am also reporting this finding to Bitwig support.
Thank you.
update: This was just an assumption that later turned out to be wrong.
Anyway:
I have found partially workaround for re-force the Global Motion to be ON by Biwtig modulator Globals. This modulator ensure the Scaler 3 Performance always turned ON when transport play in Bitwig.
How to:
For re-force the Global Motion to be ON in Scaler 3 You have to map Play modulator to Global Motion parametr in Scaler 3. This ensure that the initializing bug will be skipped.
However, we are still experiencing an issue with the Bind Zone being forgotten when reactivating the plugin in Bitwig 5/6. The Bitwig team has confirmed that this is a problem with at the plugin side.
My workflow workaround is that I have bought a Chord Prism II plugin and using the Scaler 3 purely for performances, which are now functional with a replacement modulator solution.
After installing 6.0.4, it is very interesting that the first two instances of Scaler 3 in the new project behaved perfectly correctly. However, the third instance again showed a loss of saving both parameters. Too bad.
According to my testing. One or two instances of the Scaler 3.2.2 plugin behave correctly in Bitwig 6.0.4.
In case of adding another instance of Scaler 3.2.2, the consistency is already broken across all instances of Scaler 3 in the project.
This probably indicates a problem with sharing parameters within Scaler 3. But I am not sure. Bitwig has not commented on this issue further, even though I have sent them information.
Hi @tomasmark79 thank you for all the information here. I am able to replicate this issue in Bitwig Studio 6 on Windows 11 where the global motion and bind areas are not enabled after deactivating then reactivating the Scaler 3 plugin.
Just for clarity, Scaler 3 seems to have no trouble retaining settings after bypassing and re-enabling in Bitwig Studio, or saving and loading a session. So this issue appears to only occur after deactivating then re-activating the plugin. Also after loading a saved Bitwig project after Scaler 3 has been deactivated, the project does reload correctly, except for the fact that Scaler 3’s global motion and bind area may be disabled. Does that sound correct?
We can certainly forward this to the development team to try to figure out why this is happening, but I wanted to make sure I was understanding you properly.
