View Issue Details

IDProjectCategoryView StatusLast Update
0003720ardourbugspublic2020-04-19 20:15
Reporterlincoln Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Summary0003720: Audio regions are locked when in note mode
DescriptionWhen the editor is in note mode, audio regions cannot be moved. Note mode should only have an effect on midi regions and ignored when operating on audio regions.
TagsNo tags attached.

Relationships

related to 0003719 closedcth103 Midi quantize does not work when when in note mode 

Activities

cth103

2011-01-19 21:07

administrator   ~0009951

The problem here is that MIDI regions cannot be selected in note mode, so it would seem odd to me if Audio regions could. I know the current situation can be confusing, but I do wonder whether the alternative might be more so.

lincoln

2011-01-20 00:48

reporter   ~0009954

Not really no, since when working in note mode on a midi region, it is resonable to expect to go grab an audio region to try things out in relation to midi.

Audio does not have a second mode and therefore it should behave in a consitent manner. ie a midi side setting does not have side effects on audio.

cth103

2011-01-20 01:10

administrator   ~0009955

So, if imagine that we allow selection of audio regions in note edit mode; if there is a selected audio region and a selected note, and we cut, what do we cut?

lincoln

2011-01-20 02:14

reporter   ~0009956

That is another problem with midi regions really. Selections in the midi region are sticky. Ideally when you select a note in the midi region, then select an audio region, the selection in the midi region is dropped.

As it is right now, you see selected notes remaining highlighted even if you are not manipulating a region.

So the second you select something else, drop midi region selections.

paul

2011-01-20 14:50

administrator   ~0009961

in the future "internal edit mode" will also apply to audio regions. i don't want to confuse things by making it midi-only now, and then changing it later.

system

2020-04-19 20:15

developer   ~0022376

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-01-17 14:35 lincoln New Issue
2011-01-17 19:30 cth103 cost => 0.00
2011-01-17 19:30 cth103 Target Version => 3.0-alpha1
2011-01-19 21:07 cth103 Note Added: 0009951
2011-01-20 00:48 lincoln Note Added: 0009954
2011-01-20 01:10 cth103 Note Added: 0009955
2011-01-20 02:14 lincoln Note Added: 0009956
2011-01-20 14:50 paul Note Added: 0009961
2011-01-21 00:15 cth103 Status new => resolved
2011-01-21 00:15 cth103 Resolution open => won't fix
2011-01-21 00:15 cth103 Assigned To => cth103
2011-01-25 15:50 cth103 Relationship added related to 0003719
2020-04-19 20:15 system Note Added: 0022376
2020-04-19 20:15 system Status resolved => closed