Jump to content

Jonathan Sasor

Staff
  • Posts

    1,487
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Jonathan Sasor

  1. 24 minutes ago, Dave Horch said:

    Jon, if  I may, how do you integrate jbridge with CW4BL? (I am the stupid...)

     

    BitBridge is the default way that Cakewalk loads 32-bit VSTs, however we support using the third party wrapper jBridge as well (which you would need to purchase separately). In the Plugin Manager, select your 32-bit plugin, then hit the Plugin Properties button and enable the checkbox to use the jBridge wrapper.

  2. Windows 7 is technically supported, but gets the least of our test resources as its not under active development from Microsoft (and hasn't been since 2015). The security patches run out January next year.

    Similarly, the overwhelming majority of users are running 64-bit  systems. Cakewalk will still run most 32-bit plugins via Bit Bridge (or J Bridge).

    I'm not sure where "Cakewalk on a rental basis" is coming from... We've been delivering a free version of what was previously SONAR Platinum with all its core features intact, and improving upon that for almost a year. Once the application has authorized on your system, it's not going anywhere. 

  3. 6 hours ago, scook said:

    It depends on the plug-in and how it was added to the machine. Adding the plug-ins to the exclude list in the plug-in manager is the safest approach. It will not recover disk space but it the easiest to restore if something is accidentally removed from the plug-in list. The second safest approach is moving the dlls out of the scan path. Again, easier to recover from than deleting items from the disk.

    When it comes to deleting from disk, usually the best approach for software that uses installers is the uninstall process in Windows Control Panel. For software without installers, delete is fine.

    That sums it up pretty well. Depending on the plugins, some things you can delete (like freeware plugins that do not have installers). There's a couple different ways to not display things on the Cakewalk side, excluding removes it everywhere from plugin lists. You can also make custom layouts with what you actually want to see, but as mentioned those don't do anything to free disk space. 

  4. Cakewalk will recognize plugins that are in the scan paths. The actual .dll files where the plugins load from tend not to be very large (as opposed to sample libraries), but Cakewalk will read them so long as you define any custom paths on the VST Settings tab of the Preferences. VST3 plugins use a convention where they globally install to C:\Program Files\Common Files\VST3 per the spec. Native Access allows you to choose where the VST2 install location is separate from the larger content files. 

    • Like 2
  5. You can open the AudioSnap Palette for any given clip to see if it is enabled or not. As for the larger scope of your problem though, doing a save as and choosing "copy audio with project" is probably a better workflow option than saving it as a bundle. You can always zip the new project folder if you need it compressed. 

    • Great Idea 1
  6. You'll want to be aware of the stretching algorithms using AudioSnap. The Elastique algorithms will give you the best bang for your buck for online rendering (what you hear during real time playback). You can set the defaults for this in the Preferences or change per clip via the AudioSnap Palette or Clip Properties.

    • Like 1
  7. As mentioned, it's a general "good practice" thing. If you're running a SSD, you're not going to see a huge improvement, but as others also mentioned, if you do backups on the disk and stuff you can isolate your projects from that part. Back in the day with slower drives there would be a noticeable bump in performance when writing to a dedicated drive for your projects. 

    • Thanks 2
×
×
  • Create New...