scook

Fortunately, the disk space needed is predictable. On this help page is a table of MB per minute for a variety of sample rates for 16 and 24 bit audio clips. Actually the table does not help in this case, if you are storing audio as 32 or 64bit floating point. The formula is clip duration * sample rate * bit depth * number of channels in the wav = clip file size. For example 1 minute of a stereo clip recorded @ 44.1kHz 32bit uses ~20.187 MB. 64bit uses twice as much.

There is no need to set the external as the default project location. If you want to do so, it is the Project Files entry in Folder Location in Preferences (see the help link above). That said it is possible to create projects on any drive available to the DAW regardless of the default setup in Project Files. The Global Audio Folder is where audio is stored when not using per-project audio folders. It is also where audio is temporarily stored if a project is created and used before naming the project. Once named, with per-project audio folders, by default the audio is stored in a folder where the project file is written.

If there is only one internal drive that is as good as it gets. If the projects are small, using an external drive for recording may work.

The defaults are shown in the help I linked above.

Not sure if I would go to the trouble of re-installing especially if the DAW is working. Per-project audio folders will go a long way in keeping projects and related data together. May want to review the folder locations and audio data settings in preferences.

Per-project audio folders are the way to go. It is the default and has been for some time. Don't even need to bundle, rar or zip projects for archiving. Just drag the project folder to the new location. The new location could be a local HD or elsewhere. The project folder should have at least one project file and the associated Audio folder. When projects are created using the default per-project audio structure, the project folders are portable and may be run from any local drive. Yes, re-pointing the Global Audio Folder may work for you. Usually the DAW asks where the audio is when it cannot find it during project open. One thing about using a non-default Global Audio Folder, upon starting the DAW if the the folder is unavailable, the program silently switches to the default and updates preferences. This can be a real PITA when using external drives. I always use a different internal drive for current projects and create a directory junction pointing C:\Cakewalk Projects\Audio Data to the actual physical location and leave preferences alone.

If you were not in the habit of using per-project audio folders, all project wav files are stored in the Global Audio Folder. While a user may locate the folder anywhere, the default has been the same for years - C:\Cakewalk Projects\Audio Data

The optional dll was for Quicktime video support in the DAW. Other than that, nothing shipped with SONAR that used it. Of course, it was 32bit only because Apple never ported the Windows dll to 64bit. Don't recall when it was discontinued in SONAR. My guess is X1. I moved to 64bit with X1 so I cannot say for sure when they stopped including the dll.

Does not matter Renaming ttsseq.ini just like aud.ini and cakewalk.ini is a way to keep the original file (in case there is a setting you may need to add) while letting the DAW rebuild the file the next time it is started.

Instead of removing the driver, try disabling the device in the Windows device manager

Try ripple edit, here is a similar thread (except about delete instead of insert)

Try renaming TTSSEQ.ini in your user directory. For CbB the default location for the user directory is %appdata%\Cakewalk\Cakewalk Core.

Cakewalk by BandLab includes some FX chains from SONAR which reference plug-ins not bundled with CbB. These two came from Project 5 and were included with quite a few versions of SONAR, however; they are not available at this time. For a complete listing of what CbB includes see this.

From Use the Uninstall menu option in BA to uninstall Cakewalk, then the Open button will change to allow re-install.

Both DAWs share quite a few files. It makes no sense to have multiple copies of the same plug-ins. By default TTS-1 installs in "C:\Program Files\Cakewalk\Shared DXi\TTS-1" There are several other "Shared" folders under "C:\Program Files\Cakewalk" that both DAWs use. For GM, I use TTS-1. Never needed to look for another plug-in.

Both DAWs use the same copy of TTS-1 so if it does not work in SONAR, it makes sense that it would not work in CbB too. I am guessing the DAWs were installed after the Win10 upgrade. If not, the Windows upgrade may have messed with the registry. If this is the case, I would consider re-install both DAWs starting with Platinum.

SONAR Platinum has not been available since Oct 2017. Is this the first time you have tried TTS-1? This can happen when install fails but there are error message displayed during the install. May want to ask support@cakewalk.com. This is normal. Most ASIO drivers have a fixed bit depth.

The only thing bundled for AD2 in Platinum are instructions and an activation code. The XLN installer is only available from the XLN site. Once AD2 is activated, installations are managed in your XLN account. While a Melodyne installer is included with Platinum, the latest installer is in your Celemony account. Both XLN and Celemony permit 2 concurrent installations. If you are not going to use the old PC, you may want to take the machine out of your account on their sites.

If versioning is enabled, depending on what has happened since that last good version, it may be possible to revert to something a little better. I usually set up preferences to version by the clock only and set changes to zero so that excessive changes to not overwrite versions too fast.

Could be input echo is not enabled on the track. Category tags are a VST3 feature. Other formats do not have this feature. When category support was added to the DAW, the developers added quite a few DX and VST2 plug-ins to the database where this information is stored. When a plug-in cannot supply category information, the scanner looks in the database. I believe Amplitude 4 was released after this database was built so the VST2 may not be in the database. Plug-ins that have no category information are placed in the Uncategorized folder. It is possible to modify a plug-in's category assignment(s). Here is the help page.

No special action is needed by the user regardless of the version already installed. BandLab Assistant will download and install the full version of CbB when it detects a version that cannot be updated with the smaller update release. IOW, BandLab always updates to the latest production release with which ever installer (full or update) it deems appropriate.

BandLab Assistant has nothing to do with the Early Access program. Here is more info on how the Early Access program works.

My guess is you are thinking about R-Mix SONAR which was bundled with SONAR X2 Producer.

That is what I thought, my post was intended as a reply to the post made by @Heinz Hupfer immediately before my post. I should have quoted it.

I checked several language settings - it appears the localization work has not been done for this early release. Early release preferences only updated in the English version.