scook

Record Bit Depth is set in Preferences > File > Audio Data As a rule this should be set the same as Audio Driver Bit Depth in Preferences > Audio > Driver Settings Main menu Project > Audio Files shows details about clips referenced in the project.

The new export dialog is not part of the old theme system.

This is the old standalone editor just like the link in the OP.

The first image appears to be CbB/SONAR prior to 2019.07 The second image shows 2019.07 or newer http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.076.html

The link looks like the old discontinued standalone editor not a plug-in. AFAIK Roland never sold the plug-in version, it was available only with X2 Producer. Here are couple plug-ins similar to the X2 Producer version of R-Mix : https://internetmusicsoft.com/frex/index.html https://www.quikquak.com/Prod_MashTactic.html

This is inaccurate. As I mentioned above, the restriction is one I/O driver at a time not one device at a time. There are a few hardware manufacturers that supply ASIO drivers which aggregate multiple devices. RME, Motu, Roland, Presonus, Lynx, ESI and M-Audio have, at one time, supplied multi-device drivers. Generally when a device has this capability, the manufacturer makes it very obvious in both their marketing and technical documentation. ASIO4All like other generic ASIO "drivers" can aggregate devices because they wrap WDM drivers and present them to the DAW as a single ASIO driver. In CbB, WDM driver mode supports multiple devices. Still as noted above, all the hardware must run off the same clock or the signal will get out of sync.

see To replace an instrument in https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.12.html

With the new export dialog (the early release version is currently available) it is easy to create a task to export a project using a time-based selection. Once created, it may be run as often as necessary.

One reason I went with RME is they support multiple devices with the same ASIO driver and a common clock. I bought new but like cars, used may be a better value. Trying to do this with hardware that is not designed from the ground up to work together is a waste of time and money. Here is a similar thread

The limitation to one I/O driver at a time is an ASIO restriction. Other driver modes to not have this issue. Some manufacturers support multiple devices using the same ASIO driver. Those having this feature are quick to advertise it. Regardless of the driver used, running multiple interfaces requires they all use a common clock or the devices will get out of sync. So what you are looking to do has nothing to do with the DAWs capabilities. It is up to the hardware manufacturers.

Working on the C drive and backing up projects to the external using copy or "Save As" is likely the best solution. If your projects do not contain a lot of audio, the may run fine of the external drive though. This may be something you will want to experiment with. Regarding this... plug-ins are not stored in the project. Projects store information about which plug-ins are used and their configuration (think plug-in preset). When a project is opened, the DAW reads the plug-in information from project and sends the setup information to the plug-ins. If, at some later date, a plug-in is not available to the DAW, the project will throw a "missing plug-in" warning and a placeholding is put in the project to retain the missing plug-ins data.

Yes, that contains the project and all of its associated files. It also contains extra stuff like unused audio clips, auto-copy and versions of the project file. If you want a "clean" copy of the project that contains only the audio clips referenced in the project and the current project file, perform a Save As with "Copy all audio with project" checked. This is essential what bundling does except it adds an extra step of concatenating project file and all the audio into a single file. One thing a bundling cannot do is store audiosnap information. Copying and Save As a regular project do not have this limitation. As a rule you are better off running projects on internal drives but you can run projects that are copied or created with "Save As" off the external drive. Keep in mind there is a performance penalty using USB connected drives which may limit the size of projects. Bundles must be unpacked before running.

It's covered in the documentation. Download the pdf if you have not already.

Could this be the the Zero Controllers When Play Stops setting?

All available plug-ins are in the "Sort by" layouts. Switch to one of those and search for the plug-in if it is not in an obvious place. Do not add effects to instrument custom layouts. They will not show up.

You could point to an external drive but I would not recommend it. Generally external drives are reserved for backup.

To create the directory junction to replace "C:\Cakewalk Projects" with "D:\Cakewalk Projects" Move "C:\Cakewalk Projects" to "D:\" Open a command shell as administrator and type : mklink /j "C:\Cakewalk Projects" "D:\Cakewalk Projects" The physical folder may be anywhere and have any name. For example, to relocation "C:\Cakewalk Projects" to "E:\Anything\Anywhere\Any name" steps would be Move "C:\Cakewalk Projects" to "E:\Anything\Anywhere\Any name" Open a command shell as administrator and type : mklink /j "C:\Cakewalk Projects" "E:\Anything\Anywhere\Any name" As far as the application is concerned the files and folders are still in "C:\Cakewalk Projects". Practically any folder may be relocated this way. There are quite a few discussions and worked examples on the old forum. To see the threads search Google for site:forum.cakewalk.com mklink

Pretty sure 1.7M is the approximate file size

If you prefer to use the Desktop for Cakewalk Projects why not change the default project folder to the desktop? Any folder accessible to the PC may be used to host project folders. I do not change the default location in preferences though. I prefer to replace the default folder with a directory junction to the physical location of my top level project folder. In my case, "D:\Cakewalk Project" Each project goes in it's own folder and as long as the Per-Project Audio folder is in the default location, the projects are portable. By default the project audio folder is at the same level as the project file. Except for video files, the default project layout uses relative file references to locate project data. This is why project folders may be moved anywhere the DAW has access. Projects that reference the Global Audio folder use the setting in preferences to locate this folder. All video files and per-project audio folders not in their default location use absolute paths.

There is an option to shrink the size of the QCEQ in the Console View Options menu under ProChannel called Compact EQ module. Read about it here http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22029

Using regedit look for an entry in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO that contains RealTek in the key. If there is one delete the entry. After that CbB should start up normally.

Although the installers for Rapture Pro and Z3ta+ 2 are in old Cakewalk accounts, CCC is the easiest way to install and activate software with CCC compatible installers. CCC caches installers. The path is defined in the CCC setup screen. Click the gear in the upper right of CCC to access setup. Make copies of the installers for future use. The next time, instead of downloading the software again, copy the installers into the CCC cache directory. CCC looks in the cache before downloading if it find an installer, it will use it instead of downloading it again. If this question is about Z3ta+ Classic, it is in the "Platinum Instrument Collection" installer or use an older version of SONAR Producer and run the advanced install option.

If Cakewalk does not offer an install path option, it means the installer detected a previous install. This could be an old Cakewalk (the Company) DAW or a version of Cakewalk by BandLab. Either way, all old Cakewalk DAWs and Cakewalk by BandLab must be installed on the same drive. To install to another drive, perform a clean re-install or use directory junctions to relocate existing folders. Should you elect to run a clean re-install see the following post about step 9 in the clean install process.