View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001768 | ardour | bugs | public | 2007-07-14 14:53 | 2010-10-17 12:48 |
| Reporter | oofus | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Centrino 1.6GHz Laptop | OS | Linux | OS Version | Mandriva 2007 |
| Product Version | 2.0 | ||||
| Target Version | 3.0-beta1 | ||||
| Summary | 0001768: When chasing MTC and the transport is in play and record, when the MTC stops the transport doesn't go back to stop | ||||
| Description | When chasing MTC and the transport is in play and record, when the MTC stops the transport doesn't go back to stop. Currently when Ardour receives MTC the transport changes to play and then back to stop when the MTC goes away. The same isn't true of play and record when MTC goes away. | ||||
| Steps To Reproduce | Select MTC from the internal, MTC, Jack drop down menu. Send MTC to Ardour. The transport changes from stop to play. Stop the external MTC. The transport changes from play to stop. Send MTC to Ardour. The transport changes from stop to play. press the rec button. The transport changes to show play and record. Stop the external MTC. The main clock stops but the transport remains the same ie play and record illuminated. It should change back to stop, but still observing the "Rec-enable stays engaged at stop" setting in the options menu. | ||||
| Tags | MTC | ||||
|
|
The difference between the play and record cases is: When playing, the Session::locate() that occurs on stop schedules a declick; when recording, this doesn't happen. This means that when Session::set_transport_speed() calls Session::stop_transport(), in the recording case this schedules a declick. However for some reason, Session::check_declick_out() is then never called, so the declick never happens, and stop_transport is never called again, so Session::realtime_stop() never happens. |
|
|
Thinking about it, maybe staying in record if MTC goes away is a good thing, MTC might have gone away by accident and you really want to keep recording. If this happens when just in play then the transport stops which is probably correct. This could be made more configurable with options to define what happens when chasing and timecode varispeeds or stops, but this is probably better left to a new feature request. |
|
|
see notes |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-07-14 14:53 | oofus | New Issue | |
| 2010-05-02 18:51 | cth103 | Tag Attached: MTC | |
| 2010-07-22 15:44 | oofus | Target Version | => 3.0-beta1 |
| 2010-10-02 00:34 | cth103 | Status | new => confirmed |
| 2010-10-02 01:26 | cth103 | Note Added: 0009206 | |
| 2010-10-17 12:48 | oofus | Note Added: 0009245 | |
| 2010-10-17 12:48 | oofus | cost | => 0.00 |
| 2010-10-17 12:48 | oofus | Note Added: 0009246 | |
| 2010-10-17 12:48 | oofus | Status | confirmed => closed |
| 2010-10-17 12:48 | oofus | Resolution | open => fixed |
