msmcleod

Although RPN #0 #0 is the standard for Pitch Bend sensitivity, there's no standard as to what the ranges actually mean. Some synths have a maximum of two semi-tones for pitch bend range, so the RPN values will be totally dependent on what the synth supports. When using this RPN, the 14-bit range -8912 to 8911, or 0 to 16383 will be for the maximum range the synth supports. So if the synth support 2 semi-tones, either 8911 or 16833 will be 2 semi-tones; if the synth supports and octave, then 8911 or 16383 will mean an octave. You'll need to refer to the synth's documentation to be sure.

You can always try the Yamaha S-YXG50 - it's 32 bit though, and JBridge is recommended when using it: Yamaha S-YXG50 Portable VSTi v1.0.0

The 64-bit Double Precision Engine has nothing to do with the 64-bit architecture. It's to do with the precision of audio data during Sonar's internal mixing. With this unchecked, all audio read from your tracks (or live input) is converted to 32 bit floating point inside Sonar's audio engine. Once all plugin processing/mixing has been done, it's then is converted back to 16 bit or 24 bit (depending on your audio interface settings) when sending to the hardware outputs. With it checked, it uses 64 bit floating point instead. Some plugins however do not work properly with 64 bit audio. Fixed point audio (e.g. 16 bit or 24 bit) has an effective ceiling of 0dB. Floating point however, can go to 100's of dB without ever clipping. 32 bit float has an effective dynamic range equal to 24bit audio, but unlike 24 bit, it maintains this at any volume. 64 bit float has a much, much higher dynamic range. In practise, 32 bit float should be more than enough.

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.