View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006759 | ardour | bugs | public | 2016-02-01 08:36 | 2016-03-08 19:14 |
| Reporter | ototto | Assigned To | |||
| Priority | low | Severity | trivial | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Toshiba Satellite A200-10Z | OS | KXStudio | OS Version | 14.04.2 |
| Product Version | 4.4 | ||||
| Summary | 0006759: Fader automation edit from 0 to 1, not corresponding to value expressed in dB (Ardour 4.6) | ||||
| Description | In fader automation on a track. When double-click on the blue fader-bar and enter the value from the keyboard, you can enter any between 0.0 to 1.0. When 0.0, then the bar goes to -inf. dB. When 1, then the bar goes to 0 dB. When 0.5, then it's -6,02 dB etc. | ||||
| Tags | No tags attached. | ||||
|
|
Another example is calf eq's plugins. Levels for shelves is expressed from 0.015625 to 64, centered in 0. The values in dB ranges from -36.1 to 36.1. |
|
|
> When 0.0, then the bar goes to -inf. dB. > When 1, then the bar goes to 0 dB. > When 0.5, then it's -6,02 dB That is perfectly mathematically correct. For numeric entry or a spin-box: How would you go all the way down to minus infinity? Using the coefficient makes a lot more sense. As for calf, that smells like they shoehorned things for midi (127 steps), nothing we can do about. |
|
|
That is perfectly mathematically correct. For numeric entry or a spin-box: How would you go all the way down to minus infinity? Using the coefficient makes a lot more sense. Of course it's mathematically correct, but it seems odd to me that you need to calculate log10 in mind. As for -inf, what you say makes sense. As for any other value - it does not IMHO. Plus, to keep some order, editing the value of a single key point on automation curve should be done the same way. Lastly, I didn't even think it's made that way on purpose. Your decision :) O. |
|
|
In my opinion if Ardour itself shows a specific value in dB, then the user input should also be in dB's. Anything else causes confusion :) You can input dB values in audio track volume faders, but the audio track volume automation lane fader requires the user to input to be log10 values. By the way what do you input, if you want the automation volume fader to go to -12.75 dB. Its 0.230409309 :) |
