scook

Or add the clip to a drum synth and trigger it with MIDI. One of the easiest to use drum synths around is Sitala

SONAR 7 was release a couple of years before Win7. In fact, support was dropped for this DAW around the time Win7 was released. Of course, it still works but the software is around 13 years old. According to https://www.cakewalk.com/Support/Knowledge-Base/20071226/SONAR-7-0-2-Update 7.0.1 is required https://www.cakewalk.com/Support/Knowledge-Base/20071015/SONAR-7-0-1-Maintenance-Release There is also a 7.0.3 https://www.cakewalk.com/Support/Knowledge-Base/20080207/SONAR-7-0-3-Hotfix-Maintenance-Update

Often it is possible to select the entire image as most of the buttons are grey, Changing the hue only affects the ones with color.

The image in my first post is Track Control drop down. It is the drop down to the right of the Add Track and Duplicate track buttons above the track headers and below the track view menus. When the workspace menu is set to None the keyboard shortcuts SHIFT+left or right arrow step through its settings.

What if the workspace menu is set to None and the Track Control Drop Down is set to All If is possible to override the workspace using the Track Control drop down

Input Quantize is "O" in the track inspector image below from http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.3.html#1220713

It is the workspace setting, this drop down or both

If the project drive is a spinner, a defrag may help.

May want to provide the basics...you know, hardware info, OS, DAW version.

Yes, 64bit SynthEdit took a while but the latest version does produce 64bit VST2/3 and AU plug-ins. There appear to be a few differences between the last 32bit only version that may slow porting of old projects.

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.