Jump to content

scook

Members
  • Content Count

    7,760
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by scook

  1. Review project meter changes in the Meter/Key view
  2. I had my collection of freeware years ago. Now it's mostly commercial software and I seriously doubt many of the 1500+ will be used more than a couple of times. That said, all the VST2's are in manufacturer folders under CbB default folder and all the VST3 are in the default VST3 folder, most in manufacturer folder even if I had to manually move them. Plug-ins themselves do not take up much space; samples do. Most sample-based plug-ins provide a way to relocate their libraries. For those without an easy way to move samples, it's directory junctions.
  3. It depends. This works for most plug-ins but if the plug-in has registry entries referencing files that are moved at the OS level, the plug-ins will not work properly without modifying the registry. Normally, I would recommend using directory junctions but if this is the case, it may be a little messy. In this case, if the plug-ins use an installer, the safest approach is uninstalling the plug-ins and installing them in the new location. Every commercial installer provides for changing the install path. Most freeware installers do to. Plug-ins that use a simple zip file instead of an installer may be moved using Windows Explorer.
  4. There is Channel Tools but this issue not what happens after recording. The issue is ease of creating the track in the first place. For this one could use clip groups but since the subject is one instrument with two microphones, a stereo track makes more sense to me. Once the performance is captured, the two channels can be split into separate tracks if desired.
  5. For years, authotkey has been able to accept MIDI data using midi4ahk Here is a pretty good write up about it. I have not played with it.
  6. Instead of BandLab Assistant use Cakewalk Web Installer
  7. Here is one way to remove all controller data Adding the MFX Event Filter setup like the image below to the MIDI FX rack of the track(s) Select the track(s) From the main menu select Process > Apply Effects > MIDI Effects...
  8. scook

    backup data

    I have not used bundles much since per-project audio folders were introduced 17 years ago. Instead, I prefer to create a copy of a project using "Save Copy As" to a new folder with "Copy All Audio with Project" enabled then archive the new folder.
  9. Probably. I see no reference to an expiration date in either the Arturia Software Center or my account. I did not use a third party to get the plug-in.
  10. %appdata% expands to the entire tree shown in your second image. WRT the data in the %appdata%\Cakewalk folder, I backup %appdata%\Cakewalk\Library\library.db %appdata%\Cakewalk\Cakewalk Core\Aud.ini %appdata%\Cakewalk\Cakewalk Core\Cakewalk.ini %appdata%\Cakewalk\Cakewalk Core\Master.ins %appdata%\Cakewalk\Cakewalk Core\TTSSEQ.ini %appdata%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts Of these, library.db (the plug-in category database), Master.ins and the plug-in layouts are critical as they are time consuming to rebuild. I don't do much tweaking to the ini files and they are pretty easy to reconstruct. I have drum maps in a non-default folder so that I can control when that folder is updated. The custom drum maps folder is backed up. If you use Workspaces, they are in "%appdata%\Cakewalk\Cakewalk Core\Lenses" by default. Other files in "%appdata%\Cakewalk\Cakewalk Core\" may need to be backed up depending on how one uses CbB.
  11. The default path is in %appdata% which is a hidden folder. To get to the default location type "%appdata%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts" in Windows explorer path entry. If free disk space runs low, the OS may compress folders.
  12. Did you activate the plug-in after installing?
  13. Is the folder containing the layouts compressed? The path to the layouts is defined in Preferences > File > Folder Locations Plug-in Layouts
  14. In the Plug-in Manager, what Plug-in Category (the column on the left) is Reason Rack in?
  15. By adding to or creating a layout for synths separate from FX plug-ins.
  16. Is it possible the layout contains a mix of FX and synth plug-ins and the first plug-in in the layout is an FX? If so, the synth plug-ins will not be displayed. While the Plug-in Manager allows mixing FX and synth plug-ins in the same layout, the DAW does not.
  17. To set the path click the gear in the upper right of Aquarius then click the Installation tab If all projects use the same sample rate, there is no need to have all the samples in the nebula repository. Deleting unused samples may shrink the install footprint considerably.
  18. It is unlikely the result of updating but rolling back is not going to fix it either. Check the folders in %appdata%\Cakewalk and make sure they are not compressed.
  19. Try entering the number directly If you prefer to see them in the dropdown Open "%appdata%\Cakewalk\Cakewalk Core\master.ins" in a text editor Search for ".Controller Names" Under ".Controller Names" modify the [Standard] section as desired. Or use Preferences > MIDI > Instruments Click on Define... Open the Controller Names folder Edit the Standard entry
  20. This is in the VST drop down in the standard header above the plug-in UI. AFAIK, there are only a few functions unique to the plug-in manager layout and exclude list maintenance export/import for Cakewalk preset manager some additional info about plug-ins such as CLSID and vendor name. It is the only place where DX install paths are displayed. It does not support the scanning sandbox or logging. Pretty sure it will be retired at some point once its features are replicated elsewhere.
×
×
  • Create New...