msmcleod

I think the only ones that are missing are Workspaces and the new Backup/Restore Settings (i.e. multiple config profiles) in Preferences.

The only way I can get this to happen is if: 1. I accidentally move the mouse into the clip region; or 2. I select the nodes such that all of the nodes are selected within a particular time period. This is the same for me using the smart tool or the select tool. Does making the lasso region narrower (i.e. closer to the node boundaries) help? [EDIT] - ok, I can repro this if there's a clip there and take lanes are collapsed. If take lanes are expanded, then it behaves as expected. We'll investigate further.

If input quantize is on then the MIDI is being quantized as you record it - i.e. it'll already be quantized. So quantizing afterwards is going to do nothing. Input quantize can be useful if set to a fairly coarse value (such as 1/4 notes), but if set to 1/16th notes, unless your playing is very accurate you may find notes in the "wrong" 1/16th slot. Quantizing afterwards isn't going to help as it's already quantized. It doesn't know which notes are in the wrong positions - all it knows is the ones that are there are quantized to 1/16th notes already. I'd recommend switching input quantize off, as the quantize dialog gives far more options for threshold/strength etc.

The issue is now fixed - it'll be available in the next update.

As far as I know, nothing has changed within Quantize between CbB and Sonar - is this quantize via the Quantize Dialog, or Input Quantize?

Thanks - this has been fixed for the next update.

Press P for Preferences, then go to Customization->Display. English is always the top language in the dropdown.

I replied to the original post. The issue is caused by using the "Entire Mix" category when having more than one hardware output in the project. Better to use "Hardware Outputs" in this scenario.

I can now repro. The key to the repro is to have more than one audio source when doing an Entire Mix export, e.g.: 1. Load any project 2. Add an empty audio track routed to a different hardware output 3. Export using a filename of test.wav Result: file is exported as test_.wav We'll investigate this further. If you've only got one hardware output in the list, you won't get this underscore. The Entire Mix category is really special case of category "Hardware Outputs" for simple cases (i.e. one audio output). If you've got more than one hardware output, it might be better to use "Hardware Outputs" and uncheck the one you don't want to export.

The latest version of Sonar (2025.07 build 97) should fix this issue.

Ace of Wands - Steve Hackett

That's just how articulations work in Sonar. They apply to everything underneath them. Articulations are implemented in so many different ways within VSTi's, it would be impractical (probably impossible) to implement what you're asking for and have it work in all scenarios. In your example above, the easiest way would be to cut the duration of the articulation short of the last note.

No-one is forcing you into subscription. There are very few differences between the premium and free tiers of Sonar at the moment. All you need to do is sign in to activate (assuming you're running the latest Sonar) and you'll be able to save.

There's really no reason to uninstall unless you're desperate for HDD space. Most of the installation is common to both Sonar/CbB, so you'd not be freeing up much. Also, when CbB does fail to activate, it WILL still play back if you have a problem project - only save/export is disabled.

The minimum specs are determined from what a sensible PC set-up would be for the average user (based on what is on the market now), assuming zero tuning of their BIOS or Windows installation. One of the most common things we hear from noobs is that they're getting clicks & pops, when they've loaded up their project with 100+ tracks containing an overkill of plugins that they saw on their favourite you-tube channels and a bunch of CPU intensive VSTi's. Having a more generous minimum spec helps to mitigate issues from these users. Of course Sonar will run on far slower hardware, and as @Starship Krupa says, my main DAW is an old i7 3770. My workflow is pretty old school though. I only started using VST's around 10 years ago - prior to that, all my instruments and effects were hardware. My 2 x DS2416 cards may have given me hardware EQ & Compression on 48 tracks, but it only gave me 4 effects processors. As such, I learned to use them sparingly, which has continued with how I use VST's nowadays.

Presets for individual ProChannel modules wasn't implemented until after CbB was released (in the April 2020 release IIRC). In SONAR Platinum, you only have complete ProChannel strip presets.

@aleo- Can you send your .cwp file to @Jonathan Sasor - we'll take a look.

FWIW, PC-2A is included in CbB / Sonar, which is exactly the same as CA-2A except: It's a Pro-Channel only module There's no side chaining There's no Mac version

That WONT work. SONAR Platinum didn't install CA-2A - it was always a separate installer. If CA2A isn't appearing in the Cakewalk Command Center, then it's not available for you.

You should be able to activate it via the Cakewalk Command Center - you can download the latest version here: https://legacy.cakewalk.com/Command-Center - make sure you have this one, as older versions won't connect to the new servers.

The Articulation Map editor always shows the MIDI note number alongside the C0, C-1 etc because there's no standard for middle C. The MIDI note number is for middle C is always 60 however, so if you can, refer to the MIDI note numbers instead. Changing the base octave for pitches will not affect the actual notes stored in the articulation maps - just whether it shows "C3 [60]", or "C2 [60]" etc, so you can change that setting as you see fit.

The MackieControl.dll is common to both Sonar and CbB, and there have been very few changes to MackieControl.dll - certainly nothing that would explain what you're experiencing. Can you provide screen shots of your: Preferences->MIDI->Playback and Recording page Preferences->MIDI->Control Surfaces page Mackie Control dialog page (from the Utilities menu)

Other drag/drop plugin browser enhancements: Drag/Drop an effect to the sends cluster, and it'll create a bus with that effect on it and a create a send to that bus. If you hold CTRL while dropping, it'll quick group for all selected tracks. Handy for creating sends from multiple tracks to a new reverb bus. If ALT is down, it'll do the same but using a send to an Aux track instead.

You may find that Sonar X1 requires older VC++ redistributables, as the "rollup" redists only cover VS2015 - VS2022. Sonar X1 was released in 2011. You can find the older ones here: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 Be aware though, that redists prior to 2015 are no longer officially supported in Windows 11. In saying that, Sonar X2 is working fine here on my Windows 11 machine (upgraded from Windows 10). I've got the redists for VS2005, VS2008, VS2010, VS2012, VS2013 and the VS2015-2022 installed. If you're going to install them, start at VS2005 and make your way forward, finally re-installing the latest VS2015-2022 redists.

Please provide a screen shot of your Keyboard Shortcut preferences page.