Standards and Conventions
From Audacity Wiki
Revision as of 14:01, 17 March 2020 by PeterSampson (talk | contribs) (→Amplitude Scale and Gain: conventionally we use the {{todo}} as a prefix rather than suffix)
Audacity aims to follow recognized standards and conventions whenever applicable. This includes the choice of terminology (see: Wording), Human interface guidelines, format specifications, and platform specific conventions. For various reasons, Audacity sometimes diverges from accepted norms. This page is for tracking known issues where Audacity contravenes accepted standards.
|
![]() |
Human Interface Guidelines
There are multiple "Human Interface Guidelines" (HIGs) for Desktop applications, and by and large they agree with each other:
|
Right Click Behavior
Reference: Microsoft HIG.
Date Logged: 16Mar20
Occurances of Non-Standard Behavior:
Amplitude Scale and Gain
Reference: Standard practice in audio software is to use dBFS for amplitude, and dB for gain.
Date Logged: 16Mar20
Description: Audacity is inconsistent in it's representation of amplitude, sometimes using dBFS (like the rest of the audio world) and sometimes using a linear scale of +/- 1. It is particularly confusing that Audacity's shipped generators use a linear scale of 0 to 1, and Audacity's shipped effects use dB.
Occurances of Non-Standard Behavior:
- Track vertical ruler in "Waveform" view
-
Chirp
-
DTMF Tones
-
Noise
-
Risset Drum
-
Tone