View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005549 | ardour | bugs | public | 2013-06-25 22:10 | 2013-06-27 22:46 |
| Reporter | dennismtaylor | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 3.0 | ||||
| Summary | 0005549: Playhead positioning interferes with JACK hardware monitoring | ||||
| Description | Ardour 3 -> Record monitoring handled by JACK Works as expected, until the playhead is positioned manually by (at least) the following means: - Clicking on the timeline or any of the rulers - Locating to session START or END via the transport buttons or keyboard - Using the Locations window or Regions & Marks list to jump to any location - Jumping to any mark via menus or keyboard - Shuttling backward or forward at any speed The following actions DO NOT cause this behavior: - Rolling the transport forward at normal speed, via the transport controls or keyboard, or by some other application via JACK - Stopping the transport, with or without auto-return enabled; auto-return will not trigger this condition. - Playing or looping a range via the transport controls, or by right-clicking a range or region and selecting "play..." or "loop.." - Loop recording with or without punch-in/out enabled - Right-clicking any marker and selecting "Play from marker" Settings that DO NOT affect this behavior in any way: - auto-input - global tape machine mode - track tape mode - internal/external positional sync - time master - global record-enable The condition seems to resolve itself after some number of minutes, unless and until the operator triggers it again. This is also resolved by disconnecting from JACK, restarting jackd, and reconnecting. Either way, the condition will be triggered again upon the next manual positioning of the playhead. I have not tested this with auto-play enabled, nor have I tested it by positioning the head manually via an external application. This is 100% reproducible with any build of Ardour 3. Ardour 2 does not exhibit this behavior. | ||||
| Additional Information | System: Dell XPS 420 OS: Ubuntu Studio 13.04 Ardour: All versions >= 3.0 Audio Hardware: (1) M-Audio Delta 1010LT | ||||
| Tags | No tags attached. | ||||
|
|
To clarify: The effect under these conditions is that the hardware monitoring state remains as it was before the triggering event. For instance, if an input was being monitored directly, it remains in this state until the condition is cleared. |
|
|
Additional info: Creating a new range by CTRL-dragging on any Range ruler DOES NOT trigger this condition. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-06-25 22:10 | dennismtaylor | New Issue | |
| 2013-06-25 22:48 | dennismtaylor | Note Added: 0015051 | |
| 2013-06-27 22:46 | dennismtaylor | Note Added: 0015061 |
