Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by scook

  1. As I mentioned in your thread, Scuffham have acknowledged the problem.

    They have not released a fix.

    For now, use the VST2 plug-in.

    By default the VST2 plug-in is in C:\Program Files\Scuffham Amps\S-Gear_VST

    Either add that path to the CbB scan path or move the dll into a folder already in the scan path.

  2. Running CbB 2020.04 EA2, I only see one set of presets for the Saturation knob.

    I ran the Softube update between EA1 and EA2

    FET Compressor and TSAR-1R crash immediately on insert after a second copy of the QCEQ appears in the PC.

    This may be a problem

    BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ
    PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 000000002a2f8d64
    STACK_TEXT:
    00000000`0014f660 00000000`00000000 : 00007ffc`92edc4bf 00000000`00000000 00000000`00000000 00000000`2119c158 : FET_Compressor+0x4a8d64
    BUCKET_ID:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_FET_Compressor+4a8d64

  3. Plug-ins may be installed any time using the advanced install option in SONAR X3 and older.

    SONAR Platinum bundled its plug-ins in separate installers so those too may be installed at any time.

    Products sold separately such as the PC modules in the image above and synths may be installed at any time.

     

    The only time installation or matters is installing the actual SONAR DAW. When installing the SONAR DAW or a full version of SONAR, CbB must be installed after it so that the shared libraries are the correct CbB versions. In order to install SONAR after CbB is installed - uninstall CbB using BandLab Assistant, run the SONAR installer, reinstall CbB using BandLab.

     

    The only plug-in that requires the DAW be installed is V-Vocal because V-Vocal is not listed separately in the X2 and older advanced install plug-in pick list.

     

    Regarding the PC modules in the image above

    • Boz Digital recently had the +10db (the David Bendeth Signature Compressor is part of this bundle) and Hoser XT bundles on sale. These bundles still contain their PC modules.
    • Overloud Vintage Keyboard FX PC modules are unavailable. While the bundle is still sold by Overloud, the PC modules were only available when this product was purchased from the Cakewalk store.
    • Softube Mix Bundle is no longer sold by Softube but the PC modules are still included when purchasing the individual plug-ins.
    • The other three are Cakewalk products.

     

  4. AFAIK, BandLab purchased the IP for all Cakewalk products.

    Cakewalk by BandLab is the only product released so far.

    BandLab has not mentioned any plans regarding the rest of the purchase since the release of CbB.

    Those who own old Cakewalk products are encouraged to install them.

    Installing old Cakewalk plug-ins may be done at anytime using the advanced install option in SONAR installers.

    Installing the SONAR DAW or full versions of SONAR should be done prior to installing CbB.

     

  5. WRT "Cakewalk Content" before installing anything create a directory junction on C to point to "D:\Cakewalk Content" and the X3 and CbB installers will place their content on D

    To do this, open a Command Shell and type

    mklink /j "C:\Cakewalk Content" "D:\Cakewalk Content"

     

    You should install X3 before CbB. Some plug-ins bundled with X3 need registry entries which are added at install time. Both DAWs must be on the same drive because they share files and registry entries.

     

    VST2 plug-ins may be installed on either drive but they do not take up much space so I leave them on the system drive. Large sample libraries such as Dimension Pro may be moved after install. I use directory junctions to move these folders just like "Cakewalk Content."

    The VST3 spec recommends installing in certain paths on C. Most manufacturers follow the recommendation and do not allow an alternate location.

     

     

     

    • Thanks 1
  6. If the project plays correctly at 44.1 then it was recorded at 44.1.

    The bit depth shown in the transport has nothing to do with the clips already in the project. The transport shows what bit depth the DAW will use when recording new clips. This values is read from the Record Bit Depth setting in preferences.

    There have been cases where clip headers report one sample rate and the clips are actually recorded at another. This happens when the DAW tells the audio interface what sample rate to use and the interface fails to honor the request. When the DAW writes out its audio clips then headers contain the DAW sample rate but the data from the interface may be something else. This is an unusual situation and causes clips to play faster or slower than expected than sample rate reported in the transport.

     


     

×
×
  • Create New...