That's so dumb. Everyone knows that string.h functions produce the best sound you can get, and you should prefer `calloc' so you get clean sound.
Ideally you want to write your audio rendering code in asm, too, since newer C compilers add a lot of junk to binaries that reduce the quality of the output. If you can't do this, simply use older compilers.
But if you're going to write in C, I suggest Cosmopolitan Libc and running directly from BIOS since operating systems end up doing a lot of work that produces electrical noise on your hardware.
You're better off running literally only audio rendering code for the best quality rendition.
But if you're writing in C, couldn't there be transposition issues? Like what if the music was written in a different key? Do you have to use different versions of the code written in C# or F depending on the key the input audio was recorded?
As a wood wind player primarily in B-flat, I've just taken it as norm to take the C programs and slow them down slightly. My E-flat stuff just never has sounded right speeding up the C programs. I'll have to try the D programs to see if it'll sound closer since it won't need as much pitch correction.
Ideally you want to write your audio rendering code in asm, too, since newer C compilers add a lot of junk to binaries that reduce the quality of the output. If you can't do this, simply use older compilers.
But if you're going to write in C, I suggest Cosmopolitan Libc and running directly from BIOS since operating systems end up doing a lot of work that produces electrical noise on your hardware.
You're better off running literally only audio rendering code for the best quality rendition.
/s