PLEASE PLEASE PLEASE

IDEAS: The "group" could be like, or act like - a plugin itself (see rationale here) that's a container for 1 or more other plugins, just. WHY or RATIONALE for this approach: That will allow the 'group' to gain functionality that already exists in LP for plugins.

- the group shows up in the list of plugins to add to a LP project as a whole

- I can add multiple instances of the group

- the group shows up in list of plugins when you ADD ACTION --> EFFECTS along with the individual plugins inside the group, and all of the plugins in use

It would "seem" if the group is acting like an plugin; you get a lot of functionality without extra work. There may be some "restrictions" here..... but it "seems" like a win win.

Obviously some ACTIONS can be applied to the group as a whole (like enable/disable)

Just as obvious some ACTIONS that are normally applied at the individual plugin level now have a DEPENDENCY on the group values itself. E.g. - if I have 2 plugins and they are both "enabled" but the group plugin as a whole is "disabled" then none of the plugins inside will get signal.

PLEASE, PLEASE, PLEASE..... functionality I would like to see at the GROUP LEVEL:

- user given name for the group (LP can name it internally)

- wet /dry mix for the group [PLEASE, PLEASE, PLEASE] RATIONALE: Sadly some existing plugins DO NOT have a wet/dry mix, and so.... I can put a single plugin inside this group and gain this functionality.

- enable /disable via ACTIONS in LP

- (initially) have the plugins linearly in the group, and give the users the ability to "order" the plugins in the group 1, 2, etc. and allow them to reorder them

- have a "CREATE" and "EDIT" mode; and if after creation a user edits the group; offer the ability to "SAVE AS...." if they want to make a copy or a new group

STRETCH GOALS:

- Allow the user to give a color to the group; assuming it's displayed in a channel as like a folder

- Assuming it's displayed like a folder when it's in a channel; allow something like red/green circle to indicate if it's enabled or disabled

TOUGH DECISION: Are there presets for the group? My suggestion is start simple and the only presets are for any parameters at the group level such as wet/dry mix, and the order of the plugins. If the user wants versions or presets of parameters for the plugins within the group - let them create plugin presets for those. Anything beyond storing presets at the group level is a stretch goal.

I suspect folks will want to "somehow" know which plugins are in the group as it is displayed or used in a channel. The small icons that appear not overly useful, and I've seen other feature requests to address this. Sometimes you can tell by an ICON what a plugin is, if you use a lot, sometimes you can't tell what it is. The idea above with folder color is helpful - but there's no perfect solution here. Since a "group" can have 1 or 8, or 40 plugins in it, there's no way to even think, to hope to display text on a screen....I would stick with a folder color. Perhaps have a few "folder" or "group" icon selections to choose from when creating the group? Maybe a folder icon, a box icon, a shipping container icon, a wrapped present icon. Just ideas.....

I would force the software to only allow new instances or "unused" instances of a plugin to the group. E.g. - if I have 2 instances of FabFilter Pro Q (plugin) already in use in my project, and I create a new group and I want to put FabFilter Pro Q inside the group - I HAVE TO use a new or not already in use, instance of FabFilter.

PLEASE STAT SIMPLE and make progress over time. Think Agile. Even delivering the group and just being able to allow an ACTION to enable/ disable the group as a whole is a great start.

Thanks Again for Wonderful Software!!