View Issue Details

IDProjectCategoryView StatusLast Update
0003203ardourbugspublic2020-04-19 20:14
Reporterdanboid Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003203: MIDI automation mode drawing problems
DescriptionCreate a MIDI track along with a MIDI controller automation track. After having drawn some automation data, change the mode from 'linear' to 'discrete'. Under 7183 this will simply remove the lines leaving you with the primary nodes/ end points of the lines you drew, this isn't what I expected.

Now, resize the MIDI region using the 'Stretch/Shrink Regions' tool and you should notice that your automation curve has become 'fully discrete' and is displaying in the way I was expecting of discrete mode, with each line consisting of many points, not just two.

Now that you've done that though you should notice that if your cursor is within the auto. track in linear mode you will see the lines AND all the discrete nodes but in discrete mode you see all the points if your cursor is in the track but nothing at all if not.

Note that if you resize the MIDI region with 'Select/Move objects or ranges' instead this doesn't happen.
TagsNo tags attached.

Relationships

related to 0002514 closedcth103 [ERROR]: could not reconstitute MementoCommand from XMLNode 

Activities

danboid

2010-05-31 16:50

reporter   ~0008107

These problems are still in 7198 but I've been wondering about my

"After having drawn some automation data, change the mode from 'linear' to 'discrete'. Under 7183 this will simply remove the lines leaving you with the primary nodes/ end points of the lines you drew, this isn't what I expected."

For any given MIDI controller automation line of significant length in discrete mode, is it intended to be represented by 2 points or many?

danboid

2010-06-03 08:38

reporter   ~0008141

Last edited: 2010-06-03 08:41

Automation gets messed up in the same way as in post 0000001 (cannot revert to linear editing etc.) simply by saving and then re-opening a session. When opening a session with MIDI automation I get a load of errors like this:

[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106
[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106
[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106
[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106
[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106
[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106
[ERROR]: could not reconstitute MementoCommand from XMLNode. object type = ARDOUR::AutomationList id = 106

Present under 7217

danboid

2010-06-14 22:54

reporter   ~0008240

Last edited: 2010-06-14 22:59

A3 still breaks MIDI automation simply by drawing some, saving and reloading the session under 7255 and its breaking my MIDI-deprived heart- sob!

Its this bug and bugs related to http://tracker.ardour.org/view.php?id=2946 / http://tracker.ardour.org/view.php?id=3219 that scream "I'm not ready" the loudest for A3 as a MIDI sequencer now.

danboid

2010-06-21 07:03

reporter   ~0008294

This, our final big MIDI showstopper IMO, has actually got worse in 7282 since I last tried it as sometimes after a save and reload of a session I have NO MIDI automation data and the rest of the time the lines turn irreversibly to points as described above.

cth103

2010-07-12 00:47

administrator   ~0008420

I think there are a couple of problems here:

1. MidiSources can't store whether or not a particular automation control should be in discrete or linear mode, so operations like stretch (which make new sources and build up a new MidiModel from them) can't preserve this state.

2. Editing midi automation causes AutomationList-related events to end up in the undo history, whereas I think undo should happen at the MIDI event level.

danboid

2010-07-12 16:23

reporter   ~0008424

I'm happy to see some progress being made with this issue - soon as this is fixed I can start more rigorous testing of MIDI.

cth103

2010-07-14 00:58

administrator   ~0008426

The linear/discrete issues should be fixed in SVN 7409. Undo is still broken; it just means that you can't undo changes to MIDI automation (and you'll get errors on session load as you describe).

cth103

2010-07-14 12:27

administrator   ~0008430

The undo should now be fixed as well. Are there any parts of this report that remain a problem?

danboid

2010-07-14 13:02

reporter   ~0008431

Hi cth103!

I've not tested the undo yet but I never mentioned that in this mess of a bug report anyway but its certainly good to know that should be working now too.

I gave MIDI automation a quick test earlier and it seems to be working fine now (big relief!) so if I do find any more issues with it I'll file them anew in a more clear and concise report.

Big thanks C!

cth103

2010-07-14 14:22

administrator   ~0008432

OK, thanks, I'll close this.

system

2020-04-19 20:14

developer   ~0022107

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
2010-05-28 11:48 danboid New Issue
2010-05-31 16:50 danboid Note Added: 0008107
2010-06-03 08:38 danboid Note Added: 0008141
2010-06-03 08:39 danboid Note Edited: 0008141
2010-06-03 08:41 danboid Note Edited: 0008141
2010-06-05 15:48 cth103 Relationship added related to 0002514
2010-06-08 22:19 cth103 cost => 0.00
2010-06-08 22:19 cth103 Target Version => 3.0-beta1
2010-06-14 22:54 danboid Note Added: 0008240
2010-06-14 22:59 danboid Note Edited: 0008240
2010-06-21 07:03 danboid Note Added: 0008294
2010-07-12 00:47 cth103 Note Added: 0008420
2010-07-12 00:47 cth103 Status new => confirmed
2010-07-12 16:23 danboid Note Added: 0008424
2010-07-14 00:58 cth103 Note Added: 0008426
2010-07-14 12:27 cth103 Note Added: 0008430
2010-07-14 12:27 cth103 Status confirmed => feedback
2010-07-14 13:02 danboid Note Added: 0008431
2010-07-14 14:22 cth103 Note Added: 0008432
2010-07-14 14:22 cth103 Status feedback => resolved
2010-07-14 14:22 cth103 Resolution open => fixed
2010-07-14 14:22 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0022107
2020-04-19 20:14 system Status resolved => closed