Linux public beta (4408)

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

Post

More boring than difficult?
Perhaps they check the server logs for the
week following each release and update release,
and measure for trends, and plan ahead accordingly.
Likely the mac/pc dates are not the same as
the linux versions, so their interns probably
keep different spreadsheets that get double-checked
if the revenue stream shows a jump or a dip.

I bet they'd be a success even if they switched
to selling bratwurst and strudle :hyper:
Cheers

Post

abique wrote:Hello,

I'll publish the latest build once Bitwig 2.3 Beta 1 is out.

Alex :)
Hello and thank you for your magnificent work.

I'm about ready to give up on Linux (on the metal). I presumed it would be fine on my new build, but no (or little) support for 8th gen. Intel processors yet and Linus is not too happy about the design.

I am about to go where I have not gone before and install Windows 10 (and a Mint 18 VM asap)!

Post

Hello,

Here is a new build:

http://uhedownloads.heckmannaudiogmb.ne ... 987.tar.gz
http://uhedownloads.heckmannaudiogmb.ne ... 987.tar.gz

It fixes the tag browser painting, and now zebra2 shows proper gradients in the wave editor.

Cheers,
Alex.

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
Hello,

First I want to thank you for for those amazing synths and for releasing Linux versions to public.

I am part of the Zynthian open source project which is an open hardware synth based on Rapberry.
You can find more details at http://zynthian.org (http://zynthian.org).

This platform includes many linux well known synths as ZynAddSubFX, LinuxSampler etc, as well as a LV2 host (as part of the MOD-UI project)
We wish we could use the U-he LV2 plugins on the platform but in order to work, they need to be compiled for ARM CPUs.

So, this is a question for linux experts :) :
Have you tried by chance to compile the plugins for ARM CPUs to work on Raspberry ?
If not Is there a chance to get those plugins compiled for ARM ?

Kind Regards,
Claude

Post

Only intel platform is supported for now, because intel intrinsic are used in the source code.

Post

claudev wrote: I am part of the Zynthian open source project which is an open hardware synth based on Rapberry.
You can find more details at http://zynthian.org.

This platform includes many linux well known synths as ZynAddSubFX, LinuxSampler etc, as well as a LV2 host (as part of the MOD-UI project)
We wish we could use the U-he LV2 plugins on the platform but in order to work, they need to be compiled for ARM CPUs.
Claude
Wow ... you guys are awesome. Btw, I have a MOD DUO and it's pretty mind blowing.
abique wrote:Hello,

Here is a new build:

http://uhedownloads.heckmannaudiogmb.ne ... 987.tar.gz
http://uhedownloads.heckmannaudiogmb.ne ... 987.tar.gz

It fixes the tag browser painting, and now zebra2 shows proper gradients in the wave editor.

Cheers,
Alex.
... and, abique, you're awesome! Thanks for the new builds.

Post

Thanks again for the builds abique! It is working better and better under BitWig 2.3 beta!

Tag selection works now. UI seems to work well. However, still not menus. So it is not possible to tag. Also, it is not possible to write in the search bar . dialog.64 segfaults in the usual way.

p.s: A strange thing about the builds is that the tarball has suffix .tar.gz , however, it is not compressed. Is that intentional? Shouldn't then the gz suffix removed? Cheers!

Post

octave9 wrote:
I am about to go where I have not gone before and install Windows 10 (and a Mint 18 VM asap)!
Why not install win 7, and let microsneak install win 10 while you're
not looking? :hihi:

Post

ejgallego wrote:Thanks again for the builds abique! It is working better and better under BitWig 2.3 beta!

Tag selection works now. UI seems to work well. However, still not menus. So it is not possible to tag. Also, it is not possible to write in the search bar . dialog.64 segfaults in the usual way.

p.s: A strange thing about the builds is that the tarball has suffix .tar.gz , however, it is not compressed. Is that intentional? Shouldn't then the gz suffix removed? Cheers!


So if you try to use our dialog from the terminal it crashes?
I'm not sure what to do about it. It is just a plain simple gtk application which does nothing very complex.
I could provide a debug build of this dialog executable so you can give me back a better backtrace :)

Regarding the tarball if they're not compressed then it is a mistake.

Good night!

Post

The tarballs have always been like that :) The dialog app seems to crash on every Ubuntu 17.10. Please post a debug build.

Post

abique wrote: So if you try to use our dialog from the terminal it crashes?
I'm not sure what to do about it. It is just a plain simple gtk application which does nothing very complex.
I could provide a debug build of this dialog executable so you can give me back a better backtrace :)
Exacty. It gets SIGABORT, it started happening after Ubuntu 16.10. I agree it looks very strange, it would be amazing if you could push a debug build. However, I think Ubuntu users have been able to consistently reproduce the crash so it should be easy to debug in-house too.
abique wrote: Regarding the tarball if they're not compressed then it is a mistake.
It looks indeed like it, but as mentioned by vicenzomi, they have been always like that.
abique wrote: Good night!
Good night and thanks for your help!

Post

Well, so after a bit of strace and gdb it certainly looks like the abort is coming from libmirclient, which is in turn called by GTK. I am not sure why that is happening, but I wouldn't be surprised if this is just some Ubuntu bug. abique, maybe the init code is too optimistic wrt gtk backends? Typical libgtk code quality doesn't help I'm afraid :)

The workaround is to explicitly tell dialog to load the right backend, in this case x11. Thus:

Code: Select all

GDK_BACKEND=x11 ./dialog.64 menu test
works again, and I am a very happy person that will finally go to bed with all my Repro menus working! Note that while I can input text, search seems to be a noop for now. The rest of the UI is working super. I can't believe I have the menus back after 1 year!!!

For those wanting to fix the menus, the quickest fix is to add

Code: Select all

export GDK_BACKEND=x11
to the .u-he/$plugin/dialog shell script. :party:

Post

Wow thanks a lot...

Post

vincenzoml wrote:Wow thanks a lot...
Most welcome, I assume the workaround works for you?

A guess on what could be happening is that `dialog` enumerates all the GTK backends and just picks the first. Since Ubuntu 16.10, gtk is linked with the backend MIR [which is abandonware at this moment I think, and should never ever do a sigabort anyways].

Thus, the faulty GTK backend is selected and here you have it, boom! It is very likely that Ubuntu stops shipping the MIR backend in the future, if that happens, the problem will fix by itself.

However, it wouldn't hurt to make u-he's GTK code more robust.

Post

ejgallego, thank you very much for this information!

I'll add this to the Linux README.

MIR is a strange story...

Locked

Return to “u-he”