Digital Larry
Active member
The T/X block was supposedly based on this Spin Knowledge Base article which shows how to get a smooth overdrive.
I've never really used it myself as I never thought distortion was the FV-1's strong suit. The other day I decided I'd try to see how it worked on the built-in scope and was really surprised by what I found. With the low-pass filter as high as it will go (about 5 kHz) and taking a full -1 to + 1 sine wave in at 105 Hz, there's very little visible distortion at all. Top trace is input to ToverX, bottom trace is output.
Now with the input level reduced to about 18%, all of a sudden there is some really nasty crossover distortion going on.
Much below this (about 10%) it seems to go away almost completely, at least on this scope (which is linear and doesn't have great resolution). Listening to the simulator with my standard clean guitar loop (which I think is normalized at - 12 dB), hardly anything happens. With 6 dB of gain it starts sound gated and spitty. With 12 dB of gain, it sounds like clean overlaid with a raspy fuzz.
I looked into the generated code and am pretty sure I located a coding error. This is totally not what the intention of the original algorithm was but I'm trying to figure out whether to just try fixing this, or to keep it as something separate, in which case what to call it? Anybody ever used this one intentionally?
- DL
Spin Semiconductor - Programming the FV-1
Spin Semiconductor designs and markets specialized mixed signal integrated circuits for the consumer music and audio industries
spinsemi.com
I've never really used it myself as I never thought distortion was the FV-1's strong suit. The other day I decided I'd try to see how it worked on the built-in scope and was really surprised by what I found. With the low-pass filter as high as it will go (about 5 kHz) and taking a full -1 to + 1 sine wave in at 105 Hz, there's very little visible distortion at all. Top trace is input to ToverX, bottom trace is output.
Now with the input level reduced to about 18%, all of a sudden there is some really nasty crossover distortion going on.
Much below this (about 10%) it seems to go away almost completely, at least on this scope (which is linear and doesn't have great resolution). Listening to the simulator with my standard clean guitar loop (which I think is normalized at - 12 dB), hardly anything happens. With 6 dB of gain it starts sound gated and spitty. With 12 dB of gain, it sounds like clean overlaid with a raspy fuzz.
I looked into the generated code and am pretty sure I located a coding error. This is totally not what the intention of the original algorithm was but I'm trying to figure out whether to just try fixing this, or to keep it as something separate, in which case what to call it? Anybody ever used this one intentionally?
- DL
Last edited: