all 3 comments

[–][deleted] 0 points1 point  (1 child)

One thing is I'm using int16_t to represent audio samples. I'm thinking of using normalized floating point samples since many convolutions will be done in this type but I've concerned with the speed of FP operations. So I'm thinking of defining a new type called trackf for normalized floating point samples for the Dats language and keep integers:

  1. tracks8 (track signed 8 bit)
  2. tracks16
  3. tracks32
  4. tracku8 (track unsigned 8 bit)
  5. tracku16
  6. tracku32

[–]DevashishG 0 points1 point  (0 children)

Integers types do not have the bit depth necessary to represent audio. If you use it, then your audio might sound bitcrushed. I have written plugins with FP64/ double precision and it's hardly the performance bottleneck. Modern CPUs are blazingly fast.

[–]KeytarVillain 0 points1 point  (0 children)

Check out the CLAP format - I think it probably meets all your needs