scook

I can't say if this is the case. It was the easiest place I found to scan for changes to Take lanes.

Try holding down the SHIFT key From the release notes Take Lanes/Comping section for 2019.09 https://docs.google.com/document/d/1aFOe_zJrd3x2EnaZ_Jc3iSbZPG2WANiCD4_RP83OjlA/edit#heading=h.qfyobw6rmujo

It's the page called up when clicking Help button on the plug-in UI Most of the other bundled plug-ins have Windows chm help files that are displayed by pressing the F1 key when the plug-in UI has focus.

A common problem when using 3rd party MIDI files with Cakewalk sfz engine synths.

From the 2020.09 product announcement above When complete, the last message has a link to open the download folder.

FWIW, since the addition of the in-app updater in 2020.09 installers downloaded using CbB are stored on disk. Without the 2021.01 installer, one way to re-install the current version is rollback to the previous version. Then BA and CbB will both make the update available. Either way, if I have trouble with the current release, chances are I would rollback before re-running the current installer. Links to the rollback installers are provided in the release announcement. For example, the link to the 2020.11 rollback installer is near the top of the 2021.01 release announcement.

If the Ozone 9 plug-ins are VST3 and installed under the default VST3 folder they should be picked up by the scanner. The scanner traverses all the folders under the paths defined in the VST scan path. VST2 plug-ins installed in the VST3 scan path are ignored. This is by design. In the default VST3 path, only files with a .vst3 extension are scanned. Files with a .dll extension are skipped.

The dialog to the left of preferences shows UA-4FX in the title so my guess is https://www.roland.com/global/products/ua-4fx/

In order to keep multiple versions of Cakewalk installed and switch between them, I find the safest way is always run Cakewalk from Launchpad. If you want to use some other strategy for switching between versions of Cakewalk, that is up to you. As has been mentioned before in this thread: Every release of Cakewalk.exe has an associated version of CW130Auto.dll in shared utilities. Before CbB 2019.09, the dll was backward compatible with older releases of the program. This changed with 2019.09. Starting with 2019.09 the Cakewalk.exe and CW130Auto.dll must have the same version number. Beginning with CbB 2020.04 every new release has an associated rollback installer. For most, this is probably the best way to deal with problems encountered when running the current version. The rollback installers may be successively applied to access any release from 2020.11 to 2020.01.

You could contact support@cakewalk.com They may be able to help you.

The logs appears to be a VST reset. I expected a reset to scan all the dlls. The scanner found 32 VST binaries but claims it scanned none of them. The drive properties General tab at the bottom has a checkbox for disk compression.

That appears to be what the scan log shows. Near the bottom of VstScan.log The log shows a reset was run, the registry was cleared, 32 dlls were found but none were scanned. Is the disk compressed?

BA keeps track of what it has installed. Once an add-on is installed, the install option is disabled. It is possible to edit the registry to clear the install records. This happens as part of a clean install (the link I provided above). I guess the questions now are: Do you want to start over with a clean install? Do you want to just reset the BA install records? Do you want to continue to work the SI issue and assume the rest of the install is OK? If you elect to perform a clean install be aware that step 8 will delete all 3rd party plug-ins under the "C:\Program Files\Cakewalk" folder. If you have any 3rd party plug-ins installed there (usually they would be in "C:\Program Files\Cakewalk\Vstplugins") consider save the folder to somewhere else before proceeding with step 8 and restore the folder(s) after running the CbB installer.

Make sure the plug-ins are actually on the drive. They are a separate install and depending on how the uninstall/re-install was performed, they may not be on the drive. If they are not on the drive, they will need to be re-installed. Did you perform a clean re-install? If they are on the drive run a VST reset with "Generate Scan Log" enabled. It may provide some clue what is going on with the plug-ins.

There have been a couple of posts about the SI plug-ins showing up as FX. Usually manually changing their properties to synth does not work; running a VST reset from preferences might help.

