View Issue Details

IDProjectCategoryView StatusLast Update
0000135OpenMPTFeature Requestpublic2011-05-27 19:28
Reporterharbinger Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Platformx86OSWindowsOS VersionXP
Product VersionOpenMPT 1.19.01.00 (upgrade first) 
Summary0000135: Plugin Manager - Rename new plugin
Description

While we can rename plugins when they're assigned to a track (in the "Display" field in the General page), we can't assign them initially in the Plugin Manager. When you get a lot of plugins, finding a particular one can be time-consuming, esp. when you get a new one and you have no clue what it's called internally. For example, when i first loaded the Superwave P8 (a couple of versions ago), the plugin was listed as "SuperWave." When i got the recent upgrade, the plugin was labeled simply "P8" which i wasn't expecting. I could've used the filter function, but that wouldn't have done any good. So i have to rely on the alphabetical listing in the directory tree. But that doesn't work always either -- i recently installed a new free VSTi called Cloud into my VSTi folder, and i was able to load into MPT fine. But when i attempted to locate the plugin in my long list in the Plugin Manager, it wasn't loaded under "Cloud": it was actually under "The C5 Cloud" at the other end of the directory tree. I'm sure other plugins have this anomaly, and it can be annoying if you have a bargeload of VSTs installed.

When i want to test new plugins, i have to be able to find them, so what we need is something like a customizable labeler, so even though MPT loads it under a path and file name, the user can decide how it should be labeled for the directory listing of the Plugin Manager. No more losing my new plugins...

Alternatively, an alternate way of listing the plugins (by date added instead of alphabetical) could be available.

Oh, and while we're at it, i'd like to be able to see the full pathname at the bottom of the Plugin Manager window....

TagsNo tags attached.
Has the bug occurred in previous versions?
Tested code revision (in case you know it)

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2011-05-27 19:28 harbinger New Issue