scook

Cakewalk mixed 32bit plug-ins in the 64bit path if the 32bit version of the DAW was not installed first. A few manufacturers do not provide separate 32 and 64 bit install paths. The list in the VST Inventory Tool above are a combination of those two issues.

True and if the paths are not mixed in the with 64bit paths, removing the 32bit paths from the the scan path (and re-scanning) in preferences works too.

To create a list of 32bit plug-ins using the The VST Inventory Tool mentioned above set the filter drop down to x32 entry a Y in the entry field next to the filter drop down click Submit With the list as a guide, either use the Plug-in Manager to exclude the plug-ins locate the plug-in in the Plug-in Manager. The VST Inventory can help with the category in the Plug-in Manager as there are columns identifying which plug-ins are VST2/3 (Y in the VST3 means a plug-in is a VST3) and FX/Synth (Y in the synth column means the plug-in is a synth). verify the path by comparing the Filename shown at the bottom of the Plug-in Manager to the Full Path in the VST Inventory Tool click the Exclude Plug-in button to hide the plug-in from CbB plug-in list rename the file names as mentioned above. Make sure to run a scan after renaming files. It is possible to delete the files but it is better to leave them installed just in case there are projects that depend on them. The binaries do not take up much disk space.

Not having the plug-in, I can only guess. That is, the plug-in is not activated. Under Settings may be some authorization options. The product must be authorized before it will come out of demo mode. This is an Overloud support issue. Something on this page may help but it may be best to contact Overloud support.

I just looked up the device. I thought it was a USB microphone but see it is an entry level audio interface. Since it does not have a manufacturer written driver, it must use a generic Windows USB audio driver. IOW, this is a class compliant device. The manufacturer offers ASIO4All because some audio software only work with ASIO drivers it may work better with the native Windows driver wrapped in ASIO4All The interface is no better than an USB microphone in this regard. Devices that lack a manufacturer supplied driver are not suitable for most DAW applications. Still it should be possible for CbB to communicate with the device without ASIO4All because the DAW can use native Windows drivers. In this case, it may be necessary to remove ASIO4All. I would not expect much either way from this interface.

It seems strange that no other drive mode works because ASIO4All is not a driver. ASIO4All is a wrapper around native Windows drivers to presents them as an ASIO driver. There should be some indication in the ASIO4All config regarding what Windows drivers it is using. Sometimes ASIO4All must be uninstalled to keep it from interfering with drivers. That said, ASIO4All may be the best choice for this device. In this case, a different device such as a regular microphone (IOW that plug-ins into a separate audio interface) may be a better solution.

I am guessing this means opening a project results in a missing plug-ins dialog because some of the plug-ins in the project have been uninstalled. If so, delete the plug-ins from the project and save the project or start a new project. Any time a VST plug-in is added, updated or removed the vst scanner should be run to maintain the VST plug-in inventory. By default, this is automatically done any time something changes in the VST scan path. The scan frequency may be changed in preferences but for now, it may be a good idea use the default settings. The image in the preference link shows the default settings. When a VST plug-in does not appear after a scan it is usually because 1) the plug-in dll/vst3 file was installed in a folder not in the scan path. This is the first thing to check. Most often the problem with VST2 dlls because there is no standard and a couple of conventions used for where these plug-ins should go. VST3 specifies where plug-ins should be installed so this is less of a problem with them. 2) the plug-in failed during scan. This is what happened initially happened STL Tonality. Plug-ins that fail to scan generally end up in the excluded list. Once the cause of the failure is resolved, manually running a scan with re-scan failed plug-ins enabled often results in the plug-in getting added to the VST inventory. Sometime it is necessary to run a VST reset, this clears the VST inventory and rebuilds it. 3) the plug-in shows up with an unexpected name or in an unexpected place in the plug-in lists. Some plug-ins have an identifier in the plug-in that differs from the name one expects to see. A VST3 plug-in may be tagged in a way that causes the plug-in to show up in an unexpected category. DX and VST plug-ins do not have a category designation by default (although Cakewalk did add some to their database for some plug-ins). Sometimes a plug-in gets identified as an effect when it is really a synth (this is a scan failure - fir this use VST reset) or as a synth when one expected it to show up as an effect (usually a design decision by the manufacturer). Searching the plug-in browser and using different "Sort By" layouts may help resolve these issues. When a plug-in shows up with an unexpected name (rare but does happen), Sort by Manufacturer may help. When a VST3 plug-in has an unexpected tag, searching in the browser and Sort by Manufacturer are good starting points. Also make sure to search and sort both effects and synth lists. I do not have any of the Overloud THU series so cannot say if they show up as different plug-ins or are all the same plug-in with different feature sets. I know from the image above THU was listed at one time as a VST3 plug-in. It may work like TH3 Cakewalk. This plug-in uses the same name as the full product because it also contains a demo of the full product and could be coverted to the full product by adding the appropriate license (of course, the full product is no longer available from Overloud).

