It may be true that there is no sound format for many of these, but come on, it's not that much of a stretch to add support for them in the aup format and the Audacity RAM format.

Photosounder uses these already.īump! please add native 8-bit PCM, micro-law/mu-law/u-law/µ-law/μ-law, A-law, 16-bit float (middle ground between μ-law and 32-bit float), 32-bit PCM, 64-bit PCM, 64-bit float, 7-bit PCM, 6-bit PCM, 5-bit PCM, 4-bit PCM, 3-bit PCM, 2-bit PCM, 1-bit PCM, 9-bit PCM, 10-bit PCM, 11-bit PCM, 12-bit PCM, 13-bit PCM, 14-bit PCM, 15-bit PCM, 17-bit PCM, 18-bit PCM, 19-bit PCM, 20-bit PCM, 21-bit PCM, 22-bit PCM, 23-bit PCM, 24-bit PCM, 25-bit PCM, 26-bit PCM, 27-bit PCM, 28-bit PCM, 29-bit PCM, 30-bit PCM, 31-bit PCM, custom 12-bit (user can pick what the 4096 sample values are), custom 11-bit (user can pick what the 2048 sample values are), custom 10-bit (user can pick what the 1024 sample values are), custom 9-bit (user can pick what the 512 sample values are), custom 8-bit (user can pick what the 256 sample values are), custom 7-bit (user can pick what the 128 sample values are), custom 6-bit (user can pick what the 64 sample values are), custom 5-bit (user can pick what the 32 sample values are), custom 4-bit (user can pick what the 16 sample values are), custom 3-bit (user can pick what the 8 sample values are), custom 2-bit (user can pick what the 4 sample values are), custom 1-bit (user can pick what the 2 sample values are), IMA ADPCM, Microsoft ADPCM, GSM 6.10 and all the ADPCMs from the Internet, such as this one: this one: this one: and so on - and also adapt them to μ-law. A step solution is much less likely to completely fail. Step 11: realize that these steps make it easier for many people. Step 10: allow more algorithms, like band-pass filter and envelope detection (this allows for customizable time-frequency resolution for different frequencies) Step 9: use some filtering on frequency instead of nearest neighbor filtering. Step 8: make bass quieter to compensate for bass magnifying. Step 5: automatically normalize spectrograms. keep certain resolution images of spectrograms in memory for view before loading pixel resolution Step 4: don't temporarily crash when loading spectrograms, instead allow user to use it. Step 3: use higher default window size, to reduce confusion This is what it will look like after these steps: Step 1: make volume scale linear (please this!). If you think there is no problem with current system, explain the dB marks on the gain thingies. Normalizing spectrograms is a way to properly show volumes above 1 in spectrograms. Audacity miserably fails with trying to make quietest sounds visible, and ending up with horrible contrast. Unlike logarithmic volume scale, linear volume scale has its minimum, just like brightness, so linear volume scale is accurate. Scale can be varied by gradient.png file. In white noise, bass is correctly darker (quieter) because bass is more magnified in logarithmic than linear (I mean the frequency scale logarithmic/linear this time, not the other logarithmic/linears). It uses a gamma-corrected linear volume scale, and it always normalizes spectrograms.

Photosounder 64 bit