msmcleod

1. Make sure your Cakewalk projects directories, plugin directories and sample library directories are excluded from any anti-virus, anti-malware and cloud-sync services - this includes Windows Defender and OneDrive. If these programs try to access files that Cakewalk (or a plugin) expects exclusive access to, it can cause a crash. 2. Make sure Windows is up to date, and is running the latest Visual C++ Redistributables - some plugin installers force install an older version. Note that it's normal to have different VC++ Redists installed (e.g. the 2015 redists is different to the 2019 redists, so can live side-by-side), but you should be running the latest versions of the ones that are installed. 3. Open up PowerShell ( Windows Key + X, then press A ), and run sfc /scannow to check for/repair any Windows system integrity issues. And as a general note regarding Anti Virus software.... never have more than one of these products installed at the same time. Pick one, then use it. Multiple anti-virus products will literally fight each other, slowing down your PC, and will introduce stability problems across the board.

Exactly this. The undo mechanism only works because it can reverse a command based on a known global state. Most commands affect more than just one track as even a single track operation affects the underlying routing graph - which has to be global. Undo's have to be performed in order, so that when you call the next undo the project is in exactly the same state as it was when you finished executing that command. It's like trying to ask for the primer to be changed without removing the top coat. If you want different undo's for mixing decisions, take a look at Mix Recall.

What amazes me is these features have been around since at least Sonar 1 (that's Sonar 1 from back in 2001... not Sonar X1 ), and hardly anyone knows about them. IIRC Loop Construction View came out as part of Sonar 1, but I think pitch markers were supported prior to that in Cakewalk Pro Audio... you just needed something else to create the ACID-ized loops ("Groove Clips"). LCV lets you create your own from within Sonar itself.

The Pitch you set in LCV is the pitch of the original sample - so if you recorded yourself playing an D string on a guitar, you'd put "D" here. Follow project pitch is to do with Pitch Markers and Meter/Key entries. Meter/Key entries set the project key signature - e.g. D Major, B minor etc. Once you've created your groove clip using LCV, Pitch Markers can be used to force the clip to change pitch relative to the project key. So if you're playing in C Major, and the pitch markers are set to C at measure 1, F at measure 3, and G at measure 5 the loop will be pitch-shifted to play at those pitches. However, it's important it knows the original pitch of the loop in the LCV, so it knows how much to pitch-shift it by. If you don't have any pitch markers, then the loop will play back at the project key (which will be C major if you're using the default meter/key "4/4 C"). Groove Clips / Pitch Markers can give you a kind of "poor man's chord track", in that it can change the audio from one pitch to another using the pitch markers to specify the chord. It can only shift pitch tho - not change major to minor.

@michaelrb - you need to make sure you're running the very latest version of Cakewalk by BandLab. The back-end authorization servers were changed to support the new Sonar. Older versions of Cakewalk will not connect to then new server. Once you're sure you're on the latest Cakewalk, sign out from the help menu, then sign back in again from the help menu. It should automatically re-authorise.

Ensure you download and install the latest version of Cakewalk Control Center. Older versions no longer work.

Freeze is unlikely to be aware of complex routing, so I'd recommend using Bounce to Track(s) - it can be found under the Track View "Tracks" menu. Once you've bounced, you can archive the original tracks to free up resources.

I've got both the MidiSport 2x2 and the MidiSport 8x8. I found the 8x8 is a bit flakey in Windows 10 and liable to blue screens... rock solid in Windows 7 though. Thankfully the only time I need to use it is when editing sounds on my hardware rack gear, so I'm happy to switch to Windows 7 for that. I now use the MidiTech midiface 8x8 / midiface 4x4 - they work fine in both Windows 10 & Windows 11. I did try out some cheaper interfaces, but they suffered from missing notes / sysex issues.

If you mean this bug: "Moving Comp Split Point in Multi-Tempo Project Alters Next Segment's Start Time.".... then yes, it is fixed.

