bluecat
 
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 could be wrong, but it seems to me that many potential buyers of this product would want to use it because they are interested in developing and sharing technological creations but do not want to commit to the learning curve of doing full-on C++ development with a complex API like that of Steinberg VST.  Think of SynthBuilder folks - I suspect these people should be your target.  One compelling aspect of Plug n Script is that it already covers all the bases WRT 32/64 bit and multiple platforms - something that is always a negative for any SynthBuilder-based software.  But that's just my 2 cents.

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 :-)

I'm curious to see the performance/CPU utilization/overhead before expressing an opinion as a tool for building stuff to be distributed. It's going to be a little while before I get a chance to play with it, but there's an introductory price (plus discount for Blue Cat customers) until 10/15, so I have some time. 
 
Just looking over the docs and API there were no particular dealbreakers for me, just a few, "Gee it would be nice if...".  But it looks like there is some real potential for those who know their way around a programming environment, midi and/or digital audio just well enough to get things done. I'm hoping to find out whether more limitations might be caused by the programmer than the environment. 

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!

First, let me note that the link to skinning info in the previous post starts "//http://http:" and needs correcting.  But I'm looking forward to checking out what it should be pointing to.
 
The other thing I'll add is this.  I would hope that you'll concentrate on effects usage rather than plug-ins that do sound production.  The latter category requires a lot of bells and whistles, but some very useful effects can be created with a relatively sparse UI.  And let me amplify an earlier point.  If you do end up offering a free player, I would prefer something like the following.  Allow binding a single script and optional skin into a single distributable file that be installed like a typical dll effect.  In other words, don't have the free player first require loading a script to function - that would be too prone to error.  Just let the user of a PnS-based effect have the easiest of all possible installation requirements to be up and running.  Hopefully I'm making sense here.

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.

Just bumping this, as it has already been updated to 1.1.
 
http://www.bluecataudio.com/Products/Product_PlugNScript/#History
 
Interestingly, they have already implemented one the main items on my wish list by now supporting the File I/O API. 

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