🚀 go-pugleaf

      BTW, you don't have to normalize to get a better wave display. You can
      simply rebuild the wave display under settings. You can also reduce the
      number of samples per block in the peak settings to a more granular
      initial display.





That doesn't begin to fix the floating point issue - you can have a legitimate floating point file at +350dB that will look like a solid block of green whatever you do, because Audition's scaling stops at 0dB. The only way to see this file correctly, since the scale display is also integer-based with a fixed upper limit, is to normalise it.

      It's supposed build pk files but it doesn't. In fact just this morning
      it failed to build them on several 16 bit and 32 bit files. This is happening
      on 3 different machines.




And these are definitely Windows PCM wav files? I've never experienced that on any machine - and this runs into the 10's of them in several installations. If pk files are requested, then under the correct conditions, they are created.

      Also, the 24 bit files are opened as 32 so it should build them there
      to.




.pk files are only created when the waveform is stored in the correct format, not just opened in it. The pk information from the display is generated in memory at opening time, and modified if editing takes place. And if the final result isn't stored in an internal working format, no .pk file will be generated at all.