View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002542 | ardour | bugs | public | 2009-02-04 13:14 | 2020-04-19 20:13 |
| Reporter | wicked_boy | Assigned To | drobilla | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0002542: Transport does not locate from MIDI clock position | ||||
| Description | WHen scrolling through a sequence on an external sequencer the transport does not follow the position transmitted from the sequencer. It also does not start from the position when a continue message is given. Again I understand this may not be considered complete but thought it should be noted in case it wasn't known. | ||||
| Additional Information | SVN version 4488 | ||||
| Tags | No tags attached. | ||||
| Users sponsoring this issue | ||
| Sponsors List |
Total Sponsorship = US$ 15 2009-02-11 22:17: wicked_boy (US$ 15) |
|
|---|---|---|
|
|
Known issue since the beginning, did not get around to it, because there is higher priority work to do. Sponsorship may prompt me to rearrange my schedule. |
|
|
I committed a fix right now, can you test? |
|
|
This seems to follow perfectly. I have tried at Bar, beat and tick level and this follows the external sequencer exactly |
|
|
further testing shows this isn't quite the case. Ardour does actually drift from the position of the sequencer. The sequencer is in 2/4 time and ardour is in 4/4 but this shouldn't be of consequence. I will try this with a track that is 4/4 to try and rule this out as the issue. |
|
|
I've located the problem. Ardour drifts when the tempo in Ardour is different from the sequencer. This means 2 things with current behaviour. 1. All tempo mapping needs to be replicated across both systems (not ideal but better than nothing) 2. Clock drift on either system will result in drift between Ardours position and the external sequencer. The best behaviour would be for Ardour to take the tempo from the external sequencer (if this is at all possible). Otherwise simply ignoring the internal tempo and only reading position information from the external sequencer would be okay. cheers Allan |
|
|
The tempo or the meter? (If the meter is wrong, there is no way for ardour to know it, because MIDI Clock doesnt transmit the meter, it just transmits regular pulses and it is up to the slave to interpret it). |
|
|
I tried setting Ardour at 4/4 120 Bpm and then I can pull up the master at 400BpM and then pull it down to 40 BpM on running, and it would exactly sync to it again. But as far as the meter is concerned, there is just no way to do this. Because of limitations like that, MTC has been introduced. |
|
|
Sorry, My mistake the meter. I take it there is no possible fix for this then and the work is complete? |
|
|
No way for Ardour to know the meter. The protocol doesnt provide for that. If you need meter independent positioning you'll have to use MTC. |
|
|
actually .. my apologies again.. it's changing the tempo that is the issue.. I noticed the drift.. so to exaggerate it a track running at 138 bpm in the hardware i marked as 100 in ardour.. this seemed to cause issues with locating to the exact correct position.. I will try this again.. |
|
|
Yes, thats right, if the tempos dont match there is no way locating to work correctly. Whereas, If you start synchronously (eg. from start), Ardour should pull up the transport speed to be in sync with 138 BpM with no drift. (That works here( |
|
|
okay .. thanks.. yes that works the same here too.. if that's the situation with MIDI clock then I guess this work is complete... let me know your paypal account and we can close this one |
|
|
My paypal account is: hansfbaier@googlemail.com |
|
|
paid bounty .. will duplicate as a donation to the project in one month... |
|
|
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 |
|---|---|---|---|
| 2009-02-04 13:14 | wicked_boy | New Issue | |
| 2009-02-11 04:25 | hansfbaier | Note Added: 0005695 | |
| 2009-02-11 22:17 | wicked_boy | Sponsorship Added | wicked_boy: US$ 15 |
| 2009-02-11 22:17 | wicked_boy | Sponsorship Total | 0 => 15 |
| 2009-02-12 10:16 | hansfbaier | Note Added: 0005698 | |
| 2009-02-14 04:51 | wicked_boy | Note Added: 0005700 | |
| 2009-02-14 05:06 | wicked_boy | Note Added: 0005702 | |
| 2009-02-14 06:31 | wicked_boy | Note Added: 0005703 | |
| 2009-02-14 06:47 | hansfbaier | Note Added: 0005704 | |
| 2009-02-14 06:47 | hansfbaier | Note Added: 0005705 | |
| 2009-02-14 08:14 | wicked_boy | Note Added: 0005707 | |
| 2009-02-14 08:18 | hansfbaier | Note Added: 0005708 | |
| 2009-02-14 08:48 | wicked_boy | Note Added: 0005710 | |
| 2009-02-14 11:23 | hansfbaier | Note Added: 0005711 | |
| 2009-02-14 13:17 | wicked_boy | Note Added: 0005712 | |
| 2009-02-14 14:12 | hansfbaier | Note Added: 0005713 | |
| 2009-02-14 17:21 | wicked_boy | Note Added: 0005716 | |
| 2009-02-18 22:32 | drobilla | cost | => 0.00 |
| 2009-02-18 22:32 | drobilla | Status | new => resolved |
| 2009-02-18 22:32 | drobilla | Resolution | open => fixed |
| 2009-02-18 22:32 | drobilla | Assigned To | => drobilla |
| 2010-04-24 10:28 | cth103 | Category | bugs => bugs2 |
| 2010-04-24 10:32 | cth103 | Category | bugs2 => bugs |
| 2020-04-19 20:13 | system | Note Added: 0021860 | |
| 2020-04-19 20:13 | system | Status | resolved => closed |
