Hi Derek

The message you are getting is coming from a routine that creates the project export folder, and for you that would be .../<Your Project>/VST Files/<Project Name>

It goes through the final path, verifying that each sub-directory exists, starting from the left C:\ and working to the right, all the way to the <Project Name> folder. If the subdirectory does not exist, it uses the Windows CreateDirectory( ) function. If that function fails at any point, you get that message. It is a direct result of that function failing. 

Usually, this is due to a permissions problem. Sometimes, even if you are logged in as admin, a directory may fail to create if it is in the Program Files (x86) or Program Files folder, for example. If your project name is not a valid directory name, it will also fail. In the past, some of my students had problems if the folder was on the Desktop as well. 

This is also why there is a field for the Plugin Name - it does not need to match the Project name. 

So, that's where the message comes from.

- Will

I just tried it, exporting with my VST folder set to X:\blah\project and it did indeed create the subfolder properly without problems (using v6.9.1.0). On top of that, the X drive is a Passport USB drive, mapped through Parallels in MacOS to Windows. 

However, connecting the same drive directly to the WinOS, bypassing parallels, results in the "fail to create" issue. I'll have to look into it, but I am kind of stumped. The CreateDirectory( ) function is as old as Win32 itself. 

I'll have to get back to you on that. 

- Will