Blue Cat Plug'n Script - a different take on a builder

Looks cool.

I looked over the online docs and it looks interesting, but I'd say the phrase, "With this plug-in, you can write your own effects with very little knowledge about programming" is a little misleading as you clearly do have to know how to program. But if you do know how, it looks fairly straightforward, and though they don't seem to have the included scripts online, they do have a picture of a very simple tremolo script:
 

 
You can read the docs here:
 
http://www.bluecataudio.com/Doc/Product_PlugNScript/
 
and the programming part that one would likely be most interested in starts here:
 
http://www.bluecataudio.com/Doc/Product_PlugNScript/#ProgrammingReference
 
I'll probably have to download the demo to learn more, but I'm just intrigued by the fact that it falls into the gray area between full blown programming with the VST SDK and more typical "connect the widgets" builders like Reaktor, which make some things easy, but make other things that are easy in code messy and tedious. 

I am on my cell ATM, but wanted to make a quick comment so I can find this again.

This looks ideal for me as someone with a tantalizingly small knowledge of C++. I always thought it would be fun to write the "logic" part of effects but without getting bogged down in the nerdy DSP side of it (which to be frank I just don't have the time nor the inclination to learn). Will have a good look at this, thanks. 

That's an interesting point of view. Thanks for posting!
 
It's true that the default generic user interface that adapts to loaded scripts proposes only knobs. However, it is possible to build your own user interface using our Skinning Language (descriptive XML), with tons of widgets available (buttons, switches, sliders, 2D or 3D graph displays, etc.). It is a bit more work, but you can end up with a user interface that is dedicated to your script and looks more like a custom plug-in. The current version of the plug-in supports it, but does not show examples of such custom skins. We plan to create a few ones to show this capability in a future update.
 
It is already possible to share your work with others (if they have the plug-in, that's right), and distributed as a preset with a custom interface, it can look like another plug-in. For sure, it is not the same as exporting it as an independent entity, and that was not the original intent of this plug-in. But that's maybe something we'll do in the future, probably packaged differently. Let's see how people use this and what gets produced! 

I agree with you, it could be part of the target. So far, our initial take on this product was to make it usable for people who do not necessarily have great programming skills and just want to write their own effect (MIDI effects especially are simple to write).
 
But it is not excluded that we may go one step further for more advanced programmers who would like to package and distribute their work as a product. Let's see how the community reacts to this first step! And we still have a couple of things already in work for the future :-)

CPU usage for MIDI processing is mostly irrelevant. And for Audio processing, it will definitely not compete with hand-written assembly or well optimized C++ code compiled with a good compiler, but it is still pretty decent for most applications. 
 
Feel free to tell us your "would be nice" ideas. We are actively working on future updates, so feedback is welcome!

Link fixed, thanks!
 
If we were to create a "player" or plug-in builder from scripts and skins, yes: this would be the way to go.

Looking forward to hearing your creations! Have you checked our GitHub scripts repository? It already has a couple of new user scripts!