Jump to content

Red Four

  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

Recent Profile Visitors

153 profile views
  1. I just now read this, and had to comment to say that it's maybe the single most useful thing I've ever read about Cakewalk. Thank you! I spent some time orienting myself on drum maps a couple years back, but there were some things about them that I just couldn't quite grok, like how the saved presets and the maps in a project were connected (or weren't). Your article finally makes it make sense for me -- how the presets pull those settings into a project but from that point on the map in the project doesn't relate back to the preset at all (unless a map with new settings is saved with the same name, overwriting the old preset). The way Cakewalk does this is still a bit counterintuitive for me, but now that I understand the concept, it all fits together so much better. To help justify commenting nearly a year after the last comment, here's an updated link to the Drum Map section of the manual (which will probably change again once the manual is next updated, but until then): https://bandlab.github.io/cakewalk/docs/Cakewalk Reference Guide.pdf#G19.1089104. It's good documentation, but is missing the conceptual explanation from your piece that is essential in my mind. Cheers!
  2. I wondered about this, though I've used other Waves plugins without issue with Intel processors that didn't meet the listed specs for the plugin. Clarity VX is the first one I've encountered that simply refuses to work.
  3. I'm experiencing this exact same issue. The CW plugin scan crashes every time it reaches Clarity VX, and won't proceed. I've been using various Waves plugins for years, and this is the first time this has happened.
  4. For me, this seems to happen when I have certain plugins in a project. So far in my testing, a few Waves plugins seem to create this effect. I close the program and it seems to close, but when I try to relaunch, nothing happens. I check Task Manager and Cakewalk.exe is still running, but now as a background process. If I manually close it in Task Manager and reopen, it opens and works normally. After a while, I got tired of this extra step and created a task in Task Scheduler that closes the program and all child processes, then created a shortcut to the task in my task bar. If I close the program using that taskbar link instead of the X or File menu in Cakewalk, it closes the program completely and then it will work when reopened. The task I created is: taskkill /f /t /im Cakewalk.exe
  5. This has happened to me pretty regularly for about as long as I can remember using CbB. Exit the program, there's no sign of it visually but the process is still running in Task Manager. If I try to open the program, nothing happens. Have to manually close it in Task Manager, then opening it works fine. Doesn't seem to interfere with using the program but an extra little hassle.
  6. Thanks so much for sharing this info. This install is the first time my custom theme has been incompatible and I was thinking I would have to import all the updated elements individually. Your method is a quick and easy fix. Really appreciate it!
  • Create New...