Thanks, ill look at those options. I dont have much if any experience in software development and the whole process of hiring developers. I don’t have a clue how to break down and evaluate a developers work or determine a fair rate.
To that end I have been trying to be exhaustive in my planning and concept design. I am intimately familiar with the audio engineering elements from years of studio and patchbay design and work as a professor of audio eng, teaching theory and practice of all aspects of music and audio production/studio technology.
Ive actually got a full wireframe and a complete spec on core functionality, basic and extended logic trees for the conditionals and a point summary of the workflow and principal use cases.
Ive also written a decent spec on down stream extensions to the core application itself.
I would consider coding it but I would be limited to js/html5 and poorly at that.
I could probably knock out a basic prototype of the main functions, but I wouldn’t have a clue how to handle the add-ons that require a back-end db : the drop down list of gear that tracks number/type of connections per piece of hardware, and especially not the ability to auto pop (and validate) that db with user additions to the gear list. And that’s the easy one.
<vaguely relevant tangent>
I have never been a coder per se, much to the eternal shame of my father, who was a very high level mathematician and cryptographer for the Dod, designing most of the Cray 2 systems at Ft. Meade and a key player in the development of Ada.
The only code related work I do whatsoever at any level is very specialized work in Reaktor Core (a synthesis engine and dsp enviroment for NI Reaktor, not really a language per se) and
KSP (http://www.nilsliberg.se/ksp/scripts/tutorial/), a byzantine scripting language for dsp management and sample library development in Kontakt, which is a high powered sampler engine and instrument ecosystem. It is so…different…that syntactically it is closest to Pascal and most work is a painstaking slog through large sample collections and cranky ui assets.
So yeah I can take it pretty far for an amateur and probably simplify the dev work to an extent, but I know when I am swimming in waters over my head. Budget and strong planning can help me steer the project and that’s enough for this one.