u-he

mevla · Post by **mevla** » Mon Dec 18, 2017 5:46 pm

abique wrote:Bitwig 2.2.2 will likely not display the UI because it is not calling idle() on Linux if I'm correct. That'll be fixed for the next major release.

Using latest Bitwig 2.2.2 2.2.3 here. Linux Mint 18, KDE version. Repro-5 and Repro-1 works very fine, the GUI can be resized to any size.. Building up a new piece right now using many instances of Repro-5 as you made it available yesterday. No problem in sight. Both VST and VST3 can be seen from the plugin list although Urs said to not bother with VST3, so I'm not

UPDATE: I missclicked on a VST3. Whereas the VST works just fine, the VST3 GUI will not show.

If I can be of any help by listing librairies, whatever, let me know.

bitwigRepro5.jpg

Sorry for the ungraceful cut in there. Looks like the people at Gimp do their best to make it extra hard to use their software. Last time all the tools were shown right at the start, not anymore. Going through the menus did not reveal the color picking tool. I guess they found it was becoming too easy to use.

Back on topic. Only thing I noticed is perhaps some kind of real-time interaction between the two Repros which results in Repro-1 sounds heard much less (when compared to Repro-1 alone in another session with same volume output and same patch). However, this was with the Repro-5 beta and 900 presets copied from a Mac release candidate version. I haven't checked with yesterday's version yet.

mevla · Post by **mevla** » Mon Dec 18, 2017 5:49 pm

Subarumannen wrote: Why can we not have the latest beta versions also published in the main Linux public beta thread (4408)
I know the name is wrong but some new versions are published there and some are not. The thread could be renamed to just Linux Beta thread and the freshest betas could be in first post.

If the version number is removed from the subject line, please then replace it with the date of the latest update of the bunch so it's easy to see at a glance if something was updated.

OldFuzzface · Post by **OldFuzzface** » Mon Dec 18, 2017 6:50 pm

abique wrote:Bitwig 2.2.2 will likely not display the UI because it is not calling idle() on Linux if I'm correct. That'll be fixed for the next major release.
Also this build is more like an alpha than a beta...

hi, I just tried this build on Arch with nvidia 387.34 and indeed got no graphics at all (no logs about shm though). does this mean I have to wait for a major bitwig update to use Repro? I hope not ...

I also agree that it would be very nice to have a fixed place to get new versions, stumbling onto this by accident sucks. a little.

abique · Post by **abique** » Mon Dec 18, 2017 8:07 pm

Hello everybody,

Many thanks for your testing!

So please hold on the testing for a while. I'll come back with some new builds later and maybe I'll see if I can backport the vst3 changes to bitwig 2.2 so you would have a daw to test.

Cheers,
Alex

OldFuzzface · Post by **OldFuzzface** » Mon Dec 18, 2017 10:41 pm

nice, thanks! meanwhile I reverted to 6640 for the time being.

cheers from kreuzberg!

mevla · Post by **mevla** » Tue Dec 19, 2017 1:57 am

abique wrote:So please hold on the testing for a while. I'll come back with some new builds later and maybe I'll see if I can backport the vst3 changes to bitwig 2.2 so you would have a daw to test.

Please don't break what works very well today !

Cheers/Tschüß

abique · Post by **abique** » Tue Dec 19, 2017 12:20 pm

mevla wrote:
abique wrote:So please hold on the testing for a while. I'll come back with some new builds later and maybe I'll see if I can backport the vst3 changes to bitwig 2.2 so you would have a daw to test.
Please don't break what works very well today !

Cheers/Tschüß

OKay

re23071998 · Post by **re23071998** » Wed Dec 20, 2017 3:31 am

Hi abique,

I've requested this many times.
But, can you please separate RePro-1 and RePro-5 into different .so ??
and also for Zebra2, just like the windows version

Please....

abique · Post by **abique** » Wed Dec 20, 2017 9:49 am

The plugins are built to use the shell interface, there won't be any "separation". Your best hope is that the host you are using start supporting vst shell plugins.

Regarding the new testing build, I've found that when you are using Nvidia drivers, I can't create shared pixmaps, because the pixmaps resides in the hardware memory. So I now have a fallback in such case.

New build coming soon.

hihu · Post by **hihu** » Wed Dec 20, 2017 11:12 am

Hello mevla. Seems that you are the only one without problems.

I have updated to Bitwig 2.2.3 but still the plugins don't get recognized by Bitwig studio. Can anyone confirm this? So I cannot even load them into the project.

Does it has something to do with the desktop environment as mevla is using KDE.

greetings

mevla · Post by **mevla** » Wed Dec 20, 2017 1:46 pm

hihu wrote:Hello mevla. Seems that you are the only one without problems.

I have updated to Bitwig 2.2.3 but still the plugins don't get recognized by Bitwig studio. Can anyone confirm this? So I cannot even load them into the project.

Does it has something to do with the desktop environment as mevla is using KDE.

I updated the reply I made above, the one with the screenshot, but I'll reiterate here. I missclicked on th VST3 version of Repro-5. The GUI did not appear. The OS created the window frame but nothing was drawn inside. It was transparent, showing Bitwig underneath.

So this means: on a same system, same DAW, same libraries, same everything (*), the VST Repro-5 plugin works very nicely whereas the VST3 version does not display at all, which perhaps rules out GUI toolkits and libraries. In this case. Just maybe. In all cases, both the VST and VST3 plugins are of course listed in Bitwig. I'll update this reply later with a screenshot.

I have now a couple of Bitwig 2.2.3 sessions with several tracks each with a Repro-5 regular VST. And again, as Urs replied to not bother with VST3, I'm not. I'm happy with the regular VST.

(*) Let me know if I can help by sharing library, etc, information about the system I use for comparison purposes. Linux Mint 18, KDE version, no audio repo, only the regular system + the low latency kernel provided by the LM18 repo, and some system adjustments for low latency (eg. jackd buffers, scaling governor. somesuch).

Cheers.

mclstr · Post by **mclstr** » Wed Dec 20, 2017 3:03 pm

abique wrote:....TNew build coming soon.

Thanks for the effort.

abique · Post by **abique** » Wed Dec 20, 2017 11:34 pm

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

lunardigs · Post by **lunardigs** » Thu Dec 21, 2017 12:23 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

This is the first one that's broken for me. Basically, the GUI is un-alterable with my mouse. I see blinking lights, etc., but I can't edit any parameters. Moreover, the VST3 version doesn't render the GUI at all; it just looks like a blank window frame with nothing inside--in fact, it's transparent.

I'll explore some more and report further.

Btw, no matter what, thanks for the new build!

mevla · Post by **mevla** » Thu Dec 21, 2017 1:31 am

6821 VST 1 and 5 continues to work very fine here ! Nothing broken !

System specs as described previously. If there's a difference, I'd say that it now runs smoother in Bitwig. Previously there could be some clicks heard (xruns I believe) from time to time whereas now all Repros are running very smooooth. Great to see and hear all that working well !

Or shall I say, I'm afraid everything works well !

bitwig223UheGalore.png

u-he

KVR Audio

Linux public beta (4408)