Linux public beta (4408)

Official support for: u-he.com
Locked New Topic
RELATED
PRODUCTS

Post

abique wrote:Yes this is a known issue and it is already fixed in git.
I update the plugins tonight.
Excellent.

Another thing I've noticed is that it seems that U-He plugins now more often require to be run in it's own thread in Bitwig or the audio engine may randomly crash when I initiate a use of other VSTs in the projects - this was never an issue earlier. I'm not sure if it is Bitwig or U-he who is to blame though - after all I am running a release candidate. is this a known issue too?

Something has happened somewhere.

Post

Beamboom, I use them in a single process and I have no issue, which vst are you using along the u-he ones?

Post

Beamboom wrote:... it seems that U-He plugins now more often require to be run in it's own thread in Bitwig or the audio engine may randomly crash when I initiate a use of other VSTs in the projects - this was never an issue earlier. I'm not sure if it is Bitwig or U-he who is to blame though - after all I am running a release candidate. is this a known issue too?

Something has happened somewhere.
Same here. Bitwig for Linux, 1.2.0, on Fedora 21 x86_64, with Planet CCRMA rt-kernel and Xfce WM. Adding *any* other plugin crashes BW's engine.

Best,

dp

Post

What is *any* other plugin? Can you give some explicit ones?

Post

Beamboom, what Linux distribution and kernel do you use?

Post

abique wrote:What is *any* other plugin? Can you give some explicit ones?
In this case any means literally any. Whatever else I have loaded (Vertigo, Pianoteq, Dexed, Bliss, Redux, Cabbage plugins, DISTRHO plugins, pizmidi plugins, Aspect, Sequent, et cetera) loading a u-he plugin crashes the other plugins unless the u-he plugs are designated to run in their own threads. Everyone gets along then.

But as Beamboom says, this could be all Bitwig's problem. I haven't tested the u-he plugins in Ardour or Renoise, if I have time today I'll see how they work in those DAWs.

Best,

dp

Post

OK, I'll try them along some discoDSP plugins.

Post

phantom-one wrote:Beamboom, what Linux distribution and kernel do you use?
Ubuntu 15.04 64bit, kernel 3.19.0-30-lowlatency
abique wrote:which vst are you using along the u-he ones?
Like StudioDave said it seems to be pretty much any VST, but to mention a few I'm sure I've experienced it with:

Loomer Sequent
Oxe FM Synth
Pianoteq 5 Stage
Others include the ones found here: http://distrho.sourceforge.net/ports

The effect VST don't even have to be chained to a u-he synth, it can be attached to any other virtual device: If a U-he synth (like Hive, who I most often use) exist in that project, chances are high that the Bitwig audio engine will crash.

... And then, remove the U-He plugins (like Hive), and you'll find they work fine with the other VSTs in the project. That fact is what makes me suspect the source of the problem is within the u-he plugins, and not Bitwig.

Post

Hey there,

I bumped the revision number, see the first thread.

Diva's leds are not working for now, but a few bugs were fixed. See the Linux ChangeLog.

Enjoy!

Post

Hi abique

I've just tried zebralette 3940 under qtractor and I'm happy to report that, as promised, undo seems to work now!

Thanks!

Post

Abique, please tell if there is anything I can help with in regards to the issue with the plugins needing their own threads. Don't be afraid to ask, I don't mind at all.
(alternatively send me a PM if you prefer).

Post

Beamboom, don't worry I'm on it :-)

Post

abique wrote:Beamboom, don't worry I'm on it :-)
abique Da Man ! :)

Post

Image

Post

StudioDave wrote:I haven't tested the u-he plugins in Ardour or Renoise, if I have time today I'll see how they work in those DAWs.
Tested Beatzille in Renoise without success (crashing). But I have old linux version (ubuntu 12.04).

Locked

Return to “u-he”