scook

Any version of SONAR may be run from inside or outside Launchpad at any time. 32bit/64bit it does not matter. The tricky part is running versions of CbB older than the most recently installed version outside of Launchpad. Outside of Launchpad copies of CbB older than 2019-09 will work properly after 2019-09 (or newer) is installed. This is because up until CbB 2019-09 the program would run OK with newer versions of CW130Auto.dll. Changes were made to the dll which broke compatibility with older versions. To address this, starting with 2019-09 Launchpad keeps copies of the dll and insures CbB always uses the correct version. Because you installed 2019-11 prior to running Launchpad, there is no 2019-09 version of CW130Auto.dll so, Launchpad will not use that version of CbB. Will 2019-09 run from the command line...maybe. Is it safe? I don't know and that is why Launchpad throws an error. There may be problems with automation. I like to make the Quick Copy right after a new version is installed. It is easier for me to remember to do it then rather than wait for the next update. But as long as the Quick Copy of the currently installed version is made some time prior to the next update, you will be OK.

That is a puzzle. I have Win10 home v1903 and do not have any problems with Windows Defender preventing any of my tools from running. If you get any results, just let me know and I will make the needed changes. For now, I am going to leave everything as is and remove the test version linked above.

Yes, when snap is enabled the grid lines bisect the hot spots for note placement. With Aim Assist and snap enabled in the PRV, the placement of a note is shown by Aim Assist. This only time this is true is the left edge of the PRV. Otherwise, there is just as much space to the right of the grid line as the left to place a note that starts at the grid line. To change the snap from centering the hot spot on the grid to starting at the grid line is a feature request (or a bug report depending on the devs point of view).

From the release notes for 2019-09

Thanks Hopefully, I can get confirmation that the change I just made works because I would like to introduce both changes (silently skipping unsupported products and adding Studio support) in the next release.

Here is a copy of the Launchpad executable that silently skips unsupported versions of SONAR Replace the "Cakewalk Launchpad.exe" from the zip with this one. Please, let me know if it works for you. Again, if you can tell me the name of the X3 Studio exe file, I can add it to the list of support versions of SONAR. Edit: link to test version removed

At the time that check was added, I only planned on having the program support SONAR Platinum and Producer. If you can give me the fully qualified name of the SONAR X3 Studio executable, I will add support for SONAR Studio. For now, I will modify the program to silently skip unsupported Cakewalk products.

Thanks. Yeah, it's a shame they have not done anything with the commercial modules.

To run the most recently installed version of CbB either by double clicking a CWP file or the desktop icon, make sure to enable "Restore CW130Auto.dll on exit" in the Launchpad File menu. Running other CbB versions outside of Launchpad is a little tricky. The safest way to run older versions of CbB is always run them from Launchpad. Launchpad has a variety of ways to manage lists of projects. I have no need to run CbB outside of Launchpad. Once CbB is started inside Launchpad, one has access to the CbB Start Screen and Launchpad's project lists.

Rayzoon has started its holiday sale on Dec 1. All prices shown today are good though the end of the month.

If you start using Launchpad to save versions, it should always be used to run CbB. This way the version is set up properly. It you need more details or help, please post in the tools thread...thanks.

I am not sure a simple copy of the CbB program folder still works and no longer recommend the practice. As a result of changes made in 2019-09, I modified my tool to keep track of more than the program folder. My tool thread is here.

It is your call. There is an early release of a hotfix for 2019-11 This should be formally released next week. Personally rather than sweat about new releases, I wrote a tool to keep several versions of CbB available at all times. This lets me add new releases and still have other releases ready to run, just in case. It is a lot easier than backup/restore but burns about 150MB per version of CbB on the disk where CbB is installed. I described how to use it and where to get it here

The Custom module

similar thread

There should be a drop down on the far right-hand side of the menu bar

You may either re-run the Get Started process from the help menu to review the options you originally selected or set Workspaces menu to None.

sounds like a plug-in in demo mode

install the hotfix

I just checked EZD v1.4.0 runs OK in CbB. Make sure the 64bit version is installed.

See the Recycle Plug-In Windows section in http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B07

have you applied the hotfix?

More than that, the 32bit version of EZD 1 does not work in 64bit hosts. Have no info on EZD 2. If using the fefault "Sort by Category" plug-in layout, VST2 plug-ins typically show up in the Uncategorized folder. There is no need to move the dll from the original install path. Just make sure the original install path is in the Cakewalk VST scan path in preferences. While in preferences, try a manual scan with the "Generate Scan Log" option enabled. Check the log to verify the plug-in is in there.

The build is shown on the About screen

A fix was released a couple of hours ago