scook

Sounds like this thread (includes a CAL-based solution)

AFAIK, Scuffam SGear2 VST3 does not work in SONAR or CbB. The VST2 does but it is not automatically installed. The dll is in C:\Program Files\Scuffham Amps\S-Gear_VST and needs to be copied into the scan path. Might have to bite the bullet and run a VST Reset from preferences with "Generate Scan Log" enabled. In your case, it will create quite the log but it may provide some clues. If you prefer to avoid a VST Reset move the Scuffam and KiloHearts plug-ins out of the scan path, run a scan, put the plug-ins back and run a scan from preferences with "Generate Scan Log" enabled.

If the scale is zoomed in, the names appear in the track keyboard but there are no names in the notes themselves.

Maybe there is problem with the channel assignment in the notes and forcing the channel for the track with the drop down fixes it.

CbB reads HKEY_LOCAL_MACHINE\SOFTWARE\Propellerhead Software\ReWire for available Rewire clients.

Running out of ideas. The only common element that I see are the problem plug-ins are all sample based. Voltage modular is not sample based but there are some dedicated sample modules. I use external drives for backup only. The internal sound chip was disabled when the machine was built. My DAW audio interface handles all audio. Is the external drive also the project drive? What virus scanner are you using? Try disabling it and see if the problem goes away. May want to try shutting down some of the background processes. I believe there are dropbox, Roland and Steam clients running.

It seems to work OK here. I stepped through a bunch of patchs, even with the transport running it played OK. I am running a Win10 on an i7-4970K @ 4GHz w/ 16GB of RAM The samples are on a regular internal HD separate from the system drive. I did not install the included Rex Shared Library in case it messes with the one included with CbB. It doubt it matters in this case. All the Trickster programs appear to be sfz files containing wavs. What version of CbB are you running? What is the ThreadSchedulingModel set to in CbB Preferences > Audio > Configuration File?

Is this 64bit Zampler-RX v1.07? If so, I will install it and see what happens. Any particular free sample pack to try?

With spinning drives...yes. With SSDs it comes down to disk capacity. If there is room on the disk, a single drive will do.

Have you tried lowering the buffer size? Sometimes extreme settings high or low can be a problem.

The images indicate there is plenty of memory. What are your ASIO buffer settings? Have you tried adjusting them" Have you tried WASAPI driver mode?

OK, the engine running is not the same as the transport.

Are you changing presets while the transport is running?

As you can see, this is not the case. Knowing the preset can make a difference.

The virtual B3 programs use instructions in the sfz file to setup the DP UI to control the leslie effect

I do recall some discussions in the past about DP and leslie plug-ins. Probably the reason the image above was already in my imgur account. Unlike dedicated organ plug-ins, DP can be programmed to be a lot of different instruments so there is no simple "turn the leslie off" switch. You could look in the MIDI Matrix of the programs you want to use (third button right of the current program name) and see if the modwheel is set up there. Of course this is a per-program setting. You may want to copy the programs before modifying them. Rather than mess with the programs, the Event Filter is easy and does just what you need...it prevents the modwheel data from reaching the synth. Could create a track template with DP and its track(s), the event filter, the rotary cabinet plug-in and the MIDI track to drive the rotary cabinet. Then everything you need would be all set in the template.

Yes, track 5 is setup to received MIDI from the audio interface and send MIDI back to the audio interface. There is no amount of fiddling with the other drop downs in track 5 that will cause the DAW to produce audio short of sending the MIDI to a synth and adding an audio track to received the audio from the synth. The channel assignment to 5 is not necessary. The patch assignment to ChurchOrgan is meaningless because there is no GM synth receiving the MIDI data. The MIDI data is routed straight back to the interface. In order to create sound from MIDI the MIDI data must be routed to a hardware or software synth. When using soft synths, you need to use an instrument track or at least one audio and one MIDI track to complete the necessary routing. A MIDI track by itself will not produce sound. Use the Add Track menu to add TTS-1. Read the "To create instrument tracks" section in the link, add TTS-1 to the project (step 1 and 2 from the "To create instrument tracks" section then click the Create button) and select the instrument to play in TTS-1 as I illustrated above. Forget about all the drop downs in the instrument track for now except the input from the interface and the output (which should be the master bus).

Thanks, that happened after my original post. I checked before posting and the update for the Newfangled Audio stuff was not there at the time. OP updated.

The VST3 is added by default in CbB so there should be no need to mess with the scan path Drum Replacer is not a regular VST so it will not show up in the plug-in lists. Melodyne is not an instrument it should show up in the FX list but that is not the preferred way to use it. Both Drum Replacer and Melodyne are Region FX. Here is the first in a series of Youtube videos about the Drum Replacer Here is an older video about Melodyne as a Region FX. The machanics of how to use the plug-ins are the same.

Downloads were pretty snappy when I posted the OP. I did have one error with the Anthology 64bit install. Changing the VST2 install path worked but it also dropped two of the plug-ins into the old path...odd.

I believe this is the case. The elements pointed to by "I" are unchanged between Mercury and Tungsten. There are no explicit references to this as an image or color in the theme editor. If it is capable of being altered chances are there would be side effects due to the color being used by several parts of the UI. That said, my gut feeling is this has not been exposed in the theme editor so cannot be altered without directly editing the resource file. IOW, this is a change request.

If one uses the version bundled with the old SONAR not only are the plug-ins locked to SONAR (and CbB) but they are locked to a point in time. There has been at least one update to the plug-ins. The bundled version is not getting updates. IIRC, there is a problem with the BlueVerb in the version bundled with SONAR.

Appears they updated all plug-ins to fix a VST3 crash issue In CbB, Eventide VST3 plug-ins would crash when changing interleave. While Noel coded around the problem, Eventide was researching a solution. I believe this is it. Installers available from https://www.eventideaudio.com/support/downloads Some plug-ins also got new artist presets. Update: Newfangled Audio updates hit after this post so I modified the subject line. The link is the same. Fixed the installer preset problem and a problem launching the manual from the program.

CTRL+Home For more shortcuts see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x18324 This link is in the CbB Help menu The Custom Module may be used to create a button to open the Console View

Drums maps exist in the project but may be saved as drum map presets using the Drum Map Manager. Drum Map presets are binary files stored on disk. These files may be copied and shared just like the drum maps bundled with CbB. There is a utility to create simple drum map presets from a .Note Names fragment in an .ins file. I mentioned this in the OP's other thread This can save a lot of time if one has a way to copy and paste map info from an existing document.