thanks for the answers! In terms of latency I did not mean whether the controller added some - but just that the latency of multiple Nebula reverbs adds up so much that there is a large lag between controller movements and sound changes?
SWAN wrote:thanks for the answers! In terms of latency I did not mean whether the controller added some - but just that the latency of multiple Nebula reverbs adds up so much that there is a large lag between controller movements and sound changes?
Ah,I see. There is some lag. [at least for the beta]
I had intentionally programed in some 'delays' into the circuit. Whether they stay at the +250ms value, is what I want these test for. I originally put this in as a type of safety. In the early stage, I just didn't know if the system might possibly overload or something. Those 'inserted circuit delays' may very well be pulled out when beta is completed.
In practice, the MIDI design should respond like a VSTi instrument played by an MIDI keyboard would. [as an example].
The Massive/Passive in it's full expression spans across 13 NEBULAs. That alone introduces the normal latency. Notice that as a Nebula chain grows, when we make changes on the plug itself, the normal latency delays the onset of those changes. The combined audio buffers still must stream the audio data.
Of course, the 'NebulaVirtualController' [NVC], allows individual bypassing. So if only a few EQ bands are in use, the combined latency will naturally be less than when all 13 [or more] Nebulas are in the audio chain.
An early 'snag' at the very start, helped define an important feature that could not be postponed.
We found an issue that could, and did arise, due to different versions of a library. Once a small change was made of the beta ... the real testing could begin.
It was for a reason as this, that the initial testing would be limited to a single, trusted, dedicated person of high regard.
Late last nite, with several days to 'just play' with the controller [between a busy studio schedule], I received positive comments. It works.
We have centered on the base naming convention too.
[N]ebula [V]irtual [Controller] - NVC
Understand that we are being cautious. Just as one should not update software just before a session, we must follow the same common sense, so test flights are happening in test sessions.
The mentioned 'snag' was really important to have. To this, I'm putting together the 'User Configuration' module. The NVC can then be tailored to a user specific Nebula library configuration. I've included custom naming of modules and descriptions in the GUI interface. These are saved in the configuration file, and will auto-load when the plugin is launched.
Much more happening ... just wanted to get a fast update notice to everyone.
Again, thanks for all the PM & forum comments.
OK ... getting back to work on some cool NVC features.
Last edited by RJHollins on Mon Apr 15, 2013 2:38 am, edited 1 time in total.