hopi2013 wrote:I'll just have to bite the bullet and give your method a shot... but darn I wish there was a simpler way.
I think that will happen ... you have to believe, if/when/should a simpler way for any of these functions happen, I'll be the ready to implement.
The very early design needed each preset to be hand entered into NVC
With some libraries, there were over 200 presets
That is no longer the case, as we now have an automatic 'parsing' of the 'Setups' XML file that extracts, sorts, groups, and organizes the presets for the NVC. This is a 'one-button' LOAD feature. If you never change the custom library ... then, you will not need to give it a second thought. If you decide to change the library, for whatever reason, then just one-time load that XML file again ... the NVC will be 1:1 locked to your custom library.
Once I figured out how to do that ... I expanded my custom setup with all combinations available. [believe me, I too dreaded hand entering all those values]
The BIDULE chainer is yet another great addition ... not only for making an NVC chain ... but it allows special routing, such as 'parallel' processing that is much easier to visualize and configure. It also makes for 'portability' between DAWs. [METAPlugin can do this too].
Reaper is another great tool. It's FXchain and routing are very flexible. If you watch the video I posted [it did work for me], I show the entire setup. It may look confusing ... but once you see what is being done, it is a simple pattern. Once seen, a chain can be built in less than 5 minutes. Once built, save it as an FXChain preset. Drop it into the next project and it's all ready to go.
The 'invested' time to initial setup will pale in comparison to the liberating work-flow. With all the standard features that go into each NVC, you will make better sonic decisions, with less effort, and really tune into how these libraries work [in their Nebula form]. This is as close to hardware function and operation ... with all the 'extras' that the library Devs include, that I have experienced with Nebula. My next set is to link in to a physical hardware controller. The NVC is primed for that.
I should say ... the 'you' I'm referring to is everybody who uses Nebula.
You guys know that I'm rather biased in talking NVC ... and I do apologize for the slack documentation and tutorials. There is a time crunch going on. These controllers, which primarily have favored the 'mastering' tools [though, there is no real distinction]. After some 30 years in the Profession ... I'm out of the 8 days a week as a tracking/mix engineer-producer. Discovering Nebula had pulled me out of semi-retirement. Nebula was a key motivator in my decision to build a personal mastering suite. Music is indeed my life. Nebula has allowed me to utilize EQ's, tapes, and consoles that I spent my life playing ... the nice thing ... no cartage fees, nor travel tickets to get to a different board
Now that I've been 'digitally' converted, I want my computer-based experience to [at least] match or surpass the work-flow and ergonomics that a well designed/equipped control offers [that's one reason 'those' studio cost what they did].
There is plenty envisioned for what the NVC's will be capable of. I am early in the development and programming. There are also 'tools' I'm thinking of that are not Nebula specific, but are things I see essential to audio engineering.
There are several NVC's I still need for my work, but I'll do the 'back-burner' mode and get some tutorial stuff to you guys. They won't be fancy or professionally produced [not happy about that] ... but there is the time crunch ... and the spare-time has been slim to none. But this is very important, and the easier/quicker 'you' can get up and running, the sooner the understanding for this excitement.
As Nebula evolves, and new libraries and techniques develop ... so will the NVC evolve/expand.
As with ALL our developers ... we absolutely need your support to continue.