I heard this patch on YouTube, and a viewer asked for the patch. Andy's reply was to copy it from the screen. I tried. It works, but not the way he's made it work on YouTube.

Would anybody be able to point out where I made my mistake(s)?

I named it Microsound.pd and here's a link to the patch that I've worked on, so far: https://drive.google.com/open?id=1OzpQt2HOK6w-Nb9f5HxiD9edAli0RSxl

I've tried to understand PD for at least 10 years, now it's finally starting to make some sense, but only in the most basic sort of way. Like, I now know how to connect things, and I have a rudimentary understanding of some of the objects.

Any help would be greatly appreciated!

Thank you.

@KirkMarkarian More or less.... you might want to modify the left/right values for the "granular" fader, but what I have set might be to your taste...?.
fix.zip
Fader ranges were all wrong, and the two links to [+ ] and [- ] were missing from the "jitter" fader ( not obvious on the video..... ).
You might also want to automate getting the value from the output of [expr] into the two message boxes and fader for playback speed/ direction (on the left side of your patch).....
David.

@whale-av Thank you for the help. I'm truly a novice at this, I've always just loved the sound of these types of electronic patches. I'm going to take a close look at what you've changed. Thank you for the advice and I'll be learning all kindsa new stuff!

I've been learning so much from this and trying to apply it to patches in Reason (new Grain synth is fantastic, but not as flexible as PD)

@KirkMarkarian You are very welcome. Pd is worth every bit of effort you want to throw at it......!
I will play with it a bit, and post back here if I find any other problems.
Mod2.......... fix.zip forward/back/speed automated.....
David.

@whale-av I know I'm definitely missing something here - from the "clip" object to the second slider of the granular portion of the patch, at least on my end, there is no jumping back and forth. It seems the "set jitter rate" object isn't really transferring to the granular portion and/or the random object in the granular section isn't bouncing back and forth. I know I'm probably missing something extremely obvious, but it's not becoming apparent

EDIT: Aha, pay me no nevermind... you got it! Ah, and you gave me some other neat stuff too. Thanks again!

@whale=av David - got it up and running, while adding filtering, reverb, and delay to get a fuller sound from one audio file. Next step is to see if I can duplicate a second looper to run alongside the first. Thanks again for your help!

Here's an updated patch in case anybody wants to fiddle with it:

https://drive.google.com/open?id=1P2rMgtIwpRpsHN-peVkQ9p6JEL4KYeUV

@KirkMarkarian Added a bit of very simple de-clicking..... fix.zip
If you downloaded between post end edit...... sorry....... download again.
I forgot it is using [tabread4~] so interpolated........
David.

@whale-av Thanks David! Now I'm gonna have to pick - there's this bit of me that loves the Ryoji Ikeda clicky sound, and there's a part of me that loves the click-free sound (kinda depends on the situation where it would be used).

Also, I've gotten much closer, through the use of Pure Data (no foolin'), that I can get much closer to the Ryoji Ikeda sound using some of the Rack Extensions that I couldn't figure out how to use (in that manner) before. I wish there was a way to transfer Pure Data to Reason - that would be something!

@KirkMarkarian Yes..... I missed that you want to run 2 at once......
You just need to add $0- to the start of every object that sends or receives data or audio. That will keep them separate (unique) and allow you to open as many copies as you like...... clicking or not.....!

What do you mean by "transfer to Reason"..?
Send audio from Pd to Reason?
Control one from the other?

You should probably look at https://help.ableton.com/hc/en-us/articles/211472149-Using-Link-and-Propellerhead-Reason
To connect with Pd you should be able to get [abl_link~] through Deken.
Here it is for windows........ abl_link~-v0.3-(Windows-i386-32)-externals.zip

David.

@whale-av Oh! Thank you for the $0- aspect. I will have to try that soon!

As for transfer to Reason, well, I've been composing in Reason since 2001, studying and using various forms of synthesis since 1995. For transferring PD to Reason, I wish I could use PD in Reason like one could use Max/MSP in Ableton. Not via linking, but native inside of the application.

Since my computer is not only fairly old (late 2012 Mac Mini), running OS X, and (you'll get a laugh out of this ) I won't using linking to any other applications (yep, I am stubborn!). Heck, I won't even use VSTs in Reason, even though you can now. I really just prefer working native inside one application. So, if PD worked natively in Reason - it would be fantastic!

For PD, I use it solely on its own - just like Reason, because they don't work together natively. I love them both for different aspects. Go figure. That's why I appreciate you taking the time to explain these little bits to me, because I am learning now what PD can do that Reason can't, AND finding out how to use the methods that I learn in PD when I use Reason.

So, thank you for all of this help, I really mean it! It's a lot of fun using PD as another tool to get me where I want to go