Personally, I would add the folders to the media browser, audition from the browser then drag and drop directly into the SI-Drum instrument or MIDI track. That said, here is the way to add folders of MIDI loops to SI-Drums browser. make sure CbB is not running or at least there is no instance of SI-Drums running delete C:\ProgramData\Cakewalk\Studio Instruments\SI-Drum Kit\Patterns\patterns.lst add folders containing the new MIDI loops to C:\ProgramData\Cakewalk\Studio Instruments\SI-Drum Kit\Patterns The next time SI-Drums is loaded, the new pattern folders and MIDI files should appear in the SI-Drums pattern browser. SI-Drums uses patterns.lst to build the browser display. If the file is missing, the synth builds a new patterns.lst file by scanning the folders under Patterns. I would not mix new MIDI files into the existing folders if only because it would make it difficult to restore factory settings without completely reinstalling. But the choice is yours.

Given ASIO4All is a wrapper for WDM drivers and the DAW can use WDM drivers directly, see if the DAW works better in when set to WDM/KS driver mode or one of the other non-ASIO modes.

Yes, activation must be renewed at least every 6 months. Usually done when BA updates CbB.

CCC reads data about all versions available for all CCC aware installers for a user from a server side database and uses this as the basis for the rollback lists. When rolling back (or installing) CCC checks if the installer is cached, if found it uses the cached version otherwise it downloads the installer from the server.

At startup CbB looks for audio and MIDI devices. If there are multiple audio devices available, CbB usually does not fail during discovery when a device is missing but there may be something about this particular driver/device. There was no information provided in this thread regarding the hardware other than the OS it was running. Normally, it is a good idea to have any device that will be used by the DAW running before starting the DAW.

There is no "Plugins" tab on BA, there is a settings page which may be what they are asking about. This is found by clicking the gear in the upper left on BA. Although I am not sure if the installer download path is the issue in this case. From the info in this thread, it appears the program is getting installed but fails to launch. At least that is how I interpret There may be some additional information in the Windows Event log regarding the failure to launch.

There is no need to uninstall before rollback - running the old version installer is enough. This is how rollback worked in the Cakewalk Command Center. Starting with 2018-11 if running the previous release of CbB, BA downloads an update installer instead of the full CbB installer. This is a much smaller file and may only be applied to the previous release. BA downloads the full installer only on the initial install and if the installed version is not the previous release. I force BA to download the new full installer for every release by running an old installer prior to running the update.

For the PRV, to restart scroll, right-click anywhere in the timeline. Right-click near the top of the timeline where the cursor changes to a zoom tool will not show a menu. This also works in the Track view.

Yeah, I wonder if any amount of threads like this one will have an impact on new threads regarding roll back. I have on numerous occasions posted a similar solution (and discussed its shortcomings), a tool to manage multiple versions of SONAR/CbB since 2016 and a method to retain installers since CbB was introduced.

No scroll lock key is required https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.21.html

It has always been possible to set the track interleave manually. The change that happened after X3 only affected the default track setup. Rather than default the interleave to agree with the input, interleave always defaults to stereo.

This was how SONAR worked through X3. IIRC, a change was introduced early in 2015 where the interleave was no longer linked to the track input but I do not recall the rationale for the change.

FabFilter recommends against using their mono plug-ins in new projects. Here is an example from the Pro-DS help

Could try adding the entries into the registry. They both look the same. Here is the entry for HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Shared Plugins\Perfect Space Still - may be a good time to look for a replacement plug-in. Of course, the PS IRs should load in any IR reverb that supports regular wav files. The MConvolutionEZ does.

It's not too late to stop using them. The support for 32bit plug-ins is unlikely to improve.

Still on Win10 1809 here. Just loaded the plug-in for the first time in years. Seems to work OK. I stopped using it when I transitioned to 64bit in 2011. I believe the path to the impulses is stored in LastImpulseFolder under HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Shared Plugins\Perfect Space and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Cakewalk Music Software\Shared Plugins\Perfect Space maybe something went wrong with those entries. That said, it not too late to consider using a different IR Reverb. One that is still in production and supported by the manufacturer. Perfect Space has not been updated almost 8 years. MConvolutionEZ is part of the MFreeFXBundle, as the name indicates, the plug-ins are free.

Most of Cakewalk by BandLab may be installed on any drive unless there is another Cakewalk DAW (SONAR, Music Creator...) already installed. If there is an existing Cakewalk DAW installed, CbB will install on the same drive. CbB uses around 100MB of the C drive regardless of where the program is installed.

No it's not just you... But going forward for this & other reasons I'm taking Mr. Scooks advice... Of course, aux tracks like regular audio tracks lack waveform preview. The only way to see the waveform in an aux track is record to the track (just like any other regular audio track).