View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005010 | ardour | bugs | public | 2012-07-13 14:24 | 2020-04-19 20:16 |
| Reporter | idragosani | Assigned To | tom_ | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 beta4 | ||||
| Target Version | 3.0 | ||||
| Summary | 0005010: Rewinding (reverse) with Shuttle Controller widget to session start causes shuttle and playhead to get stuck | ||||
| Description | I hit this issue when testing a Zoom R8 as a mackie-compatible control surface. Hitting the rewind button to take the playhead back to session start caused the transport to become "stuck". Pressing Play or Fast Forward buttons would not move the playhead anymore (they had worked previously). The shuttle wheel on the device correctly moved the playhead forward or backward correctly, but pressing play would make the transport continue to rewind instead of going forward. I could not get Ardour to get back to a state where the transport was usable unless Ardour was restarted. Disconnecting and reconnecting the device had no effects on this, so it seemed that Ardour was getting into this state independent of the device. I disconnected the device and then tested the same thing using the shuttle controller widget (top left). If I used the widget to rewind back to the beginning of the session, it got stuck in the exact same manner -- the transport was no longer usable. If I manually moved the playhead to a location, that worked, but pressing Play made the transport go in reverse (as if the transport was stuck in 'reverse', this happened also using the surface controller). | ||||
| Tags | No tags attached. | ||||
|
|
I am on Ubuntu 12.04 LTS and have been having the same issue with Ardour 3.0 Beta 5. Use the shuttle to rewind to start head and I can't move it afterwards. |
|
|
i have about the same issue, also on ubuntu 12.04 (related to this issue?) how reproduce: -start fresh session -set varispeed to wheel mode, set speed for instance 110%, (roll) -locate back to start (start locator at position zero) -> ardour does not repsond on input -> terminal output is a loop of JackEngine::XRun: client = ardour was not run: state = 2 JackAudioDriver::ProcessGraphAsyncMaster: Process error |
|
|
this bug seems to be gone in recent git master/cc branch |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-07-13 14:24 | idragosani | New Issue | |
| 2012-07-14 18:28 | cth103 | cost | => 0.00 |
| 2012-07-14 18:28 | cth103 | Target Version | => 3.0 |
| 2012-11-09 21:42 | CameronNemo | Note Added: 0014200 | |
| 2012-11-09 21:42 | CameronNemo | Status | new => confirmed |
| 2013-02-13 18:21 | tom_ | Note Added: 0014646 | |
| 2014-04-15 20:41 | tom_ | Note Added: 0015743 | |
| 2014-04-15 20:41 | tom_ | Status | confirmed => resolved |
| 2014-04-15 20:41 | tom_ | Resolution | open => fixed |
| 2014-04-15 20:41 | tom_ | Assigned To | => tom_ |
| 2020-04-19 20:16 | system | Note Added: 0023117 | |
| 2020-04-19 20:16 | system | Status | resolved => closed |
