sneaky wrote:nobody knows and aitb aint telling. Ive asked this before, seeing the 'coming soon!' blurb. false advertising I guess
Yesterday I was searching on internet (when I don't have a prompt answer I usually check it by myself) and I found some threads in Gearslutz that were talking about the 44.1/96 thing with Nebula, AITB, CDSM, ALex B, etc. I didn't knew that some people was so angry about this things. I am not, that's for sure!
Since I paid for FATE and W735EQ I was just hoping for an answer. I had some talks with Tim Cupwise and Michael Angel (I bought lots of libraries in my three months with Nebula) and they've answered always. I won't be upset or anything (not my style), I'm just a newbie asking... But anyway, I really like how the AITB libraries sound, so it's not a biggie if I have to work at 44,1 only with their libraries. It's just a little, very little problem, that's all
I'd love to see this happen, particularly with the Comp because I used a 'real' one at a studio once and almost jizzed . On drums it's just, well. Words fail me! However, I work in 96khz because I have a decent setup, and so everything is at that sample rate. So, even though I will prob get it, well, I have to figure out a way of including it in my workflow without it being a real pain in the ass. Obviously it is going to sound better at 44k than 44k (arrow) 96 (or the other way around I can't remember), but, well, a 96khz version would solve all that wouldn't it
I can't really go into too many details because I am not affiliated with AITB, but I do some testing for them and communicate quite a bit with them. But I can tell you that their lack of 96kHz libraries has nothing to do with them not being on the ball or laziness. They have their own opinions and experiences with Nebula and it's abilities, and because of their own work and opinions, currently have all 44.1kHz libraries because they feel like that is the best product (sonically and authenticity) for your money. That's about the best way I can put it. But on that topic, I have a "decent set-up" as well, and have done many many tests with all of the sample rates. And for my own listening tests, I have had someone else randomly select and play audio from different rates while I write down which sample rate is which (mainly 96, 44.1, and 48). I have never scored better than 50%, except for intensely dense acoustic music, like real orchestra. But with every other genre, I was really guessing. I urge everyone who is convinced that their mixes sound better at 96kHz to do this. Of course if you are using Nebula, to be fair, keep 96kHz projects with 96kHz libraries, etc. I have also done simpler tests with mixes with mismatched sample rate libraries, and honestly, they sounded different, but neither sounded better or worse. I know that everyone has their own opinions, but until you do a truly subjective and REALLY blind test, I can bet that your feelings toward higher sample rates is more "snake-oil" than fact. Give it a try.... I dare you.
I don't disagree with you about the sound quality as such, because, as you say, if you're doing mainly rock, pop etc. then you wouldn't easily notice the difference, especially given that most people stream online these days anyhow . No, I was talking more from a workflow perspective. Most of the libraries I use are at 96 (it's recommended by most to use this sample rate no?) and it is just a pain to have to bounce everything down to 44 just so I can use one or two libraries and then re-convert or some such. Even if they don't think 96 is the best sample rate or whatever, they could still include it for people. I mean they do so for the reverb libraries so why not other things? Other developers think that 96 sounds better/optimum but still include the 44 versions too...
Everyone's experience is different, but I often use libraries that are of different sample-rates than the audio. And I have always had better quality just using the library than bouncing my tracks to fit the library, and then bounce back again. For the record, not all of the devs offer multiple sample rates for their libraries, and of those I use them anyway. Like I said, AITB have their reasons, and what they have is of awesome quality. I guess my real advice is to use whatever you want and don't stress out about sample-rates. Their 44 only libraries have been around for a while now, and it is not such a simple task to go back and magically make another sample-rate for us. So if it is work-flow you are concerned about, just don't change your work-flow; use whatever library you want and get things done!
From what I understood from those extensive plugin analysis/sample rate threads on Gearslutz is that the main advantage of using higher samplerates is the reduced aliasing. That's basically it, effects wise.
I usually work @ 44.1k with 96k effects (to save CPU power) and when rendering, I reload the project to 96 and switch on the timed kernels on the master.
I have to admit that the differences are barely noticeable, but sometimes 96k manages to sound more "real", especially on the long run.