View Issue Details

IDProjectCategoryView StatusLast Update
0006195ardourbugspublic2020-04-19 20:17
Reporterahellquist Assigned Tox42  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Summary0006195: Dragging an audio region from the region list to the drop area (new track) does not create a new track.
DescriptionThis used to work and was very useful.

To work around this limitation, one has to know if the region in the region list is a mono or stereo clip and then manually create the track and drag n drop the region to the newly created track.

There is no apparent way to visually determine if a region in the region list is a mono or stereo region.
Additional InformationOne can audition the region and hopefully detect if the clip is mono or stereo but that is really not a good way to do it IMHO

Ardour 3.5-4630
TagsNo tags attached.

Relationships

related to 0006172 closedx42 region can't jump over the bus 
related to 0006205 closedx42 Dragging a region from the region list to the drop area is prohibited 
related to 0006223 new region list channel-count 

Activities

ahellquist

2015-03-08 00:51

reporter   ~0016400

Dragging a region from another track to the drop area seems to create a new track.

ahellquist

2015-03-15 23:43

reporter   ~0016442

this should be marked duplicate and instead point to 6205 which has more info.

I am sorry for filing duplicates a few days apart.

x42

2015-03-25 00:55

administrator   ~0016486

Drag from region list is fixed in 3.5-4854-g9696469.

"There is no apparent way to visually determine if a region in the region list is a mono or stereo region."
indeed. I'll leave this bug open for now (until this is filed as separate feature request).

x42

2015-03-30 09:36

administrator   ~0016518

original issue is fixed.

region-list channel-count as been filed as feature-request 0006223

system

2020-04-19 20:17

developer   ~0023412

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
2015-03-08 00:48 ahellquist New Issue
2015-03-08 00:51 ahellquist Note Added: 0016400
2015-03-15 23:43 ahellquist Note Added: 0016442
2015-03-23 21:11 x42 Relationship added related to 0006172
2015-03-23 21:12 x42 Relationship added related to 0006205
2015-03-25 00:55 x42 Note Added: 0016486
2015-03-30 09:34 x42 Relationship added related to 0006223
2015-03-30 09:36 x42 Note Added: 0016518
2015-03-30 09:36 x42 Status new => resolved
2015-03-30 09:36 x42 Resolution open => fixed
2015-03-30 09:36 x42 Assigned To => x42
2020-04-19 20:17 system Note Added: 0023412
2020-04-19 20:17 system Status resolved => closed