So I originally had an issue of my audio dropping out randomly whenever my project was playing. I did all sorts of things to try to fix the issue (increasing the buffer sizes and limiting CPU usage) but I hadn't fixed the problem yet. I read from an official documentation file on here that I should delete the contents of the Picture Cache folder in the Cakewalk Projects folder. I did this while a project file was open, so I didn't delete some of these files as they were open. I then tried to open another project, and there was a fatal crash dump error or something like that. In order to fix it, I moved the files from the Recycle Bin again back into the Picture Cache folder. I kept trying to open the projects after this, and Cakewalk would start up, but in the top left of the screen it would say "Not Responding" and then it would crash again. Someone please help. Thank you.
UPDATE: I fixed the issue! It turns out that a VST Plugin that I downloaded, Youlean Loudness Meter, was causing the crash for some strange reason. I deleted the plugin and opened the files, and my projects are working again :). This was the thread that helped me. And this was the comment that helped.
On 12/12/2019 at 6:18 AM, Electric Raven said:
Sorry I'm late for the party, but what I'm going to write now may be of help to someone else with similar problems.
I am sometimes getting a fatal error for VCRuntime140.dll
Here are some ways that you could try fixing it (the fixes might sound stupid but hear me out):
1. Up the samples on the driver you are using
- I am using ASIO4ALLv2, and I would go to "Edit/Preferences/Driver Settings/ASIO Panel..."
- I am usually using 256 samples, but when I get a crash i up the buffer to 1024 samples or higher
2. Change drivers
- For example, if you are using ASIO4ALLv2, try with FL Studio ASIO (also with increased buffer size)
- "Edit/Preferences/Devices", tick off the selected input/output and tick the deselected ones
3. Open a clean project
- If maybe a certain plugin is bothering you, try opening it (the plugin bothering you) beforehand in a clean project
4. Temporarily remove the plugin that is causing conflict
- If a certain plugin doesn't even want to load, try moving its DLL to somewhere else so that CW doesn't even load it
- My example for this is VSCO2. Replaced it with Sketching orches, no problems since then
5. Opening CW as administrator
- This is usually a simple fix for VSTs that give off lots of errors
6. Differently opening projects
- I once couldn't open a project via the "CW Start Screen" pop up, so let me show you a few more ways:
1. By pressing "File", you get a drop-down list of recent projects
2. Going to "File/Open" and searching for the project manually
3. Finding the project manually on the computer (never did this myself)
7. Do NOT go to try and download a DLL fix or anything like that - THOSE ARE SCAMS
If nothing of this mentioned above helps, I am truly sorry for your loss.