How can a DAW call "processDoubleReplacing()" ?

[Jeff McClintock]

32 bit floats sound warmer.

Sean Costello

Only through oxygen free copper cables.

I'm writting a 64-bit plugin that accuratly reproduces the distintive warmth of that (soon to be) vintage 32-bit sound.

[duncanparsons]

well, stop dithering & get it released!

[Tzarls]

32 bit floats sound warmer.

Sean Costello

Only through oxygen free copper cables.

Well, it all depends on the hard drive you're using to store your tracks and/or plugins... external hard drives sound cold and sterile, IMHO.

[AdmiralQuality]

well, stop dithering & get it released!

You should only use dithering when mixing to 128 bit.

[sinosoidal]

Trying to make Ableton Live call processDoubleReplacing but it never gets called. I have called canDoubleReplacing() in the constructor as well as setProcessingPrecision but nothing. It works in Reaper though.

Does anyone has a clue? Thanks!

[BertKoor]

Does anyone has a clue? Thanks!

Yeah, hints are on page 1 of this thread, the first few replies are still correct after a decade.

[sinosoidal]

Does anyone has a clue? Thanks!

Yeah, hints are on page 1 of this thread, the first few replies are still correct after a decade.

Yeah, I have seen those. I wonder why Ableton Live does not process at 64 bit then when Reaper does. Does anyone knows if Ableton Live is still processing a VST plugins at 32 bit only in 2023?

[FigBug]

Does anyone has a clue? Thanks!

Yeah, hints are on page 1 of this thread, the first few replies are still correct after a decade.

Yeah, I have seen those. I wonder why Ableton Live does not process at 64 bit then when Reaper does. Does anyone knows if Ableton Live is still processing a VST plugins at 32 bit only in 2023?

According to the fact sheet on their website, most of the audio engine is still 32 bit.

https://www.ableton.com/en/manual/audio-fact-sheet/

Please note that, while 64-bit summing is applied to each single mix point, Live‘s internal processing is still done at 32-bit. Thus, signals that are mixed across multiple summing points may still result in an extremely small amount of signal degradation. This combination of 64-bit summing within a 32-bit architecture strikes an ideal balance between audio quality and CPU/memory consumption.

[mystran]

Yeah, I have seen those. I wonder why Ableton Live does not process at 64 bit then when Reaper does. Does anyone knows if Ableton Live is still processing a VST plugins at 32 bit only in 2023?

Perhaps Live is processing (or at least moving around) signals in single-precision internally. If this is the case, then even if the plugin supports 64-bits, how should Live know that this is automatically better? Perhaps the plugin works just as well in singles? Perhaps it exposes a double precision interface, but converts internally to singles anyway. Perhaps it converts single precision to doubles internally too, but does it really matter if it's the host or the plugin doing the conversion?

The plugin knows whether singles vs. doubles matters and the plugin knows what it prefers to do internally. Perhaps it matters for the plugin, perhaps it doesn't. When you think about it this way, it makes a whole lot of sense for the host to always prefer whatever format it already has and only ever bother converting if it needs to.

As far as simply transporting signals around, double-precision serves no purpose other than avoiding pointless conversions if both sides want to process in doubles.

[mystran]

Please note that, while 64-bit summing is applied to each single mix point, Live‘s internal processing is still done at 32-bit. Thus, signals that are mixed across multiple summing points may still result in an extremely small amount of signal degradation. This combination of 64-bit summing within a 32-bit architecture strikes an ideal balance between audio quality and CPU/memory consumption.

This is ridiculous btw.. summing alone doesn't benefit from double precision at all.