• LarsXI

    I use that method. I've had to add an extra delay in ms to avoid clicks when the dsp switches off in a voice. I adjust while playing until problems stop.

    You can do this and still use vline~ in your patch because the output always starts exactly one block after receiving input.

    posted in technical issues read more
  • LarsXI

    i have to update!

    long live bob~

    posted in patch~ read more
  • LarsXI

    shoot! i'm still using vanilla 0.47.1 out of laziness. i haven't installed any externals, but i think bob~ was a packaged external like sigmund~

    possibly it can be found via Deken?

    posted in patch~ read more
  • LarsXI

    yes, you can definitely patch this up.

    will you want to queue note offs so that all notes release eventually, or should notes hang after at least two are pressed and then released?

    a 128 position array can keep track of which notes are held. you can use a note counter and once it reaches 0, send note offs for each note the array recorded.

    you may also want to look at the help file for [bag ]. you can flush it when the note counter reaches 0. i am nervous about using [bag ] for reasons i don't remember.

    posted in patch~ read more
  • LarsXI

    Hi. I made this patch for you. It plays a sound into a buffer at a pitch you specify, then midi input transposes the buffer down. There are some funny consequences of this setup.

    buffersynth.pd

    posted in patch~ read more
  • LarsXI

    it's messy, but possible, to use a single sample delay with clipped feedback to generate a typical compressor envelope. i don't have this patched up in an intelligible way but i could clean it up if anyone is interested.

    posted in technical issues read more
  • LarsXI

    I've been doing it like this lately, but i'm curious if there's a better way

    image.png

    posted in technical issues read more
  • LarsXI

    using [rzero~ 1] with [samphold~ ] might be interesting.
    or rather, not samphold~ but i'm not sure what...

    i think a lot of discussions about this either here or on the list end up concluding that it is preferable to just rebuild the LFO using vline~, so you know ahead of time when it will change direction. Are you using an LFO that has too complex a pitch modulation to build it with vline~?

    posted in technical issues read more
  • LarsXI

    yep, there's several ways to do it, but you can start by putting a message box in front of both you line~ objects with the message $1 5

    [tabread mutes]
    |
    [$1 5 (
    |
    [line~ ]

    this should make the volume ramp up or down over five milliseconds when it changes. the line~ object will change to the new value over the time specified by the second number in the list at the left inlet.

    the clicks you're getting now happen when the osc~ output is far from 0 at the block boundaries. the line~ objects change their output abruptly at the block boundaries and the sound of the sine wave going from some value to 0 immediately sounds like a click transient. with a 5ms time value, the line~ will instead wait for a block boundary, and then begin changing to the new value over 5ms.

    posted in technical issues read more
  • LarsXI

    on second thought, i'm pretty sure i'm wrong about this one, because of the fixed ratio operators in the tx81z/dx11

    txdxdetune.pd

    this patch is still kind of interesting and you would save a good bit of processing. on a 4 op 8 voice synth, you would save 23 phase accumulators total, but have reduced control over individual operator pitch.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!