View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002683ardourbugspublic2009-05-17 21:552020-04-19 20:14
Reporteragorka Assigned Tocth103  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
PlatformLinuxOSUbuntuOS VersionKarmic
Product Version2.8 
Summary0002683: Sends with duplicate names make session unloadable
DescriptionI was learning to use Ardour, tried to make reverb sends, and was surprised, that they are called for example Send 1 on left piano microphone, Send 2 on right piano microphone etc, not giving any idea where I'm sending the signal to. I tried to copy send and got Send 3. Trying to imagine how confusing this could be if I would have few different sends, I renamed Send 1 to Reverb and Send 2 to Reverb, and was happy that Ardour allowed me to make sends with the same names. I saved project, and when I tried to load it back, I got:

AudioEngine: cannot register port "Reverb/out 1": a port with the name "Reverb/out 1" already exists: check for duplicated track/bus names

And no chance to load my project. I won't miss this project much, but for those who are serious at using Ardour, that might be a knife in the back.

And by the way, is send naming going to be more informative in the future? If I send all my 20 tracks to reverb, how Send 6 differs from Send 19? Rearranging tracks would make those numbers even more crazy. Renaming them manually takes serious amount of time.
TagsNo tags attached.

Relationships

related to 0002694 closedpaul [PATCH] renaming a send to have the same name as a track prevents the session from being loaded again 

Activities

cth103

2010-05-02 00:13

administrator   ~0007730

This has been fixed in current 2.0 and 3.0.

system

2020-04-19 20:14

developer   ~0021916

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
2009-05-17 21:55 agorka New Issue
2009-06-10 01:27 cth103 Relationship added related to 0002694
2010-04-24 10:28 cth103 Category bugs => bugs2
2010-04-24 10:31 cth103 Category bugs2 => bugs
2010-05-02 00:13 cth103 cost => 0.00
2010-05-02 00:13 cth103 Note Added: 0007730
2010-05-02 00:13 cth103 Status new => resolved
2010-05-02 00:13 cth103 Resolution open => fixed
2010-05-02 00:13 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0021916
2020-04-19 20:14 system Status resolved => closed