msmcleod

Or change custom so it looks like ALL. You can add as many new ones as you like, so you'd not be losing anything.

I think it's just badly translated - the plugin is clearly disabled in the screenshot.

@MozartMan - Sonar Free Tier will receive updates at the same frequency as the Premium version - it's exactly the same application. New features may not be available in the Free version, but all of the bug fixes will. That's not to say that the free version won't receive new features - just not all of them.

Is this on every project load, or only on the first time you start Sonar?

There are usually options in these VSTi's to control how samples are loaded. Most have the ability to limit the memory they use for samples, and also how they load or stream samples - e.g. do they load the libraries up front, or load (or over just stream) the samples they need on demand. Certainly in Kontakt, if you set it to load on demand, and purge all samples before saving your project, the project will open extremely quickly. If you set it to load all libraries, it'll take much longer to load the project. The downside of load-on-demand, is you may have to play your project all the way through so it picks up the samples it needs, and you can expect glitches during this first playback if the libraries are large. Ensuring your sample library is on an SSD makes a huge difference. Loading a large patch in Omnisphere went from 45 seconds to 2-3 seconds when I moved from HD to SSD (although most patches load in less than a second). You can tweak your memory limit/preview size/streaming settings to optimise this. With the exception of streaming, there's no getting around the fact that those samples need to be loaded however, and they're going to take time to load, so really it's up to you when you want that to be. If you're going to use sample based instruments (and especially if you're streaming), you need plenty of memory and a fast SSD to store the samples to get optimum performance. For streaming, you'll need a faster PC too. Some even go the extra mile and use Vienna Sound Library with their samples on a separate PC dedicated to hosting the samples.

@tdehan - please save your project as a .cwz file, and send a link to it to @Jonathan Sasor.

Delay compensation is still in place when you bypass a plugin, otherwise you'd get glitches every time you toggle bypass/enable.

Check your PM.

That is what dragging to the time ruler does - it uses Melodyne to extract the tempo from the audio. This is why you need Melodyne installed for this functionality to work.

Remove the RPN events, and it'll work with SI Piano. With any external MIDI file, you should check the MIDI events and their values are actually supported by the synth you're using. Also, the velocity of the notes is very quiet.

Are you sure you're using Ripple Edit ALL ? It sounds like you're using Ripple Edit Selection, with "When clips are selected, select track automation too" setting turned off.

Fixed for the next update.

You need to uncheck both of these in preferences, and do another VST scan:

I quite like the Cerberus Bass Amp from Kuassa.

Just imported 20 audio files here at once without issue. It worked both from Windows explorer, and the browser. On new projects, audio is stored in the Global Audio Directory until you save the project. Double check that you've got enough space on that drive, and the directory is excluded from anti-virus programs. If drive space is the issue, you can always move this directory to another drive.

The first verse sounds fine without bass - it's a good contrast to the intro, but I'd bring one in after that.

The link @Ashwin Rao posted is a link to the update installer. This won't work if you've already installed 2025.09. The full installer for 2025.08 can be found here

The main reason for not recording the vocal first is that: 1. Without a rhythmic reference, most people's timing won't be consistent 2. Without a harmonic reference, most people's tuning won't be consistent This is why most singer/songwriters record their vocals with an acoustic guitar or piano as backing, as it provides both a rhythmic and harmonic reference. While you can use melodyne to fix any tuning inconsistencies, vocals tend to lack any meaningful transient information to extract a tempo map. I'd at least recommend singing along to a drum beat or metronome.

Most likely this setting: The intention of this setting is to prevent reverb/delay tails being cut off abruptly. Adjust as required.

1. Select all the tracks you want to rename 2. Open the track inspector 3. Type in the new name in the track inspector

The keyboard binding is there, but it was missing from the preferences dialog. It's been added for the next release.

From what I can see, Screenset Lock/Unlock is still active.

A couple of things to bear in mind: 1. Keyboard shortcuts are basically a mapping between a key and command ID. Whilst command ID's don't change, some are deprecated over time as new features make older ones obsolete. All this means is, that a keyboard shortcut bound to a deprecated command ID won't do anything. 2. Keyboard shortcuts are view dependent, with the current view being the one that has focus. Key Down/Key Up events are windows messages that are sent to a particular window (a Sonar view is basically a window). This is usually the window that has focus, unless whatever is sending the event has been coded to send to a specific window. I'm not sure what options Auto HotKey has for sending to specific windows or changing window focus, but unless it can do this, it will limit what can do. Based on the amount of sleep commands I see in the scripts I've seen, I suspect it's relying on waiting for a particular window to gain focus, or for an operation to complete, so that when it sends the key event, it's being sent to the correct window. Obviously the sleep time is going to be dependent on how fast your particular machine is, and in some cases how big / complicated your project is. Normally making the sleep time longer will help to avoid any potential target window "misses", at the expense of the script taking longer to complete. Finally, having the same key combination doing different things for different views should be avoided. It's certainly possible, but it's dangerous in an Auto HotKey situation as you can't guarantee a particular view will have focus just relying on sleeps - and you certainly don't want a key combination being mapped for global and also mapped for a particular view.

There are two separate MIDI messages: - All Notes Off: turns off all notes - Reset Controllers: resets all continuous controllers "Zero All Controllers" sends the latter, which has no effect on Notes, unless there's a sustain CC event that hasn't been reset. For hardware MIDI devices both these messages are sent out. Obviously it's up to those synths to respond appropriately. For software synths, it's slightly different when Zero All Controllers is enabled. Pitch Bend, Modulation and Sustain are always reset. Reset Controllers is only sent out to soft synths if the Cakewalk.ini setting SendResetsToSoftSynths is set to 1. However again, it's up to those synths to respond appropriately.