msmcleod

It's likely that you've got a zip file that Windows can't "explore" in either the project directory, or the place you launched Cakewalk from (e.g. desktop). The Media Browser is essentially a re-wrapped Windows Explorer component, and it's Windows Explorer that is trying to list the all the files, treating the zip file as if it was a folder. Check out this thread -

The Media Browser within Cakewalk is essentially an instance of Windows explorer, and it's the windows shell within it that is trying to treat the zip file as a folder and evaluate the file list within it. @Noel Borthwick - explains what is happening here:

I've got an old mixer who's mic transformers are so old, on one channel you can shout at it, and it'll pick it up. Apparently this is a common issue with old transformers - after a while they become microphonic. Pickup design isn't that different to transformers, so I guess there's no reason why this can't happen with them too... except given this guitar was brand new, the pickups are probably defective.

AFAIK a change in PSU can improve speed if the processor is capable of overclocking and the PSU is underpowered for the system. Some systems will recognise the lack of power and slow down the CPU accordingly. On the other hand, an underpowered PSU can cause no end of stability issues. I've had issues in the past with an underpowered PSU causing BSOD's at random points... and I found a resolution to a long-standing freeze issue I was seeing on one machine by slightly raising the CPU voltage in the BIOS. It used to freeze at least once a day - it's now gone 3 weeks without issue.

One of the main reasons for the sustain pedal not working, is when you've got your Keyboard Shortcuts set up like this, which intercepts the sustain pedal so it can be used like a shift key: The solution is to: Make sure that the MIDI Enabled checkbox is unchecked The controller is set to something that is unlikely to be used, just in case you accidentally enable it again, e.g:

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.

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.

It's likely instrument dependent. Fast export will attempt to export at as fast a speed as possible, but not all plugins support this.