Better sounding guitar distortion ... beyond \[clip~\] and \[tanh~\]
Yop,
Thanks Maelstorm and acreil !
My concern was about cpu efficiency, and this slow random offset is clearly (dunno how to say it in english) the cherry on top of my pie !
Anyway for cpu I will use table lookup. The article talks about 'nonuniform logarithmic sampling with a floor of about zero', but I'll start with a 'normal' tablelookup.
Thanks,
Nau
I know bt said going pass the regular distortion do you know what he is talking about ?
@ShawnPD said:
I know bt said going pass the regular distortion do you know what he is talking about ?
Sorry, I don't understand you. Who is this 'he' ?
Nau
Yop,
here is a folder containing the 'DistOdrive' project 
, both effects are modelized, modifications were made (a forgotten lop~ somewhere, a switchable upsampling (16x) section (sucks less cpu when in 'bypass' mode) and of course the second pedal, etc).
I'll be glad to read any comment, the last time I asked for it it has been efficient !
Thank you again.
The files : two guitar samples (44.1khz and 48khz) are included for comparison sake. Open 'DistOdrive.pd' or read the 'Readme' file to learn more.
--> http://www.sendspace.com/file/woa1yp
Nau
Yop,
now I'm going to replace some static coefficients calculation with numerical values, to make the patches smaller. But my attempts of retrieving values to put it into a simple message failed, as the coefficients values obtained by [print] , [number] or [tabwrite] and save to file are truncated (max 6 digits after dot), so when I copy them back into a message and send it to a [filterplot.mmb] I get a slight but significant change in shape.
I could I save float data into files with higher accuracy ? This could also be useful in table-lookup schemes.
Thank you,
Nau
Hay the artist bt said some thing about new distortion what is it and how do you go past the clipping don't he said
its not wave shaping ? I would like know what is he talking about
You're going to need to provide a link to him saying that or something. Without any context, we can't know what he's talking about.
bt is a good artist but I don't follow him he is the one who made the shutter edit vst(load of crap) and always dose alot of exponential thing with metter and fx with c sound ok so he already come out with its called trash. http://www.izotope.com/products/audio/trash/
I edited your post because I don't think this is the appropriate place to be bashing people's religious views. Please try to be more considerate. -Maelstorm
Trash has been around for several years. I doubt BT had much to do with it. Anyway, the only part of that link that says anything about "non-standard" distortion is the multi-band distortion part. That could be done with just band-pass filtering different frequencies into different types of distortion.
may be its some thing else that he was saying I know he did some thing micro with every sample point thinking its may know of like the gormeter vst where you cam delete wave points and picks to give you some thing new
Gosh ! Very rude.
I edited the sendspace link since I realized my lastly posted archive was not actually a folder but a bunch of files (sorry for the mess). fixed.
Is there anyone here that owns or knows well the TubeScreamer pedal to give me some comments about the quality of the model ?
I noticed the tone parameter is rather subtle, certainly not as the one implemented in the DS-1 model.
Thanx,
Nau
@Maelstorm said:
I would recommend using [lp10_cheb~] for this as it has a very steep roll-off. You could probably set it to about 18kHz without aliasing.
Ok. And as I'd like to take account for other sampling rates than 44.1kHz, is it "correct" to calculate the cutoff freq. of this cheby with a simple "fc=(SR/2)-4kHz" ?
This would give approx. 20kHz for a 48kHz SR example.
Thanx,
Nau
Hi,
as I was 'porting' my disto patch to Max/msp, I had to figure out what permutation and sign rules could change Puredata biquad filter coefficients into Max/msp [biquad~] coefficients. I found these rules comparing coeffcients given by the excellent [filtercoeff.mmb] made by Maelstorm to those calculated by a 'classic' [filtergraph~] in Max/Msp.
Here are two patches allowing to make this conversion in one direction or the other.
Nau
Hi,
as I was 'porting' my disto patch to Max/msp, I had to figure out what permutation and sign rules could change Puredata biquad filter coefficients into Max/msp [biquad~] coefficients. I found these rules comparing coeffcients given by the excellent [filtercoeff.mmb] made by Maelstorm to those calculated by a 'classic' [filtergraph~] in Max/Msp.
Here are two patches allowing to make this conversion in one direction or the other.
Nau
@nau said:
Ok. And as I'd like to take account for other sampling rates than 44.1kHz, is it "correct" to calculate the cutoff freq. of this cheby with a simple "fc=(SR/2)-4kHz" ?
It's better to use (SR/2)*0.8, or something like that. They roll off at dB per octave, not per kHz.
I realised (looking at videos on the net - I don't actually owe the pedal) that when bit depth/samplerate are set to maximum (best sound 'quality') and a 'unitary' wavetable is used (doesn't modify anything in the sound), the actual pedal still provides a broad "distortion/fuzz" sound. (of course the video provides clean and effected sound, ensuring comprehension)
@acreil said:
@nau said:
Ok. And as I'd like to take account for other sampling rates than 44.1kHz, is it "correct" to calculate the cutoff freq. of this cheby with a simple "fc=(SR/2)-4kHz" ?
It's better to use (SR/2)*0.8, or something like that. They roll off at dB per octave, not per kHz.
Logical, indeed. Thanks
Just re-uploading the project, DistOdrive.pd is the main patch.
Hi there Nau! I know this is an old thread, last post was 2 years ago! But do you still by any chance have your patch?
Hi SockPuppet,
here is the archive I think is "the one". I won't have much time to check it before next week, but if you encounter problems I'll do it.
https://www.sendspace.com/file/1tn9zk
Nau
Oops! Looks like something went wrong!
