• solipp

    @tungee worldclass.. :blush: thanks!
    do you share the automatonism patch somewhere?

    posted in news read more
  • solipp

    @happilylazy
    check out william brent's timbreID externals, specifically the drum-kit example in the examples package.

    https://github.com/wbrent/timbreID

    or download via help -> find externals

    posted in patch~ read more
  • solipp

    @Gabriel-Lecup thanks!

    apparently cpole~ and czero~ in pd biquad were in the wrong order. It should work now, you can find the updated objects on github (link above)

    cheers!

    posted in news read more
  • solipp

    have a look at H13.butterworth.pd and the filtergraph1 and filtergraph2 abstractions in the audio examples.
    and you'll need to delay the reference signal (2nd & 3rd outlet of filtergraph1) according to your systems latency. I haven't tried this with analog filters, but i guess it should work..

    posted in technical issues read more
  • solipp

    Pd spectral toolkit has a nice auto tune example.
    search for pd_spectral_toolkit on deken

    posted in technical issues read more
  • solipp

    version 0.2 is now available on deken!

    changelog:

    • added peak method in pp.env~ pp.env-st~
    • added rotate function in pp.fft-timbre~ pp.fft.timbre-st~
    • changed lowpass filtering in pp.doppler~ pp.dopplerxy~
    • pp.rev~ 100% wet by default
    • buffer length calc. in pp.fft-partconv~ pp.fft-partconv-st~
    • new objects: pp.twisted-delays2~ pp.spacer~
    • fixed some bugs

    posted in news read more
  • solipp

    @whale-av said:

    It could be tested to see whether its control rate message inlet will take (in msecs) small enough float values to make that happen.

    here is a test patch vline-test.pd. vline~ accepts messages at any time with sub-sample accuracy. This is also documented in the help-file.

    @lacuna said:

    [metro 1 1 samp]  
    

    How could I have known that? The helpfile doesn't mention this. (Offtopic: actually the whole forum is full of pd-vocabular-questions)

    It is documented in the metro-helpfile since pd-0.48 i guess. But i agree, there is not much redundant information in pd's helpfiles, to put it mildly ;)

    But you can „use“ the metro counts every 64 samples only, don't you?

    yes, except you use it with vline~ (see test-patch)

    When should I use [block~ 1 1 1] and when shouldn't I?

    whenever you need delay~ times smaller than 64 samples.

    posted in technical issues read more
  • solipp

    on second thought, it doesn't make much sense to me.. I think you know, but, to increase the frequency resolution you just set a higher blocksize in the fft-subpatch, time resolution is your samplerate.
    So, zero-padding to reduce latency? for a high-res spectrum display, or.. what do you want to do with your patch? I'm curious!

    posted in technical issues read more
  • solipp

    aha, so its about low latency fft? if you have a working patch, please share it!

    posted in technical issues read more
  • solipp

    there is no need for zero-padding if you want to increase the frequency resolution in a fft-subpatch (block~), or do i get something wrong?

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!