Steps to reproduce:
- Load any audio file in Reaper (I used 7.76)
- Add SpectraLayers 13 as an FX on that track (VST3 as ARA)
- Select Unmix Song, everything selected (any quality)
- Click Apply
After the ~20s “load time”, “Estimating” appears briefly, but when processing should begin, Reaper crashes, just disappearing from the screen … no crash log, nothing.
Insufficient GPU memory to load all of the models used when unmixing. You have to unmix 1 or 2 models at a time, but it seems SL13 has not delivered a workflow which allows sequential loading/unloading/loading etc
Nope, doesn’t happen in Nuendo on the same machine.
I suggest running multiple examples of Unmix Song (using a typical 3 or 4 minute song) with all models ticked, directly within SL and indirectly via ARA in Nuendo and Reaper.
Maybe 10 tests in each of the 3 scenarios.
Then run the same test with Use Shared Memory selected (or unselected if you usually have it selected)
Thanks for the suggested workarounds, but with respect, I’m not a beta tester. I was reporting an easily reproducible serious issue with SpectraLayers 13 that crashes the host application instantly.
@Robin_Lobel is this the same fix scheduled in patch 1 for the instant crash in Pro Tools?
OK - my suggestion was more about whether the crash is inconsistent i.e. is it always stable in Nuendo or standalone under identical circumstances? Perhaps that’s implicit in your original post.
I stopped using SL12 for Unmix Song because it was inconsistent and too unreliable.
I no longer use SL.
So far SL13 is always stable for me when used standalone or via ARA in Nuendo 15, but there are file-handling problems with both the Pool functions in N15 (link), and the way SL13 places files into the Pool that are not in the Nuendo project folder, but in the SL Edits folder instead.
Hi @MrSoundman I could indeed repro the crash with 13.0.0, but the upcoming 13.0.10 seems to run fine in Reaper (tested with Reaper 7.76 on Windows 11, with and without GPU acceleration).
As for the file handling in Nuendo, it’s not an issue but by design (and by ARA tech limitations, it’s been like that since SpectraLayers 6): SL has no way to know where the ARA host store its project. That’s why it’s storing the files you drag and drop into the DAW into a SL Edits folder.
It’s the responsibility of the user to check “Copy file to project folder” when a layer is dropped into the DAW, so that Cubase or Nuendo can do a local copy into the project folder:
Excellent, thank you for this!
Agreed, this is a separate issue. I “bounce selection” and then keep track of the file locations manually, but it’s error-prone.
I can confirm this crash is no longer an issue in 13.0.10 – thanks Robin! Seems very stable in Reaper now.