Tone Deft wrote:it's 64 bit summing, not across the board 64 bit processing.
Tone Deft wrote:re: summing... it's the parts of Live where two or more signals are mixed together, they're done with 64 bit precision rather than 32 bits, so the rounding errors are lower.
Could you explain please, how summing two 32-bit numbers gains additional 64 bit precision (less rounding errors)?
Simplified example of how I understand things:
32-bit precision output: 1.23
64-bit precision output: 1.23456789
32-bit precision outputs to 64-bit sum:
1.23 > 1.23000000
64-bit sum from 32-bit outputs:
1.23000000 + 1.23000000 = 2.46000000 = 2.46
(constructed) usage scenario of a more precise 64-bit sum while only 32-bit processing is used:
32-bit: 1.23 - 0.22 Fader Gain
= 1.01 - 0.01 Fader Gain = 1.00
64-bit: 1.23000000 - 0.22441234 Fader Gain = 1.00558766 - 0.00050000 Fader Gain = 1.00508766 ~ 1.01
So the my conclusion is: As long as processing takes place in 32-bit the 64-bit summing is nearly useless. It's a marketing gag that conceils that Ableton didn't deliver the real-deal. Does it matter? No, because there are other things happening in Live, like phase shifting, that are far more detrimental to Audio Quality!
Sonar and Reaper come with 64-bit processing all way through, which is a different story. Since in processing there is a whole lot more calculations being done than in simple summing the higher precision promises at least some benefits. The more processing/number crunching happens the higher the benefits. And only once you sum tracks that use 64-bit processing themselves there will be an advantage in using a 64-bit sum.