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 a non-detune-using-preset, then re-select the detune preset, it will clean back up. If it is muddy, and I choose another preset which uses detune, it will remain muddy. Does the problem get progressively worse? I don't know. Does it happen all at once (rather than being like a slow leak), I don't know. Maybe I could make a recording to show you the problem.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
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 the Graillon sounds good like your standard Detune, but the Graillon is geared toward the vocal range, so anything below 100Hz is just distorted in a non-acceptable way, so that's unfortunately mostly unusable for me.
I'm going to keep using Detune, and will start funneling you money when I have some myself.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 (0.41) from the Ubuntu Studio repo, and then I built a local copy of 0.43, and tried to import that instance of gxdetune LV2 into my running 0.41 instance). I want to see if the LV2 gxdetune behaves differently than the internal version. Any suggestion on how to do that? Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 a non-detune-using-preset, then re-select the detune preset, it will clean back up. If it is muddy, and I choose another preset which uses detune, it will remain muddy. Does the problem get progressively worse? I don't know. Does it happen all at once (rather than being like a slow leak), I don't know. Maybe I could make a recording to show you the problem.
Thanks!
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
What Sample rate do you use?
If you don't use 48kHz, you may try that.
Other than that, there is https://github.com/ycollet/mod-gxpitchshifter
which is a fork of https://github.com/moddevices/mod-pitchshifter
edited to make it compatible with guitarix.
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 the Graillon sounds good like your standard Detune, but the Graillon is geared toward the vocal range, so anything below 100Hz is just distorted in a non-acceptable way, so that's unfortunately mostly unusable for me.
I'm going to keep using Detune, and will start funneling you money when I have some myself.
Thanks!
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.
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 (0.41) from the Ubuntu Studio repo, and then I built a local copy of 0.43, and tried to import that instance of gxdetune LV2 into my running 0.41 instance). I want to see if the LV2 gxdetune behaves differently than the internal version. Any suggestion on how to do that? Thanks!
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.
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 :)