• seb-harmonik.ar

    The numerical considerations of digital arithmetic are something to think about as whale-av mentions

    Also, every effect is different. Obviously some function in a way that will alter the volume, or behave non-linearly with inputs of different volume.

    An example might be a filter combined with an expander or compressor. At different frequencies the signal will have bigger or smaller amplitude, and will therefore interact with the compressor differently.

    Another example would be a wave shaper

    There are things called "linear operations" Most filters are linear. This basically means that if you switch the order of them the outcome will be the same, or if you change the volume of the input signal the volume of the output will be proportional to the change

    posted in technical issues read more
  • seb-harmonik.ar

    Hi,
    I'm not sure what onepole~ is so I didn't look @ the patch too much, but I believe a doppler effect could be achieved simply by calculating the distance of the sound source from the listening location and then putting the amount of time that it would take sound to travel that far into vd~. So, if sound travels 343 m/s on average and your sound source is 343 meters away you would put 1 second into vd~ and update vd~ with line~ whenever the sound source's position changes. That should create a pitch shift effect automatically

    However the situation becomes more complicated with multiple sound sources as you'll need multiple delay lines. At that point memory usage would be something to consider, and perhaps the possibility of using a single delay line for all sound sources

    posted in technical issues read more
  • seb-harmonik.ar

    A few things:
    the comb filtering only happens when you add delayed and non-delayed signals. However, you only have the delayed version going into the fft.

    Secondly, I didn't know why the biquad filter was there so I removed it, and scaled the graph so the peaks were at the top of the graph.

    Thirdly, the array size has to match the block size of the fft. Since the real fft only does half a block, it's only necessary to have the graph go to 2048 in this case

    After doing those things you should be able to see it (at relatively high frequencies anyways).

    delays-1-fix.pd

    posted in technical issues read more
  • seb-harmonik.ar

    you could also do it like this
    Screen Shot 2017-02-21 at 4.27.08 PM.png

    posted in technical issues read more
  • seb-harmonik.ar

    there's a list-shuffle in sfruit that seems to do what you want, I misunderstood at first, not knowing that the re-ordering you wanted was a random one

    posted in patch~ read more
  • seb-harmonik.ar

    [list-abs/list-sort]?

    posted in patch~ read more
  • seb-harmonik.ar

    I think what you describe could be accomplished using samphold~ and a delay line if I understand correctly

    posted in technical issues read more
  • seb-harmonik.ar

    install fftw3, I recommend using Homebrew http://brew.sh. In order to store a dynamic library in a location other than the place it was linked from requires some otooling and install_name_tooling (which I wouldn't mess with), (e.g. packages/darwin_app/embed-McOSX-dependencies.sh)

    I'm not sure which version of bsaylor you have but mine doesn't have a libs folder

    posted in technical issues read more
  • seb-harmonik.ar

    the unsupported architecture probably points to trying to compile for ppc if I had to guess.
    You also need to point to the correct location of pd. Try taking out all -arch ppc and -ftree-vectorizer-verbose=2 from the makefile & run
    make PD_PATH=/Applications/Pd-0.47-1/Contents/Resources PD_INCLUDE=/Applications/Pd-0.47-1.app/Contents/Resources/include

    as for learning this stuff, unfortunately I have no concrete advice besides learning common compiler args, the make program and the gnu build tools in general. I also usually do a lot of googling of errors & such (modern luxuries)

    http://autotoolset.sourceforge.net/tutorial.html
    http://clang.llvm.org/docs/UsersManual.html

    posted in technical issues read more
  • seb-harmonik.ar

    @whale-av this still results in an infinite loop? try putting a print somewhere and it will make pd very slow

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!