View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008327 | ardour | bugs | public | 2020-07-22 20:00 | 2020-07-22 22:50 |
| Reporter | mc888 | Assigned To | x42 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | Debian GNU | OS | Linux | OS Version | (any) |
| Product Version | 6.2 | ||||
| Summary | 0008327: input meters dead | ||||
| Description | Ardour 6.2 input meters work when track 'Input' is selected but are dead when 'Disk' is selected. Audio plays back fine from disk, but meters don't register any signal. Have not seen this in Mixbus 6.1.1. Just Ardour 6.2. | ||||
| Steps To Reproduce | select disk playback and start transport | ||||
| Tags | meter | ||||
|
|
What is the meter-point set to? |
|
|
It's set to "In". Thought that was clear. The only way I can see input level from disk playback is deactivate all plugins and look at "Pre". |
|
|
Meter-point "Input" shows the raw data on the input connector (signals coming in from the outside as-is). This is unrelated to the monitor-mode "In" vs "Disk". To see unprocessed levels during playback, you can use a custom meter point at the top, before other processors. |
|
|
Well this is the first time I've ever seen it act this way. Previous versions always showed the channel input level regardless of source. Is this related to allowing multiple inputs to a channel? |
|
|
It's always been like this, as far back as Ardour 2.0 (give or take a bug). Input meter signal is tapped off prior to disk-playback. |
|
|
Really now. I've been using Ardour since 3.x, Ardour 5.12, Mixbus 5 and 6, never seen this meter behavior before 6.2. Input meter point always showed raw track disk playback level. Or source level of live input, whichever was selected for track input. If that was a bug, it sure took a long time to fix. |
|
|
Yes, it was a bug, and yes it took a long time to fix. How could it ever be a bug for the "Input" meter point to always meter the input signal? You've explicitly said "I want to meter the input signal". Older versions would not do this, which was an error. It got fixed as part of the development of 6.0, in which disk read and disk write were separated. |
|
|
It is true that these options allow you to select a monitoring option and a metering option that are not "aligned" (monitoring == disk, metering == input) You may not that flexibility, and that's not an invalid position. But the program has always offered this flexibility and it now works correctly: if you ask to meter the input, that's what it does. |
|
|
Ok, that makes sense. Thanks for taking the time to explain it. |
|
|
changed by design |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-07-22 20:00 | mc888 | New Issue | |
| 2020-07-22 20:00 | mc888 | Tag Attached: meter | |
| 2020-07-22 20:14 | x42 | Note Added: 0024783 | |
| 2020-07-22 20:16 | x42 | Assigned To | => x42 |
| 2020-07-22 20:16 | x42 | Status | new => feedback |
| 2020-07-22 20:29 | mc888 | Note Added: 0024784 | |
| 2020-07-22 20:29 | mc888 | Status | feedback => assigned |
| 2020-07-22 20:47 | x42 | Note Added: 0024785 | |
| 2020-07-22 20:57 | mc888 | Note Added: 0024786 | |
| 2020-07-22 21:12 | x42 | Note Added: 0024787 | |
| 2020-07-22 21:13 | x42 | Note Edited: 0024787 | |
| 2020-07-22 21:25 | mc888 | Note Added: 0024788 | |
| 2020-07-22 21:54 | paul | Note Added: 0024789 | |
| 2020-07-22 21:57 | paul | Note Added: 0024790 | |
| 2020-07-22 22:49 | mc888 | Note Added: 0024791 | |
| 2020-07-22 22:50 | mc888 | Status | assigned => closed |
| 2020-07-22 22:50 | mc888 | Resolution | open => no change required |
| 2020-07-22 22:50 | mc888 | Note Added: 0024792 |
