They are such amazing plugins.
Played around with adapting Bubbler for MM and it’s working really well - even at 96khz! Trying out some others and happy to share but not sure what the deal is with licensing etc though - especially as some may come a little close to certain Make Noise modules.
Any thoughts, good people?
Do you mean from GitHub - tomerbe/SoundHack · GitHub ?
This is MIT licensed so there should be no issue.
I’ve only built the PD externals myself.
[edit: oh wait that repo is the Spectral Sound Processing for the Macintosh. application. Confusing that it has the same name]
Good to know - test them at the moment, as well as some from Destroy FX.
Got these working - some even at 96khz and they certainly turn the MM into an insane audio mulcher machine.
UI’s rough at the moment and still not sure what to call them but getting there!
My question on what source you are using still stands 
Sorry! Didn’t see that - mainly from here GitHub - tomerbe/sh-pdexterns: a collection of external objects based on soundhack plugins · GitHub
With some interpretations from other online descriptions for the others.
All vibe coded, I’m a producer trying to make weird sounds and not a dev!
Ah ok, so you had the LLM convert the Pure Data externals to MM modules.
Yep. Worked well after a few attempts - needed to guide it a bit to flatten out spikes causing instant overload.
So far, so good,
This sounds lovely! Are you planning to share the mm plugins when stable?
Absolutely, and VCV versions too (as they are working) but need to check with the developers of the originals to see if that’s allowed.
sh-pdexterns is under the BSD-3-clause license. Why would this not be allowed?
Likely you’ll need to change the naming and branding as this is tied to them and their projects, but the code can of course be used under the BSD-3-clause terms.
What is the other one based on?
You’re assuming that’s something everyone is familiar with? Because I’m not.
I’ll look into it.
I’m assuming that you at least looked at the project that you mangled into MM modules: sh-pdexterns/LICENSE.txt at master · tomerbe/sh-pdexterns · GitHub
It’s your responsibility to figure out what you can and cannot do with someone else’s project, of course.
(especially if you are distributing it, for private use almost anything goes)
You still didn’t answer the other question though 
That’s an unhelpful and condescending response.
Maybe this friendly forum isn’t for you?
Sorry about that, I thought linking to the relevant document would help you find it and read it.
It’s important to understand the implications when using other peoples’ work.
All good!
And yes, I absolutely agree but more than just understanding the licensing I’m keen on getting their direct permission to share publicly too - especially as some of these might have some overlap with some very excellent Make Noise modules 