• kyro

    The state saving system and dynamic gui modules are worth a look. I haven't delved in the rest yet.

    posted in patch~ read more
  • kyro

    Maybe should you have

    [loadbang}
    |
    [float 6]
    |
    [until]

    instead? Anyway, you can execute pd with the -noloadbang option to edit your patch.

    posted in technical issues read more
  • kyro

    @oid said:

    Non-linear elements in the feedback path can be fun and do some interesting things but far from a general purpose filter, no clue if pd will play well with that sort of abuse.

    In my humble experience: very well. I've been working on an "acoustic feedback" patch for a while now. With allpass/diffusion, peak filter and basic distortion in the loop, it was quite lively and convincing.

    posted in technical issues read more
  • kyro

    Thank you, it did work here too!

    posted in extra~ read more
  • kyro

    Hi,

    Has anybody managed to get pd spectral toolkit working?
    I'm especially interested in the GEM waterfall spectrum but alas, i get

    pd-externals/SpectralToolkit/pd_spectral_toolkit.l_ia64: undefined symbol: _ZGVbN2v_exp
    pd_spectral_toolkit: can't load library
    

    on startup. make linux didn't complain about anything.

    posted in extra~ read more
  • kyro

    I love this feedback oscillator! I don't know how relevant it is, but it reminded me of https://ccrma.stanford.edu/software/snd/snd/fm.html [cascade FM: sin(sin(sin))]:

    As z increases above 1.27, we get a square wave, then period doubling, and finally (ca. 1.97) chaos.

    posted in patch~ read more
  • kyro

    @chaosprint said:

    For example, I would like to trigger a sound playback multiple times
    it layers the playback at that particular rate

    You mean, like a polyphonic sampler? If so I'd load the sample in a table and have an instance of tabread~/tabread4~ for each "layer".

    posted in technical issues read more
  • kyro

    @jameslo said:

    If you follow the algorithm in http://cgm.cs.mcgill.ca/~godfried/publications/banff.pdf, E(5,13) = 1001010010100, But if you use the much simpler one from @Stutter you get 1001001010010.

    If you flip stutter's result three digits to the left you get banff's. It's a matter of a [- 3] somewhere.

    posted in patch~ read more
  • kyro

    If I had to buy something today I'd go for Intech EN16. Fighting my impulse buy a while back, I dug out my old dusty bcr2000, found out it had a software editor and could be set in absolute mode. And I don't need anything more.

    With encoders set to absolute, no need for two-way communication, no more jumps in values, everything stays in the patch. I have a set of WIP abstractions that steal the focus of the shared unique controller, map and scale CC increments/decrements to the relevant patch parameters and deals with store/restore presets.

    I just wish there were something to faders like what encoders are to knobs.

    posted in I/O hardware diyread more
  • kyro

    http://www.pd-tutorial.com/english/ch03s08.html was a great help for me back in time.

    posted in patch~ read more
  • kyro

    @ddw_music you were right, problem solved :
    Capture d’écran de 2022-05-10 12-45-39.png

    posted in technical issues read more
  • kyro

    @ddw_music very nice! With your downward edge detection I can now divide a phasor~ by an arbitrary number. There's a thing I cannot wrap my head around though: how to reset the counter to zero every divided downward edge. So it can safely be run indefinitely.

    I don't understand why feeding the rpole~ argument with ((1-(divided downward edge detection)) delayed by one sample) only resets it once in a while and not every cycle.

    posted in technical issues read more
  • kyro

    @RT-Chris you should have a look at how it's done in Automatonism
    @jameslo absolutely brilliant!

    posted in technical issues read more
  • kyro

    so I totally gave up on solving my maths problems in pd. I used FAUST instead and run my tonestack~.dsp in [faustgen~].
    you can access the 3 parameters with [low/med/top $1( from 0 to 1.
    first time with FAUST, looks awesome.

    posted in technical issues read more
  • kyro

    Wew lads! What a complicated topic. Finding real roots for the denominator, finding either 3 real or 1 real and 2 conjugated complex roots for the numerator... The current filter is 100% highly unstable, I hope I'll get it working eventually.

    posted in technical issues read more
  • kyro

    Hi,
    I'd like to implement in pure data the tone stack model I found in the DAFX book. It's a linear third order transfer function. In the book they use mathlab which seems to have a routine to solve it so the code they give is of no use to me.
    In pd, should I find the roots of both third order polynomials and use poles and zeros objects like in Maelstorm tutorial? Does his method transpose? Should I use fexpr~ instead? Is there another method?

    posted in technical issues read more
  • kyro

    @manuels said:

    Subtracting the result of a halfwave readout of [cos~] from the regular full wave readout doesn't give zero output for the second half of the cycle.

    This reminds me of https://forum.pdpatchrepo.info/topic/13709/bug-osc-cos-circle-asymmetry-drifting-out-of-phase/1

    posted in patch~ read more
  • kyro

    @raynovich in the worst case you'll be learning things, you're in good hands with @whale-av

    posted in technical issues read more
  • kyro

    @bocanegra said:

    See also this video on reverb design which goes through the history of reverb

    Rarely did I spend an hour or so on YT so well. Thanks a lot. Do you have other interesting lectures like that to share?

    posted in technical issues read more
Internal error.

Oops! Looks like something went wrong!