abacab

It's amazing how all the synth "experts" over at the KVR instruments forum dismiss sampled synths. They ignore the sound possibilities, and just focus on the knobs and ultimate tweakability, lol!

I think 9 positive detections at VirusTotal would give me pause...

That item was in the utilities menu in Sonar Platinum. I just checked, and it's there. @scook is correct. It has been moved to "Get Started" in the Help menu. Same thing with a few tweaks for CbB...

Good tip Larry! Nice addition to several courses I already had at Udemy!

@scook I think I just figured out where my 3 missing PC modules went. By default when you create a new project, Cakewalk loads up a compressor, and a tube module in Pro Channel, along with a few other modules. So when you initially look at the Pro Channel "Add Module" list you won't see the Tube Saturation, the PC4k, or the PC76 modules listed among the available module choices. But if you delete the existing compressor and tube modules from the active Pro Channel, then they all become available to add. Ooops... I never noticed this behavior before... I think the labels in the Pro Channel threw me off. If you look closely at the default compressor, it says "PC4k S-Type" in itsy bitsy, tiny letters in the UI. But the top of the module only says "Compressor". Likewise, the Tube Compressor is only labeled "Tube".

IK Syntronik for sampled synths +1. I have UVI Digital Synsations, but I prefer the IK user interface over that of the UVI workstation. I will have the Arturia modeled synth collection eventually...

@scook Those registry entries are there, and both point to the same folder: "C:\Program Files\Cakewalk\Shared Utilities\Internal". When I look into that folder the PC4K, PC76, and Tube Compressor are still missing, even though I just re-ran the Platinum installer. I think I should probably take this discussion to another thread now, as this may not have anything to do with 2020.01. I just thought earlier that it was a strange coincidence that it was the same 3 PC modules affected.

@Jonathan Sasor Thanks, I just re-ran the full core installer for Sonar Platinum 2017-10. Still no sign of those particular PC modules PC76, PC4K, or Tube Saturation. But the rest of them are still there, as before.

Just curious, but where are those 3 PC modules in question stored on the computer, and which installer puts them there? I think I need to re-install them. I just noticed I am completely missing them, and have had Sonar Platinum [2017-10] - x64 installed since before I installed Cakewalk by BandLab. Just checked Sonar, and they are missing from there as well. Command Center indicates that everything for Sonar is already installed.

I like Komplete Kontrol, but the lack of instrument layering puts it at a disadvantage, unless you layer multiple instances in a DAW host. AKAI has VIP, which I have, and it works standalone as a plugin host, as well as a plugin for your DAW. You can layer up to 8 VST instruments (channels), 4 VST insert FX per instrument, with sends to 4 busses and then save as a multi. The lack of a standard makes it a bit hit or miss which plugins will work with it, but most of my plugins seem to be compatible. Downside to VIP is that AKAI doesn't seem to be very active in continued software development for this product (another inMusic brand), such as no VST3 support yet. AKAI seems to be more focused on hardware. That new Unify from Plugin Guru looks interesting, too. Small developer, who implies bigger things are to come! Price looks good right now, at $59 until March 1st. https://www.pluginguru.com/products/unify-standard/

What's weird is that I also have Sonar Platinum installed, and I don't even see any of those PC modules available, in either Platinum or CbB...

If the instrument is virtual, you can record that directly now. https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=SoftSynths.27.html

Matthew, I think you may be onto something there... On my DAW PC I use the basic integrated Intel HD graphics, with drivers supported by my CPU and chipset/motherboard. Rarely see any unexplained app or plugin crashes described by others. I have often wondered if graphics driver incompatibilities could be at the root of some of those issues...

If you are running Win 10 Pro you can do this to disable automatic updates:

The tutorial covered the MIDI side of things, initially using Philharmonic inserted with one MIDI source track and the 1st audio output. The plugin in this example was used with only one stereo audio output. In this case the mixer window in the plugin is capable of mixing the individual instruments and routing them as one stereo signal to the Cakewalk mixer using one Cakewalk fader. Alternatively you could have inserted Philharmonic with one source MIDI, and all audio outputs. That would result in 16 audio channel faders in Cakewalk. But then you would need to go into the Philharmonik mixer window and send each audio output to its respective channel in Cakewalk. By default, a multitimbral plugin usually mixes & routes all audio output to the first stereo output, but you then can manually change if the plugin offers an audio output for each instrument slot. It possibly would have complicated a basic tutorial to go into all these extra steps, as it really comes down to personal preference for which end you choose to do your mixing on. Obviously there may be advantages to mixing in Cakewalk if you want to use advanced insert FX plugins on specific instruments in the mix.

I forgot to mention that Cakewalk itself (at least on my system) has a sub-folder for VST2 plugins. "C:\Program Files\Cakewalk\VstPlugins". I left the Cakewalk products there, rather than risk moving them. All of the Cakewalk VST2 live here, everything from Sonar to CbB. Occasionally a 3rd party will drop a VST2 here, but I will move that to the main VST2 folder. As far as Cakewalk VST3, they all go into the general "C:\Program Files\Common Files\VST3" folder.

The Cakewalk browser panel shows a very clear indication of 32-bit or 64-bit plugins if you just look in there...

That's pretty much the way I did it, except that I didn't put the VST2 sub-folders down in the "Common Files". I left them as sub-folders a level higher up in the "Program Files".

I assume you are referring to the Windows XP days, before Sonar was published as a native 64-bit application (I can't remember the version that changed that...)

I believe CbB requires the 64-bit version of TTS-1 (included), as it is not a VST (it's a DXi plugin). CbB will ignore a 32-bit DXi, even if present on the system. But as far as VST plugins are concerned, Cakewalk will use its proprietary BitBridge to include 32-bit VST plugins.

As we used to say, "if it ain't broke, then don't fix it!". But then again, it always made me uneasy whenever something "magically" fixed itself...

The Sonar installers com with both flavors included, and they ask if you want the 32-bit or 64-bit version at the beginning. You can use your old download installer files, or access them again at your old Cakewalk account at https://www.cakewalk.com/My-Account/Login?ReturnUrl=%2fMy-Account If your product had shipped on DVD (prior to the Sonar X1-X3 series) instead of download, you can use that.

CbB is 64-bit only, and comes with a 64-bit DXi (Direct X) plugin version of TTS-1. You mentioned earlier that you had 32-bit Sonar programs installed. What do you have? (Edit: CbB will run 32-bit (VST, not DX) plugins with the included bit bridge)

Since Philharmonik 2 and SampleTank 3 use essentially the same interface, just with a different "skin", the video instructions should apply to both.

If you open the plugins view in the Cakewalk browser, it should tell you if the plugin is 32-bit, or DX, as is the case of TTS-1. Click once on the instrument or FX in the browser, and then look at the info bar at the bottom of the browser pane for details. I would install the 64-bit version of Sonar to get the Sonar plugins in the 64-bit version, and avoid 32-bit whenever possible. Pops and glitches can be due to various causes, but typically they have to do with your audio driver settings, such as too low audio buffers. Try raising them until the pops go away.