View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003964ardourbugspublic2011-04-11 06:312020-04-19 20:15
Reporterxherbie Assigned Tocth103  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003964: writing automation crashes ardour 3
DescriptionWriting automation (fader and pan automation) makes ardour3 crashing. The same behavior in touch mode. Sometimes the program crashes and sometimes the program slows down (program continues to run but the timer slows down ~ half the normal speed and no sound is played anymore).

I mad a 16track recording, everything works perfectly except the automation behavior which makes the final editing very troublesome. Workaround is to start playing the recording then switching to write modus in the track and before stopping the music switching to play modus. But the slow down and stop playing sound behavior persists even with the workaround.
TagsNo tags attached.

Activities

xherbie

2011-04-11 09:06

reporter   ~0010541

Starting in debug mode prints no messages. When loading the session or finishing the session the following message appears in the terminal:

programming error: SessionHandleRef exists across sesssion deletion! Dynamic type: ARDOUR::Crossfade

and

programming error: SessionHandleRef exists across sesssion deletion! Dynamic type: ARDOUR::AudioRegion

hope that helps

paul

2011-04-19 19:04

administrator   ~0010602

Those error messages are of no relevance at all to the reported issue.

cth103

2011-04-21 00:09

administrator   ~0010622

There are some fixes in this area in SVN 9389 (which will be in alpha5). Can you perhaps see if your problems still exist?

xherbie

2011-04-22 18:48

reporter   ~0010640

Behaves a little bit better. But I can produce a crash. Writing a Fader Automation on a track, saving the session and loading back the session und playing the automation makes a3 crashing. If I edit the ardour file an removing all events of the automation a3 is not crashing anymore. Seems to me that something is wrong when writing or interpreting the automation (events). I made a pastebin of the events that causes a3 to crash:

http://pastebin.com/bMf8yMTr

cth103

2011-04-22 22:59

administrator   ~0010641

Could you attach the .ardour file from the session that crashes on load?

2011-04-23 07:28

 

salsicDef01.ardour.01 (654,737 bytes)

xherbie

2011-04-23 07:29

reporter   ~0010649

File is attached. A3 is not crashing on load. It crashes when trying to play the automation line. Regards

xherbie

2011-04-23 07:38

reporter   ~0010650

Addendum: The error is in the automation list on beginning on line 3328.

cth103

2011-04-24 23:34

administrator   ~0010654

Are you using JACK 1?

xherbie

2011-04-25 06:23

reporter   ~0010655

Last edited: 2011-04-25 06:26

 jackd 0.120.2 standard package from ubuntu studio. I have an alesis firewire MultiMix16 Mixer. If helps you I can grant you access via teamviewer to my machine. Best regards Herbie

PS: Yesterday a3 was crashing again after writing a automation. I don't happens when I draw the gain curve by hand.

cth103

2011-04-25 19:45

administrator   ~0010656

I believe the crash on automation playback is due to a bug in JACK. This will be fixed in the next JACK release (it is fixed in JACK SVN).

Can you get a backtrace for the crash on writing?

xherbie

2011-04-25 20:50

reporter   ~0010659

I try to compile jack from svn and give you a feedback. Will take 1-2 days till I find enough time. What version do you suggest? jack1 jack2?

paul

2011-04-25 20:56

administrator   ~0010660

jack1, preferably.

xherbie

2011-05-05 20:48

reporter   ~0010697

the problem seems to be gone. I worked now about 5 hours on a project without a crash. I installed the latest jack from svn.

cth103

2011-05-05 22:13

administrator   ~0010698

Great, thanks for reporting back.

system

2020-04-19 20:15

developer   ~0022533

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
2011-04-11 06:31 xherbie New Issue
2011-04-11 09:06 xherbie Note Added: 0010541
2011-04-11 19:13 cth103 cost => 0.00
2011-04-11 19:13 cth103 Target Version => 3.0-beta1
2011-04-19 19:04 paul Note Added: 0010602
2011-04-21 00:09 cth103 Note Added: 0010622
2011-04-21 00:09 cth103 Status new => feedback
2011-04-22 18:48 xherbie Note Added: 0010640
2011-04-22 22:59 cth103 Note Added: 0010641
2011-04-23 07:28 xherbie File Added: salsicDef01.ardour.01
2011-04-23 07:29 xherbie Note Added: 0010649
2011-04-23 07:38 xherbie Note Added: 0010650
2011-04-23 15:31 cth103 Status feedback => confirmed
2011-04-24 23:34 cth103 Note Added: 0010654
2011-04-24 23:34 cth103 Status confirmed => feedback
2011-04-25 06:23 xherbie Note Added: 0010655
2011-04-25 06:26 xherbie Note Edited: 0010655
2011-04-25 19:45 cth103 Note Added: 0010656
2011-04-25 20:50 xherbie Note Added: 0010659
2011-04-25 20:56 paul Note Added: 0010660
2011-05-05 20:48 xherbie Note Added: 0010697
2011-05-05 22:13 cth103 Note Added: 0010698
2011-05-05 22:13 cth103 Status feedback => resolved
2011-05-05 22:13 cth103 Resolution open => fixed
2011-05-05 22:13 cth103 Assigned To => cth103
2020-04-19 20:15 system Note Added: 0022533
2020-04-19 20:15 system Status resolved => closed