View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010196 | ardour | bugs | public | 2026-02-20 18:46 | 2026-02-20 18:50 |
| Reporter | bzub | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Arch | OS | Linux | OS Version | (any) |
| Product Version | 9.0 | ||||
| Summary | 0010196: Novation cue integration gets confused with non-cue tracks | ||||
| Description | When non-cue visible tracks exist at the beginning of the session, using DAW integration for cues gets confusing on Novation Launchpad Pro and LaunchKey, in my testing. What I see is that pressing a pad to trigger a cue slot triggers pad LED feedback for a different column of pads. Let's say there's one non-cue track at the top of Ardour, and a few cue tracks after it. When I hit the pad for the cue track it tends to work, but then the LED response on the pads suggest I hit the next pad after it instead of the one I hit. This suggests it is counting the non-cue track when it calculates how to give feedback to the MIDI/DAW controller. | ||||
| Steps To Reproduce | 1. Create a session with a few tracks, one at the top that's not included in the cue interface. 2. Add clips. 3. Use the midi controller DAW/cue integration. | ||||
| Tags | cue | ||||
