It would be wonderful to specify an optimal volume level for each track—as a reference only, not to automatically adjust the volume—and have this displayed in the UI. This would allow listeners to manually set the volume to the previously determined optimal level as a track begins playing.
Optimal volume settings can vary significantly between tracks, so having a reference value would make it easier to achieve the intended listening experience, especially when not sitting in the ‘sweet spot,’ where volume perception can differ.
Previously, when using iTunes/Audirvana on a Mac, I would use the ‘beats per minute (BPM)’ field for this purpose. I’d listen to a track, decide on the ideal volume, and type that value into the BPM field. Although this wasn’t its intended use, it served nicely as a reference displayed in the track list. Without it, switching between tracks with very different optimal volumes could easily result in accidentally blasting the listener.
Currently, I work around this by recording track numbers and volume levels in a Google Sheet and splitting the screen on my iPad between Sense and the sheet. While functional, this is clunky, and a native solution would streamline the process considerably.
Optimal volume settings can vary significantly between tracks, so having a reference value would make it easier to achieve the intended listening experience, especially when not sitting in the ‘sweet spot,’ where volume perception can differ.
Previously, when using iTunes/Audirvana on a Mac, I would use the ‘beats per minute (BPM)’ field for this purpose. I’d listen to a track, decide on the ideal volume, and type that value into the BPM field. Although this wasn’t its intended use, it served nicely as a reference displayed in the track list. Without it, switching between tracks with very different optimal volumes could easily result in accidentally blasting the listener.
Currently, I work around this by recording track numbers and volume levels in a Google Sheet and splitting the screen on my iPad between Sense and the sheet. While functional, this is clunky, and a native solution would streamline the process considerably.