View Issue Details

IDCategoryLast Update
0000375features2012-01-19 14:37
Reportermatalos2Assigned To 
Reproducibilityalways 
Status acknowledgedResolutionopen 
Product Version 
Fixed in Version 
Summary0000375: Plugin Chain Preset
DescriptionThe idea is to store the list of plugins (pre and post individially) per track and saving the correct ORDER and the SETTINGS of the plugins(in an xml file I suppose).
An option should be added to the already existing menus(add plugin ,enable-disable plugin,etc) called "Load Plugin Chain Preset" and "Save/Store Plugin Chain Preset" or something like that.
I normally work with many PRE plugins in one track at the same time and considering the enormous amount of ladspa plugins available, I generally forget what combinations of plugins I used.It is a lot more practical to load a chain of plugins(already ordered and configured)than to close the session, load an earlier session with the plugins I used,see what plugins I used and load again the newest session.
Additional InformationI'm not sure if I have seen this feature in any audio workstation, but I believe it is extremly usefull and practical.
Btw,I know you can select all plugins and do a copy and paste, but what do you do if you only have empty tracks?That's where I think is usefull to load chains of plugins you stored in the past.
I apologize for making this so long.
TagsNo tags attached.

Relationships

related to 0001209 resolvedpaul template components 
has duplicate 0003750 new Add ability to save processor lists 
related to 0000581 resolvedpaul store track/bus templates and create tracks from templates 

Activities

taybin

2004-04-14 04:13

administrator   ~0000619

This is certainly possible. In the meantime, you might want to try out the template feature, which will setup a new, empty session, just like some other session.

matalos2

2004-05-15 22:58

reporter   ~0000723

Just to know if you were interested in including this feature in a release.

taybin

2004-05-15 23:01

administrator   ~0000724

Nope. It is "post major release". That means after 1.0.

taybin

2006-11-03 04:51

administrator   ~0002618

There has been more talk of implementing this. The UI details will be interesting, of course.

in0giro

2012-01-19 14:37

reporter   ~0012581

+1

Issue History

Date Modified Username Field Change
2004-04-13 21:35 matalos2 New Issue
2004-04-14 04:13 taybin Note Added: 0000619
2004-04-14 04:13 taybin Priority normal => urgent
2004-04-14 04:13 taybin Status new => acknowledged
2004-04-14 04:15 taybin Priority urgent => low
2004-05-15 22:58 matalos2 Note Added: 0000723
2004-05-15 23:01 taybin Note Added: 0000724
2006-11-03 04:51 taybin Note Added: 0002618
2007-02-14 22:27 taybin Relationship added related to 0000581
2007-02-14 22:27 taybin Relationship added related to 0001209
2010-07-22 14:32 oofus cost => 0.00
2010-07-22 14:32 oofus Target Version => 3.X
2012-01-19 14:35 paul Relationship added has duplicate 0003750
2012-01-19 14:37 in0giro Note Added: 0012581