Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

18 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I learned something so, checked boogex out, you're right! The Cabinet Sim/Convolver is mono, guess that means it's a mono plug and on a stereo track it's only left sensitive, I wonder if that's typical for mono plugs?
  2. Thanks again, I am aware of Launchpad, and appreciate your generosity in providing useful tools, it was the compatibility check that was a news update that I'm glad to know, and in general I've never rolled back, my interest is a comparison between current and previous for some feature at best, if at all ๐Ÿ˜Š
  3. That's good to know, thank you, and I assume for automation you're referring to CW130Auto.dll, and of the 4 dlls that have gotten updated this release, that CW130auto is the pertinent dll as I think Splat also uses 3 of the updated dlls plus CW120Auto.dll. The others in shared utilities appear to be no later than 2019. So, going forward keeping a copy of the current CW130auto along with the "Cakewalk Core" might be an idea if desperate to run a prior version of CbB, unless the compatibility check some how prevents it?
  4. This has to be so, because I assume by that, changes can occur to folders other than "Cakewalk Core" but FWIW I keep all versions of the "Core" backed up and I was able to run "Cakewalk.exe - 2021.01 bld 098 (Update 1)" from a renamed "Core" folder, and this version has the prior tempo features operable, maybe that's all Sam Stalos requires? This time running a prior version to the latest currently installed, I saw that there was no notice that a newer version was available, and following that on a startup of the current CbB there was a refreshing activation notice?
  5. I think you misunderstand, no offense, the shell loads 3 distinct 64 bit plugins which only get scanned once when the "shell plugin" was first installed and the vsts are registered, after that it's just the shell that gets scanned each time CbB starts up, the shell is just the front end for each plugin which the shell extracts, in my case, from a "WavesLib1.14_12.7_Win64.dll" file, there is no individual vst plugin dlls or vst3 files except the shell which for the vst3 is "WaveShell1-VST3 12.7_x64.vst3". Now I'm assuming that the shell maybe generic, capable of loading vsts from other libs if and when a new lib is installed and then the vsts that get loaded would be scanned when first registered. Again, no 32 bit plugins are involved and plugins loaded by the shell are scanned when first registered, and appear in the plug-in manager. It's possible the shell gets scanned every time to see if a new lib was installed, that's my conjecture. As for AAS the old installers splattered vsts all over the place, I know all the locations, but the only ones I'd delete were in the Cakewalk\VstPlugins folder the only location on my CbB's and Splat's vst path I didn't specify. The new installer is cleaned up putting the 3s in the default location and the 2s where you tell it, yahoo! I believe I saw this in one of your prior posts, that was what I implied by "a vst3 may not be suitable for all cases" and FWIW I also seem to remember that some vst2s were needed to take advantage of NKS support despite an available vst3.
  6. Yes, it's a matter of choice keeping both vst2 & vst3 versions of a plugin, a vst3 may not be suitable for all cases depending on the plugin and it's intended use. In this case the shell loads all 3 plugin flavors so only the shell needs to be on the CbB's vst path, and it seems that the plugs the shell loads get scanned once on the first time loaded, but the shell gets scanned each CbB startup, this behavior, albeit normal for a shell, was something new too me hence the OP. Regardless the shell scan is lightning fast. The plug-in manager lists all plugins loaded by the shell with unique VST IDs, but all have the same filename which is the shell's and there are no individual .dlls or .vst3s for these VSTs which I think are embedded in a lib .dll file ๐Ÿ™„...
  7. I think basically you're right which is good to know & now to be expected thank you very much. This plugin loads in 3 flavors and on an initial 1st time scan I'm sure I saw multiple scans resulting in 3 new plugins per vst2/3, but on subsequent startups it's seems only the shell for each vst gets a token scan which is really fast and not significantly adding to the startup time, if at all. So, right now an auto scan is just fine.
  8. My scan option is set to Automatic Background Scan, and typically on a CbB startup when thereโ€™s no new plugins the scan popup will show either searching for plugins and/or the Scan Complete no new plugins found list and no plugin scan notice, but since adding a Waves Audio plugin this shows up as being scanned, albeit very swiftly, prior to no new plugins found list each time on a CbB startup. The WA plugin is an indirect Shell to the actual plugin, is this why the scan occurs or, in general, a quirk of Waves Audio, or something else?
  9. I second the question, maybe you'll get a reply, I didn't see my post It's the same issue but as a reply in a different topic. good luck...
  10. Track Folder Buttons: In this and prior versions when an existing project is opened the Track Folder buttons rarely reflect the state of the tracks for all Track Folders. For example folders that only contain functioning Aux tracks should have the the "Input Echo" button on, and frequently don't. Similarly other buttons may not be properly synchronized with track states and this can occur whilst working on a project. A minor inconvenience, but still, it might reflect CbB GUI rendering issues that might be of some importance...
  11. I guess you're right, I know they overhauled the GUI code for O9, which it seems is little more resource intensive and has a couple of minor glitches, and in their thrust to push out new products they just might skimp on regression testing! Their collaboration with Exponential Audio only has iLok plugins, no CBA, maybe it's gonna be the trend?
  12. I believe this is an iZtope issue as this has occurred with other DAWS and doesn't apply to all iZotope plugins. The versions of Ozone for example, prior to Ozone 9 loaded just fine without iLok and other iZotope plugins also load swiftly without iLok, so it would seem Cakewalk's off the hook on this one ๐Ÿ˜Š
  13. @msmcleod Not sure if this is a bug but, in the Tempo inspector if there's just the initial tempo node (M.B.T 1:01:000) and a later node is added for the same tempo value, just that single node appears, but if the tempo value is different 2 nodes appear 1 at the desired M.B.T. and 1 at the end of the project. This seems like odd behavior?
  14. There's a known issue with Ozone 9 Advanced modules loading slowly if they were computer authorized, which all my iZotope plugins are. The solution is to install the iLok software even though iLok authorization is NOT being used, and this enables normal fast load times. I verified this issue with iZotope support a while ago. If you don't have iLok installed, this solution might help ...
  • Create New...