• SONAR
  • Cakewalk Plugin Manager Needs A Major Overhaul (p.5)
2015/07/21 07:14:57
jeff oliver
Craig Anderton got some great plugs I use all the time and would like to move them to certain groups; guitars, drums etc. Is there a way to do this in the PIM? They don't seem to be "manageable". Yes, they are already in groups but I have made global groups that's easier for me to get what I need. Or am I missing a step? Thanks :)
2015/07/21 14:47:31
Kylotan
Jeff, you can drag plugins around within the menu editor on the right-hand side. Is that what you're looking for?
2015/07/21 17:21:10
jeff oliver
Thanks Kylotan for your response. I'll look again soon as I get home. I can move the plugins around inside the manager but the Craig Anderton don't show up. Maybe I'm in the wrong menu. Thanks again!
2015/07/22 02:11:56
KPerry
Craig's FX are chains of FX, not individual ones so won't appear in the plug-in manager (not a bad idea though to be able to add chains to custom menus!).
2015/07/22 08:45:40
mudgel
I thought Noel's idea to work towards having plugin management take place within the browser as a much better long term solution.
2015/07/22 08:51:12
Bristol_Jonesey
I agree Mike.
 
I still use the PIM for setting up my own presets, but once I'm done with that, it's all accessible from within the browser.
2016/07/04 21:13:38
Marconix1
jsg
vmw
The plugin manager has become like the staff view, which are two areas suffering neglect. (This BTW is not to start an argument on the staff view)
The plugin manager needs refining to make it scan faster and the GUI needs some thought as well, it has been the same for multiple editions going back years. It is all well and good supplying new plugins and content through the membership model; but it would be far more appreciated if you looked at something as basic as the plugin manager and its performance.




What do you want it to do?  Plug-in Manager works fine here (Platinum).  It's just a utility that scans for plugins, scans as fast or faster than other DAWS. 
 
JG

 


That's exactly right. Out in the cold for all the rest of the plugins. With proper thought and planning a PIM overhaul could really be helpful to workflows.
2016/07/04 21:23:10
chuckebaby
what would you suggest ?
I mean is there something the plug in manager does not do right now ?
 
2016/07/05 08:31:30
dantarbill
chuckebaby
what would you suggest ?
I mean is there something the plug in manager does not do right now ?
 


As I've mentioned before...there's no good way to see when new plugs aren't included in a custom plugin layout.
 
I suggest highlighting all the registered plugins that are in the currently open Plug-in Menu Layout at least once.  That way, anything you haven't dealt with will be (what...lowlighted?).
2016/07/05 09:24:00
chuckebaby
dantarbill
chuckebaby
what would you suggest ?
I mean is there something the plug in manager does not do right now ?
 


As I've mentioned before...there's no good way to see when new plugs aren't included in a custom plugin layout.
 
I suggest highlighting all the registered plugins that are in the currently open Plug-in Menu Layout at least once.  That way, anything you haven't dealt with will be (what...lowlighted?).


fair enough.
I don't use the plug in manager to create custom layouts.
I find the most productive way to keep your menus organized is to create nest folders within windows explorer.
when I install new plug ins, I create a folder called Example "Overloud"
now any new plug in I install I install it to the overloud folder in windows explorer
(this folder is in program files\cakewalk\vst plug ins.
 
even if you have nested folders in the cakewalk\vst plug ins folder they still get scanned.
every file, folder in that directory is scanned by default.
it takes about as much time as creating a custom plug in menu wouldn't you agree ?
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account