scook

The sort in the Start Screen may look strange because the files are read unsorted from the OS (apparently limited to the first 100 entries) then sorted alphabetically for display. The sort the Template window in the New Project dialog is alphabetical too. IOW '2' comes before '3' just like 'a' comes before 'b'. So, '24' comes before '3' just like 'apple' comes before 'banana'.

Here is the link for keyboard shortcuts on the CbB help menu. Many may be customized in preferences.

Given the exact cutoff at 100, there may be a limit on the number of project templates. Looking at the number of templates included with X2 on, it appears SONAR Platinum shipped with the most project templates at 30. My custom folder has 8 templates. Instead of a large collection of project templates, For new projects, I rely on track templates, several "empty projects" and the 8 project templates in my custom folder. Does the New Project dialog show all 181 templates?

It is possible to bypass individual track/bus FX racks. Right-click in the track/bus FX rack for a context menu with the bypass options.

I don't think the plug-in manager reads anything other than the registry and layout files. VST plug-in validation and gathering data about them is the domain of the VST scanner. The exclude list is handy for reducing the number of plug-ins the DAW uses to build the dynamic "Sort by" layouts.

It does not matter where the project templates are physically located as long the the path is correct in preferences. Personally, I do not use the default path for the reason mentioned in my previous post. Of course, track templates (file extension cwx) are not show in the start screen only project templates (file extension cwt) are.

AFAIK, the only notice about the forum was posted in the old forum. My guess is this was by design to allow for a soft roll out. The next release of CbB will have a link to the forum. It will likely be mentioned in the release notes. This may have an impact on new user activity.

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingAudio.15.html

The plug-in manager like the VST scanner is a separate program from the DAW. It is shared by all versions of SONAR and CbB installed. It may be instructive to know which OS is running. If a virus scanner running and if turning off the virus scanner makes a difference.

For more about dumps here is an old Cakewalk KB article some of it still applies.

My guess is the first thing support would suggest is update CbB. The latest version is 2018-11 build 31. They would also ask which OS and if it is it up to date. May want to look in the Windows Event log for clues about what is failing. Does the problem happen when running one interface? Does the program generate a crash dump? The dumps would be in %appdata%\Cakewalk\Cakewalk Core\MiniDumps. For a hung process, there is likely no dump but one may be generated using ProcDump. If it were my problem, I would consider providing this information (including a dump) to support@BandLab.com

It is possible to use one Transpose MFX like a bus summing 16 tracks with a virtual MIDI cable. The free LoopBe1 and LoopMIDI support a single cable with 16 channels. LoopBe30 supports up to 30 virtual cables. It may be possible to create multiple virtual cables with LoopMIDI but I have not tried and don't have it installed ATM. I am not sure the TrackKey+ function still works in CAL but I know manipulating note values does. The language was deprecated around the original release of SONAR and BandLab has no plans to revive it. Even so, there is not much advantage to using CAL in this case. Stopping the transport, selecting the tracks and running a CAL script is the same effort as running Transpose from the menu.

I would not waste time pining away for this. While anything is possible, this is a pretty definitive statement from the owner regarding CAL and scripting in general.

With "Always Echo Current MIDI Track" enabled, it is still possible to manually turn on input echo but 1) it is easy to forget to do so being used to having it set automatically 2) there are times having input echo enabled on the current track is NOT wanted. For example, consider an instrument or MIDI track with its input intentionally turned off (i.e. set to None). It makes no sense to enable input echo on a track with no input setting. In this case, CbB automatically switches the input to Omni when input echo is enabled. This means the track picks up all MIDI input from the controllers AND plug-ins. Often this results in unexpected "crosstalk" on the current MIDI track. This has been the subject of more than a few threads.

The synth does not matter. Input echo would be my guess. Before recording, both the arp and the instrument must have input echo enabled for MIDI data to get to routed out of the plug-ins.

