• Booberg

    I haven't seen this method posted anywhere so i thought i'd share it. It doesn't alias audibly, within my hearing range at least, at 96k sr.

    It works by clipping the peaks of the wave and replacing them with a sine function.
    Theres some maths involved in scaling it with frequency, and patching the triangle and the sine parts together, but nothing too heavy. Uses under 1% cpu per instance on my 2010 mackbook, at 96k.

    Note.
    -I scaled the cutoff frequency (Above which it outputs a pure sine wave) for a 96k samplerate, so that might have to be adjusted a bit for lower rates. Just play with the cutoff constant (now 18800).
    -The overall amplitude diminishes as the frequency increases. Because i prefer it this way.

    splicetri~.pd splicetri~-Help.pd

    edit. Apparently abs~ is from zexy. It will work without it, but won't handle negative frequencies correctly..

    posted in abstract~ read more
  • Booberg

    Oh yeah, if i would experiment further i might try having a lowpass filter in a loop set at something like 1/8th or 1/16th of the fundamental frequency, and then use a multiplier to compensate for the volume loss (and some transfer function to save your ears when it inevitably blows up!). As you probably know, a lopass filter is basically just a 1 sample delay loop, so you could probably use that fact in some way.. Please share what you end up with :)

    posted in technical issues read more
  • Booberg

    I was inspired to put something together you might find useful :)
    KStest-Booberg.pd

    The big thing there is the impulse generator, it generates one cycle 'waveforms' with a period according to the frequency. I made one that is continuously variable between saw and triangle :)
    In the example the delay time was controlled at control speed, using smooth signals to control the time removes the ugly glitches when changing pitch.
    Also, if you want to use noise to exite the loops you might try using brown noise instead to get more low en out of it ;)

    posted in technical issues read more
  • Booberg

    Now, i've never messed around with 'KS' and don't really follow what is happening, so i might be completely off topic here. But if low frequencies start making things unstable or crunchy in bad ways you might want to try doing what is often done in analog circuits: Shelf or cut low end at the input and boost it back up at the output. The clip sounded very cool, love a crunchy bass-synth :)

    posted in technical issues read more
  • Booberg

    I was in a rush last night.. I removed some junk, fixed some filter phasing and corrected a mistake i made with the Hysteresis subpatch. Sounds pretty tight now IMHO.
    After a quick rundown i think its just dependant on two externals, Zexy and Else.
    z~ , one sample delay, from Zexy. And lag2~ + glide2~ from Else.

    I hope someone finds this entertaining :) I recommend using a cabinet convolution with this. I've used partconv from AudioLab (loaded with an ownhammer alnico silver IR) on the recording of the attached sound sample.

    ThurboDriveGuitarV2.mp3 ThurboDriveGuitar2.2~.pd

    posted in abstract~ read more
  • Booberg

    Oh now i see "dA" and some "number~"s in there.. that stuff shouldnt be there so i might have beefed it and uploaded the wrong file or something. I'll take a look at it tomorrow.

    posted in abstract~ read more
  • Booberg

    I don't really keep track of that im affraid.. usually keep to else, cyclone and maybe brickwall is from audiolab? If i wasn't lazy i think all those tanh~ objects are in there for writing tables for the transfer functions.. im not so sure how precise or heavy they are to run so i usually stay clear of them.. it's very possible to change those for a mathematical equivalent/approximation. And the brickwall~ is just for anti aliasing when downsampling so you might use other filters for that.

    I actually continued working on this for some time, specifically for guitar. I didn't really reach all the way i was hoping to, i found that it's hard to induce "shimmer" digitally... alas, i might upload the results during the week.
    Ps. A big facepalm moment when i realized that my 'pseudo-integration' method is really just a naive lopass filter with a bunch of gain :,) so that saves a lot of cpu for V2 atleast..

    Cheers

    posted in abstract~ read more
  • Booberg

    This is my best attempt at a "vacuum tube" style overdrive.
    (Edited)
    Look below for the latest version. This relies on Zexy ( for simple single sample delay) and Else. The only thing i could not easily build in vanilla was the Hysteresis emulation, which relies on lag2~ and glide2~.

    This older version is quite different and messy. Mostly experimentation.
    ThurboDrive~.pd ThurboDriveExample.mp3

    posted in abstract~ read more
  • Booberg

    I'm wondering if there is consensus in what effects "turning subpatches on/off with swtich~ objects" has, mostly in terms of cpu-spikes.
    I'm pondering if "turning off" modulation sends/receives, controlled by a modwheel for example, would be computationally beneficial. This would mean that the switch~ could trigger fairly often, and be "on" for short durations.
    So the question is:
    Do switch~'es operations cause spikes in cpu-usage in a way that would make this kind of thing counterproductive?
    A lazy secondary question: Is it reasonable to expect switches to respond smoothly in a real time application? Will there be a delay noticeable delay or are they pretty much instantaneous? (a 64s block or two is to me fully acceptable).

    Cheers!

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!