I believe that when a Neb instance opens, it looks for the sample rate of what is present. If a file is not open, I think it will get the rate from the program source preference or it will get it from the program rate.
I think if you have a 44 or 48 file open first, then open the preset chain, I believe it will load them all at the rate you want.
dpclarkson wrote:Hey Michael, thanks for the reply!Hi there,
It sounds like you just need the right setting in Nebula as a one time setting. I don't know the precise minimum setting for rate convert, but once it is done it is done, and it works well for all programs. It will simply convert the programs to 48 for you and it tests well on all systems this way.
I'm using Nebula only for offline-rendering in Soundforge 9, and I make
chains of Nebula in SF's plugin-chainer.
Whenever I create a new chain, everything loads fine, correct sampling-rate, etc.
When I save a chain as a preset and recall the saved chain, the arrow is blinking again...and reloading works, but it's a pain.
So it might as well be a flaw in SF, instead of Nebula 3 (latest version),
but I want to rule out everything completely, before pointing fingers.
Can anyone reconstruct this?