scook

Using 2019-11 build 54? Install the hotfix

The images all look the same to me.

Colored icons and text are supported in the plug-in browser. Colored icons are supported in plug-in menus. The icons and colors used are theme dependent. Regardless of the theme, the plug-in browser and menus append 32bit plug-in names with (32-Bit)

This is why I like add links to the preference page (I used to put full screen snapshots but links are better IMO). Language is a display preference http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B06 too see the page in a different language, change the language setting in the url. For example, setting language=1 returns the page in German http://www.cakewalk.com/Documentation?product=Cakewalk&language=1&help=0x22B06 2 is French 3 is English 4 is supposed to be Japanese but it is falling back to English. I will send a note to BandLab about it. They not be translating CbB into Japanese at this time.

Yeah, those threads are part of what went into chapter 11 in The Huge Book of Cakewalk By BandLab Tips by Craig Anderton Pretty handy reference for $20.

thanks for the update

There are quite a few manufacturers who do not bother to support the VST2 hide feature

It works but depends on plug-in manufacturers' to support the process.

The 64bit DPE setting is unlikely the issue with VST3 MAutoPitch. The plug-in loads and works OK for me regardless of the 64bit DPE setting. I don't bother installing Melda VST2 plug-ins any more, all the VST3s I have tried from them work OK. While I have the MTotalFXBundle, there are quite a few I have not tested. As described by the OP, the problem seems like a system related graphics issue. I am not the one to ask about hardware/driver problems. The solution I provided WRT the L-Phase plug-ins came from Cakewalk support posts on the old forum.

no

This would do it. The pan control is after the PC and FX Rack. Here is the signal flow diagram from the help. Check out the flow in the Track and Bus sections. If you want to layer the amps and pan them together set the mixer in TH3 to mono and use it to blend the two amps before panning the track. The preset in the image above is set up to have one amp on the left and one on the right. To get the desired L/R levels in this case will rely more on controls in TH3 than the track pan control which is a simple stereo balance control.

AFAIK, the CAL message function still sends to the status bar. The status bar was removed from the Skylight UI in 2010.

Yes, multiple MIDI tracks with different MIDI Event Filter settings will work Drum maps can route notes to different synths. Although called drum maps, their use is not restricted to drums. Also, some hardware keyboards have zones for this too.

Any unusual characters in the project path or name? After restarting CbB is the project listed in the File menu? If so, there may be something wrong with %appdata%\Cakewalk\Cakewalk Core\StartPageCache Rename the folder, start CbB and the Start Screen will rebuild the folder.

In the FAQ section there is a thread for forum requests https://discuss.cakewalk.com/index.php?/topic/54-how-do-i-provide-feedback-about-this-community-itself/ Don't know if the Fluid display is on all devices but on my PC there is an option to use this format in the upper right on the main page This may be close to what you want to see

There are no separate installers for most plug-ins bundled with Platinum. They are grouped together. The BREVERB 2 PC module is in the main SONAR installer starting with SONAR_Platinum_Setup.... The regular BREVER 2 plug-in is the installer starting with BoutiqueFXSuiteSetup.... If you ran the Command Center, these installers are cached on your PC. The default location for the installers is C:\ProgramData\Cakewalk\Command Center\Downloads BTW both the BREVERB 2 PC module and plug-in are installed by CbB.

@devonaire45 I just took a look at Cripple Creek.cwp in the event list view. There is a lot of MIDI data before the first note in many tracks. This is common with 3rd party MIDI files. While a GM synth like TTS-1 can handle this data, Cakewalk sfz engine synths such as Dimension Pro, Rapture, Studio Instrument and Session Drummer do not. When these synths encounter unexpected data the sfz engine shuts down and the synth goes silent until the project is restarted. The only way to prevent this from happening with a DX plug-in like Dimension Pro v1 is remove the offending data using the Event list. Removing all the non-note data should stop Dimension Pro from shutting down. Apply the two updates in my previous message and the VST2 version of Dimension Pro will be available. VST2 plug-ins have an option to ignore the data as show in my post on the first page in this thread

This is a handy command to know. Not enough there to write an entire column about but certainly something that everyone should be comfortable with.

VST3 specification details where plug-ins should go - C:\Program Files\Common Files\VST3 (and C:\Program Files (x86)\Common Files\VST3 for 32bit) VST2 does not, however; most default to folders under C:\Program Files\ and C:\Program Files (x86)\ Cakewalk can handle non-default paths for VST3 but not all host do. It is best to let VST3 install in the default path. Pay attention to the defaults suggested by the manufacturer. Most use folders under C:\Program Files. Some choose other paths often because the plug-in writes into plug-in folder. If a plug-in has a proper installer, the default is the first choice unless you understand what it means to choose an alternate location.

VST3 plug-ins use the extension .vst3 instead of .dll. They are in fact dll files but with a different file extension. There is no easy way by inspecting the file names other than the hint provided by the extension to tell if a plug-in is a VST2 or VST3. The VST3 spec calls for all VST3 plug-ins to be installed in either C:\Program Files\Common Files\VST3 or C:\Program Files (x86)\Common Files\VST3 The VST2 spec is silent regarding install paths. There are a couple of common locations such as C:\Program Files\Steinberg\VstPlugins C:\Program Files\Vstplugins and their X86 equivalent paths The VST2 default in CbB/SONAR is C:\Program Files\Cakewalk\Vstplugins and the x86 path This is one reason most installers provide a way to specify where to put VST2 plug-ins.

Don't need an account to get either DP update. v1.2 is here v1.5 is here

It is not a problem They don't take up much room. Still see reports that some manufacturers VST3 can have problems. I install the VST3 only. If a plug-in does not seem to work as expected, re-run the installing to add VST2. I have not had problems with VST3 plug-ins in some time (even with the recently fixed lost settings problem because I did not use VST3 in a way that triggered the problem). That said, there are quite a few plug-in manufacturers, hardware and software combinations, experiences may differ. Sure, it is possible because the limits of the software are determined by the machine running it.

One could delete the VST2 dll or move it out of the scan path. After the next scan the VST2 plug-in would disappear from the "Sort by" plug-in layouts. It would be necessary to remove them from custom layouts. If one uses custom layouts, simply deleting the plug-in from the layout is enough to make a plug-in disappear. Rather than mess with deleting/moving the files, I prefer to use the Exclude feature in the Plug-in Manager. Select the VST or VSTi category in the Plug-in Manager Locate and click on the plug-in Click the "Exclude Plug-in" button The plug-in will no longer appear in the "Sort by" plug-in layouts but may be included again if something appears to be wrong with the VST3 plug-in. The Plug-in Manager has its own help file. There is a help button on the Plug-in Manager UI to open this file.

CW130Auto.dll was created for CbB. SONAR releases have similar files under different names located in the same folder. What makes CbB different is rather than create a new dll and adjust the program to look for the new file, the decision was made to reuse dll name even though it is incompatible with prior releases of CbB. As I wrote above, this is CbB issue; it is not a SONAR issue. SONAR is not affected at all.

The only time I have seen the MRU list not get updated correctly is when the DAW does not shutdown normally. I have not experienced any problem with the recent releases. That said, the MRU list for CbB is stored in the registry under HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\Recent File List Another feature in CbB is the ability to pin projects in the Start Screen. I rely on my Launchpad tool for project lists. It has the ability to delete entries from the CbB MRU list in the registry. It also has its own system of creating favorites and collections of project lists called snapshots. It can also write these lists to the CbB MRU list. If I need to do some fancy editing, the lists created in Launchpad are text files in My Documents.