u-he

ejgallego · Post by **ejgallego** » Thu Dec 21, 2017 1:36 am

I've tested the last two builds (6820/6821), Ubuntu 17.04, BitWig 2.2.3.

Indeed, the GUI is not working properly in VST2. I can edit, but the lag is very high and sometimes it misses mouse clicks, it looks like the it is not running. VST3 doesn't display anything.

I'm afraid the plugin GUI is not usable in this state.

Thanks for all the hard work!

glokraw · Post by **glokraw** » Thu Dec 21, 2017 8:28 am

Groundbreaking work to overcome years of dubious
linux coding practices, or just finding better ways than what
was once considered necessary, or lots of both.
When it's ready, the path forward will be well marked,
and easier for the Cat, or whatever else comes out next.
Cheers

David Else · Post by **David Else** » Thu Dec 21, 2017 9:35 am

abique wrote:Hello guys,
Next version to try: http://uhedownloads.heckmannaudiogmb.ne ... 821.tar.gz

Remember it is a testing build, not a production one.

Many thanks

I am afraid these:

- Do not show up in Reaper on Centos 7.4. (gkt2 2.24.31, gtk3 3.22.10)

The binaries are compatible with gcc 4.8.x? Ubuntu 14.04 LTS and Centos 7.x need that... please make it work with them!

- In Fedora 27 it is a blank GUI again. (gtk2 2.24.31, gtk3 3.22.26)

OldFuzzface · Post by **OldFuzzface** » Thu Dec 21, 2017 10:46 am

my results for 6821 (Arch, 4.14.6, nvidia-387.34, gtk2 2.24.31, gtk3 3.22.26) :

VST2: GUI is showing, but (as mentioned before) extremely laggy and not really usable. It get worse somehow if one tries to use the preset browser.

VST3: does not even show.

Anyway, thanks. I have to agree: what you (and u-he) are doing here is groundbreaking stuff.

abique · Post by **abique** » Thu Dec 21, 2017 11:13 am

Yes VST2 will be a bit laggy :/ this all depends on the idle() call frequency from the host.
VST3 will be smooth but you need an host which supports the latest SDK, I've added that support to Bitwig, but for the next major release so you have to wait... a little bit I hope

I did some tests with Renoise, and I would say that it was not super smooth, but definitely usable to me. Did anyone try it with Ardour?

Many thanks guys

ejgallego · Post by **ejgallego** » Thu Dec 21, 2017 11:22 am

abique wrote:Yes VST2 will be a bit laggy :/ this all depends on the idle() call frequency from the host.

Did anyone try it with Ardour?

I've just tried; I am much afraid to say that the new version of Repro is unusable in both BitWig and Ardour

[Ardour 5.11 btw]

hihu · Post by **hihu** » Thu Dec 21, 2017 11:26 am

Hello, I have installed the newest version now (6821) but I still have no luck. The plugins don't get recognized by the host. I also tried with Ardour but also no luck. So I thought maybe some kind of permission issue as they often occur.

I changed the group permission to my user like the other plugins are and also made the .so file executable. But still not working here.

ejgallego · Post by **ejgallego** » Thu Dec 21, 2017 11:38 am

My guess is that those with less powerful computers could be the more likely to suffer the lag.

If that is the case, maybe the whole non-threaded approach is a bit worrying, as if the host is overloaded / busy even many other cores may be available lag will suffer, not to speak of having like 10 plugin windows opened.

David Else · Post by **David Else** » Thu Dec 21, 2017 12:17 pm

abique wrote:Yes VST2 will be a bit laggy :/ this all depends on the idle() call frequency from the host.
VST3 will be smooth but you need an host which supports the latest SDK, I've added that support to Bitwig, but for the next major release so you have to wait... a little bit I hope
I did some tests with Renoise, and I would say that it was not super smooth, but definitely usable to me. Did anyone try it with Ardour?

Many thanks guys

With the old VST3 version that did work, the MIDI learn never worked. If we will need to move to VST3 for super smoothness, I hope all will be well with the MIDI learn

Have you tried with the latest Reaper Linux version https://www.landoleet.org/ , do you know if it supports what you need?

Are we all good with gcc 4.8.x? I am getting a pit paranoid about the u-he compatability, spent the entire week moving my main studio computer to Centos 7.4, it is working fantastically so far. They back port all the kernel chip-set compatibility and fixes, and the Gnome is very recent now too. It may have an ancient gcc version, but everything else is very modern.

Sorry to ask so many questions, it's just super exciting to be getting repro-5 on Linux!

mevla · Post by **mevla** » Thu Dec 21, 2017 1:29 pm

abique wrote:I did some tests with Renoise, and I would say that it was not super smooth, but definitely usable to me. Did anyone try it with Ardour?

I do not know about Ardour. But it does runs fine in Mixbus32C 4.3.19 released a couple of days ago. Same system as described previously. Mixbus32C is the so-called 'gcc5' version.

reproMixbus.jpg

ejgallego · Post by **ejgallego** » Thu Dec 21, 2017 1:51 pm

mevla wrote: I do not know about Ardour. But it does runs fine in Mixbus32C 4.3.19 released a couple of days ago. Same system as described previously. Mixbus32C is the so-called 'gcc5' version.

Mevla, care to post what your system specifications are?

It seems the problem we are having could be that the new version runs laggy in systems that don't have a super-powerful CPU.

abique · Post by **abique** » Thu Dec 21, 2017 2:01 pm

Can you try with renoise?

StudioDave · Post by **StudioDave** » Thu Dec 21, 2017 2:30 pm

Greetings !

Here's what the latest Repro-1 looks like on BWS 2.2.3 :

Not so good. Repro-5 displays well but doesn't resize. Controls on R5 are sometimes unresponsive until I've tried them a few times, other controls work fluently with no "warm-up". I can select presets and the sound is good (to put it mildly).

Hardware here is an AMD FX6300 6-core CPU at 3.5 GHz, GPU is an nVidia GeForce 210 chipset. I'm using nVidia's binary driver, btw.

Best,

dp

abique · Post by **abique** » Thu Dec 21, 2017 2:58 pm

Bitwig Studio 2.2.3 is not calling effIdle() on Linux. I'll repeat myself again, that will work fine with the next *MAJOR* update of Bitwig Studio, 2.2.3 was a minor update.

mevla · Post by **mevla** » Thu Dec 21, 2017 4:10 pm

ejgallego wrote:Mevla, care to post what your system specifications are?
It seems the problem we are having could be that the new version runs laggy in systems that don't have a super-powerful CPU.

I already described the system a few replies back, although there were no hardware specs. Here they are:

Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
16 GB RAM
M-Audio 1010LT audio card (if it matters at all ...)

u-he

KVR Audio

Linux public beta (4408)