View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008458 | ardour | features | public | 2020-10-26 21:34 | 2020-10-26 23:37 |
| Reporter | Reuben | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | GNU | OS | Linux | OS Version | (any) |
| Product Version | 6.3 | ||||
| Summary | 0008458: Allow option to use ISO 226:2003 profile in trim faders | ||||
| Description | Feature request for option to enable use the ISO 266:2003 contour profile when adjusting trim. The LSP "Loudness Compensation" plugin already provides this functionality, but it's a bit finicky to be adjusting trim in a plugin, even when exposing the output control level in the channel strip. If implemented, it would probably be best to be set on a per-channel-strip basis since FFT can get expensive. One alternative might be to make it possible to assign the trim fader control to one of the controls of a plugin in the channel strip instead of the default fader. This would allow binding the trim control to the output knob in the Loudness Compensation plugin, achieving the same result with the ability to use the same functionality for many other purposes as well. But then again there may be a good case for building in an ISO 266:2003 variant of the default channel fader. | ||||
| Tags | No tags attached. | ||||
|
|
Unlikely to happen. Ardour itself does not do any DSP except for simple lossless gain staging. All signal processing is done by plugins. The only option would be to create a plugin with tight integration. Also it sounds rather expensive. Ardour easily handles 1000 tracks, but realtime FFT likely won't scale. Then there's also the question which of the usefulness of loudness contours during mixing, but that is rendered moot. |
|
|
NB. LSP's Loudness Compensator also adds a significant amount of latency (~80ms). You definitely do not want this by default on every track. |
|
|
Yes, I'm aware of the DSP load and latency stuff, that's why I was thinking the alternative would make more sense of being able to bind the trim fader to a plugin control rather than the default channel-strip fader. |
|
|
The usefullness aspect for me is when I create a submix that sums to a bus, and then go back to the mix as a whole and pull that submix down stuff gets lost in the submix in ways that seem to be helped by using the Loudness Compensator to trim the submix bus rather than the regular fader. |
