billwright2

Something to do with permissions on the 😄 drive it appears. Since there did not appear to be any way to re-install through bandlab assistant, I then tried to move the cakewalk core folder to a different drive letter. In it's place in the original folder I then created a symbolic link to it. Now everything works as expected. No raised level of access to run the app, and the double-clicking the CWP and MID files launches the application (once I remembered to change the MID association back from Cubase Elements ) Thanks for all the thoughts and things to look at.

Thanks - this only started with Bandlabs version of cakewalk - never had the issue with Sonar. I have done a cold reboot on my computer then tried to double-click a CWP file. - same thing happens - cakewalk fails to load. I then installed the trial version of Cubase elements and that works fine with it's extensions and I also changed the .mid extension to work with Cubase. The native CPR files and the MID files all open with it properly on a double-click. So, this has to be something in particular with the cakewalk installation.

OK - No zip or rar files anywhere in my project folders No instance of cakewalk running n task manager Still cannot double-click a CWP file and launch cakewalk. Also cannot double-click a midi files (associated with cakewalk) to launch. Only way to load file is to use cakewalk's file->open and browse to the file and open it. Also note that the desktop shortcut that the Bandlab installation creates will not launch the product unless you change the advanced properties of the shortcut to 'Run as administrator'. Does anyone think that uninstalling and reinstalling on a drive other than 'C':' (if it will let me) would do any good? Next step might wind up spending almost $600 and switch to Cubase

Never had this issue with Sonar - only with Bandlab Cakewalk,. Anyone have any ideas?

It will ONLY run in administrator mode on my machine. If you try to run the application in the Cakewalk Core folder in 'normal' user mode, it never starts and has no footprint in the task manager.

I am having a rather annoying issue. If I double-click a CWP file bandlab cakewalk will not launch. I suspect that this is due to cakewalk having to be run in administrator mode on my WIndows 10 Home machine. Is there a way around this. And YES - my CWP files are associated with the Cakewalk application,.

I also tried it on Cubase which is supported and had the same issue when I tried creating a piece with opus and only 6 tracks. Crashed - Everything is on SSD drives and I have AMD FX 8 core with 32 Gigs of ram so there should not be an issue

I just licensed it two nights ago and had the same experience and everything is installed on and SSD drive. Tried to run orchestrator and it crashed Cakewalk. I then tried to create a simple template for just Violins, Violas, Celli and Base - When I added the basses cakewalk crashed. I hope I haven't made $200 dollar subscription mistake.

There are no audio tracks - they are all midi tracks being output through VST Instuments. Do I need to make the vst tracks have an input?

Randomly and often Cakewalk qill just 'han'g when trying to export audio. Sometimes it works, more often than not I have to kill it in Task Manage r and try again (sometimes multiple times). This also will hang when I try to change the track output from the Inspector view. If I change it form the tracks->selecttrack output it does not hang. The export thing is driving me crazy

I would but the drive is not only getting flakey is becoming too small for my new library and vst needs. There are other things on it that must remain in place n this drive letter so I will need the room to fix the bad blocks on the drive for this other stuff. My only option is to move the VST's and their samples to another new larger drive volume

I have all my VST's for Cakewalk loaded on a single SSD drive. This drive is behaving erratically and I need to move all of my VST's to a different drive. Is there a bulk way to update all my projects so I do not have to reset each product to point to the new VST location?