scook

If this is the original project (IOW not recreated from a bundle or a copy created using "Save As") the original audio clips may be in the audio folder.

IDK, have not played with the plug-in. FWIW, the Sonitus Multiband (bundled with CbB) may be used that way.

works for me but I usually send people to the thread in this forum https://discuss.cakewalk.com/index.php?/topic/4155-updated-several-utilities-for-cbb/. It contains a link to my CbB/SONAR Google page which has tools, themes and other stuff. The thread also serves as the discussion/support page.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.08.html Reviewing the new features section of the help can be a time saver

Yes and your Huge Book of Cakewalk by BandLab Tips (actually the old 2 part SONAR version) was one of the resources I reviewed before posting in this thread.

Change the beat count to the left of BPM in the Loop Construction View, Sometimes the program gets the count wrong.

Correct because is not the same as using File > Open to open the MIDI file or dragging the MIDI file into CbB without a project open. Only these operations autoload TTS-1 when no MIDI output is specified. Import loads part of the MIDI data from a MIDI file (the tempo data is stripped during import) and does not autoload TTS-1.

It works from either end. Uses the same hot spots as slip edit.

The installers always update the factory supplied templates but only in the default folder location. It has been this way for a long time (well before CbB). So... Either do not modify the factory supplied templates (IOW try to create template names that Cakewalk will never use) or use a custom location. I do the latter and have never lost a template regardless of the names used. While basic.cwt is the factory default, any project template may be designated as the default by clicking on the star in the upper left of the template image in the Start Screen or selecting the template and clicking the Set as Default Template button in the New Project dialog.

With the smart tool, CTRL+SHIFT+drag will stretch a clip speeding it up or slowing it down without affecting pitch. Here is a video showing a clip and the BPM of the clip in the loop construction view. There are a couple of other ways to stretch a clip documented here. The original BPM is 138 Then using the smart tool CTRL+SHIFT+drag to 90% The BPM changed to 153.047 and the clip plays faster at the same pitch. Note: Using the percent change the math is not exact because the value is displayed as an integer. The calculations are more precise than the percent shown. FYI, in CbB, the stretch algorithms are set in preferences.

If it is not a plug-in, the DAW may be waiting on audio interface. Try turning the interface off and on. Plug-ins won't show up in the Task Manager because they are hosted in the DAW or in the case of 32bit plug-ins when running a 64bit DAW a separate 32bit server.

If there is no external MIDI hardware to generate the sound, the best solution is make sure no MIDI output devices are selected in preferences. When no MIDI output devices are selected in preferences, opening a MIDI file from the main menu or dropping the file onto CbB without a project open automatically adds the TTS-1 synth configuring the plug-in to play the file. This is preferable to using the Microsoft GS Wavetable synth.

The cakewalk.ini along with the rest of the file in "C:\ProgramData\Cakewalk\Cakewalk Core" are the master files that are copied into "%appdata%\Cakewalk\Cakewalk Core" (a.k.a the user directory) when CbB is run for the first time. CbB does not rely on the files in "C:\ProgramData\Cakewalk\Cakewalk Core" at run time. Instead the program read the data from the user directory. It is best to leave the ProgramData files unchanged as they may be used to restore the program to factory defaults. Users should only modify the contents of their user directory using the preference screens whenever possible.

The cakewalk.ini used by CbB for a particular user is in %appdata%\Cakewalk\Cakewalk Core Normally the user who's folder this is has full control over the file. No special action should be needed to read, write, delete or rename the file. The recommended method of modifying this file is using the Preference screen shown above.

Unbind removes user created shortcuts To "unbind" factory supplied shortcuts, in the Global Area bind the shortcuts to the function Do Nothing: Use to block pre-defined accelerators

The advantage to DPLE at the time was a smaller memory footprint. Given the machines available when SONAR 7 was released this could have been important. Like the full DP, DPLE is more than a single dll. While simple VST2 plug-ins may be installed using a copy process from one machine to then next, as a rule, if a plug-in has an installer it is best to use the installer. A simple copy process cannot add registry entries or provide other setup activities that may be performed by an installer. DPLE has numerous support files and registry entries so this would be a case where an advanced installed of a 64bit version of SONAR containing the plug-ins is the best solution. It is possible to avoid the standing BandLab recommendations regarding SONAR installation prior to performing a CbB install...sure. It all depends on what the user expects to find after performing the CbB upgrade. If it is ever necessary to actually install an older Cakewalk DAW after installing CbB, the old installer may overwrite some of the contents in the shared folders. If this happens it may be necessary to uninstall/reinstall CbB to get the latest shared files back. Not that big a deal but may be avoided with a little planning and careful building of a new install. This is why in other threads where user mentioned wanting to install things like V-Vocal - there is an order to the install process along with suggestions about the installation options to take.

BandLab Assistant uses an internet connection to download/activate/reactivate new Cakewalk by BandLab installs and updates. Reactivation happens any time CbB is updated. The is no requirement to update but reactivation must happen at least every 6 months. An internet connection is not necessary to run CbB.

Starting with hotfix build 68 for CbB 2019.09 quick group is disabled if no tracks are selected. Select the instrument/MIDI tracks then hold the CTRL key and perform the input change (or any other quick group supported action).

BA installs and activates CbB. Without activation CbB will not save projects. Currently activation must be renewed at least every 6 months. BA renews activation with every update.

In the future consider editing the OP and adding [Solved] or a similar notation to the subject when an issue is addressed. I took care of this one for you. Thanks sc

Try holding down the SHIFT key while starting CbB. This should add the missing files to your user directory.

While waiting from someone who owns an e-drum kit to reply this may get you started. According to p10 of the TD-17 Owners manual from https://www.roland.com/global/support/by_product/td-17kvx/owners_manuals/ the TD-17 brain may be connected to your PC via USB. It is a class compliant device so no driver is needed to send MIDI to the PC. Once configured according to p10 of the manual and connected to the PC, CbB should see the TD-17 brain in MIDI preferences. Unless you plan on using MIDI to record the sounds from the brain consider just selecting the MIDI input and do not select any MIDI output. With the device enabled in CbB you should be able to add a MIDI track and record the kit. With MIDI recording verified now comes the mapping exercise. There are several ways to do this. You will need to know what the drum kit is transmitting and what the drum VST expects. The notes sent by the kit pieces may be set in the TD-17 brain. The Owners manual covers this in the Customizing a Kit section starting on p14. According to p17 the MIDI note assignment is in the Other menu. If you prefer to use CbB to handle the mapping you can use either the Transpose MFX (add the plug-in to a MIDI track and hit F1 over the plug-in UI to read its help) or the drum map manager. You can either use the TS-17 documentation or simply record the kit pieces too determine the incoming data. Once the data for the kit is recorded you will need to add the appropriate notes to the map for the drum VST (the note data will be in its documentation). There are not many videos about the process. Here are a couple https://www.blades.technology/music/daws-sonar-and-studio-one/sonar-drum-maps and While recording you may want to monitor the drums sounds coming from the brain rather than the drum VST to avoid the delay added when monitoring the drum VST from the DAW. This may be done by adding the audio outputs from the brain to you audio interface or mixer.

Usually the vendor or manufacturer of the software will provide this information. Try contacting the support group of the company that sold the software.

Are the CC's implemented as automation in the track view or in the Controller pane of the PRV?