DAW development stopped ?

[enroe]

... It's simple math, let's not try to complicate things with your need to disprove anything here.

... which you still don't understand - and so you
are an easy prey for all marketing preachers and pied
pipers.

[Delta Sign]

My music sucks because I'm mixing in 32bit, it's not my fault.

[enroe]

My music sucks because I'm mixing in 32bit, it's not my fault.

[enroe]

To underline the phenomenon of the 64-bit fp marketing gag
again, here is the statement from FabFilter:

We have done extensive experiments with 64-bit processing and we concluded that it is just not necessary to use it as an audio format. You do need it internally in a plug-in for some types of processing. You don't need it when scaling the gain, or adding channels, which is exactly what the mixer in a host application does.

Keep in mind that the floating-point format is very different from a fixed-point format. It's true that you get no more than 23-24 bits of precision, which gives you a dynamic range of around 140 dB. (We never claim to have 32 bits of precision by the way.)

That means that when your audio is at the 0 dB level, the tiniest detail that can be represented at the same time is at -140 dB, way beyond the threshold of human hearing which is around -90 dB at its best. But it gets even better, because when the overall volume gets lower, the precision scales with it so the precision actually increases.

With a fixed-point 16-bit format like a CD, you can force quantization noise during low-volume sections of a song (mostly with classical music which has a higher dynamic range), if you increase the volume enough so that loud sections will be far too loud. With floating-point, that doesn't happen because during soft sections, the precision increases and you don't get quantization noise.

Why does Cubase offer 64-bit processing? Because they can, and because people are asking for it.

It is overkill, and we don't support it because we would need to have an entire separate chain of audio components for 64-bit audio in our plug-ins which would significantly increase our development, testing and support load. And we are convinced that you wouldn't hear the difference.

Cheers,

Frederik (FabFilter) — Dec 14, 2020

[chk071]

I like it when devs talk straight.

[Teksonik]

Yep they're being honest....."we don't support it because we would need to have an entire separate chain of audio components for 64-bit audio in our plug-ins which would significantly increase our development, testing and support load".

I just found that part humorous. I don't have a dog in this race and don't wish to argue 32 v 64 processing at least not enough to bump a three year old thread.....(which I just did anyway )

[dupont]

Logic added live loops a couple of years ago
bitwig for modulation
live nothing exiting, 5 years to update from 10 to 11
Reaper constantly updating sometimes with useless features for my needs but at least it is alive

Obviously as with other products there comes a time when innovation slows down until next generation... For example Apple switch Intell for silicon CPU.

[PieBerger]

live nothing exiting, 5 years to update from 10 to 11

3 years actually

[Harry_HH]

I expand this to the general music software dev.

Few years ago a lot of discussion and promiseses in implementing the AI and machine learning in music software.

Some good results we have seen, or should I say promising signals, e.g. some iZotope stuff (I must say I’m most impressed by the latest RX ”AI”).

But so far we are mainly waiting in reclaiming these promises. Lets see, (e.g.), what the Atlas 2 brings on the table. The version until 1.4 ver. were huge disappointing.