just realised when you go to download it it adds some horrible number the the name of the patch. I remember reading this forum does that to file downloads. Best to rename it to "scope~.pd" when you download it, as will be much easier to find and call into patches in the future.

@esaruoho scope~.pd its a basic abstraction I made, think there are plenty like this about from extended and in Else probably too... just pop it in your "extras" folder of your PD directory and you should be able to call on it in any patch as an object [scope~] (it does the $0- bit itself, so you can use a lot of them in one patch if you want). Let me know if it works, I've never uploaded a patch before. Also I run Purr data, so probably won't look the same...

I haven't tried from DAW to PD, but LoopBe is still fine for me from PD to Reaper on Windows (worked well with Ableton too)

@Spacechild1 Thanks, I'll give this a try. Sorry, really just my first time trying to get externals to work in Purr Data, that's really my problem i guess. Will report back if I get this working.

Sorry @Spacechild1, you're right. I'm working on windows OS, I've just put the vstplugin folder into the /extras folder for Purr data, and tried adding it as a library to the startup window, but doesn't seem to load. Just wondering if you had any experience installing it on Purr Data, I can't tell if I'm going about it the right way, or if it's even possible...I have no experience with compiling, so was hoping to avoid that...maybe this is a question more for @jancsika

@Spacechild1 Hi, thanks for all your work on this. I was trying to get this to work in Purr Data, but don't seem to have had any luck. have you heard of anyone using this in Purr Data, or is it even possible?

Amazing, that's really very helpful, thank you David!
I've been keen to explore beyond the standard lop, hip and bp too, so this will help a lot with that too. Yeah I'm beginning to understand the general idea of how it works, but implementing it is another thing. This will help a lot. One of those moments when I think I've learned enough to feel I've broken through to some kind of intermediate stage, and then...

Thank you, appreciate the link, and for feeding back about the Hadamard matrix. I guess there's no way around just having to learn how to read calculus if I want to work with filters...

I'm beginning to try to understand some basic reverbs from scratch. I know it's a huge topic, and at my level (not quite new to pd but no formal dsp education) I'm unlikely to get too deep into it unless I learn how to read algebra. I've looked at rev~1 + rev~2 to being with, but the reverb outlined in

seemed decent and well explained. It helped me grasp the basics of what is going on to begin with, but I'm still struggling to know how to implement some aspects of it.

It relies on "shuffling and inverting" multiple delay signals as an alternative form of an allpass, but I can't really understand how to variously invert multiples of a single delayed signal. Am I better off looking to the more standard allpass examples in the documentation H.15.phasor and passing the multiple delayed signals through this?

There's also two matrixes referenced, the Hadamard and the Household, and wondered if anyone had any tips on how they work, what it might look like in PD...are the matrixes combinations of additions and subtractions of signals, like in the rev2~ reverb example?