Added: 4 years ago
From: tim167
Views: 36,155
Sort by time | Sort by thread (beta)

Link to this comment:

Share to:
see all

All Comments (37)

Sign In or Sign Up now to post a comment!
  • nice patch sir !

  • Is this Program Freee?

  • @antiemo666777 yes it is free.

  • Great Amen work out ! killer PD patch

  • sounds like old squarepusher. good stuff.

  • that music at the end... what insanity! i absolutely love it!

    cool patch, too

  • @nepalnt21 thanks :) there is more of that stuff on my site, under 'music' > 'egi', though I had to move my site recently, I'm not sure if I re-uploaded that music already.

    they are guitar improvisations with pd.

  • in the past 2 years ive probably come across this video 300 times. and it never gets old!

  • Hi tim167,

    I like this very much. I've been experimenting with similar things recently - the patch I came up with looks similar (I can't see this too well!). I'm doing power of 2 as well, so I tend to make a beat with a digital drum machine that I know would "chop up" well.

    Are you using [samplehold] to prevent clips / glitches?

  • Hi astrometria, afair, I don't think I used samphold or samphold~ anywhere in this patch. How would you see that prevent clicks or glitches ?

    To do that, the most common way I know of is to use small fade ins/outs. (present in this patch too)

  • Lol, is that the amen beat you sliced?

  • so useful!

  • Hey dude - my video response was inspired by this video of yours. I was fucking with it and got it to swing (using two phasors somehow) but I didn't know how it happened :) I'll have to figure it out later. I guess cutting its speed .75 and keeping cutting times might do that but... blah blah

  • Is this how Aphex does it?

  • @amart7 I think he uses Super Collider, and MANY other things, like circuit bent instruments.

  • couldn't create omde 4...

    omde 4 ?

  • oh, I didn't remember that was in it...[omde] is an abstraction, 'om de' means something like 'each' or 'every' in dutch, it lets some bangs pass and blocks others, for example when [omde 4] receives 8 bangs, only the first and the 5th get through. it's easy to make (iirc a counter and a [sel 0] basically...), but I'll see if i can post it somewhere later...

  • This is really amazing. I'm trying to get started in pd, and if you have time I would love to see how you did this explained. Thanks for your great work.

  • My guess: The start of each drum hit is stored ahead of time.. then sprinkle some randomness to get the different beats..?

  • Hello Tim. Thanks so much for this. I have really added a lot to it but i would love to have a walk through for the build that you have on this page. i understand that this would be time consuming but i htink many new PD and even Max users would greatly benefit from your expertise.

    Again thank you for sharing

  • Incredible

  • I tried to rebuild that thing using the picture on your website as a blueprint. but it doesn't work. pd says "error: visual: no such object"

    what went wrong?

  • oh, sry, i did not recognize the link below the picture...

  • hi Thidrek,

    thanks for commenting.

    Rebuilding the thing yourself is certainly useful if you want to really understand how it works.

    About that error message: my guess is that you named a send object differently from the object it has to send to. iirc,'visual' is what I named the array to visualize the currently played slice. Maybe try 'Find>Find last error' from the pd menu, it sometimes works :)

  • Where did you learn how to use this program? I've been trying to find a thorough beginner's tutorial for making music in puredata.

  • search for the pd-tutorial by johannes kreidler on google. it is quite easy to understand and way easier than the one written by miller puckett (the inventor of pd)

  • @gogobibo some search terms to start: 'floss manuals pd', 'Programming Electronic Music in Pd', 'theory and technique of electronic music', 'pd-list info page', but I guess you found out about those by now ;)

  • awesome tim! hope UR well!!

  • thanks, been looking for this for a while(i was lazy). your website needs a scrollbar :)

  • hey, thanks for your comments all,

    just stopping by to say that I finally fixed the scrollbar on my webpage now, so anyone who had a hard time finding the patch, look again now :)

  • nice :) thanks :)

  • hi,

    the patch is online on my website, it's called slicer.pd.zip in the /software folder (add /software to the main url, there's a link to the zip)

    thanks for your interest!

  • I'm trying to get how this works but I am used to Max/MSP... How do you read the peaks from where it should play a bit? Where is the peak detection? Is there even any? I'm really curious... it's a cool patch!

  • Hi maark,

    There's no peak detection at all here.

    I prefer just calculating the divisions from the total length, because peak detection is quite error sensitive with more complex input material.

    Peak detection could be done easily too with the [bonk~] object...

    thanks for your comment!

  • By the way, I have another patch online that uses peak detection, see 'autocutup.pd' on the software page of my site. This method is useful for more rubato meterial, or speach as in the example.

  • Ok... I was already wondering where the detection was :P. In your autocutup patch, how do you analyse the file quickly? But of course I understand how you use bonk~, but it needs to go through the file in realtime to find all the peaks, right? You can't just load up a file and immediatly know all the peaks...

  • The peak detection happens in realtime, before the actual slices can be played. I guess you could cheat to make it faster, for example by playing the file at 2 or 4 times the speed when detecting the peaks, but i'm not sure how that will affect the results. You could also detect the peaks of several files beforehand, save the results as separate files along with the waves. From then on, you can load both at once so the peaks are there instantly...

  • actually, meanwhile I found out that the way to calculate a file faster is ti use an upsampled subpatch...haven't tried it myself yet though...

  • @tim167 Tim - A classic loop slicer wouldn't need to detect peaks - it would assume it is a valid 'loop' of some (western) measurement and probably skip to chunks of some reciprocal of a power of two and an integer between 0 and that power of 2.

  • @midinerd hi, the peak detection I was talking about is in another patch (the 'autocutup' one). peak detection is useful when you have very irregular and rhythmically unpredictable material, like speech for example...

  • Do you have the patch posted anywhere? I would love to dig into it a little.

    Great work!

  • nice work

  • Nice beat slicer!

Loading...
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more