scook

The Transpose plug-in would be my first choice. The plug-in should be in C:\Program Files\Cakewalk\Shared MIDI Plugins. It is added to the registry on install with regsvr32.exe. Drum maps can transpose MIDI notes. Third party tools like NoteMapper and AZ Lua can do this too.

The recommendation came from BandLab QA. I just echoed his sentiments. I am not saying zips cannot get corrupted. Any file can get corrupted. But I do not recall a thread on the old Cakewalk forum regarding zipped projects being corrupted. I doubt many bother to zip projects though. Wav files don't compress much so, if I were to use zip I would probably turn off compression. My guess is the incidence of corruption with bundles is pretty low too but when it happens the project is, for the most part, unrecoverable. Bundles are convenient and will likely always be part of the program, if only for backward compatibility. The fact that bundling cannot store audiosnap data was used to repair projects that were blown out by an audiosnap bug (I believe this bug has been fixed). With all that, packaging the files that make up a project is just one more thing to go wrong. For long term storage, the best solution is rendering all tracks to wavs. Having a project fully rendered removes the need for a specific DAW and any of the plug-ins used in the project. The wav format will likely be around a very long time.

IIRC, the change to flac happened with the full installers for v1.5. DP could not read flac files until that version. Most of the programs work fine with either wav or flac. I recall a couple of programs where flac samples did not loop like the original wavs but I cannot find an example ATM.

CTRL-L does not bring up a dialog. The only visual indication provided in the program are the rounded corners on the clips and the ability to roll out the clip. It is possible to bind double-click on audio clips to bring up the Loop Construction View in the track view options menu. Use Ripple Edit instead of Cut - Delete Hole. From the copy and paste description make sure Drag and Drop is not set to "Slide Over Old To Make Room" in preferences. This is a known problem and should be removed from preferences. Ripple Edit make the option redundant.

"Sort by Category" has the ability to create folders. Plug-ins may be in more than one folder. Folders may not be nested. This is the only layout that may be customized using the browser. The Plug-in Manager is the only program supplied by BandLab to create additional custom layouts. There is a third party program developed by @TheSteven called MenuMagic that creates custom layouts.

So don't use zip either. That said, I do not recall a single post about a zipped project not being able to be unpacked. The same cannot be said for bundles. I you don't mind the risk of unrecoverable errors, bundles are fine. When creating a project using "Save As" there is no need to save the project in the same folder. "Save As" can produce a folder containing just the data referenced in the current project.

Moving the "Mixing Latency" buffer size slider to the right is the wrong direction. The slider is already at its minimum which it several times more than an acceptable value for real time monitoring. Possibly one of the other Audio driver mode settings will provide a better minimum value for the "Mixing Latency" buffer size slider. Once the best driver mode/latency setting is achieved, the only other consideration WRT latency is Plug-in Delay Compensation.

Latency is caused by the buffer settings for the audio interface and Plug-in Delay Compensation. In this case, the "Mixing Latency" buffer slider appears to be at the minimum setting and is just a little less than one would expect using an ASIO driver at 512 samples. IOW too high for real time use. The maximum setting needs to be no more the 256. Even then some find the latency a problem. Good values for most start around 128 or about 1/3 of the minimum setting achieved using your current hardware.

There a log generated on demand for the scanner. To audit the scanner, open preferences, in scan options enable "Generate Scan Log" and run a manual scan. AFAIK, the presets have always been available in the Sonitus preset manager. Cakewalk tries to load presets from any plug-in and show them in its preset list. I am not sure why the Cakewalk preset manager is not picking up the Sonitus presets. Might be worth asking support@bandlab.com. Does running as administrator make a difference? When a plug-in provides a preset manager, I usually use it instead of the Cakewalk preset manager.

