• katz

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

    W-A, there are two issues with formatting directly to a vline~. The first is that every time the graph is changed, there will be an immediate trigger-on for the adsr, when it would normally be triggered externally from a note-on velocity msg etc. The second is the release, which must be stored until the note-off msg.

    posted in patch~ read more
  • katz

    Hi W-A,

    The 5 values it spits out are ramp1 time (attack), ramp1 level, ramp2 time (decay), ramp2 level (sustain), and ramp3 time (release)... all of which are in 0-1 range, so you'll see an example where they are scaled in "audio-test".

    posted in patch~ read more
  • katz

    Here is an interactive version using dynamic canvas creation instead of a pd-array. Has options for line resolution and color.

    adsr-g.zip

    posted in patch~ read more
  • katz

    Hi,
    This is a very simple adsr-parameter to array conversion patch for monitoring purposes. It can handle two stage decay addsr too. All parameters are within a 0-1 range. It would be amazing to be able to output new lists from array editing, but this would mean some kind of index change detection. However, I like it as is and hope someone finds it useful.

    adsr_g.zip

    posted in patch~ read more
  • katz

    This will work well enough:
    easing-test.zip

    posted in technical issues read more
  • katz

    Hi,
    This is a [line] object with added sine-easing. Messages behave
    identical to original [line].
    line-e.zip
    I think the behavior should change during a new message interruption where the easing at the start is removed but kept at the end. Does anyone know how to generate a table with a linear start and sine at the end? An option for sharper sine curve would be useful too.

    posted in technical issues read more
  • katz

    @whale-av
    Thanks for the info - I'll continue to look into it. The upsample isn't even necessary for lowpass because vcf~ behaves similarly to vcf_lp2~ (some differences with the way the q and amplitude behave) & if you want vcf_lp4~, just stack two vcf~s etc etc. For right now it's useful for the bandpass and highpass and the other "filter~" filters.

    posted in technical issues read more
  • katz

    This patch fixes the issue to an extent. There were two different unwanted sounds that I was hearing: 1) a high frequency tambourine-like sound. This went away if I put the filter in a subwindow and upsampled 2x. 2) a pop sound when a large change in filter frequency was made quickly. I created a dual-filter crossfade for this. Each has a switch~ to cut down on CPU, but the vcf_filter~ type which originally used less CPU than the vcf~ now uses more.

    Sounds like maybe this isn't an issue for some people, but here it is anyway:

    vcf-crossfade.zip

    (mp3 with the high frequency sound is included here so it doesn't have to be played in the browser)

    posted in technical issues read more
  • katz

    W-A,
    No difference. This is what I'm hearing:
    vcf_lp4~.mp3.
    What version are you using? I tried this with 0.42.5 & 0.43.4 (OSX & Windows).

    posted in technical issues read more
  • katz

    There was a thread a while back that addressed this I think, but I cant find it... about the click artifacts when changing the frequency on the filter~ & vcf_filter~ based iemlib objects. It's a shame since these seem to be the most dynamic filters available, but only seem useful when static. Has anyone found a way around this?

    Here is a patch comparing vcf~ to vcf_lp4~:

    vcf-test.pd

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!