Feature request(s): enhance Settings -> Plugins

[Naenyn]

Not sure if this is the appropriate place for a feature request, but I'm going to run with it.

I'm on Waveform 9.0.37 (64-bit) on macOS 10.13.3.

I've been slowly setting up Waveform how I'd like.. and as part of that, I created a plugin list via the Custom Plugin List window in Settings -> Plugins. It would be really helpful if there were a few functions added to this that would allow for sorting alphabetically (forward and reverse) and a way to expand all / collapse all groups.

Also, the larger containing window for Settings -> Plugins doesn't appear to use all of the horizontal space available to it. When I resize my Waveform window, the plugin list extends vertically, but not horizontally. Considering there are some longer strings contained within the columns in the plugin list, it'd be nice if that window resized corresponding to the width of the main containing window.

And lastly, is it possible to export your settings/preferences? I'd like to have a backup, now that I've gone through the trouble of setting this all up. Although, seeing as how I'm on a Mac, I suppose there's probably a plist or something similar somewhere that I could copy.. hm.

Thoughts?

Edit: Found the settings export under Settings -> General Behavior. Yay!

[jabe]

I've been wondering about reorganising my plug-in folders by creating new folders named after plug-in types rather than company names. It'd probably be neccessary to retain the company-name folders, if that's where an update would install them. Perhaps I need to give it more thought or experimentation.

[dRowAudio]

You caught me just at the right moment as I was in the Plugin settings pages already.
I've added the sorting, the openness is a bit tricky due to the way the tree is implemented though so I'll have to leave that for now.

[whyterabbyt]

You caught me just at the right moment as I was in the Plugin settings pages already.
I've added the sorting, the openness is a bit tricky due to the way the tree is implemented though so I'll have to leave that for now.

Any chance of

1) User-definable 'display names' for plugins
2) User-switchable alternate menu structures

(Both of these existed in Sonar, and were very, very handy)

[dRowAudio]

1) User-definable 'display names' for plugins

Have a guess at why I was in the plugin settings page code...

2) User-switchable alternate menu structures

Not quite sure what you mean here? Do you mean macros to control the type of menu being used? Or the ability to create several custom menus and switch between them?

[whyterabbyt]

1) User-definable 'display names' for plugins

Have a guess at why I was in the plugin settings page code...

2) User-switchable alternate menu structures

Not quite sure what you mean here? Do you mean macros to control the type of menu being used? Or the ability to create several custom menus and switch between them?

The latter.

[dRowAudio]

That feels like a slightly over-engineered solution to a problem.
One of the key features of the custom menu is that you can create multiple sub-menus for different tasks perhaps using the same plugins. Wouldn't this be a more appropriate solution?

The only drawback I can see is a single menu level but that's probably easier to navigate than having to remember and switch which "menu structure" you're using?

[whyterabbyt]

Multiple submenus off one single fixed menu isnt as convenient, IMO. In particular you've got no way to exclude given plugins from the menu entirely, so while you can present multiple access routes to a given plugin, you cant present a clean single-task-based menu.
Is there a way to have plugins in the menu listed/filtered by tags, maybe?

And unless the custom menu creation gets a bit 'smarter', its still a fair bit of faff to add those extra submenus in, especially if you're repeating sets manually. Ive suggested before that it should be possible to populate the skeleton of a custom menu from existing info (folder structure, manufacturer etc), but going down this route, you'd also want cut, copy, paste at a minimum.

[Naenyn]

You caught me just at the right moment as I was in the Plugin settings pages already.
I've added the sorting, the openness is a bit tricky due to the way the tree is implemented though so I'll have to leave that for now.

Wow, good timing!
Hope you can add the expand/collapse eventually. Sometimes I'll go in there to change something and they'll all be expanded, so it means a lot more closing/collapsing.

[netsvetaev]

Hi!
Is there a way to export plugins or, at least, plugins' list / settings from Waveform on Windows to MacOS?
I already saved projects archives, but don't know how to migrate plugins easier.

UPD. Last time I tried to open projects in new W8 on new OS, I'd lost some plugins' settings. Like in Fabfilter Pro-Q and Melda Eq — they were just flat after first opening. Now I just copied archives to mac, install plugins and have no issues. It seems that Waveform 9 works better. Thank you!

[dRowAudio]

Hi!
Is there a way to export plugins or, at least, plugins' list / settings from Waveform on Windows to MacOS?
I already saved projects archives, but don't know how to migrate plugins easier.

UPD. Last time I tried to open projects in new W8 on new OS, I'd lost some plugins' settings. Like in Fabfilter Pro-Q and Melda Eq — they were just flat after first opening. Now I just copied archives to mac, install plugins and have no issues. It seems that Waveform 9 works better. Thank you!

This isn't really possible between OSes because plugins will have different IDs (and also different formats sometimes). Plus the file locations will be completely different.

What you need to do is simply set up your plugin locations on the new machine, perform a plugin scan and then as long as the plugins are named in a suitably similar way, Edits should find the plugins.

[netsvetaev]

This isn't really possible between OSes because plugins will have different IDs (and also different formats sometimes). Plus the file locations will be completely different.

What you need to do is simply set up your plugin locations on the new machine, perform a plugin scan and then as long as the plugins are named in a suitably similar way, Edits should find the plugins.

Thank you. I realize that last night

But I explored an interesting way to make dll's work in macos daw. There is netvst.
It can be run through wine, then routed to daw through network (). Not easy, but it works.