brummer10 / guitarix.vst Goto Github PK

Hi,

Just got it to compile successfully in Fedora37. This is the list of the packages in the same order as you listed those for Debian (if you'd like to add it to the docs). There are some exceptions:

• For libgcc I didn't find any dev packages, so I installed also gcc for good measure and it compiled okay.
• I installed all "normal" packages and dev packages
• For boost-system and boost-iostreams there is only one dev package called boost-devel

Here is the list:

• freetype-devel
• glibmm2.4-devel
• glib2-devel
• libsigc++20-devel
• fftw-devel
• libsndfile-devel
• lilv-devel
• liblrdf-devel
• boost-devel
• libstdc++-devel
• glibc-devel
• libgcc
• gcc
• alsa-lib-devel
• webkit2gtk4.0-devel
• gtk3-devel
• avahi-gobject-devel
• avahi-glib-devel
• avahi-devel
• eigen3-devel

Hope this helps!

Do y'all plan on adding any nam type modelling to the guitarix stack ..it would be really cool to have physical and neural modeling in one vst. Y'all's physical modelling is great

I have found another effect not functional while trying the Musiclab presets: the Fuzz Master. It immediately dies in static (only tested it at 96khz). This is very low priority as I don't particularly need it, just letting you know.

Testing with Bitwig Studio via Flatpak on Fedora 39, commit 33e5986 of guitarix.vst and commit 80e951fb3212c058c507c421cecfacca1f6d2932 of guitarix.

Selecting menu items using the mouse is very difficult as the menu sometimes flickers in and out of existence after just one mouse click.

Here's a 30 second video showing the issue. It gets more obvious towards the end. I'm not doing anything weird with the mouse clicks, just clicking once each time to open the menu, which sometimes works and sometimes doesn't. When you see the menu flicker on and off quickly, that's the bug.

Separate issue I guess, but mousing through small menus is quite annoying - it would make this easier to add keyboard shortcuts and/or a "Next" button to navigate through the menus. Or perhaps I can MIDI map this somehow - need to investigate.

Thank you for your work here, really nice! I'm using Bitwig in Fedora, installed as a Flatpak - and Flatpak installations have no access to most system libraries, and loading the plugin fails with

[2024-01-14 19:06:46.579 indexer info] Could not read metadata for Guitarix.vst3 com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: 
Failed to load VST 3 plug-in /home/anselm/.vst3/Guitarix.vst3: libgiomm-2.4.so.1: cannot open shared object file: No such file or directory

libgiomm is installed, but not available. Something like make static? Pretty please?

Hold your horses! It seems to be working now as intended. I didn't do any changes, so don't know how.

Just compiled latest vst3 (juce) source (today's date) and it worked at first, when scanned from inside Reaper. But when restarting Reaper there was no sound although the meters in the plugin showed incoming signal. But when clicking the stereo button in the plugin- effects returned. Weird. Disappeared again when clicking back to mono. In mono it was just the original guitar signal without effects.

Is there something I can do? Some setting somewhere?

Reaper 6.73.xxx.dev.xxx, Devuan 4. jjcale_guitar on Reaper forums.

By the way, this seems to be the best guitar plugin I've ever seen.

Another issue (also tested in Bitwig):
if you add three instances in three tracks, load some presets (not containing the JCM800) save and reopen, the sound is very faint or fades to silence until another preset is opened.
The behavior is not exactly the same each time but problems seem to happen quite reliably.
I found nothing in the Bitwig logs.

When trying to control the Thick distortion volume knob, it quickly goes to a "nan" number, and then freezes the UI. The effect still works though, but the UI is uncontrollable after that. I'm using Ubuntu 22.04 64-bit, host is Renoise, and the commit is 22dcdcf.

[ERROR]: Could not load VST3 plugin '/home/mb/.vst3/Guitarix.vst3/Contents/x86_64-linux/Guitarix.so': libcurl-gnutls.so.4: cannot open

When loading on Ardour 8.4.0
Using Archlinux

Fixed by installing "libcurl-gnutls" package.

Maybe list it as "required" for a new section "Arch"?

Gday I've got a problem where guitarix will stop sounding it's effects in reaper.

The meters in the plugin gui still move but it is only dry signal coming through.

Off-lining them and re-enable will work but then after a few transport starts and stops there is only dry signal again.

Any idea where I could look for more info? Tried running from terminal, but doesn't appear to be any useful info.

Last test with Reaper 7.15 and Guitarix.vst3 0.3.

Very frustrating bug.

The guitarix.vst plugin makes Ardour crashing. -->Core Dump
Manjaro Linux, Kernel 6.7.5, Ardour 8.3. (downloaded from Ardour.org) Alsa Backend. AMD Ryzen 9, 8 Core APU.
If I insert the plugin than it is working. But if I save/close the project and reopen than Ardour 8.3 crashes.
Manjaro Distro Package - Ardour 8.2-3 working.

A change of cabinet doesn't take effect immediately: the cabinet module needs to be deactivated/reactivated for the change to be applied. This looks like a defect compared to the behavior of Guitarix standalone.

Would it be possible to add a projucer or cmakelists.txt file to the project in order to make it easier to build this in a format other than vst3?

On my current system (debian sid, gnome, Wayland) vst3 plugins built with JUCE have flickering menus that behave very similar to the closed issue #15. VST2 and LV2 plugins built at the same time don't exhibit this. So I've been preferring LV2 where possible. This issue doesn't just affect guitarix.vst, it happens to any JUCE plugin I build as vst3. It doesn't happen under x11.

With most projects I find on github it's easy to configure this via the options mentioned above but here there is only a makefile provided.

Title says it all, really. I switch to stereo mode, save the project, and when I load it again, it has reverted back to mono. It makes no difference whether I change it in the host or the GUI prior to saving. I'm using Ubuntu 22.04 64-bit, the host is Renoise, and I'm using commit 22dcdcf.

Otherwise really great work on this plugin! It is a huge improvement to have access to all the Guitarix modules!

If you have one unit above the amp stack and one below, and you close the GUI and reopen it, the upper one gets moved to below the amp stack. The sound doesn't change until you touch one of the controls in the misplaced unit though. If you close the project completely and reopen, then the order is correct upon the first open, but again wrong on the second open.

Tested on Linux in both Renoise and Carla.

Hi! I would love to try your Guitarix VST3, but when I scan the plugin with Ardour that error message comes up.

"/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found"

I tried googling all over, but couldn't find a solution to this, even though this particular error occurs with multiple different packages, at least there are dozens of results.
I don't know what to do about my libstdc++6 version, it's the most current one according to synaptic, 10.5.0-1ubuntu1-20.04. It only provides up to GLIBCXX_3.4.28

I'm running Ubuntu Studio 20.04.

Any pointers? I have all the other dependencies. Could I build from source without that requirement?

Hey again!

So, Ardour imports the vst correctly, but then I see two instances (see screenshot below).

If I select the first instance, it works fine. If I select the second instance, it makes Ardour crash.

Hello!
During playing the Guitarix plugin inside Ardour DAW I've noticed that the Guitarix changes it's scale dependently on the Ardour's UI scaling. If it is possible to make GX UI independent scale from Ardour - that could be more comfortable (IMHO). For example if I increase Ardour GUI more than 150% - the GX UI can't match the monitor (for notebook 150% Ardour's scale not enough sometimes):

Thank you for GX! ⚡

As the title says:
The kxstudio lv2-dev (1.18.10-kxstudio) changes the folder structure in /usr/include/lv2 and there is an error message about presets.h missing.

Solution:
Downgrade lv2-dev to the one included in the distro. (1.16)

source for solution here, also guitarix related:
https://linuxmusicians.com/viewtopic.php?t=26365

Solution for dummies like me:
Force version in Synaptic to 1.16, Apply. Then build.

This fail to build on aarch64

egrep: warning: egrep is obsolescent; using grep -E
INFO: Submodule up to date
INFO: Using included Juce modules [../../JuceModules]
INFO: optimised for x86_64
[2%] Compiling include_juce_audio_devices.cpp
Assembler messages:
Error: unknown architecture `x86-64'

Error: unrecognized option -march=x86-64
Assembler messages:
Error: unknown architecture `x86-64'

Error: unrecognized option -march=x86-64
Assembler messages:
Error: unknown architecture `x86-64'

Error: unrecognized option -march=x86-64
Assembler messages:
Error: unknown architecture `x86-64'

Error: unrecognized option -march=x86-64
cc1plus: error: unknown value ‘x86-64’ for ‘-march’
cc1plus: error: unknown value ‘x86-64’ for ‘-march’
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a armv8.7-a armv8.8-a armv8-r armv9-a armv9.1-a armv9.2-a armv9.3-a native
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a armv8.7-a armv8.8-a armv8-r armv9-a armv9.1-a armv9.2-a armv9.3-a native
cc1plus: error: unknown value ‘x86-64’ for ‘-march’
cc1plus: error: unknown value ‘x86-64’ for ‘-march’
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a armv8.7-a armv8.8-a armv8-r armv9-a armv9.1-a armv9.2-a armv9.3-a native
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a armv8.7-a armv8.8-a armv8-r armv9-a armv9.1-a armv9.2-a armv9.3-a native
make[1]: *** [Makefile:834: build/intermediate/Release/include_juce_audio_devices_63111d02.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:829: build/intermediate/Release/include_juce_audio_basics_8a4e984a.o] Error 1
make[1]: *** [Makefile:388: build/intermediate/Release/include_juce_audio_plugin_client_VST3_dd633589.o] Error 1
make[1]: *** [Makefile:839: build/intermediate/Release/include_juce_audio_formats_15f82001.o] Error 1
make: *** [makefile:39: Builds/LinuxMakefile] Error 2

Build system seems to assume x86_64.

It's build with make.

I got two occurrences of the JCM800 stopping to produce any sound in Bitwig.
The vst plugin itself didn't crash (I could open other presets), but I had to close the document an reopen for the JCM to get back to work. Unfortunately I couldn't gather any meaningful information. The git revision: r0.g9dc30ea
I tried to let it run for ~8 hours non stop without the problem occurring, so this is really random.
This is if I remember correctly an old Guitarix issue that could never be completely fixed.
I couldn't find any existing report on github, so opening a new one...

Error:

2024-04-30T11:44:11 [ERROR]: Could not load VST3 plugin '/usr/lib/vst3/Guitarix.vst3/Contents/x86_64-linux/Guitarix.so': /usr/lib/libavahi-gobject.so.0: undefined symbol: g_once_init_enter_pointer

Two parameters in the Amp Stack are not restored correctly when loading a preset, but rather seem to be restored to their default value:

• Pre gain
• Drive

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:

Ardour:

But the alternative UI works:

Thanks for the awesome work tho :)