All the controls are always displayed in the track inspector regardless of the track control drop down setting. This drop down default has not changed in years and the setting does not affect TTS-1 operation. I do set the drop to All but my motivation has nothing to do with TTS-1. Do not confuse with a manual available on the internet. In this context, "online" means the help is available on your PC instead of a hard copy. This usage predates the internet. Like most plug-ins bundled with CbB, the help is installed locally on the drive with the plug-in. The default url for the TTS-1 help is file:///C:/Program%20Files/Cakewalk/Shared%20DXi/TTS-1/Help/index_e.htm

This is true but has nothing to do with the list of synths shown in the Add Tracks menu which I suspect is the subject of the OP. It is odd that with no other action I am guessing the layout shown in the Add Tracks menu is "Sort by Category" and not a custom layout and the SI plug-ins did not somehow land in the Uncategorized folder. If this is the case, make sure the plug-ins are still on the drive and they are not shown in the FX plug-ins using one of the "Sort by" layouts.

v2.0.9 - One "final" refinement to the exe/dll sync logic. This update affects only Launchpad. The other tools remain the same.

Using the plug-in browser set the layout to one of the "Sort by " layouts supplied with the DAW and search for "ozone 9" If the plug-ins are there, make sure any custom layouts are updated. Only the "Sort by" layouts supplied with the DAW are automatically updated. If the plug-ins are not found it is likely a scanning issue. Are the plug-ins in the scan path? Verify the plug-ins are somewhere under the paths shown in preferences. Was the scanner run after adding the plug-ins? Do the plug-ins show up in the scan log? To generate a scan log, select "Generate Scan Log" and click the scan button in preferences.

Export is used to create files for use outside of the project. Bounce to tracks is a function to manipulate data at the track level inside the project. If export is creating a single file containing the last song, it may be because the clip(s) for the last song are selected and the other clips are not. By default, export creates a file from all the data in a project unless there is an active selection. If clips are selected, export uses the selection. So, before exporting either selected everything, clear the current selection or click the project radio button in the Export module to export the entire project. My preference is select all the tracks to export then select the start and end time to export. When exporting the entire project, the time-based selection is sufficient. Or Is this a question about the Audio CD burner?

If I had to guess why the audio from the DAW is not working it may be due to the choice of ASIO driver mode in the DAW and the SB ASIO driver. Try the WASAPI driver modes. The MS GS Wavetable works because it is an external hardware synth driven by MIDI from the DAW and is not dependent on the audio configuration in the DAW or the SB ASIO driver.

W10 = Windows 10 OP = original post or original poster If input echo is enabled on the track being recorded, the signal coming from the audio interface should part of the return signal from the DAW. The downside of monitoring this way is the delay caused by converting the DAW signal back to analog and any delay added for the plug-ins to keep everything in sync. The amount of delay depends on the audio buffer settings and the plug-ins used in the project. To avoid this delay, most interfaces provide a way to mix the input signal from the audio interface directly with the DAW signal. This is often referred to as direct monitoring, hardware monitoring or zero latency monitoring. Using this method, input echo is not enabled on the tracks being recorded in the DAW. I took a quick look at the Delta 66 documentation and could not tell if the software mixer supplied with the interface could be setup for direct monitoring. If the interface is capable of direct monitoring, it will be done using the software provided by M-Audio.

Yes, their support could be better. You need to be very clear about the problem and the version needed.

@Noel Borthwick Any help would be appreciated. When I first encountered the problem I had an exchange with @Jonathan Sasor including dumps. If you need new dumps I can send them. AFAIK all their PC modules fail. I have tested every public release since 2.4.83 and they all fail. Fortunately, it is possible to use the old versions as PC modules and still have the new releases installed too,

It is difficult to say whether Softube support their PC modules or not. My experience with their support has never been that great. I reported the problem to Softube in April 2020. Since that time I have received several emails from support with apologies and excuses but no mention of fixes other than to try the current release. When I receive the emails, I report back the results with the release they suggest. To date, all releases newer than 2.4.83 fail the same way. I do not believe they publish links to 2.4.83. At least, the Passive-Active installer I see is 2.5.13. I could not find 64bit Windows installers in the legacy downloads area. They may still provide the installers on request. It is hard to recommend Softube products.