Just a FYI... it's been a while since I've checked this, but when I first got the Virtual Guitarist series I found I was getting loads of clicks & pops, regardless of what ASIO buffer size I set. It seemed to affect all the UJAM plugins - in my case both Virtual Guitarist & Virtual Drummer series of plugins. My workaround was to check the "Load with jBridge Wrapper" setting in the plugin properties (obviously you need jBridge installed). This allowed me to use it at lower buffer settings. I wouldn't use this setting unless necessary though - if they work fine without jBridge, it's best to use them without it.

Some videos on the Loop Construction View - some cover general groove clip stuff, but soon get into the Loop Construction View. SWA Complete Sonar X2 (35/50) SONAR X2: Get Started - Loop Construction View Groove Clips and Looping-Cakewalk by BandLab Tutorial

I think he's mixing up native ASIO drivers with ASIO4ALL.

IIRC, the tempo map is only loaded / saved when you do an Open or Save / Save As. Import / Export doesn't include tempo information.

NRPN is a 14 bit controller, where CC# 98/99 are the MSB/LSB of a 14 bit pair. CbB is showing both messages as one entry (i.e. CC98 = 0 / CC99 = 111) , because they're meant to be interpreted as a single 14 bit message.

The key information would be in the Range panel - I suspect the ranges are different for some reason (probably automation or tempo envelopes after the project end).

I've got a couple of these, and also a couple of ADA8200's. The ADA8000 is fine for line levels, and the outputs are pristine, but I found the mic-pre's a bit harsh/brittle sounding. The ADA8200's are much better in this respect with it's "Midas designed" mic pres.

This is the one I use now. The great thing is I can use my 18i20 for one of the inputs/outputs, which has my bread & butter gear (keyboard rack / guitar fx processor / vocal processor) permanently connected. It also lets me easily swap back to the 18i20 if I'm taking the RME elsewhere. The other I/O's are connected to three Fostex VC-8's - two of them fed from the direct outs of my A&H MixWizard WZ3 16:2, and one from my preamp "collection". The best thing about the RME Digiface is that you can upgrade the pre's / converters as and when you need. The VC8's aren't exactly the top of the range, but they suit my purpose for now until I feel the need to upgrade... and I can do so without changing my interface.

I can almost guarantee this is the cause. Cakewalk will automatically refresh activation if it's logged in and it detects you're close to needing an activation refresh.

Is your project empty? The most common reason for this is having "Stop at Project End" checked ( bottom of Track View "Options" menu).

No, it's not mandatory. Quite often programs like TONEX (NI Massive is another) have an internal library database of all their presets, libraries etc - in TONEX's case it's all of its amp models. When this is run from inside a DAW while the plugin is first being loaded, it can cause the DAW to think it's being unresponsive and something has gone wrong. Massive used to take literally minutes to update its patch library. Other things that can happen after updating is checking the your authentication is up to date. By running the plugin in standalone mode, it allows it to update its internal database in its own time, meaning that when the DAW loads it as a plugin, it responds instantly. Yes - just do a normal scan without a full reset. If the plugin parameters have changed for whatever reason, it will allow Cakewalk to pick this up.

Are you definitely running the very latest version of Cakewalk by BandLab? The back-end servers were changed earlier this year to support the new Sonar, and earlier versions of Cakewalk will be trying to connect to servers that don't exist any more. The latest version (as of this post) is 2024.02 build 98 (29.09.098).

From what I could see, it was TONEX that was crashing Cakewalk - not the other way around.

What I normally do with these: 1. Create a new project based on the Basic template 2. Navigate to your old project folder in the browser 3. Drag the project from the browser to a blank space in the track view 4. Delete the two tracks (Audio / Midi) that were created as part of the template. This ensures all imported audio tracks are created with a Pro Channel.

So Tonex 1.6 was installed, I updated to 1.7.1 and it crashed Sonar... so I did my usual with VSTi's that are also stand-alone: 1. Run Tonex standalone... let it sort itself out, then exit the app 2. Run Sonar 3. Run VST scan from Preferences 4. Drag Tonex into an FX bin - success! I recommend following these steps for all VSTi's that have a stand-alone version.

The buses are matched by name - are you sure the Master bus has exactly the same name as the one in your template?