B-Wise wrote:Trusty Dusty it is!
Man, that let that dude doubt get to you. We know what you're about.
nah man, this stuff has zero importance in my life so there's nothing to get to me, besides I'm really thick skinned and I can't force anyone to believe in the stuff that actually is... unbelivable
That post was kind of tongue and cheek toward Ultros as he's the one who brought me to this stuff and showed me what can be done. Before that dude's era, my knowledge of Linux was at "rm -rf" level. I guess what I'm trying to say is that you guys don't fully understand what a nugget you have here and what is he capable of lololol
Ok, but enough with that brown nosing
bitermc wrote:What did he say about Pure Data?
Did he say Pure Data have always been there???
Yes Pure Data... The exact Pure Data you think of

It seems that MPC does have (or had) support for multiple different types of plugins: LADSPA / SOUL /PURE DATA etc. but it looks like the only latter one can be actually enabled atm because they went into effort of limiting the number of instances of the PD inside of MPC app. My guess is that it's used to quickly create a patch for testing purposes, for example when you want to quickly create a specific scenario with a specific state of plugin/ get a test waveform going/ send some midi data - you're not going to compile a new plugin that just does that, you wil quickly pull PD connect some dots, input some numbers and bada bing bada boom you have instance of plugin running. Problem is that it's too much effort to find out what the trigger mechanism is. I think that SOUL had the same purpose but this format was dead on arrival so they've stop using it - there is still some content embedded in the firmware though.


