msmcleod

I find shifting the whole arrangement over so it starts on bar 2 cures this for me in most cases.

Yamaha do have an office in Norway ( https://no.yamaha.com/index.html ) so you should be ok.

Given that it's the shared plugins that are giving the problem, it may be that you need an earlier VS redistributable. Some of the shared components haven't been recompiled for years - long before VS2015 was around. Try installing VS2013 redist: https://www.microsoft.com/en-gb/download/details.aspx?id=40784 You could even try the VS2012 redist: https://www.microsoft.com/en-gb/download/details.aspx?id=30679 I doubt if you'll need it, but here's the VS2010 redist https://www.microsoft.com/en-gb/download/details.aspx?id=5555

Exit code 3 means could not LoadLibrary. This normally means that the DLL file is corrupt. It could be a security thing, but running as Admin should negate this. Have you got any virus scanners running? Try disabling them. Failing that, try deleting the download files and re-installing (you can find the Download Path by pressing CCC's settings button on the top right, and clicking on the paths tab).

Another one available 2nd hand: https://www.bhphotovideo.com/c/product/801547765-USE/cakewalk_10cwsr20010c_sonar_2_2_software.html

You should check the manual for your motherboard. You should be able to download it somewhere. It normally recommends what configurations work the best, and what slots to use if you're using 2 sticks vs 4.

Some plugins are just heavy on CPU, so you can try increasing your ASIO buffer size. However, some other's just don't play well with Cakewalk. I usually use the "Load with JBridge wrapper" option on the plugin (you'll need JBridge though). If it still clicks & pops with this option, then it's genuinely just CPU hungry and you'll need to up your ASIO buffer size. If it is a CPU thing, up the buffer size then freeze the track - you can then put your ASIO buffer back to normal.

X2 is VERY different from Sonar 2.2, Sonar 2.2 came on CD not DVD, and it needs a Serial Number as well as a CD Key to install.

Sorry, I made the jump straight to Sonar 3 from Sonar 1XL. There's one on eBay at the moment - it's the Japanese version though. Maybe someone at Cakewalk can confirm whether it has the option to install in English or not. https://www.ebay.com/itm/Cakewalk-SONAR-2-0-Japanese-DAW-Sequencer-Cakewalk-2-0-DAW/273824412366?hash=item3fc134f2ce:g:h3MAAOSw19dcjaSO

FWIW I use SSD's for everything nowadays, using my old HDD's for storing backup images. The only issue I had was with a SanDisk Plus, which died during the warranty period. SanDisk replaced it with a SanDisk Ultra II (free of charge) which is running great. Most of my other SSD's are Crucial MX300's / MX500's. Personally, I can't see you having any issues using them for casual tracking. For really heavy tracking, an SSD is still fine, but you'd maybe want to look into getting a SLC (Single Level Cell) based SSD which will cope with far more writes than the other types. For most uses the standard MLC (Multi Level Cell) technology is fine. I personally wouldn't use the TLC (Triple Level Cell) SSD's, but I guess they would be fine for your OS (assuming your swap file / hibernation file is on another disk), or a disk full of samples.

Yamaha are usually excellent for spares, regardless of how old your equipment is. It might be worth ringing them and getting a quote first, so you can compare to eBay prices.

Following on from my previous post, it's worth mentioning that I tried various combinations of using VST2 & VST3 versions of SoundSpot Kickbox (both with "Replace if Possible on Project Load" on and off) to try to reproduce this issue. I figured if anything would do it, something with a different list of parameters would. All the tests were done in their own projects, and I restarted Cakewalk before each save / load. However, all the VST settings were restored properly. Also, with the VST3 "Replace if Possible on Project Load" setting checked, the VST2 version is still present - presumably because Cakewalk knows that it can't apply the VST2 settings to a VST3 plugin due to the parameter differences. So at least for me, everything is working and no matter what I do I can't reproduce this issue.

Have you got your projects directory / picture directory & global audio directory excluded from the your virus scans? If it's not excluded, I've seen it crash Cakewalk, but it's conceivable that it could just be interfering with the recording process.

You could try grouping your tracks together and switching off the metering group by group, leaving on only the meters you're currently concerned with. Not saying this will fix it, but it's worth a try.

Yes, there's a big difference between them when stopping and restarting recording. This accounts for half of my 144 combinations - i.e. whether you're loop recording, or stopping/starting. The combinations I'm looking at for Comping / Sound on Sound / Overwrite are: Loop Record / Record+Stop+Record+Stop Auto Punch On / Off (Auto Punch On only) Auto Punch Mute Previous Takes On/Off Store Takes in a Single Track / Store Takes in Separate Tracks Create New Lanes of Overlap On/Off New Takes on Top On/Off There's 48 combinations of the list above for each of the 3 recording modes. So 144 in total. I'm now questioning how useful documenting such a list would be... it's a bit overwhelming.

This further supports the VST2/VST3 theory... here's SoundSpot KickBox. Notice the extra bypass parameter between "ratio" and "bypass warmth" (parameter 1): This is not the only example - loads of the Waves plugins have this difference between VST2/VST3, except in the Waves case it's usually the first parameter that is the extra "bypass" for VST3.

Maybe the instruments and/or samples don't match the sample rate you have in Cakewalk?

It could also be that a problem restoring one plugin has a knock on effect (no pun intended!), meaning other plugins lose their settings.

Build 27 was a hot-fix release, released on Jan 22nd (maybe the 23rd) - less than a week after build 24. Put it this way, the file date says the 22nd, but I installed it on the 23rd. It was released specifically to fix the MixRecall issue. I don't know exactly what all of the MixRecall issues were in build 24, but maybe snapshots created using that version are corrupt somehow and can't be used. That would certainly explain why a hot-fix version was released so quickly. Have you tried creating a new snapshot in the latest version and trying to recall that?

The confusion for me, is that some of the options seem to be functionally equivalent, or at least only very subtly different, depending on what recording mode/options you use. So I'm never totally confident that I've picked the right one. Take Sound on Sound vs Overwrite for instance. If I'm set to loop, and I've Auto Punch to the same selection with "Mute Previous Takes" on, and Store as separate lanes: Sound on Sound - Records each take in a different lane, previous takes cannot be heard during recording, but all lanes are active and will play together once recording stops. Overwrite - Records each take in a different lane, previous takes cannot be heard during recording, only the last lane is active and only this will play once recording stops. However, in both cases using the smart comp tool (i.e. clicking the lower half of a clip), will result in only that clip being the active one. So the end result in this case is exactly the same. But if I didn't use the smart comp tool, in either case, right clicking on Clip Mute/Unmute can obtain the same results in both cases, so: Takes recorded in Overwrite - Clip Mute/Unmute can be used to make all lanes playable, just as if they were recorded in Sound on Sound mode. Takes recorded in SoS - Clip Mute/Unmute can be used to make all but the last lane silent, just as if they were recorded in overwrite mode. So the differences are subtle, but knowing what each one does can speed up your workflow depending on what state you want your clip lanes to be in after recording. This is good in a way, because in most cases you're only a few clicks away from getting exactly the same result regardless of what recording mode you selected. I've identified 48 different option combinations for each recording mode (that's ignoring Multi-track grouping & Allowing Arm Changes), so that's 144 different combinations in total.... a lot to go through!

Most likely Windows has made your Roland device it's default device, and it won't share it with Cakewalk. I normally have Windows set to use my on-board realtek sound device, so it leaves my audio interface alone.

I normally assign "A" to aim assist within Keyboard Shortcuts. Just type aim into the search area, and it'll come up. You can then bind it to the A key. Pressing A will then toggle it on/off.

I get this notification on some of my projects when using Jamstix. Quite often, I'll stick the audioM8 plugin on its own bus, so I can control the level of audio sent to it from each track. As audioM8 doesn't have an audio output, the bus is always silent, hence the notification. Maybe I could get around it by using Aux tracks, but the bus works fine for me.

I've seen a number of track related issues when using Lenses. I suspect things get confused if you're adding/deleting tracks (or moving to & from folders) and you've got the "Track View Control Order" setting checked within the Lens Manager. Does it still cause issues if this option is unchecked?

I've had similar thoughts about the AIR package - it's a fantastic set of instruments, even if it's a bit dated now - and it was good enough for ProTools for a long time. The effects package is pretty good too.