Old Project Opening Issue

[Chima]

Good day,
I have had an ongoing issue with my version 13.1.2 of Waverform Free. If I open any new project, it refuses to open as it will constantly be in a 'Not Responding' state for what what seems like eternity. I made this report to their technical team some months ago. They requested i send them the crash logs. But the thing is, there were no crash logs at all so, i wasn't able to complete the request. I don't know if it's just me or if there are others facing similar issues. If so, does anyone have an idea of resolving it? it'll be greatly appreciated. Thanks.

Note: i used it with Waveform 12 for a long time before this issue arose and i experienced the same issue with Waveform12 as well.

[Maarid]

Hello, there are a lot of initial data with a very small amount of input data. The first thing to try is, is it possible to create a new empty project? For example, I did not understand from your statement that you are discovering something new. Are old projects opening previously created ones or are they hanging too?
If you can't create a new project, it means you have problems with read\access rights on your disk.
If you have difficulties with certain old projects, then you need to try renaming the folders for the "vst3" "vstplugin" in order to eliminate the possibility of a failure or hanging of a part of the script.
And most importantly, the "edit" file is a regular text file and you can always try to open it with any text editor to make sure it works (if you have a physically damaged disk and the program has to wait for the disk to respond to the request)

[Peter Widdicombe]

Which template are you using (if any?), and are you opening the content for that edit which may not be present? (Default edit and don't load the content should take minimal resources).

Destination disk - write enabled and not full?

Actually, not clear on the case. Are you creating a new project, or trying to load an old project? If it's an existing one it shouldn't prompt for that dialog; but all the resources of that old project may not be available? Or you have changed permissions (even inadvertently) at the OS level?

[talby]

Try deactivating Plugin Sandboxing in the Settings. If this solves the situation, then search for the plugin which crashes the Sandboxing feature and remove it from the Template which becomes loaded upon creating the new project.
Good Luck!