brummer10 / guitarix.vst

guitarix vst3 wrapper for linux
62 stars 1 forks source link

UI not loading (getting blank window) #13

Open khashayarmotarjemi opened 8 months ago

khashayarmotarjemi commented 8 months ago

I get a blank window when trying to use the UI. I've built it from this repository, and I'm using Arch Linux. I did a system update and tested it again and still got the blank screen.

Reaper: image

Ardour: image

But the alternative UI works: image

Thanks for the awesome work tho :)

brummer10 commented 8 months ago

Do you've the same issue with the prebuild binary?

khashayarmotarjemi commented 8 months ago

Do you've the same issue with the prebuild binary?

Yes. I just now installed the binary again and got the same UI.

brummer10 commented 8 months ago

Very strange. I've no idea what that could be. Here is how it looks for me on debian/sid: i

a other idea may be building it against the system juce. make USE_SYSTEM_JUCE=1 but that is just a shot in the dark.

crshrprt commented 7 months ago

I have the same problem, on Debian Sid, with the binary release. If I compile it with make USE_SYSTEM_JUCE=1 the UI loads correctly.

I tried on these hosts: Ardour 8.2 BespokeSynth nightly Carla 2.5.8

brummer10 commented 7 months ago

Using debian/sid here as well. The binary version loads here fine in all hosts I checked so far, including Ardour 8.2 from debian/sid and as well in the official Ardour nightly build. However, it's good to know that it works with the sytem juce flag in cases were the provided binary didn't work. I may consider to updated the used juce version.

maxigaz commented 6 months ago

On Arch Linux, using Guitarix.vst3.zip from the releases page (v0.3), the UI window is empty for me as well when loaded in Bespoke. In Carla, the UI window doesn't appear at all.

I've tried building it myself with the USE_SYSTEM_JUCE=1 flag, but it fails with an error. Here's the terminal output (after git clone https://github.com/brummer10/guitarix.vst and git submodule update --init --recursive).

❯ make -j $(nproc) USE_SYSTEM_JUCE=1
egrep: warning: egrep is obsolescent; using grep -E
INFO: Submodule up to date
make[2]: arch: No such file or directory
make[2]: arch: No such file or directory
INFO: Using system Juce modules [/usr/share/juce]
make[1]: arch: No such file or directory
make[1]: arch: No such file or directory
[10%] Compiling include_juce_core.cpp
../../JuceLibraryCode/include_juce_audio_plugin_client_utils.cpp:8:10: fatal error: juce_audio_plugin_client/juce_audio_plugin_client_utils.cpp: No such file or directory
    8 | #include <juce_audio_plugin_client/juce_audio_plugin_client_utils.cpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[11%] Compiling include_juce_data_structures.cpp
make[1]: *** [Makefile:870: build/intermediate/Release/include_juce_audio_plugin_client_utils_e32edaee.o] Error 1
[12%] Compiling include_juce_events.cpp
make: *** [makefile:39: Builds/LinuxMakefile] Error 2
brummer10 commented 6 months ago

Seems they've removed juce_audio_plugin_client_utils.cpp from the juce modules. I've implemented a fix for that now in the makefile. You should pull the latest revision, should work now.

make[1]: arch: No such file or directory

You should as well install the Coreutils package to allow optimisation for your build.

Alternative there is a arch package available here: https://aur.archlinux.org/packages/guitarix.vst

maxigaz commented 6 months ago

Seems they've removed juce_audio_plugin_client_utils.cpp from the juce modules. I've implemented a fix for that now in the makefile. You should pull the latest revision, should work now.

~I tried it again recently, and build still failed.~

You should as well install the Coreutils package to allow optimisation for your build.

I already had coreutils installed.

~I'm going to open a separate issue for the build errors I'm seeing so as not to deviate too much from the original topic.~

Update: I've just tried building once again with USE_SYSTEM_JUCE=1, and no issues this time. Thank you!

indeedwatson commented 5 months ago

I'm on arch linux, and I have this issue even if I build with USE_SYSTEM=JUCE=1, anything else I can try?

maxigaz commented 5 months ago

I'm on arch linux, and I have this issue even if I build with USE_SYSTEM=JUCE=1, anything else I can try?

Did you try USE_SYSTEM=JUCE=1 or USE_SYSTEM_JUCE=1? Only the latter is correct.

indeedwatson commented 5 months ago

I'm on arch linux, and I have this issue even if I build with USE_SYSTEM=JUCE=1, anything else I can try?

Did you try USE_SYSTEM=JUCE=1 or USE_SYSTEM_JUCE=1? Only the latter is correct.

Yeah that's a case of me making a typo in the comment, not in the actual command.

But while we're at it, I'm gonna double check that this is the section where that should go:


build() {
  cd $_pkgname
  make USE_SYSTEM_JUCE=1
}
brummer10 commented 5 months ago

make print a INFO line inform you if the included or the system Juce modules been used to build. Do you've the issue with other juce based plugs as well, or just with guitarix.vst?

indeedwatson commented 4 months ago

make print a INFO line inform you if the included or the system Juce modules been used to build. Do you've the issue with other juce based plugs as well, or just with guitarix.vst?

Sorry for the delay. Do you mind telling me how to print the INFO?

I don't have any issues with other plugins but I'm not sure which others are juce based.

tsundokul commented 4 weeks ago

@indeedwatson do you use wayland? I'm having the same issue, I have compiled against system JUCE 7.0.3 and still no UI. However for this version, Projucer doesnt run on my Wayland system but the latest 8.X does. So in my case I suppose it's related to the JUCE version being used by the plugin

tsundokul commented 4 weeks ago

UPDATE: I FINALLY GOT IT WORKING!!! 💜

The solution was to use JUCE 7.0.5, compiled with JUCE_DIR

edit: so I guess the easy fix is to bump the bundled JUCE version from 7.0.3 to 7.0.5