scook

No need to mess with channel assignments  preferences. That screen is designed for hardware.

The only part plug-in users need is the Define button to access the Instrument and Note Names dialog in order to import/edit plug-in note names.

Once the note names are set up in preferences, in the PRV when the instrument/MIDI track is displayed:

• right-click on the keyboard to the left of the Notes pane to bring up the Note Names dialog
• click the "Use these note names instead" radio button and
• select the appropriate entry from the drop down

The AD2.ins above shows in the drop down as "AD2 Standard"

Alternate note names is a per-track setting.

Note: if the Define button is disabled on Preferences > MIDI > Instruments it is probably because no MIDI output device is enabled in Preferences > MIDI > Devices. Currently, to add/edit instrument definitions an output device must be enabled. For those who run CbB without a MIDI output device, temporarily add one (make sure to click apply after selecting the device) to enable the Define button.

The data needed to display note names in the Label pane next to the Note pane in the PRV.

I used the  Addictive Drums keymap pdf and CC data from the Addictive Drums 2 manual

AD2,ins in on my google page or use this direct link to download.

If you need info about adding this to CbB or creating your own custom note names entries, feel free to ask in this thread.

Export defaults to the Render Bit Depth in preferences but I am pretty sure this can be overridden using an export preset and IIRC, that setting is persistent.

Starting with SONAR 4 it has been possible to chain creating a wav and another format as long as there was a command line encoder available for the other format. Many used this feature instead of purchasing the mp3 license from Cakewalk. I believe Cakewalk even supplied external encoder definitions for lame and a few other encoders at one time. The command line options are limited though.

Great, that saves me a lot of typing.

I did walk through of adding an external encoder for a user on the old forum and there are a few other threads on the subject over there.

No but file creation would probably not happen concurrently. The files would be created one after the other or at least after the wav is created.

Having SONAR X2 through Platinum installed, I am not sure if the old Cakewalk External Audio Encoder Setup utility is still part of CbB. 

If this tool is on the Utilities menu, it is possible using external encoders to create whatever formats you wish along with a wav. The wav file is used by the external encoders to create the other formats.

The utility creates the registry entries used during export to drive external encoders.

Even without the tool, my guess is the hooks are still in the export process to support the feature.

11 minutes ago, Mark Morgon-Shaw said:

How do the Devs evaluate and decide which if any to implement..i.e this is a useful feature and several of the competition have had it for years, and on the surface it would seem like one of simpler FR although I've not written any code for decades so I could be wrong. 

I have no first hand knowledge about what goes into their decision making process. I am sure comparing feature sets with other DAWs is part of equation but it is just one of many.

Simple requests do not necessarily translate into easy to implement features. IIRC, this one is a big change.

Of course, that does not mean it cannot or will not be done. It may be on the short list, IDK.

15 minutes ago, Mark Morgon-Shaw said:

@scook even replied in 2016 !!

Yes, in one form or another, this has been an FR for years.

That said, most of the FRs posted on this forum are repeats.

If you upload the project or put it on One Drive or Google Drive and post a link to it

I will take a look at the project

This is the first time I have read a report like this.

I would make sure to  download the latest version of the plug-in from the manufacturer.

After installing and scanning, retry setting up the plug-in in a new project created from the CbB basic project template.

5 minutes ago, Starship Krupa said:

One thing you can try is use Cakewalk Plug-In manager to force a re-scan of your plug-ins. It launches from the main Utilities menu.

While the VST scanner may still be called from the plug-in manager, the recommendation for years now is run the scanner from preferences. 

The plug-in manager does not have access to all the features provided when running the scanner from preferences.

The OPs problem does not read like a scan problem but a VST Reset would not hurt.

CbB includes an older version of the VST2 plug-in installed in PC modules folder.

AFAIK, the only way to acquire the VST3 format is download it directly from Softube.

There is a ProChannel on every bus.

Make sure to use the latest version of the TAL Vocoder from their website

The label on the drop down in the standard header depends on the plug-in format.

There is no need to post registration data here. 

DP standalone or the DAW must be run as administrator to activate the synth

OR

use the Cakewalk Command Center to install it. This tool automatically activates Cakewalk products as it installs them.

Once activated, the standalone and the plug-in do not need administrator to run.

I did notice the unusual path but did not know you were using the old SI Suite installer.

For sure, I would suggest using the add-ins installer supplied by BandLab Assistant.

As a rule, I don't recommend the registry edits unless absolutely necessary.

I prefer to use directory junctions. They are easy to use and allow relocation without the need to mess with the registry.

There have been reports of SI plug-ins scanning as FX. The fix is forcing a rescan of existing plug-ins. There are a couple of ways to do this, VST Reset is the easiest. Creating a log while running the Reset is a good idea if the Reset fails to solve the problem. The log provides a lot of detail about the scan.

Glad you solved the problem.

Yes, audio interface buffers and plug-in delay compensation are the two largest contributors. Fortunately, these are things the user has control over.

Except for WASAPI shared which is fixed by the OS, the audio interface buffers are set in preferences or, in some cases, software provided by the interface manufacturer. For 44.1/48K sample rates most find 128 is the largest usable buffer size although some can work with 256.

Plug-in delay compensation is determined by the plug-ins on the track/bus requiring the largest buffer setting.

If the track with the largest PDC requirement is not the track being recorded, bypassing the effects will reduce the PDC. Since the track being monitored requires FX, the global FX bypass in the Mix Module cannot be used but, individual FX rack/PC module bypass is available. Also PDC may be overridden on the live track using the PDC button in the Mix Module.

So does Hoser XT

Please keep the discussion about CbB

The unrelated dialog between @Jeff Bowman and the OP needs to stop now.

Thanks

Run a VST reset from preferences by clicking the Reset button to the right of the Scan button

Enable "Generate Scan Log" too, just in case the plug-ins don't show up.

Make sure the interface driver is current.

My want to re-install it, just in case.

Must have tested with the VST2 format only.

In most cases, I install both formats and have both VST3 migration settings turned off in CbB preferences.

Not a big fan of the DAW automatically hiding or changing my plug-in choices.

My guess is the auto-replace option was added for Waves as they only support VST3 in SONAR/CbB, they require VST3 for sidechain support and mixing their VST2 and VST3 plug-ins in the same project is a problem.

I tend use VST3 format but there are some manufacturers providing poor VST3 implementations (I guess Voxengo falls into this category) and some features have not made it to the format.

Have a look at the 64bit TenCrazy PW-Map MFX from https://www.tencrazy.com/gadgets/mfx/

Not all plug-ins can send or receive MIDI data.

The TAL Vocoder does not send MIDI data so "Enable MIDI Output" is disabled.

It can receive MIDI data so "Enable MIDI Input" is available. This is the option that needs to be enabled for the plug-in to appear in a MIDI track's output drop down. IOW, the plug-in must be set to receive MIDI data in order for a MIDI track to send it data.

I doubt re-installing the DAW will make a difference but you can always try it.

Yeah, not real happy with Softube since I got the news this May.

AFAIK, Softube has no plans to fix their PC modules.