Just wanted to report that changing my Rate Conversion to 9000.00 msec did not fix the SRC flash issue. Still having to hit reload every time I instantiate Nebula3 Reverb. This is now tested on Reaper 64 for mac
I think you may be right, RJ. So attached is an .xml of my Fenix Red. Here's an extra bit of info which I am finding confusing. Just today I opened a PT12 session which I "Saved Copy In" _from_ a 96k session _to_ a 48k session, i.e. all plugins and everything were the same. The VSTs were hosted in Bluecat's Patchwork. When I opened the Bluecat's, these instances of Nebula will NOT lock to the 48k session no matter if I press Reload or with the 9000.0 ms RATECONV. It's like they remember being brought in at 96k. I feel like this shouldn't happen - do you have any idea what's up with that?
Hopefully my .xml file shows something weird so I can get this fixed.
Unfortunately, no. I believe I stopped trying to fix it when Support asked me to reinstall Nebula, which I haven't found the time to do. I'm surprised more people haven't had this issue, and I'm hopeful Neb4 will fix it!
It is not a common issue, and may very well be specific to your session. And I don't think that NEB-4 is the solution. No need for that.
We tried [earlier] to cover some of the possible obvious things ... which didn't solve this for you. [unfortunately].
There could be several variables that make it difficult to suss from just reading the thread. That is why Tech has a 'ticket' procedure. The needed details to get to the source of the error.
It could be as simple as the DAW samplerate is in conflict with the soundcard, and telling Nebula the wrong rate at start-up.
Is it possible the library you are using does not have the native samplerate library you are running the session at? [48kHz]. If you start a session at 44.1, save and reload, do you have the same issue ?
Is it all the custom Nebula's ... even the base Nebula ?
Again ... more than one variable ... we're then guessing [which is not fun, and can add to the confusion]. It is much better and to a faster solution if working directly with TECH through the 'Ticket' system. But you have to stay on it. They need system details, and maybe even an example session submitted. Whatever it takes to get to the bottom of this and get it resolved.