Now the questions is completely different and you should consider:Shibata wrote:Enrique
Normaly, ASIO buffer in audio interface, compensate the latency by host.
But Nebula only one vst who had personal internal buffer and who reacts differently.
Normaly if you render two files with identical settings, and reverse phase in one of them, you'll get zero 0, because the signal is subtracted each other.
Look, i render the tape preset with 128 internal buffer two times, reverse phase and get zero. You see that RME mixer shows -оо ( infinity )
And if i render one file with 128 and one with 8192 the difference will be obvious. Look at my previous post in this thread. There are screens and audio examples.
So, internal buffer not compensate by host. No matter which. I tried Cubase, Nuendo, Studio one, Digital Performer and in Reaper.
Furthermore, the higher internal buffer, the fastest the rendering and light to CPU and vise versa, which suggests that he is doing less computing at rendering and miss a part of a signal. This is even worse than just lower the sound quality because we lost the raw signal. And my test before with phase show it.
PS: Use standart vst like Ozone 7 full loaded with his modules and render file with my audio interface buffer ( RME AIO ). 128 and my max settings 4096. Reverse phase and get zero.
So, the internal nebula buffer is unique, although it is not the buffer problem, but RTE which it affect.
- Does Nebula playing/processing always the same set of kernel?
- Also happens with INIT?
* We understand reverse phase as polarity reverse.
Nebula DSPBuffer setting is time delay in samples this time is reported to the host using the plug-in protocol.