scook

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

3 hours ago, Odys said:

Right now to put note in a specific grid I have to click on left half of it. Clicking on right half puts note on grid next to it. I would love to disable this feature. Giving me half the space means that i have to be zoomed in twice as much horizontally to get same precision. 

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

Quote

Cakewalk must be periodically activated via BandLab Assistant, but will no longer switch to demo mode during a session. A notification will remind you 14 days before the application needs to be reactivated.

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.

3 hours ago, User 905133 said:

Re: LaunchPad: Do I need to uninstall unsupported versions, or can I just exclude them from being searched somehow? If so, is there a list of supported and unsupported versions? Thanks.

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.

35 minutes ago, Yan Filiatrault said:

I wonder if it’s a Black Friday price or if it will stay at 119$ all December?

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

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

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

Before one can proceed with installing X3 producer, the installers must be available on a local drive.

This has always been the case.

The detailed instructions for X3 are here.

Once all the 02_SONAR_X3 parts are downloaded, starting part 1 will present the 64bit and advanced install options.

44 minutes ago, User 905133 said:

The problem that I generally have with the online search is that it usually lists links and descriptions of those links for pre-CbB products.

The website does not have CbB indexed. Until that is done, don't expect to see any of the CbB links in search results.

For many pages, changing the product in the search result urls to Cakewalk yield the current pages. For example, searching for prochannel shows the following url

https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=ProChannel.01.html

replacing everything after "product=" in the url to the ampersand with Cakewalk results in the CbB page

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=ProChannel.01.html

Of course, the older versions have fewer pages in common with CbB. That said, when the product substitution in the url does not return the correct page, the old page may still be of value. Often the information still applies. When it does not, the location of the page (IOW, the path immediately above the navigation buttons), section headers and terms used in the page provide clues on where and what to look for in the current documentation.

Finally, if a subject is not found, it may be in new features. New features are best reviewed by scanning that part of the help directly.

Like https://www.softube.com/products/harmonics?utm_source=Softube+Newsletter&utm_campaign=b3a3e4e3a9-EMAIL_CAMPAIGN_2019_11_19_02_45_COPY_03&utm_medium=email&utm_term=0_97a92143ea-b3a3e4e3a9-33320817#/

says:

Quote

All of the grunt, none of the drawbacks.

Make sure to only add folders that contain VST2/3 dlls.

Never duplicate folders. In this scan path

the second path is a duplicate because it is already in the scan path as it is under the first path. That said, check exactly where the spicy guitar dll is located. That is the path that should be scanned. Added unnecessary paths and scanning areas that do not contain plug-in dlls can create problems.

Usually VST2 plug-ins have an option in their installer for VST2 install path and display where the plug-in will be installed. You could uninstall then reinstall the plug-in and see where the plug-in dll is actually installed. It may be in one of the first two paths in the image or it could be somewhere else.

As far as CbB and its scanner are concerned, it does not matter where plug-ins are installed as long as the plug-in dll is in the scan path.

A scan log may help. The option is shown on the preference screen above.