CbB has a built-in arpeggiator. Unfortunately, there is no pattern editor. At least not now. Project 5 could create and edit patterns. Some of the old pattern files are still available here and here. These links came from an old forum discussion about the built-in arpeggiator.

I believe Kirnu is the free precursor to Kirnu Cream a plug-in sold by Arto Vaarala.

Here is how to setup BlueArp, Cream or any VST arp which is recognized as a synth in CbB (or any synth that generates MIDI data). 1) add the arp to the project, I use an instrument track but it will work when added with an audio and MIDI track. NOTE: all synths in CbB must have an audio track even if the synth does not make a sound. Adding an arp with only a MIDI track does not work. 2) make sure "Enable MIDI Output" is checked. It should be by default but is a good idea to verify. 3) Add the synth(s) to drive with the arp. 4) Set the synth input(s) to the arp 5) make sure input echo is enabled on the arp and synth(s) instrument/MIDI tracks WRT input echo, I find it easier to manage manually. This means turning off "Always Echo Current MIDI Track." For arps that use lower MIDI note values for control, consider creating drum maps, instrument definitions or step sequencer pattern templates.

An output set to None or set to hardware no longer available to the DAW will generate this message too. There is a global setting to prevent the messages from being displayed - set WarnSilentBuses to 0 in Preferences > File > Initialization File.

There is no local help for CbB. The local help option in Preferences was removed. I do not believe there are any plans to release the help in alternate formats. There was some discussion early on about making the html downloadable but there has not been any mention in some time. It would be nice to have search available for the CbB help. Until that time, here is how I located the urls for posting here: 1) use the web search to generate results for old Cakewalk products 2) narrow the search for Platinum, Professional and Artist Documentation using the link at the top of the search results 3) select a topic 4) if the topic is what I am looking for, I replace SONAR in the url to Cakewalk 5) open the new url Most times this will open the appropriate CbB help. If it does not, for example if the SONAR page is in "New Features," I fall back to the CbB help index. AFAIK, the local help code switch "UseOnlyOfflineHelp" and the supporting code are still in place. Most of the most recent SONAR help is still applicable to CbB. I have not tried it recently but it still may be possible to use the chm from SONAR by copying the chm into the CbB program folder and setting "UseOnlyOfflineHelp" to 1 in HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core

By default, project templates are stored in C:\Cakewalk Content\{DAW Name}\Project Templates I prefer to change the Template path in Preferences because a custom path is not updated by the installers and I do not have to copy templates with each new DAW. Since Platinum and CbB the copy is less of an issue but updates by the installers are more frequent.

The MS library to support multi-touch prevented XP from installing X2a.

It does not matter - some force everything into the Cakewalk default folder, some use a folder outside of Program Files, some use manufacturer defaults. There is no standard location for VST2 plug-ins. The VST3 spec provides a standard location and VST3 installs should use it but even then Cakewalk will load VST3 plug-ins found anywhere in the scan path. Some programs are not as forgiving.

Starting with SONAR X3 there is no need to configure any effect as a synth. If the VST plug-in reads MIDI data, make sure "Enable MIDI Input" is selected on the VST2/3 drop down above the plug-in UI. If the plug-in sends MIDI data select "Enable MIDI Output" from the same drop down. Doing this will cause the plug-in to show up in the input and output drop downs of MIDI tracks Here is an image of both options selected for the MidiShaper plug-in by CableGuys To summarize, the setup is the same for any effect plug-in that reads MIDI data. The steps are: 1) add the plug-in to the FX rack of the track/bus to be affected 2) Use the VST2/3 drop down above the plug-in UI to "Enable MIDI Input" 3) Add a MIDI track with input set to the controller, output set to the plug-in, enable input echo For plug-ins that send MIDI data in step 2 "Enable MIDI Output" then there is an additional step to add the plug-in to an instrument or MIDI track input. The additional step may be instead of step 3 depending on the plug-in.

CbB runs on Win7 but is developed and optimized to run on Win10. Very little testing is performed on Win7.