scook

It is easy to rename the Step Sequencer either using a drum map or a step sequencer template. I believe we have had this conversation before. One only has to create the map or template one time and the note numbers are replaced with whatever names you wish. Don't let this tiny learning curve dissuade you from a better solution. Drum maps are not hard, they are a boring typing exercise. For this post, I just build the drum map for the the Sitala Clean 808. It is on my Google page at the top under presets. Put the drum map in your drum map folder. The path to this folder is in CbB preferences. After adding Sitala to a project, add the drum map to the MIDI output in place of Sitala. The output drop down for instrument tracks is in the MIDI tab ("T" below) of the Track Inspector, just below "I" in the image below It is easy to add sounds to Sitala. In addition to the library of sounds in BandLab Assistant, CbB includes drum samples in unexpected places like the kick, snares and tom wav files used in the Drum Replacer. There are quite a free drum samples on the net and one could even rip the samples out of old 32bit plug-ins if they had a desire. Sitala is a much better long term solution than a SynthEdit based drum synth.

Have you tried Sitala with the step sequencer built into CbB?

Stop using 32bit plug-ins and find replacements for the ones that do not have a 64bit versions such as plug-ins developed using the old SynthEdit toolkit.

Resolution when drawing in the PRV is determined by the snap setting. Either use a smaller duration when snap is enabled or turn snap off. Depending on the plug-in, better results may be had with plug-in automation. Automation may also be used for MIDI data as well in the track view.

Best to start looking for replacements for 32bit plug-ins ASAP This error is due to the plug-in with insufficient privileges trying to write to disk. This may be addressed by installing this plug-in in a different folder where anyone may write, changing the permissions of the current folder or running the DAW as administrator.

BTW, if you have not cleared out the Cakewalk Command Center download folder, the installers are on a local drive. By default, they are stored in C:\ProgramData\Cakewalk\Command Center\Downloads the actual location is displayed in the Command Center setup Paths tab. Click the gear in the upper right of the Command Center to open the setup. One can save a lot of time by backing them up, installing the Command Center on a new machine/drive and copying the installers into C:\ProgramData\Cakewalk\Command Center\Downloads. The Command Center looks for installers locally before downloading. Will still need a password reset so the Command Center can activate products after install.

Contact support@cakewalk.com for password reset

Yes Yes There is some delay when monitoring through the DAW. How much depends on the I/O buffer setting of the audio interface driver and any plug-in delay compensation for other plug-ins in the project. Also the DAW records the signal at a track's input. This means the signal recorded from the track hosting Guitar Rig is the dry signal from the audio interface. To record the signal after the FX rack requires routing the signal from the track hosting Guitar Rig to another track. This is done by setting the track output or a send to a patch point or aux track. If using a patch point, another track is setup to receive the signal from the patch point. Then record enable the aux track or second track for recording to capture the wet signal. It is a good idea when recording this way to also record the dry signal on the original track.

pls edit the OP and update the subject with [Solved]

I have Boz plug-ins on a couple of machines

rollback installer for 2020.04 to 2020.01 is in

This is what the 2 PC modules look like (the image predates 2020.04, they now have the same preset management as all the other PC modules) The full VST versions include a channel strip (both plug-ins in one container) and a few more features on the compressor and EQ plug-ins.

No iLok, no USB, serial number only. Can't recall how many concurrent installs. I don't believe they count installs.

Not supported by any Cakewalk sfz engine synth including the CSC. These events shut down the synth engine requiring a restart of the project. Try using wheel events either as MIDI automation in the Track view or CC data in the PRV. Set the wheel type in either method using the MIDI envelop dialog.

Other than a drum map here are a couple of tools to try (I have not tested myself) MIDI Notemapper Veloscaler MIDICurve available from https://code.google.com/archive/p/pizmidi/downloads get the latest file called pizjuce_x64_20120111.zip

When features seem to be missing check the workspace menu If set to Basic, try one of the other settings, set it to None or create your own workspace.

Importing a cwb into a project causes CbB to open the file at it would any wav. See http://forum.cakewalk.com/Are-Cake-Walk-Bundle-files-the-Best-Way-to-Save-Everything-m1415907.aspx#1417418

Guessing the FX Racks are not displayed. If this is the case change the workspace menu to Advanced, None or create your own workspace.

If you wish to send the "complete" project with ALL audio whether currently used by the project or not, zip the current project folder and upload the zip to Dropbox. If you prefer to send a clean copy of the project with just the audio referenced in the project (similar to what bundling does), use "Save As" with "Copy all audio with project" enabled to a new drive location. Zip up the "Save As" copy and upload it to Drop box. The choice is yours whether to retain the original project or not. For those having problems with bundles here is a reminder: if a bundle cannot be opened, the audio may not be lost. It is possible to play and edit the bundle as a regular wav file by changing its extension from cwb to wav. IIRC, bundles also support safe mode like regular projects so if the problem is during project load (IOW after unpacking), this may help. That said, bundles are a poor substitute for regular back ups of projects on a per-file basis. Regardless of what the documentation says, bundles are not suitable for long term project storage. They are too fragile. My understanding is the reason bundles are still available is backward compatibility. Since the introduction of per-project audio folders, bundles as a method of managing projects became redundant. AFAIK, since the introduction of per-project audio folders there was one case where bundling was indicated, recreating project files suffering from a bug in audiosnap.

Certain out of scope for this thread but... Instrument tracks are convenient but hardly essential or a significant improvement over an audio+MIDI track pair. There is one time I always use them and that is for "synth" plug-ins that produce no audio such as sequencers. For a "synth" to work in CbB it MUST have a output track. To satisfy this requirement rather than create an audio track for "synth" plug-ins that produce only MIDI data, I use instrument tracks.

I wish this were the case. Unfortunately CbB does not discriminate between actual hardware and virtual MIDI cables in MIDI output preferences. This is why I asked about adding a switch in preferences to always open MIDI files with TTS-1.

What the OP wants to do may be outside the scope of the Basic workspace.

Opening a MIDI file does not use instrument tracks so the solutions I recommend do not either. It is easy enough to create instrument tracks after the fact if that is the preferred layout but they offer little when working with MIDI files.

It could be the OP is not trying to use a different synth though. This may require using the Event List View to remove patch info from the file along with changing the channel, bank and patch drop downs in the track inspector or track so the TTS-1 reassignments stick. I usually remove all this data and set the patches in the plug-in UI.