View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001165ardourbugspublic2005-12-13 10:112008-11-20 23:50
ReporterKat Manton Assigned Topaul  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version0.99 
Summary0001165: MMC misbehaviour
DescriptionI'm experimenting with ardour and an external MTC/SMPTE synchroniser and am finding some weird behaviour. I've tried to figure out what's going on and have logged midi data for these problems.

Ardour is set up to send MMC and synchronise to incoming MTC.

The synchroniser is set to 'swallow' MMC messages without returning them, and to generate and output SMPTE and MTC, feeding MTC back to ardour.

First off, 'stop' needs hitting twice before an MMC 'stop' message is sent. I'm also not sure what the purpose of the two 'locate' messages being sent at this time are.

'Additional Information'.contains a log of this.

That's the straightforward one out of the way.

Next, with the return connection made things get more weird.

Basically, I hit 'play' in ardour, whereupon ardour and syncroniser roll together very briefly then stop. If I hit 'play' repeatedly I can sometimes get it to start and keep running.

'Additional Information' contains a log from hitting 'play' once.

Hope this is of some help; if any more info or experimentation on my part is needed I'll see what I can do. I might take a peek at the source later as well; though I guess it'll take a while to find my way around something as large as this :)

Regards, Kat
Additional InformationEvent log for 'stop' misbehaviour:

Connections:
ardour 'seq' out to synchroniser in only
return connection not made in this case
monitor attached to ardour 'seq' out only (130:0)

Events:
Press 'play' in ardour - we get MMC 'play' and the syncroniser
starts rolling:

69913,130:0,System exclusive,,6,f0 7f 7f 06 03 f7

Press 'stop' in ardour - no data sent, synchroniser continues.

Press 'stop' again - we get a 'locate' then 'stop' then 'locate'

80348,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 00 00 f7
80348,130:0,System exclusive,,6,f0 7f 7f 06 01 f7
80348,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 00 00 f7


Event log for 'it all grinds to a standstill after a few frames' problem:

Connections:
ardour 'seq' out connected to synchroniser
syncroniser return connected to ardour 'seq' in
monitor attached to ardour 'seq' out (130:0) and synchroniser return (64:0)

Events:
Hit 'play' in ardour, we get an MMC 'start' message, the synchroniser responds a
nd starts returning MTC messages.

1632,130:0,System exclusive,,6,f0 7f 7f 06 03 f7
1671,64:0,MTC Quarter Frame,,0,
1675,64:0,MTC Quarter Frame,,16,
1680,64:0,MTC Quarter Frame,,32,
1685,64:0,MTC Quarter Frame,,48,
1690,64:0,MTC Quarter Frame,,64,
1694,64:0,MTC Quarter Frame,,80,
1699,64:0,MTC Quarter Frame,,96,
1704,64:0,MTC Quarter Frame,,114,
1709,64:0,MTC Quarter Frame,,2,
1714,64:0,MTC Quarter Frame,,16,
1718,64:0,MTC Quarter Frame,,32,
1723,64:0,MTC Quarter Frame,,48,
1728,64:0,MTC Quarter Frame,,64,
1733,64:0,MTC Quarter Frame,,80,
1738,64:0,MTC Quarter Frame,,96,
1742,64:0,MTC Quarter Frame,,114,
1747,64:0,MTC Quarter Frame,,4,
1752,64:0,MTC Quarter Frame,,16,
1757,64:0,MTC Quarter Frame,,32,
1762,64:0,MTC Quarter Frame,,48,
1766,64:0,MTC Quarter Frame,,64,
1771,64:0,MTC Quarter Frame,,80,
1776,64:0,MTC Quarter Frame,,96,
1781,64:0,MTC Quarter Frame,,114,
1786,64:0,MTC Quarter Frame,,6,

Then, at this point, without any user action, ardour spews out a bunch of MMC 'locate' and MMC 'stop' messages and it all grinds to a standstill.

1787,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 04 00 f7
1787,130:0,System exclusive,,6,f0 7f 7f 06 01 f7
1787,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 04 00 f7
1809,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 03 3c f7
1827,130:0,System exclusive,,6,f0 7f 7f 06 01 f7
1846,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 03 3c f7
1856,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 01 07 1e f7
1856,130:0,System exclusive,,6,f0 7f 7f 06 01 f7
1856,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 01 07 1e f7
1908,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 06 00 f7
1908,130:0,System exclusive,,6,f0 7f 7f 06 01 f7
1908,130:0,System exclusive,,13,f0 7f 7f 06 44 06 01 00 00 00 06 00 f7

TagsNo tags attached.

Activities

atreju

2006-11-07 19:05

updater   ~0002704

Is the issue still relevant with 2.0beta 7 ?
I remember having the same problems with an old 0.99, but I think it already worked well with 0.99.3

paul

2006-11-13 18:12

administrator   ~0002767

did you tell ardour to sync to MTC in the "it all grinds to a halt" scenario? that would be, uhm, very bad.

paul

2006-11-17 14:51

administrator   ~0002797

i have fixed the double locate message at transport stop.

paul

2006-12-20 21:08

administrator   ~0002944

scheduled to be marked resolved by end-of-2006 if no further feedback.

paul

2007-01-03 20:26

administrator   ~0002988

see notes for history.

Issue History

Date Modified Username Field Change
2005-12-13 10:11 Kat Manton New Issue
2005-12-13 10:11 Kat Manton E-mail => kat@technogoths.org.uk
2005-12-13 10:11 Kat Manton Name => Kat Manton
2006-11-07 19:05 atreju Note Added: 0002704
2006-11-13 18:12 paul Note Added: 0002767
2006-11-13 18:14 paul Status new => feedback
2006-11-17 14:51 paul Note Added: 0002797
2006-12-20 21:08 paul Note Added: 0002944
2007-01-03 20:26 paul Status feedback => resolved
2007-01-03 20:26 paul Resolution open => fixed
2007-01-03 20:26 paul Assigned To => paul
2007-01-03 20:26 paul Note Added: 0002988
2008-11-20 23:50 seablade Status resolved => closed