Activity for Aaron Walker
-
Aaron Walker posted a review on guitarix
-
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 :)
-
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...
-
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!
-
Just noticed something, and perhaps it will help with debugging.... I'm playing on a fretless, and after I was sitting on this preset for a while, I could slowly slide up a string, and it would sound like it's quantizing or forcing it to fit a pseudo-chromatic scale (like an auto-tune). Very interesting.
-
Thank you sir, I'm giving those a try... and not happy :) By the way, yes, running at 48k. Trying out the GxCapo, and its behavior is very erratic, to say the least, and at one point locked up Guitarix. The GxHarmonizer* plugins (nor the GxVoice) don't load in Guitarix, and I don't have the energy to parse through the ttl to figure out what's making guitarix unhappy. Plus another plugin I was trying (Graillon) got wiped out, bewilderingly. I had to remove it, refresh everything, and restart. I find...
-
Here's a sample, where I play an open string. In the first half, you hear how it's muddy. Then I select a preset which does not use detune, then re-select the original preset. You can hear how the tone is much less distorted. Detune is set to: Detune: 0 Dry: 0 Wet: 100 Sub: 2.0 Low: 2.0 Mid: 0 Hi: 0 Octave Up, compensate, and high quality Thanks!
-
Hi, happy user of Guitarix 0.41 on Ubuntu Studio. Detune is my bread and butter. You do it better than others. I have a slight problem, though. After a certain period of time, something gets out of whack, like some frequencies get cached, for lack of a better way to say it. I'll just call it muddiness, just to apply a word. So, I start playing with a preset using Detune, and after a period of time (perhaps... maybe it has to do with the range that I play), the sound will get muddy, and if I select...
-
Awesome! Works great! Thanks for the quick response!
-
Hi. Within Guitarix, I'm trying to demo Auburn Sounds' Graillon pitch changing lv2 plugin (https://www.auburnsounds.com/products/Graillon.html). I put it in my .lv2 directory, and I can't get Guitarix to find it, and I see no errors in the log related to it. Ardour had no trouble accessing and using the plugin. I tried putting it in /usr/lib/lv2/ as well. No luck. One thing interesting about this plugin is that it comes only with the shared lib (so file) and manifest.ttl (while I noticed that most...
-
Ah, figured it out. It was the difference between running the cpus in performance mode vs. powersave. Interesting.
-
Well, I will walk that back a bit, as at this moment, the cpu usage currently seems on par with past expectations. Although I don't know what's changed. Often I'll just look at the "DSP Load" output on the Jack audio connection kit, and with a certain guitarix patch, where normally I would see something around 20%, now I was seeing something in the 40s. When look at top, it seemed that it was Guitarix processes at the top, using the cpu: hence my original assertions. I'm not in a much better place,...
-
Hi all, happy guitarix user. I'm running on Ubuntu Studio 20.04, and upgraded from 0.39 to 0.41 recently (all using the packages provided by Studio), and based just on my eyeball, it seems like some part of guitarix has roughly doubled its CPU usage. I would be happy to try to revert on my machine to document it properly (or walk back my claim), but I'm afraid of losing my setup/config if I revert :P If you want me to do that, would I uninstall 41, and then install 39? Not sure what all gets wiped...
1
