scook

It may be more than patch settings. Cakewalk by BandLab is much more than a MIDI file player and all the extra data has to be stored somewhere. Data such the plug-ins used, audio clip locations and audio routing information are all stored in Cakewalk project files. Since none of this is MIDI data, it is not saved to standard MIDI files.

I've never had this particular use case, but I probably will some day, so... If I "apply trimming" the DAW will permanently delete the unwanted portions of the clips? Yes, while the documentation seems clear, I learn best through experimentation; "Apply Trimming" screams "TRY ME on a test project"

@azslow3 wrote a Cakewalk project to Reaper tool. Maybe a no frills return flight is possible too.

Recompute pictures using the last option in the clip context menu https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Dialogs1.20.html#1210581 or Loop properties from the Loop Contruction view Clip menu https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Dialogs2.141.html#1459073 or clear the wav image cache by deleting the contents of the path in Picture Folder. This will cause all projects to rebuild their wav images the next time they are opened.

I don't recall the original thread apply trimming in the clips menu and the check boxes "Copy all audio with project" and "Create one file per clip" in the Save As dialog may be of use.

The plug-in database "%appdata%\Cakewalk\Library\library.db" is used by all the last series of SONAR products and CbB. With that in mind, I might not want to have more than one of these DAWs open at a time for fear of corrupting the database. There are some subtle default path differences when installing 32bit Cakewalk DAWs before 64bit versions of the same DAW. As a rule, if 32bit DAWs are going to be installed, install them first. If I still needed a 32bit version of SONAR, I would treat its installation just like any other legacy Cakewalk install...after installing any legacy DAW (re)install CbB to insure CbB is correct.

starting the transport stopping the transport

Depends on how much value the 16-year-old project represents. There is no reason to wrap Dimension for future use as it was eclipsed by the 64bit Dimension Pro VST2 plug-in you also have licensed. All you need P5 for is the plug-in. To load the project requires a 32bit version of SONAR or some other program that can read a SONAR projects and load 32bit DX plug-ins. PSYNII and Pentagon I were shipped as both 32 and 64bit DX plug-ins. AFAIK, Dimension was never sold separately. In fact, there were quite a few plug-ins bundled exclusively with P5 that were never ported to 64bit DX or VST format.

DX plug-ins have no bridge and as the OP observed wrapping them removes their identity for existing projects. In short, to load projects with 32bit DX plug-ins requires a 32bit DX host. CbB is a 64bit DX host and as is completely unaware of 32bit DX plug-ins. Are you sure P5 can open SONAR projects? According to the product info I found on the internet there was. The plug-in was bundled exclusively with early Project 5. IIRC, I bought P5 when Cakewalk bundled DP with it as a promo for the new synth.

IIRC, Dimension was a P5 plug-in. This means it is likely 32bit DX format and will require 32bit SONAR to load the project if you can find the P5 install disks for the synth.

Cakewalk updates templates in the default path For example, my template path is set to "D:\customizations\Cakewalk\Project Templates" not the default. This has been my project path across a couple of OSes, various releases of SONAR and CbB on several PCs. The only files in the path are the ones I put there. Cakewalk updates have never written into "D:\customizations\Cakewalk\Project Templates." The same holds true for drum maps. I have ~30. Practically none of the ones in the folder came with a Cakewalk product and none were added or modified by a Cakewalk update.

Default template handling has not changed for some time. Either method may prevent lost template updates. The template path is one of the two paths (the other being drum maps) I change in folder preferences both for the same reasons: the aforementioned update issue and to limit the number of templates and drum maps. In most cases, I prefer to use directory junctions and leave DAW defaults alone, but directory junctions don't address either issue presented by templates and drum maps.

In your previous thread about 32bit interfaces, I posted a link to a section of the CbB documentation that covers the precision used to communicate with plug-ins. This is indicated with dots below the plug-in strip in FX racks. Plug-in technical details may be covered in the plug-in documentation. Without this documentation, a way to inspect the plug-in internals (not a typical user level activity) or a cooperative developer willing to provide these details, the internal workings of plug-ins are hard to know.

support@cakewalk.com is the email address for current Cakewalk support They may promote BandLab stuff because they are BandLab employees. BandLab runs the legacy Cakewalk servers. Here is a link to the main Cakewalk support page https://help.cakewalk.com/hc/en-us. This is also linked in the menu at the top of this forum. Support email goes to this group.

