I was wondering if it's possible to resample nebula libraries using something like SoX? I realize that Nebula resamples on the fly, but I was wondering if SoX might do a better job, and if nothing else, lessen the CPU demand on the system.
Most of my libraries are at 96k. Some at 44.1. Would it even help to do what I'm suggesting? I normally work at 96k, but I've found that doing OTB summing with 16 tracks, that my interface won't hold at 96k, so I'm using 48k a lot. Thought it might help to have them converted ahead of time.
saddle wrote:Can you explain further about resampling the vectors, not the audio? That's a new point to me.
Well, it's more a feeling I have . Now that I think about it, it might not have any difference.. but let me try to explain anyway:
See it this way, you have your original audio, untouched, and an effect is applied to it (Nebula in this case).
Nebula resamples its effect (the vectors of the Nebula program) and applies that to your - untouched - audio signal.
It's not that your whole audio is resampled.
For instance, if you're working at 44.1K, and you use a 96K nebula program:
I assume that the 96K gets resampled to 44.1K, and then applied to your audio. I assume it's NOT the case, that your audio gets upsampled to 96K, nebula applied, and then back resampled to 44.1K... that would be...a waste I guess .