scook

A soft synth requires both a MIDI and an audio track or a simple instrument track (a simple instrument track is a hybrid displaying MIDI input and audio output controls in a single track) in order to receive MIDI data and return audio to the DAW. The last 2 images show the synth and a MIDI track only. Add and audio track to the project and set the input of the audio track to the synth.

It works like any audio track and has always been this way. Typically tracks using a patch point as their input, such as an aux track, never record; they simply stream the data they receive. To hear this signal requires enabling input echo. This is why an aux track has input echo enabled by default.

If I had to guess https://www.perforce.com/blog/vcs/what-team-foundation-server Most VC systems don't do much with binary files like CbB project files. The existing versioning built into CbB is how most VC systems handle them - opaque blobs of data.

It is a single one-time use voucher with no minimum spending. See the Subscription Bundles: Sub 2 Own - Cash-Back Voucher section of https://www.plugin-alliance.com/en/support.html

Try CbB There have been a lot of updates since X3e was released in 2014. CbB installs as an upgrade to X3 in its own directory updating the shared files and utilities. Both DAWs will be available after the upgrade. Instructions on how to upgrade are here. Other than that adjusting disk buffers in preferences may provide smoother playback.

When a track has input echo enabled, if the track input is set to None, it changes to Omni. By default, Always Echo Current MIDI Track is enabled so any time a track gets focus the input will change from None to Omni. This is why I recommend turning this setting off and manually set input echo as needed.

fixed

It does not matter if the CbB step sequencer is used or not. It may not be a case of a synth sending MIDI data. Check the input drop downs on all the instrument/MIDI tracks. If they are set to "All Inputs" or the Virtual Controller with input echo is enabled will cause the MIDI to be echoed on those tracks too.

The "Get Started" wizard runs when CbB is run for the first time.

This is often the cause of unexpected MIDI playback

To contact support for BA directly use support@bandlab.com BA is developed by a different group at BandLab.

It is are on the way. See the video in starting around 18:50 Jesse talks about the new articulation map feature coming soon.

For issues related to BandLab Assistant exports contact support@bandlab.com. It is a different support and development group. AFAIK, they rarely appear in this forum.

You may want to perform a full install of SONAR 8.5, reinstall Professional, upgrade DP to v1.5 and Rapture to v1.22 then re-install CbB These are from the Hollywood Edge FX. The Hollywood Edge FX and a couple of other libraries are on the SONAR Producer 8.5 Additional Content disk.

Retiring 32bit plug-ins should be the goal. Most plug-ins that lack a native 64bit version are unsupported and have not been maintained in years. Using these plug-ins in new projects is asking for trouble.

Make sure the aux tracks have input echo enabled.

In addition to adding the CC to the controller pane be aware the X series has a problem handling CC64 when it equals 0. This is the last thread about the problem http://forum.cakewalk.com/FindPost/3030997 In this thread is an explanation of the bug http://forum.cakewalk.com/FindPost/3108848 And a CAL script to fix the data http://forum.cakewalk.com/FindPost/3108868 This is fixed in Cakewalk by BandLab. Consider upgrading.

You need to reassign the plug-in automation to the instrument track. To do this click on the synth in the synth rack and use the synth automation menu (J) or the insert soft synth options dialog (E) This image is from http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x20234

Don't read more into my post than is there.

MIDI channel is a property of MIDI notes. MIDI channel may be set for each MIDI note just like pitch and velocity. Cakewalk can force the MIDI channel per-track by setting the MIDI channel drop down in the track. If the channel is not set on the track the notes are sent with whatever channel value is in the notes.

IDK what "this" is. The freeze feature works the same as it has since it was introduced in 2004. I have no idea about the future.

Best leave VST3 plug-ins in the default "C:\Program Files\Common Files\VST3" folder and DO NOT create a directory junction to it. The scanner treats the VST3 folder a little differently than other VST folders.

One thing I failed to mention is the effect of directory junctions on the scan path. Scan path entries should be unique. Review the scan path and remove redundant entries. In the example above based on mklink /j "c:\program files\Cakewalk\vstplugins\steinburg" "c:\program files\steinberg\VST" I would remove "c:\program files\steinberg\VST" from the scan path.

As a rule, if a plug-in uses an installer, the best way to relocate the plug-in is uninstall and reinstall paying attention to the installer screens. Usually installers ask where the VST2 plug-ins should be installed. If the plug-in does not have an installer, it is safe to copy the plug-in and any associated files to a new folder. An alternative to actually moving files is leave them where they are and use directory junctions to logically consolidate plug-ins. For example, if I have plug-ins in c:\program files\steinberg\VST and want them to appear in c:\program files\Cakewalk\vstplugins\steinburg I would open a command shell as administrator and type mklink /j "c:\program files\Cakewalk\vstplugins\steinburg" "c:\program files\steinberg\VST" Directory junctions (mklink /j) can work across drives. There is very little advantage to putting the actual plug-ins on an SSD. The files are small and load pretty fast regardless of the drive type. Samples used by some synth plug-ins DO benefit from being on SSDs.

Before extensively editing a frozen track, I copy frozen clip to another track. Not only is the copy easier to work with there is no way to accidentally thaw the track loosing the edits. Alternately, if I know in advance, rather than freeze, I prefer to bounce to another track and archive the source track(s). Often times I move the archived tracks into a dedicated archive folder to "hide" them from the rest of the project.