Have not tested email changes on this forum but did confirm the feature exists on the new forum software before posting. I do not know if this forum and BandLab accounts sync up email

There is no email service from legacy servers. Legacy accounts are managed by support@cakewalk.com. You should have access to your forum and BandLab user profiles. In the PC forum layout access to your user profile is in the upper right of this screen.

Yeah, DP has always been separate and unless one needs the DX format for legacy projects any v1.5 installer will work. The Cakewalk Command Center still works and for products with a CCC aware installer like DP v1.5, CCC is the easiest way to install activate legacy Cakewalk products.

This is up to you. If you are going to re-install the folders and files will be re-installed anyway. If you wish to perform a clean install, removing all legacy Cakewalk files and CbB, the old clean instructions still work https://legacy.cakewalk.com/Support/Knowledge-Base/2007013372/Clean-Install-All-Cakewalk-Software. Be careful with these or any instructions regarding removing Cakewalk software. The instructions call for removing the default VST2 plug-in path "C:\Program Files\Cakewalk\Vstplugins" which may be a problem if the path is used for 3rd party plug-ins. Move/backup the 3rd party plug-ins before deleting the folder. Wasn't the "good" version of Pantheon the one released before 8? IIRC, it was multichannel with some extra controls the stereo version bundled with 8 did not have. Regardless, both have been long eclipsed but if you want the plug-in, an advanced install should get it. Don't remember if it was updated in 8.5. As far as actually installing SONAR, I start with X2 to grab V-Vocal. may want to review the SONAR Plug-in spreadsheet from this post to see what else only came with X2. Run the X2a update to get the last version of V-Vocal. Then run a full install of Platinum. Using the SONAR Spreadsheet again backfill with advanced installs of any other DAWs for plug-ins only. The old LP plug-ins were discontinued during Platinum. If you need those, the easiest way is an advanced install of X3- but, if necessary, I can look up which Platinum Engineering Suite installer has them. I know it has been posted before. When done with legacy stuff...install CbB. Really, advanced installs of legacy stuff can happen anytime. CbB needs to be installed as the last DAW so that SONAR and CbB use the latest plug-in manager/scanner and shared plug-ins.

Recording Mode is in the Project preference settings. Project preferences are inherited from a template during project creation. Change the project template and all future projects created using the template will reflect the changes. Of course, existing projects require changing one-at-a-time because Project preferences are stored in project and project template files. To prevent a DAW update from wiping out user created/modifed project templates either: use a custom template location - set in Preference > File > Folder Locations, Cakewalk updates the default template location only or, use unique template names - not my choice but it should be pretty easy to create names Cakewalk won't use.

IIRC 01_READ_FIRST_SONAR_X1.exe contains install instructions 02_SONAR_X1_Producer is a two-part installer. As with any multipart installer, only the first part (the exe file) is run. The rest of the parts are run by the install process itself. 03 Beatscape content w/o the plug-in was reorganized and repackages as loops and one shots in X2. Install both to waste 5GB of disk, I did not bother performing a full install of X1, too old, too many updates (including Producer Expanded). In fact, I would not bother with full installs of anything prior to X3.

It is pretty easy to create volume autmation. Open the automation lanes and volume automation is created automatically. To delete any automation envelope from the automation lanes, right click on the envelop to bring up its context menu and select Delete Envelope For more info see https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.11.html#1154521

It has been hermetically sealed in a mayonnaise jar on Funk and Wagnall's porch since noon today

Try the preset manager in the plug-in

The VST specifications provides for individual and banks of presets. The FXP extension is typically used for individual VST2 presets. Not sure about RPL, that may be a reaper file format. The SPP files created by Cakewalk are proprietary and the company does not publish file specs. Unless you can hack the format to do what you want forget about the Cakewalk preset manager. To get plug-in presets out of Cakewalk for use in a different DAW, use the preset manager built into the plug-in to save presets. Plug-in preset managers work the same regardless of the DAW hosting the plug-ins. If the plug-in lacks a preset manager complain to the plug-in manufacturer. It may still be possible to extract presets by using @azslow3's Cakewalk>Reaper project conversion utility to get the projects loaded into reaper w/ presets intact.

All the versions you have mentioned have advanced installs except for Platinum. Platinum broke the main installer into several smaller ones. Updates can contain plug-in bug fixes so that is something to consider (ex. the last version of V-Vocal is in the X2a update). For more fun reading including a link to a spreadsheet containing SONAR plug-ins by version see