DX plug-ins are not scanned. They are registered when installed. You can see the physical location for any plug-in when clicking on the plug-in name in the plug-in manager. From the description provided, it appears you used the Cakewalk plug-in manager pointed to by arrow 1. Any custom presets saved in this system are stored in the registry. These presets rely on the Cakewalk Plug-in Presets buttons in the plug-in manager for export/import. Do the Sonitus presets show up under the Preset button pointed to by arrow 2? FYI, the forum resizes images. To embed images without resizing use an image server. The image in this post is on http://imgur.com

"Save As" is the more reliable solution for project archiving. Bundles are fine for sharing projects but should not be used for archiving projects.

Wrong plug-in. The LP-64 EQ was the old linear phase EQ that was dropped from Platinum when the new LP EQ was introduced Ultimately the new LP series was removed from the Engineering FX Suite and had their own installer. The cfx files are managed by the preset browser built into the top center of the plug-in UI.

AudioSnap, RegionFX and Groove Clips are mutually exclusive. If the clip was processed using AudioSnap or a RegionFX bounce should render the clip so that it may be changed to a Groove Clip.

Unless you purchased the 32bit Sonitus Suite, the plug-ins are not VST format. The bundled Sonitus suite DX plug-ins. The ones you see in CbB should be the ones installed with CbB in the "C:\Program Files\Cakewalk\Shared Plugins" folder. Clicking on the plug-ins in the Plug-in Manager will display its location at the bottom of the Plug-in Manager display. The factory presets are in ini files in "C:\Program Files\Cakewalk\Shared Plugins." Getting custom presets back depends on how the presets were saved. The Sonitus preset manager is accessed using the Presets button in the body of the plug-in. The Cakewalk preset manager is in the standard header above all plug-in UIs. If the presets were saved using the Sonitus preset manager then they should be in the old ini files. If they were saved in the Cakewalk preset manager then they are in the old PC registry. The plug-in manager provides a way to export/import presets stored in the registry.

It depends on the plug-in not the DAW. All the DAW needs is the path to the plug-ins added to the VST Scan Path. Some plug-ins rely on registry entries including path information or have activation routines requiring the plug-in be installed instead of copied or added by mounting a drive.

CAL is one answer, Here are two scripts, one to advance Now by one beat, one to go back one beat from Now. Create files for each script in the CAL folder and bind them as needed. Advance now by one beat Go back one beat from now

No, following these instructions takes care of both the Project and Global Audio Folder preferences (assuming Project and Global Audio Folder are set to factory defaults). You could not create a junction for "C:\Cakewalk Projects\Audio Data" if you wanted to because "C:\Cakewalk Projects" is no longer a physical location. Any activity in "C:\Cakewalk Projects" is actually happening in "D:\Cakewalk Projects."

When emailing support make sure to include OS and DAW version. May also want to mention OS and DAW localization info too.

If one experiences a crash when attempting to change keybindings make sure when sending support@bandlab.com the report to include the steps to generate the crash and the dump file.

Saving installers whenever possible is a good idea. Toontrack provides the option to keep their installers. When the installers placed in the ToonTrack Product Manager download folder, the program will use them instead of downloading them again. Just like the old Cakewalk Command Center. Using per-project audio folders makes it easy to copy complete projects to any location available to the PC. No special software required.

Keybindings are not stored in the project. If changes are made to keybindings saved with "Save Changes for Next Session" enabled, the changes are written to the registry and recalled the next time the DAW is started and any project is loaded UNLESS a lens is loaded. If the "Save Changes for Next Session" is not enabled, keybinding changes are forgotten when the DAW is shut down.

Few bindings are reserved. A project must be loaded before most binding are active and before the may be changed in preferences. Once changed they may be saved for future sessions. This appears to be by design. To modify keybindings before loading a project would be a feature request.

Screensets are stored with the project. Lenses are global and may be applied to any project.

Colors in the PRV are per track. The PRV is not take lane aware so all lanes show up as a single track in the PRV. With data on different lanes and hide muted clips enabled in the PRV Options menu, it is possible to control was is shown in the PRV by muting clips in the track view.

Good news