Jump to content

scook

Members
  • Posts

    9,681
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by scook

  1. Good Now that the 64bit plug-in is there I will answer the question about getting the standard header for 32bit plug-ins. The standard header is in a separate window. To open the standard header hold down the ALT key when adding a 32bit plug-in to the FX Rack or when opening the plug-in UI. Usually the header window opens behind the main plug-in UI. That said, as a general rule 32bit plug-ins should be avoided and always try the 64bit plug-in first, if one is available.
  2. I just downloaded the 64bit plug-in from the link above. This is what the main screen looks like and the info tab Notice the plug-in standard header added by CbB. The VST2 drop down in the center of the header has an "Enable VST Input" option.
  3. Not sure what this means. The plug-in in the image above is definitely the 32bit version. What plug-in layout are you looking at? You can see the path to the plug-in dll in the Plug-in Manager by looking in VST2 Effects (or Synths if you changed its properties to "Configure As Synth").
  4. The image above is the 32bit version of GSnap. While it is possible to access the standard header for plug-ins hosted by BitBridge there is a 64bit version of GSnap. Usually it is preferable to use the 64bit plug-in when one is available. It is not necessary to use the "Configure As Synth" option in the plug-in properties. Use the 64bit plug-in and "Enable MIDI Input" from the VST2 drop down above the plug-in UI.
  5. before dragging the clips to other folders, previewed and clips already added to CbB may already be in folders in your "Documents\BandLab\Sounds"
  6. To hear live input from the DAW, input echo must be enabled on the track. It is the button to the right of the record button Monitoring this way will result in some delay between the time the strings are plucked and when the sound arrives to your ears. The amount of this delay is determined by the ASIO buffer settings and plug-in in the project. Most interfaces, M-Audio included have a direct monitoring feature which sends the signal going to the DAW directly to its outputs along with the rest of the audio from the DAW.
  7. Should be able to drag them from BandLab Assistant and drop them into Cakewalk tracks.
  8. Depends on the ASIO driver. For example, one should avoid the RealTek ASIO driver, It has been the source of several problem reports. If using an audio interface with manufacturer supplied ASIO driver, it may help to provide the make and model of the interface. If using the PC internal sound chip, try WASAPI Exclusive (if running Win10), WDM or MME in that order. Or try ASIO4All while not a true ASIO driver (it is a wrapper for the WBD driver) it is worth checking out.
  9. Good news Check the dates on the PluginManager.exe and VstScan.exe in "C:\Program Files\Cakewalk\Shared Utilities" If they are not this year, consider uninstalling and re-installing CbB to restore the current shared folders. The CbB uninstall is in BandLab Assistant Ignore "Install Add-ons..," circled in red, I am recycling an image used for another thread.
  10. Manual registration requires running the DAW or standalone DP as administrator. Once registered, the synth will run without admin rights.
  11. The latest installer was written for the Command Center. Installing with the Command Center automatically handles activation (just like all the other Command Center installers). For products available through the Command Center, I recommend using it to install them. Manual DP install is OK. Remember to run the standalone or the DAW as administrator to activate the synth. Once activated, there is no need to run as administrator to use the synth.
  12. Does the stand alone work? Was it installed using the Command Center or manually running the installer? Additional questions regarding a similar problem with plug-ins
  13. Automatic assignment of TTS-1 on MIDI file open depends on having no MIDI output device selected in preferences. If a MIDI output device is selected, opening a MIDI file will not have TTS-1 automatically loaded and mapped to the tracks. Automatic assignment of TTS-1 is handy when starting with a complete MIDI performance but not so much for collections of smaller MIDI clips like MIDI drum loops.
  14. After adding a synth plug-in with an instrument track or audio/MIDI track pair, drag and drop the MIDI clips into the instrument or MIDI track.
  15. Depending on how ProgramData was changed means the factory defaults may have been altered. This would only be a problem if one needed to restore a user directory to the original factory defaults. Worst case it may require uninstalling CbB, manually removing the ProgramData folder and reinstalling. Something I believe you have already done. It gets easier every time. :)
  16. I am surprised a scan with "Rescan Failed Plug-ins" did not pick it up. Regardless, aside from the extra time a Reset takes, it is a fairly harmless action. IIRC, it does lose custom property settings like "Do Not Intercept NRPNs" but does not touch layouts or the category database.
  17. C:\ProgramData\Cakewalk\Cakewalk Core contains a master set of files used to (re)populate the user directories %appdata%\Cakewalk\Cakewalk Core Best leave the files in ProgramData alone. CbB reads the data from user directories.
  18. You can if the manufacturer accidentally shipped their VST3 plug-in with a dll extention. I have had to do it one time. However, I have on several occassions temporarily renamed vst3 files to dll in order to get check their version info.
  19. er, unless it's changed, cbb installs as a seperate app, but still using a bunch of "shared" stuff? they made some fuss about that in the beginning Yes, that is how upgrades install (think upgrade from X2 to X3). Updates overwrite the existing DAW.
  20. Start a new thread for this if you need help.
  21. AFAIK, that is the only list. Is the log entry above from a VST Reset? If not then a Reset may be in order. If it is then this is a support@cakewalk.com issue.
  22. The Exclusion List in the Plug-in Manager is the blacklist. Not sure about renaming plug-ins with dll extensions to vst3. Unless I know for certain the plug-in is VST3 I would leave the file names as the manufacturer supplies them. I only know of one case where a manufacturer (not IKM) accidentally used dll for the extension of their VST3 plug-in but I suppose there could be more. I cannot speak directly about SampleTank. Don't have the plug-in.
  23. Usually the scanner detects when a dll is updated unless the scanner is set to manual scan. If the scanner is set to manual scan, run the scanner from VST Preferences. If this plug-in is in the Exclusion List it may be restored without running a VST reset. To check the Exclusion list: open the Plug-in Manager click on "VST3 Instruments (VST3)" in Plug-in Categories click on the "Show Excluded" radio button see if the plug-in is in the Registered Plug-ins list If the plug-in is in the Exclusion List, to restore the plug-in to to VST preferences set the scan options drop down to Manual Scan enable "Rescan Failed Plug-ins" click Scan disable "Rescan Failed Plug-ins" restore the scan drop down
×
×
  • Create New...