scook

Currently, selection length is displayed in the large Export Module

That or use one MIDI track and a drum map routing the data to up to 128 synths along with an equal number of audio tracks.

I consolidated all my DP, Rapture and Rapture Pro sample libraries into one big folder several years ago. Since that time, I have built a couple of machines and have not relied on installers for programs or samples. Instead, I use the copy process detailed above along with directory junctions pointing to the Rapture Pro sample library for DP and Rapture. While I have not tested all 20000+ programs I am reasonably certain the method works. Before posting I checked a couple of the Holiday Pack programs.

Native VST support was added in SONAR 6. SONAR 4 used a VST-to-DX adapter.

Sfz files mostly contain instructions to the plug-in about where the samples are located and how to play them. Rarely do they contain the actual sounds used by the plug-in. In DP like all the other Cakewalk sfz engine synths, sfz files are part of a hierarchy used by the plug-in. Programs may contain multiple sfz files which in turn may reference multiple samples. IOW for a package like the "Holiday Pack" to work there are usually three parts installed: Programs - these go in "C:\ProgramData\Cakewalk\Dimension Pro\Programs" Sfz files - by default these are found in "C:\Program Files\Cakewalk\Dimension Pro\Multisamples" Samples - by default these are also in "C:\Program Files\Cakewalk\Dimension Pro\Multisamples" If you have access to the old machine, copy the entire "Dimension Pro Holiday Pack" folders from "C:\Program Files\Cakewalk\Dimension Pro\Multisamples" and "C:\ProgramData\Cakewalk\Dimension Pro\Programs" After copying both folders open up the DP program browser and click the F5 key to refresh the list.

Yes, either with the MFX Event Filter plug-in forcing the channel using the channel drop down in the track or a drum map

I might have made the process sound smarter than it really is. The DAW defaults to the first MIDI output selected in preferences. By going to the Add Track menu and selecting TTS-1, the plug-in is added along with the instrument track to send the plug-in MIDI and receive audio back from it. The DAW does not natively contain a synth engine to interpret MIDI data into audio. This is a job for plug-ins or external hardware synths. It has always been this way. Cakewalk includes several synth plug-ins and all PCs contain the MS GS Wavetable synth, a very basic GM hardware synth. Generally, if one does not have other hardware synths, it is best not to rely on the MS GS Wavetable synth instead use TTS-1 for General MIDI and have nothing selected in the MIDI output devices preferences. When no MIDI output device is selected in preferences, upon opening a MIDI file the DAW will automatically add and setup TTS-1 to play the MIDI file.

The difference between inserting a MIDI track and the Add Track menu is adding a MIDI track does not necessarily result is MIDI data going anywhere useful. The DAW makes a guess where to send the MIDI data, but this may not be very helpful. by default, the Add Track menu adds the TTS-1 plug-in along with an instrument track. An instrument track is a one-track presentation of an audio+MIDI track pair to handle the I/O for a synth plug-in. Consider browsing the tutorial section of this forum. There are quite a few videos that may be helpful.

If antivirus software is running, make sure to exclude at least CbB.

To monitor any plug-in that has no data in its tracks must have input echo enabled. Input echo is not necessary when tracks have data because the data is driving the plug-in. Input echo may be enabled on as many tracks as necessary, but it is important make sure the appropriate inputs are set for all tracks. That said, keeping input echo to a minimum is a good idea. It is very easy to have unwanted data coming into a track with a bad input setting.

Not sure what settings you are referring to, but the first error indicates a re-install. The second error is a setup problem.

If the install option was missing, it means the clean install instructions were not followed and the registry entries were not removed. Clean up the registry and the re-install process should work.

It works fine. Cakewalk is on the list of supported DAWs. From https://vcvrack.com/Rack

If any plug-ins have "Enable MIDI Output" selected, the data from those plug-ins may be recorded on any track with their input set to "All Inputs > MIDI Omni". By default, any synth that can send MIDI data has "Enable MIDI Output" selected. To see if a plug-in has "Enable MIDI Output" selected, open the VT2/3 drop down in the standard header above the plug-in UI.

Are you reviewing the data in the Event List View?

If this is the error I am thinking of, it means some other process is preventing Cakewalk from creating files. Generally, it is a good idea to post an image of the English version of the error message instead of interpreting them. The problem may be antivirus or antimalware software blocking disk writes. Make sure these programs are up to date. Years ago, there was a rogue antimalware program called ByteFence that was secretly installed with some software. It is known to cause this problem. The solution in this case was uninstalling ByteFence.

no

The notes supported by SI Drum Kit are documented in its help. To open SI Drum Kit help, open the plug-in UI, click in the UI and hit the F1 key. The note map is in the "Using the Drum Pads" section. To play a side stick requires MIDI note 37 so, either the controller must send note 37 or some note sent by the controller must be transposed to note 37 or the notes must be entered some other way such as directly keying in the notes or dragging some existing notes to the appropriate value. Often drum controllers may re-assign the notes triggered by the kit. Cakewalk has two methods of mapping incoming notes to different values the MFX transpose plug-in and drum maps.

I see you have installed Cakewalk in the past. Are you using the in-app update process, BandLab Assistant or the Cakewalk Web Installer?

Just like the message says...let HOFA know. The crash is happening in their plug-in. May want to try the VST2 plug-in if there is one.

The old Cakewalk servers are in archive mode. They have no email services running. To reset a password on the old servers requires assistance from support@cakewalk.com For more info see https://help.cakewalk.com/hc/en-us/articles/360021666254-I-used-Cakewalk-a-long-time-ago-but-now-Cakewalk-com-says-account-creation-is-disabled-

If there are any plug-ins in the project the delay may be caused by buffering needed to keep everything in sync. To see if Plug-in Delay Compensation is the cause, click the FX button in the Mix module. If the delay goes away, the cause is one or more plug-ins in the project. Most often these plug-ins need to see into the future, such as certain dynamics processors or require time to perform calculations such as impulse response reverbs. Often plug-ins that introduce PDC have some mention of it in their documentation. It is possible to override PDC on tracks with input echo enabled by clicking on the PDC button in the Mix module.

Is that what the scan log says? I assume is actually "C:\Program Files\Common Files\VST2" and this is in the scan path in preferences.

Given the scant information in the OP, my guess is this is similar to

select a plug-in