scook

It may be a memory issue. Union recommends a minimum 8GB. IIRC, Zampler and Sampletank load all of the samples needed for a preset into memory, Consider going to 16GB or more if using a lot of sample-based instruments.

Once multiple PRVs are created use the filter to restrict which tracks are visible in each instance of the PRV.

This is possible today. After creating a PRV, right-click the tab if docked or the left Windows menu if undocked and lock the contents. Once locked, create another PRV and so on for as many copies of the PRV as needed. For stacked and synced PRVs, the only option today is the inline PRV.

Yes, Launchpad was developed and runs on 64bit Win10.

Instead of freeze try this http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=SoftSynths.12.html Freeze disconnects the synth. To reconnect a synth - When the synth rack is in the browser pane click on the synth in the synth rack to select it and use the synth settings menu "D" in the image below to access the connect option When the synth rack is in the multidock or undocked click the power button "A" in the "Undocked" image below

1. no 2. it requires editing HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\Recent File List in the registry Because of these and a couple of other issues, I wrote an tool called Launchpad. This free tool can create lists of projects without any size limit and delete projects from most recently used list in the registry. Here is the thread about this tool and other things I have written

Using the Virtual controller the following inputs work for both synths. All Inputs - MIDI Omni All Inputs - MIDI Ch, 1 Virtual Controller - MIDI Omni Virtual Controller - MIDI Ch. 1 The difference between these 4 input settings are All Inputs accepts data from from all MIDI devices including the virtual controller Virtual Controller accepts data from the Virtual Controller only MIDI Omni accepts data from all channels from the specified device MIDI Ch.1 accepts data from channel 1 only from the specified device AFAIK, the Virtual Controller only transmits on channel 1. FYI, SI plug-ins play all notes in the instrument's range regardless of their channel assignment. Just like recording audio, there is no need to select a track to record just click the record button. Also like audio, to hear the track while recording, input echo must be enabled. Again like audio if two tracks are set to record from the same input (in this case the four inputs identified above are effectively the same) they both will record the same data. Finally, if both are set to input echo they both will play whatever data is at the track input just like audio tracks. They should but it is common practice to leave an empty measure or two at the beginning of a project to allow virtual instruments time to prepare for data. SI series should not be that sensitive.

Use the MIDI Even Filter MFX to block modwheel data from going to DP.

I think this may work better for you Install LoopBe1 Configure it as a MIDI input and output device in CbB preferences. In the project add a MIDI track and load the drum map preset to use in the track. Notice the outputs are routed to LoopBe1. Of course, the drum map may be skipped and use LoopBe1 out directly and if desired drum maps may be added to the actual drum synth tracks created in the next step. If a drum map is used in this track it may send notes to all tracks listening to LoopBe1 or to individual synths. Add the drum synths using instrument or audio+MIDI tracks. Set the inputs on the instrument/MIDI tracks to LoopBe1 and enable input echo. Program the drums in the MIDI track with LoopBe1 as the output. As a safety measure consider setting the input on this track to virtual controller to prevent accidentally creating a feedback loop in LoopBe1.

This problem may come back to haunt you. Consider running uninstall from the BA meu where the Add Ons option is located, correcting the problem using this info and reinstall CbB.

The "Link to Original Clip(s)" in the lower left of the dialog is not checked

That's right, using alternate note names is not persistent. This request has been around for some time.

Whether a track uses a drum map or not the notes in the track will trigger only one target. A drum map can send data to multiple plug-ins but the notes in the map may be assigned to only one synth at a time. To have the same MIDI data trigger more than one synth (whether using a drum map or not) the tracks either need to be cloned using linked clips or a virtual MIDI cable must be used to broadcast the MIDI data to multiple tracks.

This is by design as this area is intended for use with MIDI hardware. The screen is disabled when no MIDI output devices are setup in CbB. It is possible to define alternate note name entries for the PRV Note Pane with a text editor. Open the master.ins in %appdata%\Cakewalk\Cakewalk Core in the text editor (may want to make a safety copy of master.ins before editing) Under .Note Names create a section called [AD Drums] (or whatever you want between the brackets) and add the MIDI note number=Drum Name pairs to appear instead of the keyboard in the PRV Then under .Instruments create a section using the same name (in this example [AD Drums] and add the following Patch=1..128 Key[*,*]=AD Drums Drum[*,*]=1 Save master.ins Now the new section should appear in the drop down in the PRV note names dialog. That said, the drum maps (I know you have already posted a request about them), track and project templates have already been built for AD2 and are available in the old Knowledge Base https://www.cakewalk.com/Support/Knowledge-Base/2007013364/Setting-up-a-Drum-Map-for-Addictive-Drums-2-in-SONAR If one creates the .Note Names section as a free standing ins file. There is a utility to convert it to a simple drum map. The utility may be found at http://dis.sesseler.de/ in the Cakewalk Sonar section.

Select a smaller font size using the File menu

Enable input echo on Track 1 using the button to the right of the record button. The delay is caused by the interface driver buffer settings and plug-in delay compensation. Make sure the interface is running ASIO driver mode and set the ASIO buffers to 128 samples or less. Chances are the ASIO buffers will need to be set in software supplied by Roland.

This image Shows Output Latency of 1333 samples and Input Latency of 304 samples for a total round trip of 33 ms about 3-5x more than usable. See if the drop down above these values will help. If not try the driver mode WASAPI settings.

The reason the gif is not embedded in the post is because the link points to the imgur page hosting the image. To embed an image/video requires linking to the image/video itself and not the page hosting the image. The url reported for the video is https://i.imgur.com/DZSfFaf.mp4 I describe how to embed an image in detail here I upload png and animated gifs to imgur. Never uploaded an mp4 to imgur. WRT sidechain, I do not have Neutron so cannot test. Sidechaning in CbB works the same for all plug-ins that have a sidechain input. A send to the plug-in needs to be created on the track transmitting data to the sidechain input.

Make sure to use the 64bit version of EZD. 32bit versions of Toontrack products do not work in 64bit hosts.

@Robert Bone SONAR/CbB install order has been pretty thoroughly discussed in this thread

Or at least open the preference screen and give focus to the Driver Mode (not Driver Model) entry when closing the error message.

If using the same audio device for Windows and CbB make sure both are set to the same sample rate.

It is as I suggested, the error message is telling you the driver mode selected in the DAW has no devices available and it is providing information on where and how to remedy the problem. IOW, when the Focusrite interface (which normally uses ASIO) is not available the DAW shows the message you received because the PC sound chip cannot use ASIO mode except for a very buggy RealTek driver. So the driver mode must be changed to one of the WASAPI, WDM or MME modes in order for the DAW to use the PC sound chip.

Turn off Always Echo Current MIDI Track and assume manual control of input echo then double check all the instrument and MIDI track input assignments. Keep in mind when an instrument or MIDI track has input echo enabled and the input is set to None, CbB changes the input to "All Inputs - Omni" so the track has some input to echo.

use the virtual controller