Activity for guitarix
-
brummer posted a comment on merge request #29
Hi I'm sorry, guitarix here on sourceforge is badly outdated, so I can't accept any merge request here. I've marked it now as moved to github. You would find the latest revision here: https://github.com/brummer10/guitarix
-
Illia Ostapyshyn created merge request #29 on Git
Do not check errno on pthread_create failure
-
David Runge posted a comment on ticket #133
Sorry for the long delay: This worked for me as well!
-
aieaks525 posted a comment on discussion General Discussion
Hi all, I installed Guitarix on Raspberry Pi4, I also installed Jack Audio Connection Kit, the guitar is connected to a sound card, I selected the sound card in Alsamixer, but there are other settings to set so that the guitar signal reaches Guitarix, can you help me?
-
Hi Yes, the old forum is gone. New one is hosted on reddit: https://www.reddit.com/r/Guitarix/ It's already fixed in the top line but forgotten to fix in the text. regards hermann Am 14.01.23 um 00:46 schrieb John Chaney: Hey, at the bottom of the main page (https://guitarix.org/) under Contribute, it has a link to the forums, which link to a now-dead sourceforge forum. I was actually trying to get the metal tone preset used in the video on the main page (https://www.youtube.com/watch?v=hlGKDQj2Wmk),...
-
John Chaney posted a comment on discussion General Discussion
Hey, at the bottom of the main page (https://guitarix.org/) under Contribute, it has a link to the forums, which link to a now-dead sourceforge forum. I was actually trying to get the metal tone preset used in the video on the main page (https://www.youtube.com/watch?v=hlGKDQj2Wmk), and in the description of the video he links to the preset which was also on the old sourceforge forum I guess, but now that it's dead I can't find the preset either. Just wondering if this "discussion" page serves as...
-
Jason D. Stone posted a comment on discussion General Discussion
Got the issue fixed. You need to create a group with realtime priorities, then add your username to that group. The tuner works great now, the solution is on the Github site
-
Fix issue #110 GxTuner Issues
-
Fix issue #110, adjust scale for TET settings
-
Fix issue #110 GxTuner Issues
-
guitarix released /guitarix/guitarix2-0.44.1.tar.xz
-
Update Version
-
Fix race condition when build with Faust
-
-
Update Version
-
Update faust version to 2.40.0
-
Hi I've had a similar report for the git package of guitarix here: https://github.com/brummer10/guitarix/issues/104 does that solution may work for you when I push out a new release?
-
Builds using LTO fail
-
Implement glib version check for g_atomic_int_compare_and_exchange to adjust volatile keyword
-
Aaron Walker posted a comment on discussion General Discussion
I'm looking at the code, and some of the differences may be either the difference between multiplying by 0.25 vs dividing by 4 (would that create a minutely different result? I don't know), and in SimpleResampler, one seems to use int sometimes while the other uses int32_t. I'll be toying with this stuff on my copy. We'll see what comes out. If it sounds like I don't know what I'm doing, well, you're probably right :)
-
Fix issue #107 simplify logic
-
Build Errors: Linux Mint Guitarix0.43.1
-
Anonymous posted a comment on ticket #132
Hi. Resolved. Reloaded Linux in a bigger partition and installed Guitarix from the Software Manager.
-
Fix issue #107 guitarix crashes on NSM Save when never visible before
-
Anonymous created ticket #132
Build Errors: Linux Mint Guitarix0.43.1
-
You can't load the LV2 version into guitarix, as it requires a feature (work:schedule) which guitarix didn't support. Other than that, the difference in code is only related to create the LV2 interface.
-
Wow, almost a year old! I still want to figure out how this works. So, in Ardour, I created a track and added the gxdetune plugin to it, and didn't notice any deterioration over time. That's good. I didn't realize that the LV2 version and the "internal plugin" were different code. So, I was wondering if there was a way to load the LV2 version into guitarix (as an external plugin)? I tried, and couldn't get it to show up in the plugin manager (among other things, I have the default copy of guitarix...
-
Anonymous posted a comment on ticket #131
Both suggestions worked. Thank-you.
-
Maybe you could try building in your home directory. For example, I created the "mylocal" directory in my home directory, and installed there, then I could run guitarix from the binary in /home/fred/mylocal/bin/ (for example). First, create "mylocal" directory in your home dir, and also create the following directories under "mylocal": bin etc include lib man sbin share src Then: ./waf configure --prefix /home/fred/mylocal ./waf build ./waf install Good luck!
-
Hi I've no idea what goes wrong here. It looks like your system fail to create symlinks for the library. Which configure flags do you use? Maybe you could try to use the --static-lib configure flag, then symlinks wasn't needed.
-
Anonymous created ticket #131
V 0.43.1 Compilation fail on Fedora 35
-
k_amlie committed [2443f3]
Fix wrong max value for Tube Model in gx_amp LV2 plugins.
-
GitHub committed [17a96d]
Merge pull request #106 from kramlie/master
-
Hubert Figuière committed [6a0141]
LV2: remove dependency on glibmm when building lv2 only
-
GitHub committed [70d54d]
Merge pull request #105 from hfiguiere/gtkmm-deps
-
Fix issue #104 Build failure on Arch Linux
-
Fix issue #104 Build failure on Arch Linux
-
Fix issue #103 Noise Gate doing nothing
-
Fix issue #103 Noise Gate doing nothing
-
Re-enable Gainline edit in the Convolver
-
GxTuner does not take into account other frequencies than 440hz
-
Hi Still I don't understand why this workaround is needed here, The tuner widget is a special case, which have multiple adjustments for one widget, so it may be that I've made a mistake in the implementation (which I never noticed). But I'm glad that we could solve it.
-
Anonymous posted a comment on ticket #130
Hi @brummer10 thank you so much, that actually fixed my issue! I wonder if this would have any broader consequences for future plugin developement, but anyways thank you so much! :)
-
As I said, I can't reproduce the issue, but I've implemented a function to ensure that the used reference pitch is in sync with the reference pitch shown in the UI. Please checkout from git and let me know if that solved the issue for you.
-
Anonymous posted a comment on ticket #130
Yes ArchLinux here. Well that would be awesome, if you find the time. It would be awesome if this bug could be worked worked out. Trying the best I can to help figuring it out.
-
Fix Bug #130 GxTuner does not take into account other frequencies than 440hz
-
So you are using Arch Linux? Maybe I need to make a test install with Arch.
-
Anonymous posted a comment on ticket #130
I just reproduced it with the Guitarix git version (from AUR). Still happening. Bummer... I guess we need to find somebody else to try and reproduce then :/
-
Pipewire shouldn't make a difference. However, I really can't reproduce that issue.
-
Anonymous posted a comment on ticket #130
Oh and I don't know if it makes a difference, but I am using PipeWire! (Please don't ask me to set up jack l tried and failed, but PipeWire just worked for me using the PipeWire-Jack backend)
-
Anonymous posted a comment on ticket #130
Well, I have tried it on Ardour now and I am getting the same behaviour. Are you sure that you are not hitting the bug? The GxTuner GUI still shows 432hz, but when you hit the string it shows being out of tune (even though the gutiar is tuned to 432hz). So what is displayed can be deceiving. Then when just touching the frequency slider suddenly it shows the string is in tune. So it needs to be tested with an actual instrument Im afraid. At least in this scenario.
-
Well, I tried it with reaper v6.21+dev0130 and can't reproduce the issue therewith. You may try Ardour or Carla which is my most used test host for LV2 plugins.
-
Anonymous posted a comment on ticket #130
So just be be complete, here is how to reproduce it a 100% of times: Start Reaper and Monitor guitar input Go to FX and add GxMetallAmp and GxTuner, uncheck GxMetallAmp for now In GxTuner set the frequency to e.g. 432hz. It should work correctly. Now activate GxMetallAmp, you will see GxTuner now suddenly tunes to 440hz In GxTuner, change the frequency slider in any direction. Now the bug is fixed. @brummer10 So you say this might be a reaper issue? Btw Reaper is free so you could test it out if...
-
Well, I can't say much about how reaper implement the LV2 standard, it may be that reaper reset the values to default when activate the plug, without inform the UI about it. So the UI and dsp don't be in sync. Moving a control will sync them then. But I can't believe that a other plug (GxMetalHead) could have any influence on that.
-
Anonymous posted a comment on ticket #130
Ok and the way to "break out" of this bug is to change the frequency slider in any direction. This will fix the bug immediately. As I say it happens in Reaper while activating and deactivating the mentioned plugins in the FX panel.
-
Anonymous posted a comment on ticket #130
Ok I think I know how to reproduce the issue. The issue is that I had the GxMetalAmp running, which (I guess??) is set to 440hz. So when I set GxTuner to 432hz with the GxMetallAmp running it shows me to tune up my guitar! However, and this is the crucial part, after I disable the GxMetalAmp, GxTuner is still behaving the same! So basically if I tune my guitar with GxTuner now it will be 440hz even though I set 432hz.
-
Anonymous posted a comment on ticket #130
I am on Guitarix v0.43.1. Yes it it weird, currently it works correctly, too. However I am absolutely certain that it was misbehaving. Becasue I had my guitar tuned to 432hz with a hardware tuner yesterday. Today I activated GxTuner VST inside Reaper, and immediatly set the frequency from 440hz to 432hz. Then I wondered why apparently my guitar was tuned to low on every string... so I tuned it according to GxTuner. Then I took out my hardware tuner again, checked it, and my guitar was tuned to 440hz!...
-
What? So you mean you've this issue with the tuner coming within guitarix? If so, which version do you use?
-
Anonymous posted a comment on ticket #130
Thank you. I am actually using the tuner inside Guitarix, where it is called GxTuner :)
-
Anonymous posted a comment on ticket #130
Ok after fidding around, going up and down, suddenly GxTuner "accepted" the new frequency and tunes correctly. So it seems GxTuner intermittently has issues applying it's settings. I cannot give exact steps to reproduce unfortunately since it behaves in a random fashion. But I do not see myself using GxTuner if its results are apparently random...
-
GxTuner is very old now, and not any more maintained. You could try Xtuner https://github.com/brummer10/XTuner or using the tuner in guitarix.
-
Anonymous created ticket #130
GxTuner does not take into account other frequencies than 440hz
-
Fix: don't save on exit when under NSM control
-
-
update changelog to 0.43.1
-
update version to 0.43.1
-
Fix issue #100 GxAmplifierX (LV2) produces weird noise after buffer size changes
-
Issue #98 - Install metainfo in prefix (and validate)
-
GitHub committed [5b7491]
Merge pull request #99 from hfiguiere/metainfo
-
Hi Nice to hear that it works now for you, and yes please, when you fetch a issue, report it here, so I could squash it. regards hermann
-
Simo Erkinheimo posted a comment on ticket #128
Hi, Sorry it took a long time to respond. I kind of migrated my projects already to GxPlugins and then I had some major issues with my python which prevented me from building Guitarix. Anyway, just to let you know that I now managed to get it up&running and I'm doing some side-by-side comparions every now and then when searching for a tone. At least initially I didn't notice any of those issues I reported, but I'll post here if I encounter any of that again in the future. Once again, thank you for...
-
-
Removenot needed extern C definition from before LV2_SYMBOL_EXTERN in all LV2 plugs, remove no longer needed lv2:requiredFeature guiext:makeResident from all *.ttl files
-
Fix warning in dsp2cc for coverd_ui.glade
-
Switch to faust version 2.37.3
-
That means you use a unsupported faust version. Try to build with the --no-faust flag. Anyhow, you better check out from git repository, a new release will coming soon.
-
Anonymous created ticket #129
Compilation error on Ubuntu Linux 20.04 and Guitarix 0.42.1
-
Hermann Meyer committed [af954e]
Fix issue #96 add X-NSM-Capable=true to the .desktop file, add metadata.xml file for AppStream
-
Hermann Meyer committed [a1f8ba]
Fix issue #56 Guitarix at ultra low latency
-
Hermann Meyer committed [b31c5e]
Fix issue #86 GXAmplifier-X & GXAmplifier-Stereo-X are also affected by issue #82
-
Hermann Meyer committed [b3ebbb]
Fix issue #77 Gx-plugins
-
Hermann Meyer committed [9bed17]
switch faust version to 2.33.1, remove glibmm dependency from several LV2 plugins
-
Hermann Meyer committed [3d6953]
Removing glibmm dependency from GxAmplifier (mono stereo) and GxCabinet
-
Hi I've found some time and going to fix the issues you reported, please checkout from git repository and let me know if the latest git version solved your issues. regards hermann
-
Tristan Tarrant committed [dc7049]
Issue #18
-
GitHub committed [4f595a]
Merge pull request #93 from tristantarrant/41tet
-
Hermann Meyer committed [289452]
Merge https://github.com/brummer10/guitarix
-
Hermann Meyer committed [2e91fa]
Fix issue #94 cycling through cabinets/pre-amps/tubes is skipping items, fix bug #128 GxAmplifier-X seems to have major issues in Ardour
-
This sounds to me as it is worth to report to ardour devs. Leaking over multiple cores is clearly a job of the host.
-
Hey @brummer10, I believe this could be a race condition -issue. I tested various GxPlugins (very nice!) and at some point noticed "leaking" of an effect (GxSD2Lead) from muted channel to another having the same effect (but different instance). In Ardour there is an option to use multiple cores for signal processing. I set that to single core and didn't experience the leaking anymore (after Ardour restart). Then I set it back, restarted Ardour and tested again and the leaking is back.
-
Thanks for the reply. I checked the output and you are right: There seems to be buffersize changes, and both cabinet and presence convolvers report update buffersize fail. There's also "no configure" message every now and then. It's this "case 1" that is the biggest issue here. UI glitches and (especially predictable) crashes are just secondary. I'd go as far as say that there's no point looking at any other Ardour related issues unless that buffer handling issue can be fixed in near future version...
-
You may try one of the Amplifiers from the GxPlugin suite, which all don't have such issues with ardour. https://github.com/brummer10/GxPlugins.lv2#amplifiers
-
Hi Thanks for reporting the issues. 1.) Most likely it's a issue with the presence engine in GxAmplifier, as it is convolution based. Ardour doing a lot of buffersize changes this day's, and GxAmplifier couldn't handle that so good. When you start ardour from terminal you'll likely see some messages like: presence convolver update buffersize fail buffersize changed to 16 buffersize changed to 16 convolver didn't run buffersize changed to 256 convolver didn't run buffersize changed to 256 buffersize...
-
GxAmplifier-X seems to have major issues in Ardour
-
Hermann Meyer committed [84641a]
Finaly fix issue #50
-
Hermann Meyer committed [ad14a6]
Next attempt to fix issue #50 Fuzz Face Mayer broken in git
-
Hermann Meyer committed [e86680]
New attempt to fix issue #50 Fuzz Face Mayer broken in git
-
Hermann Meyer committed [a102f3]
Revert wrongly commited change for issue #85
1 >
