Cache doesn't clean up when closing Cubase project (ARA)

SpectraLayers
1

With SL 13.0.20 when I close a Cubase project where I have used SpectraLayers as an ARA extension the SL processed wav-files are still left in the SL cache folder, even if I have made extensions permanent in Cubase or removed extensions from selected events.

If I remove the remnants from the cache folder the actual events in Cubase will be empty the next time I open the song (.cpr file).

This seem to be an intermittent quirk and sometimes the cache files are gone from the cache folder without my interacting and then they will be gone from the Cubase project forever.

This is quite serious since many hours of thorough editing with SpectraLayers in Cubase disappears without notice.

Is this a known bug @Robin_Lobel ?

(Cubase 15.0.30, MacOS 15.7.4)

2

Hi Marshall,

The Cache folder is the folder shown in Preferences > System > Cache Path.
But I suppose given you’re issue that you’re more referring to the External Edits folder shown in Preferences > System > External Edits Path.

image
image1484Ă—488 75.7 KB

The Cache folder has no link at all with Cubase, it’s just internal data that is being deleted at the end of each session.

The External Edits Path is only a transition folder from SpectraLayers to Cubase, and it’s entirely up to Cubase and the user to manage its content when something is imported back into Cubase. The standard practice is to always check “Copy file to project folder” when importing anything back into Cubase, otherwise you’re indeed at serious risk of losing those files at some point.

image
image1386Ă—836 91 KB

3

Thanks for answering!

This is not about imported audio files not being copied to the project/audio folder; I always do that. It’s about Parts/Events being edited with SpectraLayers in Cubase, where the edits later are missing when opening a saved project in Cubase.

It turned out my External Edits Path in SpectraLayers was pointing towards the SL Cache folder, so both cache fragments and edits ended up in that folder. I’ve now created an Edits folder to which the path is directing, hoping this will solve the problem.

I have a vague memory of having changed the original path earlier this summer since I didn’t like it pointing towards an iCloud folder (“Documents”). Oh well…:face_with_spiral_eyes:

Mystery solved now, I hope, thanks again!