• bilberry79

    Here's a little example of the one-sided finite version.
    dsf1fin~.wav

    posted in abstract~ read more
  • bilberry79

    Hi,

    I'm creating abstracts of DPW oscillators according to Välimäki's paper from 2010.
    http://mac.kaist.ac.kr/pubs/ValimakiNamSmithAbel-taslp2010.pdf

    He proposes the DPW in different orders. (1st, 2nd ... 6th) to reduce the aliasing of digital oscillators. the 1st to 4th order models work absolutely fine but the 5th and 6th order version get heavily distorted if I go below frequencies of 200Hz (for the 5th-order version) and 600Hz (for the 6th order verision).

    Here are my abstracts. The inlet expects frequency in Hz and the outlet is an audio signal.
    DPW6th_saw~.pd
    DPW5th_saw~.pd

    Does anyone know why? Did I do something wrong in the patch?

    best,

    Matthias

    posted in technical issues read more
  • bilberry79

    Hi,

    I made some modules out of the equations from Moorers paper from 1975 https://ccrma.stanford.edu/files/papers/stanm5.pdf

    It's about the discrete summation formula to create complex audio spectra.

    Find the modules on my GitHub:
    https://github.com/bilberry79/PureData#discrete-summation-formula-dsf-adapted-from-moorer-1975

    Comments are appreciated.

    best,

    Matthias

    posted in abstract~ read more
  • bilberry79

    Oh right. Thanks that might really help. I'm going to adjust this patch a little and share the results.

    posted in pixel# read more
  • bilberry79

    I think about it. Thanks for your help.

    posted in pixel# read more
  • bilberry79

    @whale-av thanks for the suggestion but you're right, the scale still will be linear.

    @LiamG I never used data structures in PD before, though I read this manual real quick and it looks like it might be possible but it's a hell of a workaround :)

    Would be great if we had logarithmic representations of arrays in PD.

    posted in pixel# read more
  • bilberry79

    Hi,
    here is a patch demonstrating what I try to do:
    abstract_spec2.pd
    It writes the magnitudes of an audio input (the one inlet) in two arrays. One with a linear frequency scale on the x-axis and one with a log frequency scale. My goal is it to label the x-axis with the matching frequencies in Hz and not just the indices of the array (aka the bin numbers).
    Thanks for your help.

    best,
    Matthias

    posted in pixel# read more
  • bilberry79

    Hi,

    Can anyone explain to me how I add a logarithmic label to an array. Right now I'm using the internale message (; array1 xlabel 0 1 2 3 ...) to add labels to my array. But this only gives me a linear scale.
    My scenario is as follows: I display a frequency spectrum with an array. The standard is of course a linear view if the bins. I already managed it to display my spectrum in a logarithmic scale. Now I also want to add a label to the x-axis with a logarithmic scale.

    Thanks for your help.

    Best,
    Matthias

    posted in pixel# read more
  • bilberry79

    Hi,

    can anyone confirm or deny my suggestion about the different transient detection methods in bonk and fiddle?

    in fiddle the energy of complete analysis frames are compared with successive frames and on this base decisions are made if there's a tranient or not.

    in bonk distinct frequency bands are compared and the energy evolution of these are the base of transient decisions.

    thanks,

    matthias

    posted in technical issues read more
  • bilberry79

    Hi,

    i receive following from an object box: 0, 0, 0, 0, 1, 1, 1, 1, 2, 2, 2, ... etc. every time i recevie one number it triggers a tabread4. i want that the tabread4 only gets a trigger when the number changes. that means one trigger at the beginning, one trigger at the first 1, one trigger at the first 2 and so on.

    at the moment it looks like this.

    [for++ 512]
    | \
    | \
    | \
    | \
    [/8]
    |
    [tabread4 array]

    any ideas,

    best regards,

    matthias

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!