After working with Nebula for a few years now it's been really stable for me so I've decided to experiment a little and switched to TIMED to see how it sounds. I bounced a session which had been mixed with the default FREQD settings and then switched to TIMED. There's a noticeable difference to me in the EQ's. It sounds better to me but TIMED is way too much for my CPU to handle so I figure I could mix in FREQD and then switch to TIMED when I'm ready to bounce the sessions. However, this is tedious.
So, do I have to change from FREQD to TIMED in every single instance of Nebula or is there an easier way like changing something in the xml file?
It is not in our plans due your are rendering your work with a setup of parameters that can't be monitored in real time.
If you feel this feature is an critical and strategic for your work, request it to sales department, but our point of view is, build a new computer with more CPU core, there are now 72 core CPU computers available in the market.
Well, what I do now is create a new plugin from the library with nebula setups and tweak the parameter to 50ms, so whenever I use that plugin, when I'm ready to bounce, I just gotta click the arrows to timed. It makes the process way less tedious, especially since I only use timed for eq's.
I don't notice a difference using timed for consoles or compressors, stuff like that, might even make it worse. But for eq's, it's like night and day. If you want to know the difference between analog and digital, bounce a song in freqd and then switch your eq's to 50ms timed bounce that and compare.