scook

Dimension Pro LE, the synth included in the package to play the Garritan Pocket Orchestra

I am guessing this is SONAR Home Studio 7 XL the last version of this product. It is a 32bit DAW so any plug-ins bundled with the product are 32bit too. 64bit versions of Boost11 and Studio Instruments are bundled with CbB. CbB also has an integrated step sequencer. It includes a 64bit version of TH3 Cakewalk amp sim. The only unique bits of the XL pack are the 32bit DP LE and the bundled content. While the content may be useful, you may be better off using a 64bit sfz player like sforzando instead of 32bit DP LE.

DX plug-ins are host bitness specific. 32bit DX plug-ins are not visible in 64bit DX hosts and 64bit DX plug-ins are not visible in 32bit DX hosts. IOW, when running a 64bit DAW only 64bit DX plug-ins are available.

Could be. If the laptop does not have an SSD, the drive may be a limiting factor. Adjusting the ASIO and playback buffers may help

The software is mentioned on page 9 of the users manual http://download.steinberg.net/downloads_hardware/UR-RT2/Manuals/UR-RT2_UR-RT4_Operation_Manual_en.pdf

The ability to use the buffer slider depends on the driver mode and the driver in use. Some ASIO drivers do not respond to the slider. In those cases, the slider is disabled and manufacturer supplied software must be used to adjust the buffer. WASAPI Shared buffer size is fixed and cannot be adjust so the slider is disabled for this driver mode. AFAIK the rest of the driver modes can use the slider. I assume you are not trying to use both interfaces at the same time.

Look in the FX browser in the MIDI tab, the plug-in list for FX Racks on MIDI tracks or the MIDI tab in the Inspector for instrument tracks.

Make sure to run the scanner from preferences with "Scan in Sandbox" enabled. Avoid running the scanner from the Plug-in Manager.

might be a question for support@cakewalk.com Include OS info in the report

I believe the SD80 is in the Roland.ins By default this file is in "C:\Cakewalk Content\Cakewalk Core\Instruments"

Working in CAL I have Emacs in Lisp mode so formatting happens automatically.

V-Vocal shipped as a 32 and 64bit DX plug-in. It was developed by Roland and not part of the sale to Gibson so, starting with X3, the plug-in could no longer be bundled with SONAR. Since Gibson did not own the product, it was not part of the IP purchased by BandLab. The plug-in was last updated in 2011. Software does not age well. Regardless of its utility, relying on old, unmaintained, unsupported software is unwise. That said, I just loaded up the plug-in into a new project in CbB and messed around with a clip without crashing the DAW. I am running Win10 though. Providing the crash information to BandLab as suggested in the thread below may help the developers address the problem

It is not clear what you moved. It is unlikely anything in appdata is part of the plug-in unless you inadvertently forced the plug-in to be installed under appdata. The installer available at https://www.orchestraltools.com/store/get-sine provides an option to install the plug-in. I believe this tries to install in a VST plug-ins folder somewhere in "Program Data" by default. This should be installed in the existing VST scan path. Rather than try to sling files around by hand, it may be more productive to uninstall and re-run the SINE_Player_1.0.2.436.exe and install the plug-in correctly.

If a plug-in has "Enable MIDI Output" disabled it means the VST scanner determined the plug-in does not support the feature. Not all plug-ins echo or generate MIDI data.

It sound like you are pointing the scanner to where the sample library is stored. This library uses the Orchestral Tools Sines player. This player should be installed in the VST scan path not the sample library. This thread may be useful

Of course any plug-in with a side chain input may be used. The routing for regular plug-ins is the same as the PC modules in CbB.

Open the Melodyne plug-in or a clip as a Region FX and check the algorithm default.

Can't help you with this plug-in other than to mention, from the description on their website, it appears the plug-in should show up as an FX plug-in. After adding the plug-in to an audio FX rack "Enable MIDI Input" should be set in the VST2/3 drop down in the standard header above the plug-in. This procedure was added starting with SONAR X3 eliminating the need to configure FX plug-ins as synths.

all three lines should be in the do block like this (do (dword takt) (= takt Now) (insert takt 1 NOTE 60 100 240) ) or use a one liner (insert Now 1 NOTE 60 100 240) BTW Is not an assignment statement. This is (= takt Now)

Here are a few randomizers A CAL script called HUMANIZE.CAL The Velocity MFX has a Randomize section. Press F1 over the plug-in UI for its help. An MFX created by @Variorum called CSHumanize

Similar thread

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.

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.

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").

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.