Not exactly sure how to request this, but something like this ...
Having a configuration situation developing, whereby, particular libraries are requiring modified settings in NEBULA's 'kern' page.
In particular, the Gemini HQ compressor, along with personal mods to specific PreAmps.
Additionally, without VST inserts, the CDS tape plugs, and all Acqua plugs are out of the equation.
But first ... in order to render out files, the available solution is to do things in sections [really kills workflow]. Staying within the REAPER DAW, for example, allows for a more coherent process ... but it, too, has obstacles that I'm learning to overcome.
In particular ... each track in a mastering project can be assigned and have its own effect chain. In the master bus section, I can have all 'global' inserts that all tracks will eventually get. This was the particular area I'd hope to call on NEBULAMan to handle [but not fully possible].
As I learn the workings of REAPER, I can 'freeze' individual tracks [optionally] ... but I'm looking into 'render stems' to be able to process each track of the album through the 'global' chain, and save these off as individual files. Later to be assembled, edited, level balanced, and dithered, etc, in WaveLAB as a proper CD format.
OK ... that's a basic scenario [with variations].
In looking forward, and to include NebulaMan into the workflow, I hoped to generate some ideas, suggestions to expand the flexibility and usefulness before the coding architecture gets to locked in [if still possible].
Any comments? suggestions? opinions ? constructive conversation?
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64
NVC [Nebula Virtual Controllers]