View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010449 | ardour | features | public | 2026-07-25 09:36 | 2026-07-25 09:36 |
| Reporter | GhostsonAcid | Assigned To | |||
| Priority | high | Severity | tweak | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | macOS | OS | Mojave | OS Version | 10.14.6 |
| Product Version | 9.7 | ||||
| Summary | 0010449: Ensure “gaincontrol”/"trimcontrol" (i.e. fader/trim) values are “1” and “0.5” for any “-0.0” and “-6” in-DAW values respectively | ||||
| Description | Although this is partially a bug, I suppose it's mostly a feature request to tweak how two specific fader (gaincontrol) values are set and used by Ardour. When doing fairly extensive ‘invert+sum’ testing for various mixing techniques that rely on the *perfect* inversion then summing of certain signals in order to cancel-out everything *except* whatever specific processing I’m trying to isolate, I uncovered some inconsistencies (and/or inconveniences) with how Ardour is calculating and saving its “gaincontrol” values (i.e. fader values) as shown in the XML. I devised a simple, quick test below to reproduce the behavior. In the XML, instead of the expected fader values of: value=“1” value="0.5" -You will often get values such as: value="0.99999994039535522" value="0.50118720531463623" -And this is partially dependent on what specific sequence of *actions* you take in the DAW. (-Again, follow the demo below.) In a nutshell, my request is that when setting a fader (or Trim knob) to exactly *-6dB*, the corresponding “gaincontrol” value should always = exactly “0.5”. And whenever (and *however*) any fader is explicitly set to “0” (or shows “-0.0”), that the corresponding “gaincontrol” value always = exactly “1”, not some approximation. If approximate values are used instead, then the result is that any use of an ‘invert+sum’ signal flow does NOT cancel-out completely, and instead leaves you with a fairly prominent audio ‘bleed’ into the rest of the mix. (-Pinpoint accuracy is key here.) Anyway, THANK YOU for considering this tweak/'fix'! : ) Cheers, -Joe | ||||
| Steps To Reproduce | 1. Create a test project (at 48kHz, or whatever). 2. Add 1 stereo Audio Track, and 1 stereo Audio Bus. 3. In the Track’s mixer strip, click on the fader value and type to change it to “-6”, hit Enter. 4. In the Bus’s mixer strip, click on the fader value and type to change it to “-15” (or whatever), hit Enter, *THEN use Shift+LMB* to ‘reset’ it to “-0.0”, supposedly. 5. Save the project. 6. Open the XML (.ardour file) in an XML-viewer, and search for the 3 instances of “gaincontrol”. 7. Observe how you will have something like “0.50118720531463623" and "0.99999994039535522" for the Track and Bus respectively. (Note: The latter, near-1 approximation only occurs with a use of Shift+LMB, as far as I can tell.) | ||||
| Additional Information | Note that this approximating behavior ALSO effects the *Trim knob*, saving a value for -6dB in the XML like: <Controllable name="trimcontrol" id="200" flags="GainLike" value="0.50118744373321533"/> | ||||
| Tags | fader, gaincontrol, trim knob | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-25 09:36 | GhostsonAcid | New Issue | |
| 2026-07-25 09:36 | GhostsonAcid | Tag Attached: fader | |
| 2026-07-25 09:36 | GhostsonAcid | Tag Attached: gaincontrol | |
| 2026-07-25 09:36 | GhostsonAcid | Tag Attached: trim knob |