scook

that seems wrong, all my vst3 korgs have the .vst3 extension in that location (as opposed to .dll in the vst2 path) I believe this is a typo or miscommunication with KORG support. Even though they are actually dynamically linked libraries, all VST3 plug-in binaries MUST have a vst3 extension. Files with a dll extension under "C:\Program Files\Common Files\VST3" are support files and are not scanned. AFAIK KORG does not have any files with a dll extension in the VST3 area. Like most manufacturers KORG permits users to specify where VST2 plug-in should be installed, however; some of their installers also put a copy of the VST2 binaries in "C:\Program Files\Common Files\KORG\Collection".

It might be the one in CSC. All the bundled CSC content came from DP and Rapture. I can't imagine anyone using CSC if they had DP/Rapture unless the program came from a CSC expansion pack. I purchased one CSC Expansion pack but instead of using it in CSC, I moved the samples to my Rapture folder and reconstructed the programs in Rapture.

This is usually because a project is open. The MIDI driver mode cannot be changed when a project is open.

SONAR Home Studio (later versions), Artist, Professional or Platinum all included a 64bit version of Rapture Session which can load and play CSC programs. Running the Rapture Session installer after CSC will automatically pick up the CSC programs making them available in Rapture Session.

Scrub Tool Keyboard shortcut J toggles the tool

The ASIO driver is an audio driver. The MIDI driver mode has nothing to do with the audio driver but can prevent the DAW from seeing MIDI data if it is set to the wrong MIDI driver mode. Check the link in my previous post for more info.

Not in my experience. Here is an example of a clip containing notes of different durations all set to two beats by directly entering the value in the Event Inspector

They may be reverting to the historical update schedule used when SONAR was active. The local help and User Reference PDF are reformatted snapshots of the web-based documentation. The web-based help received updates between releases and with every major release. The local help (re-introduced with 2022.06) was synced to the web-based help every major release. The User Reference PDF was updated less frequently often skipping several releases between updates. Something that has not happened since the introduction of CbB is the integration of the "What's New" section into the main body of the documentation. Prior to SONAR Artist/Professional/Platinum series, this was done with every new product release (ex. X1 to X2). During the SONAR Artist/Professional/Platinum era, it would happen every year or so. Now that all three documentation formats are back, it may be time for integrating "What's New."

After creating a track template, using something like autohotkey can reduce adding the template to a project to a single key combination. The following autohotkey snipped uses Windows+SPACE to load my Guitar track template into a project (note: I keep all my templates is a folder called "Custom"). #space:: Send,!it WinWait,Import Track Template Send,Custom{Enter} Send,Guitar{Enter} Return

Are SONAR and CbB using the same MIDI driver mode?

More flexible MIDI routing would be nice. Until that time. Here is a method for sharing MIDI data hosted in one track across multiple tracks that does not rely on linking, copying or recording the same data multiple times. Add an instrument track with a synth plug-in that sends MIDI data such as Code FN42 MidiChFilter, NoteMapper, or VeloScaler. Then use the plug-in from step 1 as the input for all the instrument and MIDI tracks needing to share the data. Modify the data in the instrument track created in step 1 and all the tracks in step 2 respond to the change.

The controls shown in the track view depend on the workspace setting and track control drop down (image below)

It is no different than any other MIDI controlled plug-in that manipulates audio data. Create an audio track with input set to the appropriate audio source and enable input echo Drop the xils vocoder plug-in into the audio track FX rack Add a MIDI track with input set to your controller, input echo enabled and output set to the xils vocoder The setup may benefit from adding a compressor before the vocoder in the audio FX rack.

This or bounce+archive (+disconnect for synth) to ensure access to the audio and save custom presets by project or take note of factory presets used in the project notes and when possible, save installers. KORG leaves installers on disk after install so, they make it easy to backup installers. KORG is new to VST3 and they have struggled with their first attempts. Might be best to use the VST2 plug-ins for a while longer at least until their VST3 release notes are clear of showstoppers such as lack of persistent presets.

Like the page says at the bottom - "Login to get your personal offer"

As a rule, all audio should ultimately pass through the master bus and the master bus should be the only source of audio data coming out of the DAW to the main monitor inputs of the audio interface.

Since the introduction of VST settings in X-series preferences, scanning and setting scan preferences in the Plug-in Manager has been discouraged in favor of using preferences. The plug-in manager supports a subset of the VST settings available in preferences and is intended to be used with older Cakewalk products that do not have VST settings in preferences.

Yes, tracks or lanes, mute is not solo. This is the process This is how take lanes work in the PRV. The PRV works at the track level. Instead of take lanes for MIDI consider using separate tracks.

Soloing a track does not mute clips; it causes the DAW to ignore non-soloed data. Muting clips is a separate per-clip function and is the only function that works with "Hide Muted Clips."

To have more than one plug-in UI open at a time read the Recycle Plug-In Windows section on this page.

CbB no longer includes the Melodyne 4 Trial Version and BandLab no longer distributes the Melodyne 4 Trial either through BandLab Assistant or Cakewalk Installer. If you did not retain a copy of the Melodyne 4 Trial installer there is no way to install it.

A VST Reset: clears the VST Inventory in the registry then runs a VST scan The VST Inventory contains information about the plug-ins gathered by the scan along with has some parameters that users can set. The VST Inventory contains all VST2/3 plug-ins scanned whether they passed or failed the scan. This is why plug-ins that failed to scan may be listed in the scan log. The VST inventory is used by the DAW, along with registry entries created at install time for DX plug-ins to create plug-in lists bundled with the DAW.

Make sure HKEY_LOCAL_MACHINE\SOFTWARE\ASIO in the registry only contains an entry for the Behringer UMC 204. If there is an entry for RealTek, delete it.

There is no need to ever change a plug-in from an FX to a synth. If an FX plug-in can use MIDI data, open the VST2/3 drop down in the plug-in standard header to turn on "Enable MIDI Input". When an FX plug-in has "Enable MIDI Input" turned on, the plug-in will appear in MIDI track output drop downs.