Anders Madsen Posted June 12, 2019 Share Posted June 12, 2019 (edited) I want to ditch most of my 32 bit plugins. Especially those that were installed alongside a 64 bit, and there is a redundancy. (I can not tell the difference in the VST-list, as there are two identical instances) But how do I do this? Just delete the DLL's? How do I recognise the correct ones to delete? I really whish there were an interface for this kind of.. uhm maintenance.. Edited June 12, 2019 by Moxica Link to comment Share on other sites More sharing options...
msmcleod Posted June 12, 2019 Share Posted June 12, 2019 The way I would do it would be: From the plugin browser, right click on the "Plugins" tab and select "Manage Layouts" Go through the plugin tree, looking for the ones in green - these are the 32 bit ones. Right Click->Properties on each one. The full filename will be shown. Copy this path to Notepad Once you've gone through all of them, go through your list in Notepad and rename them from myplugin.dll to myplugin.dll.bak Then re-scan your plugins Alternatively, you can use RegEdit: Windows Key + R, type regedit and press enter Navigate to "Computer\HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory" This lists the path of each VST / VSTi Look at a the isX64 key for each entry. If it's set to 0x00000000 (0) then it's a 32 bit plugin If you just want to exclude it, set the isVst value to 0 If you want to delete it permanently, copy the path (FullPath key), paste in to Notepad and once you've gone through all of them, go through your list in Notepad and rename them from myplugin.dll to myplugin.dll.bak Re-scan 2 1 Link to comment Share on other sites More sharing options...
sping Posted June 12, 2019 Share Posted June 12, 2019 I use Scook' s "VST Inventory Tool" to locate my VST's. I know he have linked to it here, but can't find it atm. Link to comment Share on other sites More sharing options...
HIBI Posted June 12, 2019 Share Posted June 12, 2019 15 minutes ago, sping said: I use Scook' s "VST Inventory Tool" to locate my VST's. I know he have linked to it here, but can't find it atm. 2 Link to comment Share on other sites More sharing options...
Skyline_UK Posted June 12, 2019 Share Posted June 12, 2019 It seems to be on this list: https://docs.google.com/document/d/1eiVH_I1clbbRtWFh4-3Mo7HANjCxR8SwqHJtYXy19gw/pub 1 Link to comment Share on other sites More sharing options...
Anders Madsen Posted June 12, 2019 Author Share Posted June 12, 2019 Fantastic! There will be a weight reduction later today, of significant proportions! Thank you! Link to comment Share on other sites More sharing options...
scook Posted June 12, 2019 Share Posted June 12, 2019 To create a list of 32bit plug-ins using the The VST Inventory Tool mentioned above set the filter drop down to x32 entry a Y in the entry field next to the filter drop down click Submit With the list as a guide, either use the Plug-in Manager to exclude the plug-ins locate the plug-in in the Plug-in Manager. The VST Inventory can help with the category in the Plug-in Manager as there are columns identifying which plug-ins are VST2/3 (Y in the VST3 means a plug-in is a VST3) and FX/Synth (Y in the synth column means the plug-in is a synth). verify the path by comparing the Filename shown at the bottom of the Plug-in Manager to the Full Path in the VST Inventory Tool click the Exclude Plug-in button to hide the plug-in from CbB plug-in list rename the file names as mentioned above. Make sure to run a scan after renaming files. It is possible to delete the files but it is better to leave them installed just in case there are projects that depend on them. The binaries do not take up much disk space. 2 1 Link to comment Share on other sites More sharing options...
scook Posted June 12, 2019 Share Posted June 12, 2019 True and if the paths are not mixed in the with 64bit paths, removing the 32bit paths from the the scan path (and re-scanning) in preferences works too. Link to comment Share on other sites More sharing options...
scook Posted June 12, 2019 Share Posted June 12, 2019 Cakewalk mixed 32bit plug-ins in the 64bit path if the 32bit version of the DAW was not installed first. A few manufacturers do not provide separate 32 and 64 bit install paths. The list in the VST Inventory Tool above are a combination of those two issues. Link to comment Share on other sites More sharing options...
Anders Madsen Posted June 12, 2019 Author Share Posted June 12, 2019 Weird how the Nomad factory bundle does not appear green in the list, but shows up as 32 bits in the Inventory tool. Thanks for that, by the way. Cakewalk is already tons slimmer. Metric tons that is. :) Link to comment Share on other sites More sharing options...
razor7music Posted June 12, 2019 Share Posted June 12, 2019 Just curious, why are you getting rid of all of your 32 bit plug ins? Is it because you also have 64 bit versions of the same ones? Link to comment Share on other sites More sharing options...
Anders Madsen Posted June 12, 2019 Author Share Posted June 12, 2019 (edited) 12 minutes ago, razor7music said: Just curious, why are you getting rid of all of your 32 bit plug ins? Is it because you also have 64 bit versions of the same ones? As it turned out, getting rid of redundant VST2's where I allso have the VST3 was what I really needed. Less clutter. Besides, the 32 synths tend to be unstable. I have such a coverage, that if the effect does not exist in 64 bit, I don't need it. They are mostly old, and sometimes redundant, as I have both. Edit: Had both. Edited June 12, 2019 by Moxica Adding more info 1 Link to comment Share on other sites More sharing options...
scook Posted June 12, 2019 Share Posted June 12, 2019 The color of the plug-ins in Cakewalk plug-in layouts is determined by the theme. All 32bit plug-ins have (32-bit) appended to their name in plug-in layouts. The Inventory Tool reports bitness along with other parameters based on the Inventory registry. The same registry information read by the DAW. Make sure to verify the paths as reported in the Plug-in Manager and Inventory Tool are the same file. Link to comment Share on other sites More sharing options...
scook Posted June 12, 2019 Share Posted June 12, 2019 22 minutes ago, Moxica said: As it turned out, getting rid of redundant VST2's where I allso have the VST3 was what I really needed. I use a combination of excluding, deleting and installing outside the Cakewalk scan path for the redundant VST2 plug-ins. Sorting the Inventory Tool by name then by vendor will organize the the plug-ins showing alternating VST3 and VST2 where both are preset. To sort by a column, click on the column name. It may also help to filter by vendor then sort by name. To filter by vendor select Vendor in the drop down and enter all or part of the vendor name (ex. for iZotope, Inc. - izo works for me) It is also possible to export lists from the tool and load them into a browser or spreadsheet. 1 Link to comment Share on other sites More sharing options...
Anders Madsen Posted June 12, 2019 Author Share Posted June 12, 2019 (edited) 1 hour ago, scook said: The color of the plug-ins in Cakewalk plug-in layouts is determined by the theme. All 32bit plug-ins have (32-bit) appended to their name in plug-in layouts. The Inventory Tool reports bitness along with other parameters based on the Inventory registry. The same registry information read by the DAW. Make sure to verify the paths as reported in the Plug-in Manager and Inventory Tool are the same file. Yes, I did. I got it to where I like it by renaming dll's. Thanks again. You guys are great! Edited June 12, 2019 by Moxica Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now