scook

I guess the 64bit version of X2 did not get installed.

No big deal, unless V-Vocal is needed.

All the 64bit plug-ins including R-Mix may be installed using the advanced install option without installing the DAW core. Using advanced install for plug-ins only does not require re-installing CbB.

If V-Vocal is needed, a minimal installation along with whatever plug-ins would be required (video below). Doing this requires re-installing CbB to restore the shared components.

Running uninstall for 32bit SONAR does not affect 64bit installs but may affect your ability to open old projects.

Projects using 32bit plug-ins that have no 64bit version may load with the plug-ins missing.

If the 32bit VST plug-in is available, the DAW will load it in BitBridge. 32bit DX plug-ins cannot do this so go missing if there is no 64bit port.

The 32/64bit project port loop

• Prep the project in a 32bit DAW with plug-ins that are known to have 64bit versions. Remove and replace all 32bit only DX plug-ins. 
• Load the project in the 64bit DAW and verify,
• Repeat

Now if it's an R-Mix replacements you are looking for.... that is something else entirely.

1 hour ago, T-Boog said:

Anyway, I thought the safer buffer size is supposed to cause less probs on playback cause it has more time to look ahead.

Extreme settings, large and small, can be difficult for software to manage often resulting in unwanted artifacts such as clicks and pops.

This is not the same as the "look ahead" most often used to describe the buffering used by plug-ins to do their job. Driver buffer settings are separate from plug-in look ahead buffer requirements.  Plug-ins that need look ahead buffers manage it themselves. Some are user adjustable.

The have been no plans announced for a free IPad version any product from Cakewalk.

If you wish to run a free BandLab Technologies DAW on your iPad use BandLab.

Projects made in BandLab may be shared with CbB, Sonar and Next users.

As you figured out Aud.ini is does not affect the MIDI driver mode.

So how to figure out where this value is stored.

I could not remember but since Aud.ini is not a contender this usually points to the registry. 

There are two possibilities:

• HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk
• HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk

The CbB specific values are stored in Core under these paths.

To test if this value is stored in the registry, I

• Exported both registry entries using regedit
• Changed the MIDI driver in preferences
• Exported the registry entries again
• Used diff forcing a text comparison of the registry exports and 
• Determined the MIDI driver value is stored in CoreMidi in HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core

The values for CoreMidi are

• 0 for MME
• 1 for UWP

If I had no way to figure this out, a clean install of the DAW includes removal of the registry entries. This would solve the problem too. Be aware that step nine of the clean install process may result in the loss of 3rd party plug-ins. Consider moving the VSTplugins folders out from under these paths to a safe location before performing this step

Quote

Open the following directories and delete their contents: C:\Program Files\Cakewalk and C:\Program Files(x86)\Cakewalk

https://www.sweetwater.com/c703--PCI_Audio_Interfaces

All audio FX plug-ins that use MIDI data for control are setup the same way in CbB.

Just now, Traveler said:

I've started keeping previous versions on my hard drive as a backup.

A good idea in general

Yeah, I've resigned myself to using them. 

This one was a pleasant surprise.

Is the DAW excluded in the AV software?

7 minutes ago, Razoryhoney said:

so throw CbB on Win 7 Desktop and try it out???

Why not?

At a minimum you will get bug fixes for the shared files used in X3. This trick used to be one recommended by support.

Just remember when working with multiple products based on SONAR, it is important to install the most recent product last. This is to insure the most recent version of shared files are used by all the DAWs.

Testing on Win7 stopped some time ago but there are Win7 users running the DAW.

6 minutes ago, Razoryhoney said:

I specifically purchased x3 so I could utilize the COMPING track feature so does the CbB have that feature as well?  

yes, see Comping

I'm going to Vegas

seriously, KORG has a colorful past with their VST3 implementation

I turned off automatic VST3 migration back in the SONAR days.

prefer to handle migration on my own, thanks.

capture a minidump for the devs

8 minutes ago, Colin Nicholls said:

Yes, that box is checked :-). Then I realized that the installers put both versions on the disk so that couldn't be it.

yes the migration may the problem if the old project used VST2

Try turning off VST3 migration and see if the new VST2 works.

If it does not, you may be able to manually update the projects but it will require a little dll/vst3 swapping

If this is a VST3 migration problem that is between Noel/KORG.

If you are not getting minidumps, try setting ExceptionHandlingSeverity to 7 in Preferences > File > Initialization File.

I have been playing around with ELECTRIBE-R and KAOSS PAD VST3s for the last couple of days without incident.

Would take me some time to find a project with M1 in it.

Is VST3 migration enabled in CbB? If so, do you think the old project used the VST2 plug-in?

Do you regularly clear out the KORG Software Pass folder? If not, the old installers should be there.

Freezing a track can considerably lower CPU and memory requirements for a project. Frozen synths no longer need to compute audio from MIDI data and FX plug-ins no longer have to do their work.  All the synth and FX plug-ins that are frozen with the tracks are rendered to audio and completely removed from memory. The frozen tracks are now audio clips are ready to play.

Streaming audio in a DAW is a very efficient operation and does not require much CPU power or RAM with the audio clips buffered as they are read from disk.

Freezing a single instance of TTS-1 is not likely to show much impact on a project.

That said, freezing reduces the number of things that can go wrong when playing a project because fewer things are happening. This can be a bonus when playing live as the less work the DAW has to do the more predictable/stable the performance will be.

2.0.10 is the latest production release

2.0.13 was pulled almost immediately after release, It's OK to use but was not supposed to be released.

11 minutes ago, mibby said:

I'm glad you posted @Aaron Robinson!

me too

Looks like ripple edit is enabled

16 minutes ago, Base 57 said:

Be sure that Input Echo is turned on for each instrument track.

Yeah, best when getting fancy with MIDI routing to disable Always Echo Current MIDI Track and get familiar with manually controlling input echo. 

"Always Echo" is one of the few defaults I still turn off and leave off but if one keeps it simple, "Always Echo" is convenient.

MIDI input assignments in CbB are either all channels (Omni) or one channel for a MIDI port.

Code42 notemapper is a nice tool. Been around for years.

CbB drum maps may work too. Use the Track Inspector (MIDI tab "T" below) output drop down (between "I" and "J" below) to change the MIDI output to the drum map. Drum maps need updating along with their name as they are not exclusively for drums.

I needed to update KORG Software Pass to v1.2.6 and found M1, WaveStation, MS-20, PolySix , MonoPoly and MDE-X were all updated to v2.4.0.0

AFAIK nothing has changed since this post

FBM has given away several decent plug-ins over the years.

Cakewalk Sonar is intended as a replacement for CbB.

It is based on the same code base CbB  and SONAR before it.

The product in still in development so the following is all speculation. 

Cakewalk Sonar will be handled like all the upgrades in the past similar to SONAR to CbB, The file organization and workflow should reflect this.

WRT file organization, there will be product specific folders for the program, programdata, content and appdata. 

During installation there will be an opportunity to migrate settings which I will decline as has been the recommendation for years. Instead, I will take all defaults and modify the new DAW based on my old setup but only after I see how it runs with default settings. Some prefer to migrate settings.

Both Cakewalk Sonar and CbB will be available using the same set of "Shared folders" containing the plug-in manager, VST scanner, Pro Channel, DX plug-ins, etc updated for Sonar backward compatible with CbB and older products based on the same code.