View Issue Details

IDProjectCategoryView StatusLast Update
0002447ardourbugspublic2020-04-19 20:13
Reporterthorgal Assigned Toseablade  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product VersionSVN/2.0-ongoing 
Summary0002447: Autoplay screwed up
DescriptionClicking on different points of the transport bar does not trigger transport properly in Autoplay mode. It stops immediately after transport is supposed to roll on. After that, if you activate transport with the play button (which works fine), stopping then the transport triggers a very fast stop/start sequence but fortunately short (half a second or so). Autoplay is thus buggy.
Additional Informationsvn@4148
TagsNo tags attached.

Activities

thorgal

2008-11-15 18:44

reporter   ~0005230

well, in fact, the interaction GUI/transport is sort of screwed and behaves erratically.

thorgal

2008-11-16 13:32

reporter   ~0005231

things are fine again. No action was required ... weird ...

thorgal

2008-11-17 11:13

reporter   ~0005235

things are screwed up again. This is quite erratic. I wonder if there is any connection with the impossibility to create location or loop / range markers.

nowhiskey

2008-11-18 12:32

reporter   ~0005239

hey thorgal,
have you tried removing the ardour.bindings file, or the hole .ardour2 directory.
some weeks ago i had a lot of strange issues and removing the bindings file solved all of them.

cheers,
doc

thorgal

2008-11-18 15:37

reporter   ~0005240

I removed the dir. The problem is that I cannot reproduce this issue. I also installed the latest jackmp release (1.9.0) and my system has been ultra stable since then. I do mean stable, no glitch, no nothing at 1ms lat for 48 hours and tons of stuff running! Impressed I am :)

seablade

2008-11-24 09:33

manager   ~0005305

thorgal, have you been able to reproduce this at all(even erratically) since updating jack?

thorgal

2008-11-24 10:01

reporter   ~0005313

nope, it's just been working fine all the time since I updated jack. But I cannot say why it happened in the first place. Anyway, feel free to close this issue :)

seablade

2008-11-24 10:36

manager   ~0005320

Ok going to set the status to resolved for right now, if you have another problem post back up but ill fully close this out in a couple of weeks otherwise I think. I suspect the problem was related to Jack with the symptoms your reported myself.

    Seablade

system

2020-04-19 20:13

developer   ~0021818

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.

Issue History

Date Modified Username Field Change
2008-11-15 18:40 thorgal New Issue
2008-11-15 18:44 thorgal Note Added: 0005230
2008-11-16 13:32 thorgal Note Added: 0005231
2008-11-17 11:13 thorgal Note Added: 0005235
2008-11-18 12:32 nowhiskey Note Added: 0005239
2008-11-18 15:37 thorgal Note Added: 0005240
2008-11-24 09:33 seablade Note Added: 0005305
2008-11-24 09:33 seablade Status new => feedback
2008-11-24 10:01 thorgal Note Added: 0005313
2008-11-24 10:36 seablade cost => 0.00
2008-11-24 10:36 seablade Status feedback => resolved
2008-11-24 10:36 seablade Resolution open => no change required
2008-11-24 10:36 seablade Assigned To => seablade
2008-11-24 10:36 seablade Note Added: 0005320
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: 0021818
2020-04-19 20:13 system Status resolved => closed