2d.wave~ so snappy

    Gexe
    Mar 14 2014 | 10:19 am
    Hey all, I know I could totally just read back and find this answer so no need to mention that, but I have like an hour of free time for this stuff every few days. Just wondering if anyone has simple or even more elegant solution to the pops and snaps you get from jumping around a file in a buffer~? Like with 2d.wave~. Believe me I'd love to just sit down and solve it myself, but have mercy. Thanks in advance there's a file as an example of what I'm talking about attached. :D
    • Gexe
      Mar 14 2014 | 10:20 am
      Oh,I guess there isn't a file attached "Output 1-2.mp3: File exceeds allowed file size." lol. But anyone who knows what I'm talking about doesn't need to hear it anyway.
    • vichug
      Mar 14 2014 | 10:46 am
      see the grooveduck and grooveduck2 abstractions. The base techniques is there
    • roger.carruthers
      Mar 14 2014 | 2:18 pm
      I guess it depends on how you're jumping about within the buffer with 2d.wave~ - if you're making discrete jumps, you're going to get clicks, but you can smooth the y (rows) input with something like rampsmooth~ to reduce the effect.
      However, in my experience the worst clicks you get with 2d.wave~ are not coming from jumping about within the buffer using the y input, but from basic looping (i.e.the x input), and for that you need some kind of ducking or crossfading.
      There is an abstraction or sub-patch somewhere in the example patches (sorry, not at a Max machine right now) called wavefader, which crossfades between two wave~s - substitute 2d.wave~ for wave~ and you're heading in the right direction, though I'll admit it's not perfect.
      It works well with percussive sounds where the clicks and pops are often masked by the transients of the sounds themselves, but have yet to find a solution that works well with more melodic material.
      Maybe the answer is to do like Eno says and "Honour your mistakes as intentions", i.e. call it 'glitch' ;-) Cheers Roger