Package Details: guitarix-git 0.44.1.r121.g056c2577-1

Git Clone URL: https://aur.archlinux.org/guitarix-git.git (read-only, click to copy)
Package Base: guitarix-git
Description: virtual guitar amplifier for Jack/Linux
Upstream URL: https://guitarix.org
Keywords: amplifier emulation guitar lv2 pro-audio tube
Licenses: GPL3
Groups: lv2-plugins, ladspa-plugins, pro-audio
Conflicts: guitarix
Provides: libgxw.so, libgxwmm.so, lv2-host
Replaces: guitarix2
Submitter: None
Maintainer: Gimmeapill
Last Packager: Gimmeapill
Votes: 12
Popularity: 0.014790
First Submitted: 2012-04-13 09:51 (UTC)
Last Updated: 2023-09-17 07:19 (UTC)

Required by (52)

Sources (1)

Pinned Comments

Gimmeapill commented on 2017-12-03 20:10 (UTC) (edited on 2017-12-03 20:11 (UTC) by Gimmeapill)

This package will automatically retrieve and build the latest development snapshot of Guitarix from git.

It does not need to be updated on every release, so please do not flag out of date unless the build itself breaks or in case of an actual packaging issue.

If you are looking for the latest official release instead, see https://www.archlinux.org/packages/community/x86_64/guitarix2/

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Gimmeapill commented on 2016-05-13 06:10 (UTC)

Ok guys, I got it (had to clean my own cache ;-)). But still no clue about that gcc error, so I raised a question upstream: http://guitarix.sourceforge.net/forum/viewtopic.php?f=12&t=4718

Ralf_Mardorf commented on 2016-05-13 04:55 (UTC) (edited on 2016-05-13 05:04 (UTC) by Ralf_Mardorf)

Building on x86_64 fails with either yaourt or makepkg. The only thing unusual for my install is $ pacman -Q jack2 jack2 1.9.10.r177.g7bdad49-1 $ jackd --version jackdmp 1.9.11 Official repositories provide $ pacman -Si jack2 | grep Version Version : 1.9.10-4

Joermungand commented on 2016-05-13 01:16 (UTC)

I get the same error as Ralf_Mardorf. System is up to date, using default flags, clean cache.

Gimmeapill commented on 2016-05-12 19:33 (UTC)

@Ralf_Mardorf: cannot reproduce here. Is your system up to date? Did you cleanup the cache & are you using any exotic build flags?

Ralf_Mardorf commented on 2016-05-12 12:45 (UTC)

Building 0.35.0.r6.g3ec2109 fails. [snip] [ 155/1039] cxx: build/default/libgxwmm/gxwmm/radiobutton.cc -> build/default/libgxwmm/gxwmm/radiobutton_86.o In file included from default/libgxwmm/gxwmm/iredit.h:29:0, from default/libgxwmm/gxwmm/iredit.cc:6: ../libgxwmm/gxwmm/gainline.h: In function ‘bool operator==(const gain_points&, const gain_points&)’: ../libgxwmm/gxwmm/gainline.h:25:110: error: call of overloaded ‘abs(double)’ is ambiguous ool operator==(const gain_points& p1, const gain_points& p2) { return p1.i == p2.i && abs(p1.g - p2.g) < 1e-4 * (p1.g + p2.g); } [snip] Build failed: -> task failed (err #1): {task: cxx iredit.cc -> iredit_86.o}

Gimmeapill commented on 2016-05-11 21:10 (UTC)

@Ralf_Mardorf: Dependency on ttf-roboto removed...and replaced by the bundled one as suggested by the build script. It's ugly but at least won't depend on another AUR package. It should still build if you disable it completely though (see line 38 of the pkgbuild).

Gimmeapill commented on 2016-02-06 21:12 (UTC)

@Ralf_Mardorf: please direct your UI design recommendations here: http://guitarix.sourceforge.net/forum/viewforum.php?f=12&sid=61e74b806d8e6494d16aacd50c00203d As for the pkgbuild, feel free to edit it to your needs or use the official one. In it's current shape, including the recommended font does improve user experience, and is therefore more likely to reduce the number of complaints about the UI. I'd be more concerned with the dependency on bluez-libs if I had to go nitpicking...I'll review those and the build flags after the new version is released.

Ralf_Mardorf commented on 2016-02-06 20:11 (UTC)

It's nothing new, already 0.34.0.r76.g8d2a959 recommended to install the font. However, the guitarix UI is per se a PITA, I don't see how a font, that deviates from the chosen WM font, would improve anything, it's the other way around. A user does chose the font that fit to the user's needs, if an app decides to use it's own font, for no good reason, it breaks a sane work-flow. Why not making the font by default an optional dependency? What is the reason to make it a hard dependency?

Gimmeapill commented on 2016-02-06 19:08 (UTC)

@Ralf_Mardorf: to fix a build warning - that was brought in by the new UI. It will still build and run fine for now, but may look ugly. If you want to test and report on the new UI, better have it.