Hello,
In Linux 64 bit (Linux Mint 17), using the latest Bitwig 1.3.9, there is a problem loading VST plugins from different makers, when a u-he synth is used.
The workstation has i5 quad core processor 3.40GHz with 16GB RAM.
Reproducing the problem is easy. For instance, load a few instances of any u-he synth. Say, 5 synths. You may mix them, you can go light and have 5 Hive plugins or go a bit more heavy and have 5 Diva loaded. It does not matter. The problem also shows with having only one plugin. I am using many to show that there is no issue in loading many plugins.
Next, load one DiscoveryPro 6.6 synth or one Redux. All plugins will crash. Click on reload them all, and all will crash again. Reload only DiscoveryPro/Redux and it will load. Then reload a single u-he synth and both plugins will crash.
Vice-versa is also true. Start with 5 DiscoveryPro synths then load a single u-he synth. Crash.
However, load 5 DiscoveryPro and one Redux and they will live together just fine. Or 5 Redux and 5 DiscoveryPro: just fine.
This obviously makes working with VST plugins from different makers impossible with u-he synths.
If needed I will be glad to provide debug log info, etc, if you tell me how.
Bitwig: u-he plugins cannot work with other makers plugins
-
- KVRAF
- 3729 posts since 3 Nov, 2015
-
- KVRAF
- 6542 posts since 9 Dec, 2008 from Berlin
Do you run the latest versions of all plugins concerned?
Did you try the option to run each plugin in it's own process?
Preferences -> Plug-in management -> "Each plug-in"
Any other option will crash all plugins if one plugin crashes, so using the above option should help you find the offender.
You can also check on the same preference page the button at the bottom "Show errors found with plugins".
Did you report the issue to Bitwig tech support too?
https://www.bitwig.com/en/support/tech-support.html
Cheers,
Tom
Did you try the option to run each plugin in it's own process?
Preferences -> Plug-in management -> "Each plug-in"
Any other option will crash all plugins if one plugin crashes, so using the above option should help you find the offender.
You can also check on the same preference page the button at the bottom "Show errors found with plugins".
Did you report the issue to Bitwig tech support too?
https://www.bitwig.com/en/support/tech-support.html
Cheers,
Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube
UrbanFlow.art · Instagram · YouTube
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
I think I have the recent versions.
Now, the "Each plug-in" option solves the problem, thanks. I did a simple test loading many DiscoveryPro with several u-he synths and they are all OK. This was a simple test, though, nothing elaborate.
What are the implications of using "Each plug-in" on performance ? It's not the default after all. Should it be made so that the exclude list contains all plugins that work together well ? Or just wait for problems to start excluding ?
I haven't notified Bitwig simply because the DiscoveryPro and Redux plugins works well together using the original plug-in management option. That very likely puts the emphasis on the u-he synth plugins.
Now, the "Each plug-in" option solves the problem, thanks. I did a simple test loading many DiscoveryPro with several u-he synths and they are all OK. This was a simple test, though, nothing elaborate.
What are the implications of using "Each plug-in" on performance ? It's not the default after all. Should it be made so that the exclude list contains all plugins that work together well ? Or just wait for problems to start excluding ?
I haven't notified Bitwig simply because the DiscoveryPro and Redux plugins works well together using the original plug-in management option. That very likely puts the emphasis on the u-he synth plugins.
-
- KVRAF
- 6542 posts since 9 Dec, 2008 from Berlin
I always used the "Each plugin" option. For me, the implications on performance are close to nil. I often use unstable plugins, so this option is just brilliant for me.
Just check it out on your machine with the same project and the three different options and see how many plugin instances you can use before you get crackling with the different options.
"32-bit/64-bit" means that all plugins of the same bit depth run in the same sandbox and all crash together if one of them has a problem. I personally think it's the least interesting option.
The most performant option (in theory at least) would be "Only as bit-bridge" where plugins of the same bit depth as the OS (= the the same bitdepth as the BWS audio engine) are running directly in the audio engine (basically like in most other DAWs, without sandboxing), so if one plugin crashes, the audio engine crashes (but not the application and the audio engine can be restarted with the button in the upper left corner). This also allows using plugins that communicate with each other by running in the same address space (like Satin, some Melda plugins etc.).
"Each plugin" used to be the default, I don't know exactly why it was changed.
I personally don't care for "defaults" - I try to use what makes sense.
If "Each plugin" works well for you (as it does for me for years now), there is nothing to worry about. If you have a slow computer, try "Only as bit-bridge" and see if it improves performance for you.
BTW. I originally thought you posted in the Bitwig forum - I didn't intend to interfere with you asking u-he about he problem - sorry about that
Cheers,
Tom
Just check it out on your machine with the same project and the three different options and see how many plugin instances you can use before you get crackling with the different options.
"32-bit/64-bit" means that all plugins of the same bit depth run in the same sandbox and all crash together if one of them has a problem. I personally think it's the least interesting option.
The most performant option (in theory at least) would be "Only as bit-bridge" where plugins of the same bit depth as the OS (= the the same bitdepth as the BWS audio engine) are running directly in the audio engine (basically like in most other DAWs, without sandboxing), so if one plugin crashes, the audio engine crashes (but not the application and the audio engine can be restarted with the button in the upper left corner). This also allows using plugins that communicate with each other by running in the same address space (like Satin, some Melda plugins etc.).
"Each plugin" used to be the default, I don't know exactly why it was changed.
I personally don't care for "defaults" - I try to use what makes sense.
If "Each plugin" works well for you (as it does for me for years now), there is nothing to worry about. If you have a slow computer, try "Only as bit-bridge" and see if it improves performance for you.
BTW. I originally thought you posted in the Bitwig forum - I didn't intend to interfere with you asking u-he about he problem - sorry about that
Cheers,
Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube
UrbanFlow.art · Instagram · YouTube
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Sieth gut aus!
I'll leave it at the "Each plugin" option. Thanks for the "bit-bridge" overview.
Tschüß.
I'll leave it at the "Each plugin" option. Thanks for the "bit-bridge" overview.
Tschüß.
