View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007894 | ardour | bugs | public | 2020-02-02 20:34 | 2020-04-29 23:47 |
| Reporter | lack | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | Ubuntu | OS Version | 19.10 |
| Product Version | 5.12 | ||||
| Summary | 0007894: Latency Measurement Tool should allow me to proceed even with inverted wiring | ||||
| Description | I have Soundcraft Notepad-12FX external mixer with USB IO. When I attempted to automatically measure the latency, I connected the USB to the AUX bus and hardwired it to the input 0000001, selected the right ALSA audio equivalents in Ardour, and started the measurement. As I adjusted the mixer levels I immediately got reasonable-looking results, but with it ended with: "Systemic latency: 593 samples (13.447ms) (inverted - bad wiring)" At this point the latency was measured, but I couldn't proceed - The "Use results" button was grayed-out. After an adventure using two stereo cables and some alligator clips to fix the inversion, the final latency measurement was identical to the one when I hard-wired with the inversion. I think I should have been allowed to proceed to use the originally-detected values, even though the signal was inverted. I think the warning about the inversion is useful, but shouldn't be blocking since the main point of the tool (measuring latency) doesn't seem to depend on the inversion. Maybe if I click "Use results" with a detected signal inversion, there should be a small popup dialog warning me about why this signal inversion is important (I'm actually not sure why it matters - Everything this hardware does sounds correct to my ears), but let me proceed anyway after confirming I have read the warning. | ||||
| Steps To Reproduce | Measure latency with an inverted signal path. | ||||
| Tags | No tags attached. | ||||
|
|
Is the reported number realistic? It's usually a result of an invalid measurement, crosstalk, and not simply a polarity inversion. |
|
|
I have the exact same issue with a Soundcraft Signature 12MTK Mixer. Using the "hacked" cable trick worked. As user lack I suggest not greying out the "use results" button for this specific issue. |
|
|
I have the same problem with my device (Berhinger FCA1616). Inputs's polarity is inverted. But why are they ? This is not documented in the manual of the device. |
