scook

An option I have not tested but looks like the closest thing is Allow MIDI Recording without an Armed Track

I don't know of a single SynthEdit development ever ported to 64bit. For synths stuck at 32bit the solution is easy, render the audio. There are some 32bit plug-ins that have 64bit jBridge wrappers though. It is a service provided by jBridge. Dedicated wrapper or not, it is still an extra layer of buffering and code that must be dealt with by the 64bit host.

By default 32bit SONAR installs in C:\Program Files (x86) along with a set of 32bit "Shared" folders. Of course, there are separate 32 and 64bit registry entries. The version folders in "Cakewalk Content," user directory and ProgramData are shared by the same 32/64 version of SONAR.

Yep, in the new features section of their product announcement https://www.cakewalk.com/Press/Release/1142/09-15-09-Cakewalk-Announces-SONAR-8.5-Producer-and-SONAR-8.5-Studio-Now-Available grabbed a new copy of the spreadsheet

I must be using an old version of your spreadsheet.

The best solution for migrating 32bit projects is opening them in a 32bit DAW and replacing the plug-ins will ones that have 32 and 64bit versions. One can run pretty old 32bit Cakewalk DAWs on Win10. Time is running out though. Some plug-in manufacturers have stopped producing 32bit products entirely.

CbB includes no 32bit plug-ins. As noted in the previous post, CbB does not include Session Drummer 2. In fact, Session Drummer 2 was not part of SONAR for some time. It was replaced by Session Drummer 3 in X1. Session Drummer 2 that shipped with SONAR included both 32 and 64bit versions.

Generally projects ARE backward compatible but the DAW will issue a warning about the project being created with a newer product. Of course, the DAW opening the project may not have the ability to support all the features referenced in the project. In this case, the unsupported feature(s) will not be present. Projects containing patch points and aux tracks will not open in DAWs that lack support these features. Patch points and aux tracks are supported in CbB and SONAR Professional/Platnum Oct 2015 or newer.

No, both archiving and freezing remove the synth from memory.

This has nothing to do with the OP's beat count issue. It is an audio setting so it would not affect MIDI clips. This setting was replaced in SONAR X3 when VST3 support was added. The new settings is called Always Stream Audio Through FX

I don't have Kontakt so can't offer plug-in specific advice but keep in mind input echo is needed when trying to monitor the data at a track's input.

Not quite but it is a good one...possibly with the lowest latency. I use Voltage Modular's MIDI routing for certain applications. Reaktor and other synths could work too. When using a synth instead of a virtual MIDI cable it is necessary to provide a complete routing (IOW an instrument track or audio+MIDI track pair) for the plug-in even though its audio output may not be used or even exist. Failing to provide a complete routing results in no MIDI data being sent from the plug-in.

Comparing software solutions to hardware is not an apt analogy but do not worry now that I recognize the user name change I can ignore the posts. Good luck.

Just another reason to follow the plug-in makers lead and forget about the 32bit plug-in.

32bit plug-ins must be bridged to run in a 64bit host. This image shows a plug-in running in BitBridge. The VST2 drop down is on the standard header. Plug-ins running in BitBridge have a separate window for the standard header. To open the standard header hold down the ALT key when inserting the plug-in or opening its UI. The standard header window usually opens behind the plug-in UI. That said, a decade ago was a good time to start looking for a 64bit replacement plug-in. Continuing to rely on plug-ins the manufacturer abandoned years ago is not a good idea.

Maybe, I suppose my recollections about using those entries and developing a different way to handle "Save As" when it changed could be false memories.

Yeah, it is nice to have the dialog respecting the path entries again.

The default scan path for 64bit Studio Instruments is C:\Program Files\Cakewalk\Vstplugins 32bit Studio Instruments is C:\Program Files (x86)\Cakewalk\Vstplugins "Default - All Plug-ins" is the default plug-in layout used in SONAR 7. It has been about 15 years since I have used SONAR 7 so I cannot be more specific. The VST reset and scan functions for SONAR 7 are run from the plug-in manager.

64bit SONAR and CbB use the same plug-in manager, VST scanner and 64bit version of Studio Instruments. They maintain their scan paths and list of scanned plug-ins in different parts of the registry. Make sure the scan path is correct. Then launch the plug-in manager from SONAR 7 and run a VST scan. If the plug-ins do not appear in the "Default - All Plug-ins" list run a VST Reset. You should only use the VST scan and reset options in the plug-in manager for SONAR 7. For CbB, use the VST settings in preferences for these functions. 32bit SONAR 7 has its own plug-in manager, scanner, scan path, list of scanned plug-ins and 32bit plug-ins. Make sure the scan path contains the 32bit Studio Instrument dlls (these will need to be installed using the SONAR 7 installer) and run a scan. FYI, please do not cross-post on this forum. It just makes more work for others and does not get a faster reply.

It is easier than that if no changes will be made to the data. Set both synths to record at the same time. No copies, no extra routing needed. But, if one want to change the data and keep it consistent across multiple synths, links clips or a virtual MIDI cable can save a lot of time and effort.

Do you mean the VST2 plug-in does not work (I can't help in this case, don't use Antares software) The VST2 plug-in is not in the plug-in list make sure to use one of the manufacturer supplied "Sort by" layouts or update your custom layout if the plug-in is not shown in the Plug-in Manager VST Audio Effects category, verify the VST2 plug-in is in the scan path then see this post for how to scan for failed or missing plug-ins

I do not have Purity but expect the plug-in should have documentation concerning its operation. As to how set up a MIDI file using plug-ins in general consider taking advantage of the automatic mapping built into Cakewalk. Make sure no MIDI output is selected in preferences. Use File > Open to open a MIDI file. This will cause Cakewalk to add TTS-1 to the project and set up all the instruments in the MIDI file. At that point one can review how the synth is setup, play the file, change the instrument assignments and add new synths to the project to replace TTS-1. If new synths are added to the file, make sure to save it as a Cakewalk project. Saving as a MIDI file does not retain non-MIDI data such as plug-in assignments.

Yes, a drum map works well as keyboard splitter but restricts notes to a single output. Now if a drum map could send notes to multiple targets....

Create a master MIDI track and send the output to a virtual MIDI cable. Use the virtual MIDI cable as the input for the synth instrument/MIDI tracks. I use LoopBe1 for this.

FWIW, Channel Tools was added to CbB 2020.08 This was mentioned in the OP's thread in the main forum. Along with a post from @Craig Anderton about a way to use the plug-in. Reworking the panning in the DAW itself may pose some interesting backward compatibility challenges.