scook

For FX plug-ins that listen for MIDI data make sure "Enable MIDI Input" is checked on the plug-in's VST2/VST3 drop down This will cause the plug-in to be listed in MIDI track output drop downs.

To take this analogy a little further... A DAW is more like a word processing program than a text editor. When saving a word processing document as a text file, the data is converted and saved but the word processing features are not stored the text file. Re-open the file in the word processor and it displays the text as found in the file. In fact many word processors display a message warning that document formatting and features will be lost when saving as text only.

For future reference, the forum automatically downsizes large images making their details unreadable. When posting images do not upload full screen images instead use an image service such as imgur.com and post a link to the image or upload images of much smaller parts of the screen.

The first screen image is intended for hardware synths not controllers like the V25. There is no need to set anything in this screen unless you have hardware synths. The second image is the screen that sets up the input and output MIDI devices. This is the one that is important for getting MIDI note data to the DAW. I would recommend disabling all MIDI output devices on this screen for now. The third image is the setup for using the a controllers sliders and knobs to adjusts DAW and plug-in controls. For now, I would recommend taking V25 out of this screen. Then try the following: 1) Create a project 2) Add the TTS-1 using the Add Track menu by clicking A, B and N in the image below 3) Then click input echo on the new instrument track and hit some keys on the controller. This should make some sound. Of course this assumes your audio device is configured properly in Cakewalk.

Usually the largest consumer of disk space related to a DAW (not including the projects created by the DAW) are audio samples use by plug-ins and audio loops. The actual plug-ins do not take up must space. It may be better to leave the plug-in where they are and look for what is really taking up most of the disk. Some plug-ins provide an easy way to point to sample folders. For those that do not directory junctions are a good solution. Directory junctions also work well for the plug-ins that have path preferences in their UI too.

Did you try before posting? For me, experimenting is the best way to learn. There is nothing preventing multiple MIDI tracks from pointing to the same output.

Perhaps this is something to re-visit now. The only thing preventing the ability to save MIDI files and work with features that are not part of the MIDI standard is the refusal to save Cakewalk project files along with the MIDI files. Of course one can wait on changes to suit personal preferences, however; in this case, it may be a while considering the reply provided above by the principal developer of the software.

Use a directory junction. There are a bunch of examples of how to create directory junctions using mklink in the old forum like this thread and this thread. For more examples use this search string in Google site:forum.cakewalk.com mklink

Try clicking the keystrokes button in the upper right in the plug-in header (J in the image below) to send all keystrokes to the plug-in..

Automation in the track view is not part of the MIDI standard. It is a feature of the DAW and is stored in the project file format. The MIDI standard uses CC7 for volume. So, when saving a MIDI file the DAW converts the track view MIDI volume automation to CC7 just like what the DAW does on the fly when playing the MIDI track. This results in a standard MIDI file. Upon opening the saved MIDI file, the DAW does not see track view volume automation. Instead the file contains CC7 data. It is possible to manually convert CC data to automation although the data is altered slightly during the conversion process. To avoid the converting MIDI track volume automation to CC7, save the project as a Cakewalk project file.

similar thread

Make sure to install the VST3 plug-in. It is the one used for ARA2 functions such as drag to timeline..

Drag to timeline to create a tempo map uses Melodyne.

Or hit "F" to fit to screen or hit SHIFT+z twice to toggle Auto Track Zoom on and off.

It is true, CbB records the data at its inputs. So, to record a signal after an FX rack requires routing the signal through the FX rack and recording it on another track. For audio, this may be done using patch points. For MIDI, this may be done with a virtual MIDI cable. I know of two free virtual MIDI cables, LoopBe1 and LoopMIDI. The signal flow to filter live MIDI data is - Controller > MIDI track 1 with input echo enabled and MIDI Event Filter in FX Rack > Synth instrument or MIDI track

Look at the MIDI Event Filter MFX. The help file for the plug-in is installed along with the plug=in.

One way to bulk change channel information in MIDI clips uses the Event Inspector - Select the MIDI data to change. Enter the channel in the Event Inspector.

Cakewalk by BandLab There is an option to create a scan log on the VST preference page. Enable the option and run a VST Reset. The log will show if Z3ta+ and Session Drummer dlls are getting scanned.

Z3ta+ Classic ships with 2 effects dlls and one synth dll. The plug-in normally appears in both effect and synth plug-in lists. I have not seen a Steam based SONAR installation but suspect the plug-in paths need to be manually added to the CbB scan path in preferences. FWIW, all the plug-ins bundled with 64bit Platinum show up in CbB including the 3 Z3ta+ Classic plug-ins and Session Drummer.

V-Vocal is DX format. This means it must be the same bitness as the host and cannot use BitBridge. IOW, CbB will only work with a 64bit version of V-Vocal.

The latest scanner is much improved over the X2 scanner too. In addition to bug fixes, the sandbox and log features can help with problem plug-ins. Unfortunately for the OP, it won't directly help with 32bit X2 (there is no 32bit version of the latest scanner or DAW) but might help get the 32bit VSTs that lack 64bit versions running in 64bit X2 and CbB,

Since Behringer does not supply a driver, the device must be class compliant or ASIO4All would not work. So the interface uses a driver supplied by Windows. This is not the first manufacturer to supply ASIO4All instead of a proper ASIO driver. The best thing the owner of this device could do is try to return the product to the seller and purchase an interface more suited for DAW use - a device with a manufacturer supplied ASIO driver.

Not all plug-ins may be copied into the scan path. Some must be installed in order to populate the required registry entries. Generally if a plug-in has an installer, use the installer instead of copying the files. In the case of older32bit plug-ins, they may need the SONAR to run as administrator in order to scan and load properly. Even when running as administrator, plug-ins may hang or crash the scanner. If this is the case, it may take some sleuthing to figure out which plug-ins are at fault. Adding plug-ins into the scan path a few at a time may help. Finally, upgrading everything except the DAW and its plug-ins is a recipe for pain. Windows does a decent job of backward compatibility but there are limits.

Keyboard shortcut "E" bypasses all FX Racks.

It is possible today. I wrote a utility called Tools Editor to make it easier to add any program including audio editors (and almost anything else including pdf and html documents) to the tools section of the CbB utility menu. It is available on my google page. Help is built into the program and there is a readme pdf with illustrations including the setup for adding a version of SoundForge. Once added to the tools menu, to edit a clip, select a clip and launch the audio editor from the menu. Not sure if Audacity will work as an audio editor though. For a program to work, it must be able to take a wav file as a command line argument. That is how CbB (and many other DAWs) send files to external editors. There are quite a few free and paid editors that do take wav files on their command line.