View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002753||ardour||bugs||public||2009-06-25 18:02||2013-04-06 23:09|
|Summary||0002753: track templates: creation of multiple tracks in one go fails due to naming conflict.|
|Description||here's the error:|
[ERROR]: AudioEngine: cannot register port "2AMB mono channel/in 1": a port with the name "2AMB mono channel/in 1" already exists: check for duplicated track/bus names
easiest solution might be to give them default names like "Audio N" and use the default unique name generation method.
|Steps To Reproduce||create a track template.|
session->add tracks->from template (more than one)
|Tags||No tags attached.|
||should be resolved in SVN rev 5322 (and 2.8.1). please confirm.|
the original issue appears to be fixed, thanks.
there is a related issue however:
it would be highly desirable if route templates could include sends (standard usecase: reverb) or even inserts. these will still generate name clashes:
if the original track that was saved as a template contains a ">send1", ardour will try to create a new track with ">send1" also (same for inserts), which fails.
maybe just re-use the logic behind the "new send"/"new insert" button in the mixer strip context menu, which apparently traverses the list of all sends/inserts and automatically creates a new name of the form "[send|insert]N+1".
since the ardour-internal name for this feature seems to be route template, i'm adding this note for the benefit of the search index:
route template, route-template, route_template. :-D
||another minor issue with route template generation: the color of the track is copied as well when using a custom template, which shouldn't happen by default.|
The issue seems to be fixed in current SVN 3.0.
However, the template still tries to create sends with identical IDs, but then some sanity check intervenes and says:
[WARNING]: aux send ID 2 appears to be in use already
Then, the new track is created correctly with all sends, apparently with implicit ID corrections. I wonder what happens if the ID namespace is scattered with holes, but for now I'm marking this as resolved.
||This issue has reappeared as of 3.0-185-g096fe04 (that's when I noticed it - might have happened several weeks or months earlier).|
|2009-06-25 18:02||nettings||New Issue|
|2009-07-04 18:23||paul||Note Added: 0006253|
|2009-07-04 18:23||paul||Status||new => feedback|
|2009-08-13 16:56||nettings||Note Added: 0006514|
|2009-08-13 17:00||nettings||Note Added: 0006515|
|2009-08-16 13:07||nettings||Note Added: 0006559|
|2009-08-16 13:48||nettings||Status||feedback => assigned|
|2009-08-16 13:48||nettings||Assigned To||=> paul|
|2011-11-30 16:25||nettings||Relationship added||related to 0004303|
|2013-01-22 00:21||nettings||cost||=> 0.00|
|2013-01-22 00:21||nettings||Note Added: 0014547|
|2013-01-22 00:21||nettings||Status||assigned => resolved|
|2013-01-22 00:21||nettings||Resolution||open => fixed|
|2013-01-22 00:21||nettings||Product Version||SVN/2.0-ongoing => SVN 3.0|
|2013-01-22 00:21||nettings||Fixed in Version||=> SVN 3.0|
|2013-04-06 23:09||nettings||Note Added: 0014835|
|2013-04-06 23:09||nettings||Status||resolved => feedback|
|2013-04-06 23:09||nettings||Resolution||fixed => reopened|
|2013-04-06 23:18||nettings||Relationship added||related to 0005437|