View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000275ardourbugspublic2004-02-23 17:502008-11-20 23:44
ReporterFishB8 Assigned Topaul  
PrioritynormalSeveritycrashReproducibilityrandom
Status closedResolutionfixed 
Summary0000275: Pan/Gain automation curves have issues
Description1) When moving keys (proper termonology?) on Pan and Gain automation, all points behind or in front of the selected point are moved as well.

2) Curves for Pan and Gain are very unstable and can result in illogical curves causing Ardour to crash. (Point A -> Point B -> Point C, where Point C somehow becomes located between Point A and B causeing the automation curve to not follow the linear progression of time.)
TagsNo tags attached.

Activities

FishB8

2004-02-24 20:39

reporter   ~0000460

Ok, I figured out that the point will move without affecting others when CTL key is used. Wouldn't this be better the other way around though? Don't you want to move the keys independantly most of the time? Maybe it could be changed so that if you hold CTL while moving a key, all the keys behind it move, and holding ALT will make all keys in front of it move?

paul

2004-02-25 20:32

administrator   ~0000461

yes, we plan to switch the behaviour so that the ctrl-driven one becomes the default one.

its debatable which should be the norm, but from experience to date, this seems like the best decision. should happen very soon, maybe even before beta11.

also, could you provide some more details on how you managed to edit the curves into the state you described in the bug report?

FishB8

2004-02-25 20:51

reporter   ~0000464

If you screw with the automation curves long enough (with the intent of trying to get it to crash of course :), it showes up in a state like I mentioned.

I'm not sure if the state I described is actually what is happening, or if the automation curve is just being rendered incorrectly. I'll get a screen capture that shows what I'm talking about. Usually Ardour crashes soon after achieving this.

2004-02-25 21:02

 

ardour.png (6,909 bytes)   
ardour.png (6,909 bytes)   

FishB8

2004-02-25 21:04

reporter   ~0000465

uploaded ardour.png

This is just an quick example. I've had some that looked like a tangled mess.

paul

2004-06-16 12:49

administrator   ~0001042

please test this out again with 0.9beta16 - there were some clear and egregious bugs in the automation list code that have been fixed. things now work much, much better for me.

FishB8

2004-06-29 16:01

reporter   ~0001133

I've noticed that this is much much better in the latest betas. The only bug still outstanding as of beta 15 was bug 0000509. I can't see if test if that bug has been fixed as well in the latest beta as I am currently in Ireland.

tito

2004-06-29 23:45

reporter   ~0001146

Paul: Try touching automation while looping -- you'll get funny curves.
cvs 06/29/2004 Ardour/GTK 0.520.4 libardour 0.820.1

vandongen

2004-12-14 13:07

updater   ~0001724

Ardour/GTK 0.545.2 running with libardour 0.849.0
yes touching/writing while looping makes funny lines.
No crashes though
That should be a new mantis report, unless I manage to fix it before then :)

paul

2005-01-15 12:34

administrator   ~0001854

see bugnotes.

Issue History

Date Modified Username Field Change
2004-02-23 17:50 FishB8 New Issue
2004-02-24 20:39 FishB8 Note Added: 0000460
2004-02-25 20:32 paul Note Added: 0000461
2004-02-25 20:51 FishB8 Note Added: 0000464
2004-02-25 21:02 FishB8 File Added: ardour.png
2004-02-25 21:04 FishB8 Note Added: 0000465
2004-06-16 12:49 paul Note Added: 0001042
2004-06-16 12:49 paul Status new => feedback
2004-06-29 16:01 FishB8 Note Added: 0001133
2004-06-29 23:45 tito Note Added: 0001146
2004-12-14 13:07 vandongen Note Added: 0001724
2005-01-15 12:34 paul Status feedback => resolved
2005-01-15 12:34 paul Resolution open => fixed
2005-01-15 12:34 paul Assigned To => paul
2005-01-15 12:34 paul Note Added: 0001854
2008-11-20 23:44 seablade Status resolved => closed