msmcleod

IIRC the AIR installers stopped working properly after Windows 10 2004 came out. The fix is to re-install the latest version of all of the VS redists immediately after installing any of the AIR instruments (including XPand2!). Noel packaged up all of them into a handy installer, which is in the topic below. Just run this immediately after installing XPand2.

You should be able to do all of this from the event list. A few important things: 1. Set the correct Bank Select method in the track, which should be "Normal" if you want to send both #cc 0 & cc #32: 2. If you're adding the CC/Patch events manually in the event list, make sure you leave the bank/patch blank within the track inspector: 3. Finally, incorrectly defined .ins files can interfere with the bank select methods. I found this with the bundled XG instrument definition, which refused to allow a bank select change back to cc#0 = 0, cc#32 = 0 if you'd already changed bank . IIRC, it was the Patch[*]=XG Bank 0 entry that caused this - removing it forced the correct bank select CC's to be sent.

One thing I know can definitely cause issues with the ProChannel, is if the folder that contains them is compressed. Make sure the following folders are uncompressed: C:\Program Files\Cakewalk\Shared Utilities C:\Program Files\Cakewalk\Shared Plugins Although that may explain some of what you're seeing, it doesn't explain Boost 11 / Sonitus Compressor not appearing... that would indicate that a VST scan wasn't done ( Boost11 ) and the Sonitus plugins weren't registered. A full reinstall of Cakewalk followed by a VST scan should fix this.

Those plugins come with SONAR Platinum, not Cakewalk by BandLab. If you need those plugins, install SONAR using the Cakewalk Command Center, then re-install Cakewalk by BandLab.

Drum Replacer is meant to be used as a RegionFx, not in the fx bin. It’s disabled as a standard plugin by default for that reason.

Is Cakewalk definitely crashing, or it this a dropout?

Are you using any workspaces in Cakewalk?

There's definitely nothing wrong with the project file itself, so there must be something else causing this issue. Can you capture a crash dump and send me the dump file? Instructions on how to do this can be found here:

I got the project - loaded fine for me.

CbB 2022.02 automatically adds the new location ( %localappdata%\programs\common\vst3) into your scan paths. A re-scan should pick up the new location of MCP automatically.

Strange... it's appearing in the menu on my system:

@dogufo - as CbB uses the audio device for timing by default, you could try adding a blank audio track, or a software synth and see if that improves your MIDI timing.

If you're working in the PRV, this can generate a lot of changes as IIRC a lot of operations are done on an individual note by note basis ( as opposed to the clips view, where operations are done on a clip by clip basis ). The best thing to do when you're still at the stage of editing events/clips is to set your auto-save to be time based.

I honestly can't say to be honest, but I doubt it'll make much difference if you're getting issues with a blank project just recording MIDI. Are these pure MIDI tracks, or MIDI tracks with a soft synth?

@Esteban Villanova - Thanks for the report. The issue seems to be related to trying to copy a section with events in a project with no clips. We can reproduce the issue and are looking into a fix.

Have you ruled out USB sleep settings? 20 mins sounds like the sort of time sleep might kick in... Check your power settings within Windows and ensure USB sleep is disabled.

I've tried various combinations (e.g. copying the tracks, copying just the clips from 4 different tracks, normal copy, copy special etc), and all are working fine for me.

@IgoRr - the dump file would seem to indicate some heap corruption, but I can't see how this error could occur. Can you PM me your project? I've tried to build up a similar project, but everything is working for me.

As far as I know, the Pro Channel modules and Sonitus effects haven't changed since SPLAT, unless I guess you're installing a really early version of SPLAT. They're all in a central location in any case, and given the fact that most people are happily running SPLAT alongside CbB, something else must be at play here. I appreciate it's not very helpful, but to avoid any possible issues, just make sure you install CbB after you install SPLAT. If you do install SPLAT after CbB, you can force a full install of CbB by rolling back more than one version - e.g. if you're on 2022.02, roll back to 2021.12 and then roll back again to 2021.11. When you next update, it'll download the full installer. You can find the rollback installers in the EA threads for each version, i.e. the 2021.12 rollback installer is in the 2022.02 EA thread; the 2021.11 rollback installer is in the 2021.12 EA thread etc.

Can you also post screen-shots of your Copy Special & Paste Special dialogs ( with the advanced options shown)? I need to know what all the other options were. [Edit] - the "New Track" field just sets the starting track of the paste, so it shouldn't matter that there are multiple tracks.

Is he definitely running the latest 2022.02 release? There was a known issue in 2012.12 that was causing crashes when pasting. If you have a minidump, please sent it to me.

We've not imposed any limit, but if you go too deep, you'll have to stretch your track's pane to the point where you can't see your clips any more... and CbB might start to slow down as it has to calculate the folder comp clip at each level.

FWIW, I'm running 21H2 on all of my Windows 10 machines without issue. All but one have Cakewalk running on them. The oldest machine is a Dell Vostro 1700 ( 2.2Ghz Intel Core Duo with 4GB RAM ) and even that is fine. IMO, unless you've got a specific technical reason for running 20H2, I'd recommend upgrading.

Normally this is indicative of an ASIO buffer size that is too high, but it could also be down to a MIDI feedback loop within your virtual instruments. Make sure that the MIDI output of any VSTi's is disabled if you're not using it:

Not sure about Win 7 home x64, but FWIW CbB 2022.02 is running fine on my Win 7 Pro x64 boot. I can't imagine it would be any different for Win 7 home. The only thing that might be an issue is the available RAM. Microsoft limited the amount of available RAM in the Home editions. Home Premium is limited to 16GB, which is fine, but the Home Basic edition was limited to 8GB which might be a bit too low for some projects.