Crock. Upconverting a 24-bit file does not suddenly embue it with any greater fidelity.Strave said:Yes, Sonar 6 can bounce 64 bit files (I just did). You're stuck in the tracking frame of mind Fairview and you've forgot about 1. virtual instruments 2. 64 bit effects processing. Cakewalk prides itself in it's utilization of 64 bit summing, mixing and processing.
What convertors do you have? What OS?Strave said:Yes, Sonar 6 can bounce 64 bit files (I just did). You're stuck in the tracking frame of mind Fairview and you've forgot about 1. virtual instruments 2. 64 bit effects processing. Cakewalk prides itself in it's utilization of 64 bit summing, mixing and processing.
It it 64 bit floating point or fixed?Strave said:Yes, Sonar 6 can bounce 64 bit files (I just did). You're stuck in the tracking frame of mind Fairview and you've forgot about 1. virtual instruments 2. 64 bit effects processing. Cakewalk prides itself in it's utilization of 64 bit summing, mixing and processing.
If it is anything that was recorded through converters, you have 24 bit audio, not 32 bit. There is no such thing as 32 bit converters.DRUM said:Did system just convert 32 bit audio to 64 bit after mixing it?
brzilian said:I do not know if Sonar 5/6 employ a 64bit float audio engine, but if they did, it would not provide any significant benefit over a 32bit audio engine and be useless overkill.
We seem to be confusing wordlength of the audio file with the wordlength that your processor can handle. Having a larger audio wordlength would tax the cpu more. Having a 64 bit processor will give you more volume of data over time. We are talking about two different things here.Middleman said:You are so wrong. It allows many more multiple processes to be utlized during mixing. More plug ins, more synths less stuttering. Basically more volume of data over time. The 1s and 0s stay the same but the total volume of bits processed in a given time frame increases.
Middleman said:You are so wrong. It allows many more multiple processes to be utlized during mixing. More plug ins, more synths less stuttering. Basically more volume of data over time. The 1s and 0s stay the same but the total volume of bits processed in a given time frame increases.
You are talking about processor word length, we are all talking about audio file word length. Two different things, that's why you aren't making sense in this discussion.Middleman said:Terms? Such as?
solo.guitar said:Is there really any point in going above 24?
Middleman said:See from the Cakewalk site below.
"SONAR has set new standards for sound quality with the first, end-to-end, 64-bit double precision floating point mix engine. Every subtlety of your performance—from the decay of a fine acoustic guitar to the reverb tail of a cathedral—can now be clearly present in your mix.
SONAR achieves this unmatched level of audio quality by providing spacious amounts of headroom and footroom through extended dynamic range. You will also realize more definition in your mix through the improved summing and pristine digital signal path provided by 64-bit mixing.
SONAR’s unique mix engine maintains the 64-bit signal path from track to plug-in to bus, making it possible to retain absolute integrity of your audio throughout the production process, even when passing information to and from plug-ins.
Best of all—SONAR’s 64-bit mix engine is seamless and accessible even on 32-bit computers, so you can get the sound quality you deserve with the computer you already own.
SONAR 6 also features native support for 64-bit floating point audio files, allowing you to import, stream, and render tracks and mixes at the highest quality available in the industry."
Can you export a mix down to 64 bit files in Sonar? Yes.
Will it then play on your soundcard, no. They are meant to be production files for mixing and mastering in Sonar alone. They are designed to provide things like lower noise floor and higher headroom.