When I try to use the export (any format) I get a popup from RAFX saying "Could not create destination project folder", lists the path then says "Check permissions".
I'm using the "Use \Project Folder\VST Files" option as the export folder path.Â
Just upgraded to 6.9.1 from 6.8 I think today so maybe I missed something new?
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.
I am able to export anywhere on the C: drive. Either the default RAFX folder, or folders I create on C:Â However, I get those error permission on every other drive. I've used both internal and external drives and checked that the permissions are exactly the same as the C: drive folders I create.Â Are you able to verify you can export to another drive letter?
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 v188.8.131.52). 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.Â
OK, FYI - I found the issue; its not with the CreateDirectory( ) function, but with the path validation function that uses MFC's CFileFind, which has a problem with mapped drives and requires special handling, namely UNC paths. I'll add this to the next version. RackAFX will let you know when its ready.Â
Thanks for the report!
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Moderators: W Pirkle: 689