scook

Yes, if you are willing to edit the registry. This may be performed with regedit or the Launchpad tool I wrote.

If the projects have the same name, I don't believe it is possible using the Start Screen but Launchpad shows the project path.

The greyed out value next to the 64bit DPE check box is driver bit depth. Most ASIO drivers use one bit depth so this drop down is disabled. Moreover, driver bit depth has nothing to do with sample rate or the problem reported. FYI, this is not the record bit depth which is set on the File Audio Data preference page. This too does not affect clip playback speed but should no lower than the driver bit depth.

Choice of driver is made on the Audio Playback and Recording preference page, however; changing to a different driver mode is likely not the solution.

The choice of 32 or 64bit engine does not affect clip playback speed. Neither does creating projects on 32bit software and playing back on 64bit software.

One thing that can cause the DAW to play clips too fast is the sample rate of the clips is lower sample rate then the sample rate reported by the clip headers.

This can happen when the DAW sends the audio interface (currently running at a lower sample rate) a request to change sample rates and the interface ignores the request. When recording the DAW writes the data at the interface sample rate but the clip headers are set to the DAW sample rate.

One way to see if this is what happened here is modify the clip headers. One such tool I have used in the past to preform this task is sox.

Using sox to change a clip header to 44.1k is

sox -r 44.1k clip.wav fixedclip.wav

If loading the fixedclip.wav into a Cakewalk project running at 44.1 plays OK, it means the project was actually recorded at 44.1k.

If the fixedclip.wav runs too slow check higher sample rates.

Given the state of the two check boxes at the bottom, the folder associated with the image does not appear to be compressed or encrypted.

AFAIK, BandLab does not provide individual files for download. 

@jon sasor [cakewalk] first suggestion was a clean install.

I suppose you could contact support@cakewalk.com and ask them but my guess is they would agree with Jon's recommendation.

Could not tell whether you verified the PC module folder was compressed or not. I have seen a few reports over the years of odd plug-in problems that were caused by compressed folders. Some users knowingly tried compressing folders, others only found out the folders were compressed upon inspection.

This is true.

The original ProChannel had one slot for each type of module. It worked like reskinned PX-64 and VX-64 plug-ins. It was possible to change the order of the effects and turn individual effects on/off but there was no way to have multiple copies of the same effect in the same PC. As a result, the original PC modules were written to allow only one instance of each type of PC module per PC. This is why the PC4K S-Type Bus Compressor and PC76 U-Type Compressor cannot reside in the PC at the same time. The original PC had one compressor slot.

With X1 Producer Expanded the old fixed slot design was changed to allow multiple instances each type of module, however; the original PC modules were not rewritten to take advantage of this feature.

The Q&A section is the only one setup with that feature. It also has a slightly different layout that is less geared toward discussion.

For the rest of the forum consider adding [Solved] or the like to the subject when a topic has a resolution.

The only reason to run Cakewalk as administrator is if you are using old (XP era) plug-ins that access parts of the drive or registry that require elevated privileges on newer OSes. Even running these old plug-ins, often it is possible to either install them in a user writable location (for those writing into the install folder) or change the permissions on the disk or registry to get around the problem.

Unless you have plug-ins that require elevated privileges, there is no need to run CbB as administrator.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.08.html#1294603

Modifications to registry VST inventory entries made using the plug-in properties dialog.

VST reset does not affect plug-in layouts

Other than exclude list and plug-in layout management all VST operations should be performed in Preferences. The Reset button is right of the Scan button. The reset function clears and rebuilds the VST inventory.

Cakewalk did not offer physical media for Platinum. You will have to create the disks yourself.

The installers are available in your old Cakewalk account.

Addictive Drums and Melodyne  are managed by their respective companies.

XLN Audio has a universal installer for their products. It is available at their site

Melodyne should be downloaded directly from your Celemony account.

With the exception of these two products, the rest of Platinum should be installed using the Cakewalk Command Center. The installers used by the Cakewalk Command Center are the same as the installers in your old Cakewalk Account. They are cached on your PC. The default location is C:\ProgramData\Cakewalk\Command Center\Downloads.

Cakewalk By BandLab can use everything bundled with 64 bit Platinum. CbB started with the Platinum code base so the DAW is very similar to Platinum except it does not include most of the plug-ins and content bundled with Platinum. Of course, CbB has been updated regularly since BandLab purchased the code.

Currently BandLab recommends performing a full install of SONAR Platinum then install CbB.

Yeah, it's not a 2020.01 issue.

It is strange.

Uninstall CbB and reinstall. The uninstall option is on the menu to the right of the CbB open button in BA. This will force a download of the full 2020.01 installer and should get the PC modules back. It will also insure they are the latest versions (in case something was updated since 2017).

By default the Tube Saturator (PCS-CakeSM.dll), PC4K S-Type Bus Compressor (PCS-BusCM.dll) and PC76 U-Type Compressor (PCS-NukeCM.dll)
are installed in C:\Program Files\Cakewalk\Shared Utilities\Internal

As  @jon sasor [cakewalk] mentioned the path is not shown in VST preferences but is silently added when scanning (although it is visible in the Plug-in Manager scan path options).

This path is stored with the VST Inventory in the registry. For example, for CbB the path is in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST\VSTInternalPath

X1 through Platinum have a similar record stored in their VST Inventory area.

I believe these plug-ins could go missing if Platinum is uninstalled after upgrading to CbB.

If the definitions are they way you like them in X3 then

• rename the master.ins file in %appdata%\Cakewalk\Cakewalk Core
• copy the master.ins from X3 folder in %appdata%\Cakewalk into %appdata%\Cakewalk\Cakewalk Core

The X3 folder is product specific so it could be SONAR X3 Producer, SONAR X3 Studio or just SONAR X3 depending on the version you purchased.

Plug-in Properties is in the drop down above the Plug-in UI.

The Plug-in Properties dialog is available in the Plug-in Manager too.

Another way to make low end mono using M/S EQ

Do not use the Microsoft GS Wavetable Synth. It is likely the major cause of the delay you are experiencing. In fact you may as well disable it.

Instead use soft synths instead. Rather than adding a MIDI track try adding TTS-1 or any other soft synth to the project using the Add track menu. See the To create Instrument tracks section on this page.

Unless you need to send MIDI to the soundcard, disable it. Even if you do use the MIDI output, for now it may be a good idea to temporary disable it and see how CbB sets up TTS-1.

Adding soft synths to a project may be done in a variety of ways. Different methods have different ways to add (or in this case not add) tracks to the project.

Several use the insert soft synth options dialog. This dialog has check boxes to control which track types are added for the synth.

The add track menu has its own option settings. Midway down the page is the To create Instrument tracks section.

Regardless, it is easy enough to point an existing MIDI track to a synth and delete the newly created track(s) using the MIDI track output drop down.

A complete synth routing includes at least one MIDI track and one audio track (or an instrument track which is a hybrid track consisting of a MIDI track and an audio track).

To create a new project from a MIDI file, open the file using File > Open from the main menu. If the MIDI output section in preferences has nothing enabled, CbB will automatically add TTS-1 assigning the appropriate instruments to the MIDI file.

It is possible to add a MIDI file to an existing MIDI track using File > Import > MIDI but import strips out the MIDI tempo data.

Run the standalone version of Melodyne and  update it from there

or

Set the check for update in the Melodyne help menu to manual.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.10.html

When documented features seem to be missing the first thing to check is the Workspace setting.

The first image shows the Workspace is set to Basic.

The Basic Workspace does not include the Video view.

Try setting the Workspace to Advanced, None or create your own.

could be related to this thread from the old forum.