scook

ASIO is an audio specification. If one interface is used just to connect MIDI devices to the PC, it does not need an audio driver at all. Here is a little more info about ASIO drivers in general. There should be at most one ASIO driver installed for each interface. If a generic "driver" such as ASIO4All is installed it can be a problem for interfaces that have a real ASIO driver installed because the generic driver serves as a driver for all audio interfaces. Some manufacturers do not supply real ASIO drivers instead relying on generic drivers. Some DAW manufacturers such as Steinburg, MAGIX and FL Studio install generic ASIO drivers. CbB uses the registry entries in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO to determine the drivers on the PC.

At the top of the plug-in is the most recently used section. It really has nothing to do with what plug-ins are available at the moment. It simple shows which plug-ins were last used. The section with the plug-in categories is built from the currently available plug-ins and EZD is not there. I doubt running as administrator will make any difference. EZD should scan and work without admin rights. At least it does on my machine. Hopefully the 64bit version of EZD was re-installed and where ever it was installed is in the VST scan path. The 32bit version of EZD does not work in 64bit DAWs. Assuming the correct plug-in is installed and in the scan path, from preferences run a VST Reset with "Generate Scan Log" enabled. If the plug-in does not show up review the scan log.

This is how it works today. Double-clicking on a row in Drum Grid Pane header opens the row in an editor.

Their video is almost 2 years old.

And a budget May be able to help with this too especially if it is not too old and you want the content and 64bit plug-ins available for CbB.

For stuff like this, there is a fair chance I check the software/documentation before posting.

Do not use the RealTek ASIO driver. Try the WASASPI driver modes.

Contact support@cakewalk.com for password reset

In the tool tip for the - in the lane header. And that is what the - on the lane header does. It removes the lane. It does not remove the automation envelope. Above, I provided a link to the documentation on deleting automation envelopes.

The relationship between the PC keyboard and the virtual keyboard in CbB is hard-coded. It is possible to create translation tables for MIDI note data using the Transpose MFX or a drum map.

There is no requirement to store any user data in the SD3 folders. Not sure exactly what the problem is. It may help to see an image of the sfzlog.txt I just tested by loading a sample directly into one pad and an sfz file into another. Both were outside of the SD3 folders on a different drive. Saved the project, shutdown CbB, re-opened the project and both were found. Saved as a program and kit. Both the program and kit were saved outside of the SD3 folder. Both the program and kit loaded OK in new SD3 instances.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.11.html#1154521 The single delete also works in the automation lane.

Email services were shut down in Nov 2017 for the old Cakewalk company. The old Cakewalk account database is archived; new account creation is not possible. Access to old accounts is manually maintained by support@cakewalk.com

contact support@cakewalk.com

Got it This (offline activation) should still work If it does not it may be necessary to reinstall CA-2A using Cakewalk Command Center. it is the easiest way to install and activate anything with a command center aware installer.

The CA-2A is an upgrade to the PC-2A. It may automatically replace the PC-2A if the the old PC-2A is completely removed from the scan path. The default PC-2A folder is C:\Program Files\Cakewalk\Shared Utilities\Internal\PC2ALevelingAmplifier

Bypassing plug-ins can be done globally (keyboard shortcut "E") and at the track FX rack levels.

That sounds more like unauthorized plug-in

should be getting a dropout code http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.32.html

Just ran the installer to confirm

I believe it should be on the advanced install component pick list as one of the plug-ins.

These plug-ins were bundled with every version of SONAR starting with 8.5 through to Platinum (including X3). They were first bundled with Project 5.

IIRC, Bitflipper made a tool to report VST plug-ins from the VST Inventory in the registry. The only tool I know of for reporting project contents is ProjectScope. A link to the program is in this thread

IDK, never wanted to separate a project file from the audio folder below it. This is the default per-project audio folder layout and it is this way for a reason. Keeping the default per-project audio folder layout where the project's folder contains project's file(s), autosave and versions Audio folder containing project's audio Melodyne folder containing project's melodyne audio clips MixScenes folder for the project's mix scenes insures the project is complete and portable. The folders are stored in the project using relative paths. Placing folders outside of the default path breaks portability because the the folder locations are stored as absolute paths.