scook

ALL DP programs start with a prog file in "C:\ProgramData\Cakewalk\Dimension Pro\Programs". DP is hard coded to look there for its programs. Those prog files refer to data in the mutlisamples folder. Is it possible the prog files made their way to "C:\Cakewalk Content\Rapture Pro\Programs"?

exc = exclude these values

But to answer your question Select the track Process > Find/Replace Unclick all events except for Note in the Event File - Search dialog and enter the Min and Max note to change (ex. A 0) Click OK On the Event Filter - Replace dialog enter the new Min and Max values (ex. Ab 0) Click OK

It seems like it would be easier to open the track in the PRV click on the keyboard to select all the notes of one pitch then SHIFT+drag one of the notes to whatever value desired

Make sure to install Cakewalk by BandLab after installing any old Cakewalk DAWs otherwise the old "shared" files will cause problems.

Using old Cakewalk products requires old Cakewalk installers. Access to those installers depends on which versions of SONAR you had licenses for and if you created a Single Sign On account on the old Cakewalk site between 2014 and 2017.

It might be easier to perform a "Save As" or "Save Copy As" to the new project name, without copying the audio clips unless they are needed in the new project. This will preserve not only the MIDI data but the instrument setups too. It really depends on how much of the old projects needs to be copied.

If I was copying into an existing project, I might copy entire track(s) at a time instead of copying individual clips. Often, it's a lot easier to delete unwanted copies than to mess with only copying what is needed. And since the source and target both start at 0, alignment is easy.

One refresh would be enough if the programs were in the program folder. If your old machine had DP setup the way you want, replacing the multisamples folder and "C:\ProgramData\Cakewalk\Dimension Pro" on the new machine with the folders from the old machine will replicate that setup. This is what I do when building a new machine. I only rely on the installers to the plug-ins installed correctly. The data always comes over from the old machine.

There is no need to use a drum map for alternate note labels. The keyboard left of the notes pane in the PRV may be replaced with alternate note names from instrument definitions.

Since it is a new project, consider saving the original project as a MIDI file then open the MIDI file and save it as the new project The new project will have all the MIDI including the tempo map as the original file.

If the multisamples folder was populated correctly; chances are the programs folder "C:\ProgramData\Cakewalk\Dimension Pro\Programs" was populated too. To force a program rescan, open the DP program browser and hit the F5 key. The other way is delete "C:\ProgramData\Cakewalk\Dimension Pro\Programs\programs.lst". The next time DP runs it will rebuild the file. This is what the good installers do so the user does not have to manually rescan with F5. Some installers skip this step.

Try the event list view

Reinstalls of anything using the CCC are very fast as long as the installers are cached. When the installers are cached, CCC does not bother downloading installers again instead going straight to install.

Any expansion packs made for Dimension Pro should work in Dimension Pro (duh) but newer installers look for Rapture Pro first and install everything in the Rapture Pro folders and not the Dimension Pro folders. If you want to abandon Rapture Pro, I believe the fastest way to get everything setup for Dimension Pro is Uninstall Rapture Pro Remove registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Rapture Pro Delete any leftover bits of C:\Cakewalk Content\Rapture Pro C:\Cakewalk Content\Cakewalk Sample Data Reinstall any 3rd party Dimension Pro packs. With Rapture Pro is gone, the installers should use legacy folders. Disclaimer, I have never attempted to revert to the legacy synths, and everything above is my best guess of what it will take to get the new installers to work with the legacy synths. I have a very good understanding of how all the Cakewalk synths install but there are certain combinations that I have never tested. Worst case, if it all goes south, might have to reinstall of the synths. This is pretty easy albeit time consuming.

X-series Instrument track inspectors have always had all the MIDI and audio controls. I have no recollection of instrument tracks prior to X1. Did not use them prior to the X-series.

Just like MFX plug-ins, use the track inspector to add a drum map to an instrument track. The MIDI output drop down is near the bottom of the inspector MIDI tab channel strip.

Partitioning is done mostly to accommodate backup strategies. From a performance perspective, partitioning is not a substitute for multiple drives. The best case for M.2 drives is large streaming sample libraries. If the samplers are not streaming, the only benefit is faster load time. Once the libraries are in memory, the drive makes no difference. The only time more RAM is important is if the DAW runs out of RAM. Overall, the decision to upgrade CPUs, drives or RAM and the impact on performance depends on which resources are being taxed on the current system. What needs to be improved should not be a mystery. Windows provides the tools necessary to monitor CPU, disk and RAM performance. If the current system is CPU bound a new CPU may help. It really depends on what the CPU is doing. If all the cores a loaded, more cores may be the answer. If one core is pegged, this may indicate a faster clock speed disk bound, more and faster disks may help. I have not partitioned a disk since XP. Instead, favoring more physical disks. My current DAW has 6 internal disks with the DAW and plug-ins installed on the system drive, projects on another and the rest contain samples (and the picture cache). Not using streaming samples, I have not bothered with M.2 drives. RAM bound then add RAM. Performance plummets when the OS uses virtual memory

This is true for all Cakewalk sfz engine synths including the Studio Instrument series. The easiest way to avoid this problem is by enabling "Do Not Intercept NRPNs" from the VST2 drop down in the standard header above the plug-in UI or plug-in properties in the plug-in manager.

It was never endorsed by Cakewalk. The old Cakewalk forum had a section for user created software and content. There were a handful of users, including myself who contributed. Revamping drum maps has been on the Cakewalk to-do list for some time. The relatively recent addition of persistent note names in the label pane has significantly reduced my desire to work with drum maps.

Look at the instrument definitions for the drum plug-ins I mentioned above in the instrument definition area.

Thanks, I moved the post to the instrument definition area.

The developer of ins2map partially reverse engineered the drum map format and AFAIK did not publish the source to ins2map or his findings about the file format.

If you cannot see the images on the website, refer to the user guide pdf. The "synth icon" is the icon used in track two of your post. The terms "instrument track" and "split instrument track" are part of the normalization of simple instrument tracks in the documentation. As I mentioned above an instrument track is a SIT. The relatively recent addition of "split instrument track" refers to the MIDI+audio track pair used by a synth. It could also be referred to as a MIDI+synth track pair but this is a little confusing. Remember the only track required for a synth plug-in is an audio track, in the form of an audio track (synth in the FX rack), synth track or the audio track in a (simple) instrument track. A synth plug-in must have an audio track even if it does not generate audio, however; the MIDI track is optional. Although it is very common for synth plug-ins have some type of MIDI track sending data to the plug-in.

Yes, but if all one wants is a way to label MIDI note values, consider instrument definitions. Note names from instrument definitions may be used to replace the keyboard in the label pane left of the notes pane in the PRV. Instrument definitions may be built using the tools in Cakewalk or with a text editor and imported into the master instrument definition file (master.ins in the user directory). There are examples of instrument definition files in this part of the forum. Some were specifically created for drum synths such as EZDrummer 2, Superior Drummer 3, SI Drum Kit and Addictive Drums 2. And the good news is, even if one prefers to use drum maps instead of instrument definitions, the first step to creating a simple drum map from a text file uses the instrument definition layout. So, create and share both on the forum. There is a 3rd party tool called ins2map (it is in the Cakewalk Sonar section under Tools) that takes a simple instrument definition file to create a drum map. Information about this utility is available on the old forum in this thread.