GOAL: Make a cross-platform realtime gui and audio programming environment/framework to improve the ease of producing and distributing sample library products.
My project/plan is to create a framework for authoring digital audio instruments, more specifically sample libraries. The framework will allow you to visually and textually assemble a sample library product, and allow you to script the audio engine like Native Instruments Kontakt, except that the scripting platform will also be the same engine that runs the VST (or that seems to be the plan at the moment). In other words, the sample library developer could program the sample playback engine from scratch using guides that the framework offers, or use the framework to assist in accomplishing all of the most common needs of a sample library product, generate the code, and BOOM! A working VST sample library (btw since this is an audio engine scripting, unlike Kontakt/KSP, this could also be used to create full-fledged synthesizers rather than a sampler, or a hybrid sampler/synth).
Another VERY important addition is that the framework will also establish standards that all developers will be able to easily follow so that one developer's product can run in the same window nicely along side another developer's product, a la Kontakt rack view. This is possible with protoplug (see more info below).
The framework will consist of 4 parts:
1. Assembling the audio files (samples) into groupings, defining "where" they sit in a grid of midi velocity/midi note (MAPPING ENGINE). The samples can even be left "floating" (so the sample/voice triggers only based on events).
2. Assembling the user interface with image files, defining types, positions, functions, etc. (GUI BUILDER)
3. Generating code from steps 1 and 2
4. Interpreting the code (protoplug? projcuer?) and adding additional scripting for specific usage of audio and gui. (NOTE: If using projucer, then obviously you'd have to actually assemble it into a VST whereas protoplug is already a VST, but the point is they are both real time coding languages, both visual, but projucer may have some advantages)
I'm putting together a multi-page PDF that I will be distributing to interested parties. It will also discuss sources of funding. So far I have a flow chart of how all of this will work.
My first idea was to generate code for Protoplug, which is a LuaJIT VST with JUCE bindings, check it out, it's very awesome: http://www.osar.fr/protoplug/
Then I watched a video abou Projucer and that seemed really awesome. Now I'm wondering if I should remove protoplug from this project and somehow leverage Projucer instead. However, I am not an experienced programmer and I don't know if that's an idea that makes sense.
I explained this as best as I could, sorry if I sound very lost! Just kinda looking for advice, maybe the terms I'm using are incorrect, maybe my flow chart doesn't actually make sense with how things work. I'm half-confused in all of this, but I know my vision. I can answer questions to clarify things. Thanks for your time!
[edited for further clarification]