• katz

    @weightless

    Ok here is a final one that simulates the cz waveforms in series by writing half of the array in the first chosen waveform and the other half by the second. If both waveforms are the same, the second phase slider won't do anything.
    txcz-wavs3.pd

    As far as the array size I am not sure, but I believe at the really low resolutions the actual shape of the waveform is simply altered.

    posted in technical issues read more
  • katz

    @weightless

    I tried your idea with the alternating tables only, but even the "set" messages will cause some clicks, so here is one with tabread4~ & volume alternating that works. The extra cost is one tabread4~ & two sets of line~s and [*~]s but with effective [switch~]ing you could take away the extra tabread4~.

    I also experimented with different array sizes (see the switcher at the top-right), and certain waveforms are affected quite a bit while others remain the same, so if someone wants to go this route, the whole setup could be fine-tuned per waveform. In this patch the [*~] before the tabread4~s is changed by a 20ms line~, but if you wanted to change the waveform per voice in a polyphonic setup, before the volume envelope kicked in, and each waveform had a specific table size, this would have to be done immediately with a way to avoid the click.
    txcz-wavs2.pd

    posted in technical issues read more
  • katz

    @weightless

    I thought it might be nice to group all the waveforms to be read from a single tabread4~ for each operator, and here is the result. The trade-off is that the casio waveforms cannot be modulated at the 2nd input since they are now calculated statically (you can change them live but since the tables are being redrawn, its unusable that way). The feedback is in here too and a comparison w/ the original cos~ style.
    txcz-wavs.pd

    posted in technical issues read more
  • katz

    @weightless

    I cheated to get some pre-made waveforms with this one (waveforms 2,4,6,8 may not be accurate), and I am wondering if there is an advantage to using the audio math instead, because this one is certaintly lighter. I added a tri-wave at 9 too.

    tx-wavs.pd

    posted in technical issues read more
  • katz

    @weightless

    Ah that was right there in your first example. Nevertheless, amazing - thanks.

    posted in technical issues read more
  • katz

    @weightless

    I don't have any answers for you to get those arcsin-looking waveforms... but I have also been curious about how to use tables instead of the phasor-cos~ pairing... since the latter generally has nicer sounding modulation
    cos_vs_sintable.pd

    posted in technical issues read more
  • katz

    Two more versions. The first one only adds the lateral restriction to graph-adsr-v2 while keeping the minimalism. The second is a kind of hybrid between the last two postings.

    adsr-g2.zip

    posted in patch~ read more
  • katz

    @Balwyn

    I separated the background canvas from the nested gop, as you did in your adsr, and made sure the gop was created later in the object order, relative to the canvas. It seems stable now.

    adsr_g.zip

    posted in patch~ read more
  • katz

    I gave the struct challenge a go myself. It seems to have been a success, except for these really annoying graphic drop-outs. I added as many tricks as I could think of to get the structs to reappear in various scenarios.. like edit dragging, menuclose, and first mouse click after opening window. It would be nice to at least have a reliable way to show it as the patch loads.

    adsr-g.zip

    posted in patch~ read more
  • katz

    Another version with creation arguments for width and height :
    adsr-g.zip

    posted in patch~ read more

Internal error.

Oops! Looks like something went wrong!