scook

This is a better link https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=INI_Files.4.html Very unlikely the SONAR page will be updated when CbB Cakewalk.ini variables are updated.

It's the metronome plug-in. Uninstall then reinstall CbB if you cannot retrieve the Groove Player folder and files from the deleted files.

yes

Use copy and paste from the context menu You will need to save the theme under a new name if you are currently using Mercury or Tungsten.

The easiest way to get the old Tool icons is open both the CbB and SONAR theme editors (assuming you do not have the old CbB available). Then locate the images in both editors, I searched for smart Then copy the SONAR image over the CbB image (right-click the image for a context menu) There are now two sets of button images used for the smart tool - one when all options are enabled and another when some of the smart tool options are disabled. Whether you wish to maintain this is up to you. The same process may be used for the Select tool too.

By default the file is empty. Add options and values to it and they will appear in the top window.

1/1.25 = .8

Yes reducing the constants to a single value simplifies the equation making the exercise easier to compute.

Cakewalk Command Center is an install manager created by the old Cakewalk company for some of their products. If you did not have any Cakewalk products and an account set up prior to November 17, 2017 the Cakewalk Command Center is of no use to you.

edit the original post and add [Solved] to the subject

I top and tail after export as part of a finalizing step so don't bother about specifying the exact beginning and end before export. If I wanted an exact export I would make a rough selection on the timeline then instead of clicking in the track view try adjusting the selection markers in the timeline or the values in the large select module. If I were going to export the same selection multiple times I might note the values in the select module and create markers based on them then use the markers as the basis for future selections. There is no need to split clips before exporting a selection,

Contact support@cakewalk.com They will need something to go on to determine your old Cakewalk account name.

The math is correct. Add it to the project and see if this is still needed by the plug-in. It is a nondestructive change so it can easily be modified if necessary.

Check preferences for a custom keyboard shortcut assigned in the Track View area for Open Clip FX Rack

Adding parentheses to aid in reading (960/60000)*50 = 0.8 960 is the default number of ticks per quarter note set in preferences There are 60000 milliseconds in a minute reducing the units in the formula to determine the units of the result ((beat/minute)*(ticks/beat)/(ms/minute))*ms simplifies to ((ticks/minute)/(ms/minute))*ms simplifies to (ticks/ms)*ms or ticks

I so rarely looked at the tool I completely forgot about it preferring to work in preferences and then rarely changing device setup. The Audio and MIDI Setup Tool was in Utilities through 2019.09. It was moved in 2019.11 and renamed as part of the new user setup process. Thanks for reminding me about the change.

You are correct. Starting with 2019.11 latency slider works for some ASIO drivers. RME does not support this feature so I saw no change in slider behavior. Thanks for reminding me,

I am not familiar with a setup tool on the Utilities menu. There is a "Getting Started..." option on the Help menu that walks through setup.

The Mixing Latency fader depends on the Driver Mode selected. It was never used for ASIO mode. It was disabled for WASAPI Shared starting with CbB 2019-11 because the DAW cannot change the value.

Review https://www.cakewalk.com/Support/Knowledge-Base/2007013301/SONAR-X2a-Update for changes that apply to the plug-ins you are installing.

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.