B
Bob's Mods
New member
Well, I recorded my first tune using the 96 kHz sample rate and I must admit, I was pleasantly surprised. I easily heard improved track to track definition and improved plug-in detail. At least with my rack, the improvement in playback was noticeble without any ear strain.
I've used 44.1 since the beginning of time and experimented with 48 kHz, which, sounded the same as 44.1 kHz. I've never been able record in 96 kHz previous as my gear topped out at 48 kHz. My sound card, a WaveTerminal 2496 circa 1990, is supposed to do 96 but it had problems at that rate. I think the clock has too much jitter at 96 kHz. Since I picked up a dbx Quantum, it does work at 96 k without a problem, so I was finally able to record at the higher rate.
I've read various posts of others attempts at, and use of, 96 kHz. Some guys love it for the reasons I've described. Others, didn't find much improvment and felt it wasn't worth the hard drive space and cpu time. I feel each person's experience may well vary as gear quality and user expertise is all over the map. For me anyway, it was one of the bigger jumps in record quality I have experienced.
The opinion of many is "Why record at 96 when human hearing tops out 20 kHz"? This is the common argument. My feeling is that we all have been viewing this in the wrong light, its not so much the wider bandwidth that brings out this improvement, its more bits in the recorded range! More bits mean greater math precision, more detail. The unfortunate downside is the wasted portion of the bandwith. When recording at 44.1 you are "grabbing" one audio sample every 22.7 microseconds. When recording at 96 you more than doubling your sample rate grabbing a sample every 10.4 microseconds. Now, when you record for one second at 44.1 kHz this means 44,100 samples are recorded in one second which translates into one sample every 22.7 uS. At 96 kHz, you are grabbing 96,000 samples every second. This translates into one sample every 10.4 uS. As most of us are using 24 bit converters these days, I will use that as my baseline. In one second, for one mono track, at 24 bits, you have a total possible bit count of 24 bits X 44,100 = 1,058,400 bits. A one second mono audio track at 96 k would be 24 bits X 96,000 = 2,304,000 total possible bit count. The bit count has more than doubled over that in the 44dot1 world. Hence, there more bits to perform more detailed math calculations. This is why cpu cycle time goes way up, more bits to work with, more calculations to do! Your processor is getting warm! (I am not sure if your plugins do math on that part of the bandwidth where there is no audio data, hopefully it only calculates the audio data it sees).
The focus has been on the "wasted hard disk space", well I got a 120 MB Seagate, so that ain't a problem here. And my plugin use? I don't use a lot and the ones I use are cpu misers. If you like to use cpu hog plugs in realtime you may have a problem at 96 kHz unless you have one of the newer more powerful machines. The focus also has been on why record a bandwidth of 96 k when we hear 20 k max? These are valid points against using 96 k. The reason for using 96 kHz, more samples per second "in band" which means finer resolution for mixing tracks and plugin calculations. You've got to take the good with the bad if your gear can cleanly handle recording at 96 kHz.
The pain factor is a little higher when recording at this rate too. Its not just a HD, CPU intensive problem. For me to record at this rate I have to turn off all VST plugins. Something I don't have to do at 44.1 or 48k. My system easily handles plugins being on in realtime when recording at 44.1 and 48 but it generates "spikes" in 96 if the plugins are running when recording so they all have to be off. There is also the down sample thing too. Cool Edit Pro handles that without a problem though. And yes, the improved clarity does translate when downsampled to 44.1. Some guys where saying this wasn't the case for them but in my case, the sonic "hit" caused by downsampling to the CD standard was miniscule at best.
If your gear supports it, and you don't mind the extra fuss (and waste) related to working at this lofty rate - and your gear produces the sought after benefits (mine did), you may find the results to your liking.
My conclusion is track to track definition is not simply just a mic/preamp issue, it is also related to sample rate. If you find your tracks are not standing out in the mix with the detail you would like, 96 k should help. The detail in your plugs and esp reverb is really cool too. I suspect, in ages yet to come, we will migrate to a 96 kHz world. I think DVD sound is there now?
Bob
I've used 44.1 since the beginning of time and experimented with 48 kHz, which, sounded the same as 44.1 kHz. I've never been able record in 96 kHz previous as my gear topped out at 48 kHz. My sound card, a WaveTerminal 2496 circa 1990, is supposed to do 96 but it had problems at that rate. I think the clock has too much jitter at 96 kHz. Since I picked up a dbx Quantum, it does work at 96 k without a problem, so I was finally able to record at the higher rate.
I've read various posts of others attempts at, and use of, 96 kHz. Some guys love it for the reasons I've described. Others, didn't find much improvment and felt it wasn't worth the hard drive space and cpu time. I feel each person's experience may well vary as gear quality and user expertise is all over the map. For me anyway, it was one of the bigger jumps in record quality I have experienced.
The opinion of many is "Why record at 96 when human hearing tops out 20 kHz"? This is the common argument. My feeling is that we all have been viewing this in the wrong light, its not so much the wider bandwidth that brings out this improvement, its more bits in the recorded range! More bits mean greater math precision, more detail. The unfortunate downside is the wasted portion of the bandwith. When recording at 44.1 you are "grabbing" one audio sample every 22.7 microseconds. When recording at 96 you more than doubling your sample rate grabbing a sample every 10.4 microseconds. Now, when you record for one second at 44.1 kHz this means 44,100 samples are recorded in one second which translates into one sample every 22.7 uS. At 96 kHz, you are grabbing 96,000 samples every second. This translates into one sample every 10.4 uS. As most of us are using 24 bit converters these days, I will use that as my baseline. In one second, for one mono track, at 24 bits, you have a total possible bit count of 24 bits X 44,100 = 1,058,400 bits. A one second mono audio track at 96 k would be 24 bits X 96,000 = 2,304,000 total possible bit count. The bit count has more than doubled over that in the 44dot1 world. Hence, there more bits to perform more detailed math calculations. This is why cpu cycle time goes way up, more bits to work with, more calculations to do! Your processor is getting warm! (I am not sure if your plugins do math on that part of the bandwidth where there is no audio data, hopefully it only calculates the audio data it sees).
The focus has been on the "wasted hard disk space", well I got a 120 MB Seagate, so that ain't a problem here. And my plugin use? I don't use a lot and the ones I use are cpu misers. If you like to use cpu hog plugs in realtime you may have a problem at 96 kHz unless you have one of the newer more powerful machines. The focus also has been on why record a bandwidth of 96 k when we hear 20 k max? These are valid points against using 96 k. The reason for using 96 kHz, more samples per second "in band" which means finer resolution for mixing tracks and plugin calculations. You've got to take the good with the bad if your gear can cleanly handle recording at 96 kHz.
The pain factor is a little higher when recording at this rate too. Its not just a HD, CPU intensive problem. For me to record at this rate I have to turn off all VST plugins. Something I don't have to do at 44.1 or 48k. My system easily handles plugins being on in realtime when recording at 44.1 and 48 but it generates "spikes" in 96 if the plugins are running when recording so they all have to be off. There is also the down sample thing too. Cool Edit Pro handles that without a problem though. And yes, the improved clarity does translate when downsampled to 44.1. Some guys where saying this wasn't the case for them but in my case, the sonic "hit" caused by downsampling to the CD standard was miniscule at best.
If your gear supports it, and you don't mind the extra fuss (and waste) related to working at this lofty rate - and your gear produces the sought after benefits (mine did), you may find the results to your liking.
My conclusion is track to track definition is not simply just a mic/preamp issue, it is also related to sample rate. If you find your tracks are not standing out in the mix with the detail you would like, 96 k should help. The detail in your plugs and esp reverb is really cool too. I suspect, in ages yet to come, we will migrate to a 96 kHz world. I think DVD sound is there now?
Bob
Last edited: