View Issue Details

IDProjectCategoryView StatusLast Update
0002662ardourfeaturespublic2020-04-19 20:14
Reporterpmcginley Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version2.8 
Target Version3.0-beta1 
Summary0002662: remove/replace plugin presets
Descriptionit would be useful to be able to remove and/or replace plugin presets. as it stands, there is no way to remove an obsolete preset from the dropdown list, and an attempt to replace by giving a new one an identical name results in multiple presets of the same name.
TagsNo tags attached.

  Users sponsoring this issue
Sponsors List Total Sponsorship = US$ 10

2010-12-04 01:35: josh (US$ 10)
  Users sponsoring this issue (Total Sponsorship = US$ 10)

Relationships

related to 0002779 closed Can't delete or rename plugin presets 

Activities

danboid

2010-12-05 08:25

reporter   ~0009548

This applies to 3.0 still too so it'd be good to see this make it into the final release of 3.0 if not the beta.

Of course, this request was filed against 2.8.x. Does this have a chance of getting into A2 now or should this be modified to being a 3.0 request? Be best if both could be upgraded in this respect.

cth103

2010-12-06 02:41

administrator   ~0009550

This has been improved slightly in A3 SVN: now you can't save different presets with the same name, and you can replace one with another. We still need a way to delete presets.

cth103

2010-12-06 04:31

administrator   ~0009551

Last edited: 2010-12-08 01:27

3.0 also now has a dialog to allow deletion of presets, so this should all be fixed. It's quite a big patch so I'm afraid it's unlikely to make it into Ardour 2.

josh

2010-12-14 19:52

reporter   ~0009628

i took a look at the latest. it's nice progress and i'll definitely pay out the sponsorship, but i would recommend going a little further with it. the user should be able to hit a "save" button right on the plugin settings instead of opening a new window and typing in the same name. "delete" should work similarly. a new window is not needed (in my opinion). still, this is a major step forward, thanks!

cth103

2010-12-15 01:07

administrator   ~0009632

Good points, well made! This should all be sorted in SVN now. Please re-open this bug if you have further suggestions. Thanks!

system

2020-04-19 20:14

developer   ~0021906

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-08 10:55 pmcginley New Issue
2009-07-13 22:53 cth103 Relationship added related to 0002779
2010-12-04 01:35 josh Sponsorship Added josh: US$ 10
2010-12-04 01:35 josh Sponsorship Total 0 => 10
2010-12-05 08:25 danboid Note Added: 0009548
2010-12-06 02:41 cth103 Note Added: 0009550
2010-12-06 02:42 cth103 Status new => acknowledged
2010-12-06 04:31 cth103 Note Added: 0009551
2010-12-08 01:27 cth103 Note Edited: 0009551
2010-12-14 19:52 josh Note Added: 0009628
2010-12-14 22:09 cth103 cost => 0.00
2010-12-14 22:09 cth103 Target Version => 3.0-beta1
2010-12-15 01:07 cth103 Note Added: 0009632
2010-12-15 01:07 cth103 Status acknowledged => resolved
2010-12-15 01:07 cth103 Resolution open => fixed
2010-12-15 01:07 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0021906
2020-04-19 20:14 system Status resolved => closed