Low memory experiments by dynamic save/reopen in unpacked experiments?
Wed, 05/02/2018 - 12:50 pm
I imagine that even if that's possible, it's not going to be implemented any time soon, so I wonder whether there is something I might be able to write myself. In that regard, I wonder whether there is a way to get a "wave hook"-like function called whenever a wave is about to be accessed or modified? (I could see that hook slowing down processing quite a bit, but nevertheless...) if so, I could 1) check the wave name against the list of waves I want to "load only when in use" 2) reload matches if necessary, perhaps killing and replacing a placeholder before the access/modify begins.
If that type of more general background-running solution isn't possible, I will of course revert to more manually saving waves to hard drive, killing them, and reloading them before I need them.