Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by scook

  1. 5 hours ago, Robert Bone said:

    The VstScan.exe program should be in the C:\Program Files\Cakewalk\Shared Utilities folder

    This is true unless

    • the install was forced onto a non-system driver
    • the OP has managed to installed SONAR and CbB on different drives

    The former is OK as long as all Cakewalk DAWs and CbB are on the same driver

    The later is almost guaranteed to be a problem

  2. 42 minutes ago, Stony Buckner said:

    Check with going to the next required step of actual activating this version by creating a "Cakewalk/user account" I get the posted " No new Accounts being enabled"? or allowed? Lol Really Bandlab?!

    If one is trying to create new accounts on the old Cakewalk site, yes that database is archived.

    As noted above activation of Cakewalk by BandLab uses BandLab Assistant and the BandLab account created to download CbB NOT an account on the old Cakewalk site.

  3. Even if you had a 64bit version of SONAR, some of the DX plug-ins were never ported. When transitioning from 32 to 64bit it is a good idea to install the last 32bit version of SONAR available so project will open completely. Then find replacement plug-ins for the project or commit the old plug-ins. While 32bit VST plug-ins will load in 64bit DAWs look for 64bit replacements.

    Other than the 32bit DX plug-ins that were not ported, any project made in 32bit SONAR/MC should open in 64bit CbB.

     

  4. Installing CbB first means after installing other 64bit versions of SONAR/MC there is a good chance the contents of the shared folders will be old.

    To correct the problem, just uninstall CbB and re-install it after adding any older DAWs.

    Running the advanced install options to add plug-ins only will not affect CbB. This may be done at a any time.

     

    No project will be lost but any projects created in 32bit DAWs using 32bit DX plug-ins that were not ported to 64bit will not load the 32bit plug-ins when opened in 64bit DAWs.

     

    Installing a DAW does nothing the existing projects.

    Loading a project in a DAW does nothing to a project.

    Saving a project loaded in a DAW affects a project.

     

    Any time you are concerned about possibly messing up a project make a copy before making changes.

    If projects are important to you, they should already be backed up somewhere.

  5. Yes this has been asked and answered numerous times

    To regain access to your old Cakewalk account contact support@cakewalk.com

    CbB will run any plug-ins bundled with 64bit SONAR/MC including the 64bit DX effects and instruments.

    The best practice is install any full versions of 64bit SONAR/MC that you need then install CbB. After that run advanced installs of older versions of SONAR to add any the missing plug-ins.

    Some DX plug-ins bundled with old Cakewalk products were never ported to 64bit. If projects contain these plug-ins, they will only open completely in 32bit SONAR/MC. To ease the transition to 64bit, install the most recent version of 32bit SONAR available and replace these plug-ins.

     

    • Like 1
  6. FWIW, the PDC is probably not the PSP Lotary. It is not the type of plug-in that needs compensation. IIRC, it is a little heavy on the CPU though. This would cause the stuttering. Bouncing and archiving the tracks with this plug-in will solve that problem.

    It could be the reverb if it is IR-based or it could be a compressor or limiter with a large look ahead buffer.

     

  7. If it is not driver I/O buffers, the delay is likely caused by plug-in delay compensation. If bypassing plug-ins eliminates the delay, one or more of them are the problem.

    To bypass all plug-ins toggle the FX button in the Mix module. While reading about the FX button review the PDC button function as well.

    One way to avoid dealing with driver buffer settings and PDC is listen to the audio being recorded using the zero latency monitoring provided by the interface.

     

  8. 14 minutes ago, Steve Guckemus said:

    On the second note, Switching to WASAPI Shared seems to have made me some progress. I can now set output to my speakers. But do I have to do it on a track by track basis? or is there a quick way to reroute all output to my speakers at once?

    All of the audio tracks and  buses should be routed to a default "master" bus. This bus should be pointed to the hardware.

    This is how all the project templates bundled with CbB work.

    When the hardware changes, the default bus needs to point to the new hardware and the rest of the project is unchanged.

     

    Quick groups can change more than one track/bus output (or most other settings)

     

    When running CbB and Windows using the same audio device make sure the sample rate in CbB and Windows are the same.

  9. PC modules are modified VST2 plug-ins and do not throw the install time dll error.

    While many seem to find a solution to the DX install issue on the forum, contacting support is always an option.

     

    • Like 1
  10. Any plug-in that generates MIDI data can have the MIDI data captured in a MIDI track.

    Make sure "Enable MIDI Output" is selected.

    M9I2IRu.png

    This will cause the plug-in to show up in MIDI tracks as an input source.

     

×
×
  • Create New...