Auto Save !

[XORadmin]

If possible. Please implement this ASAP. Especially while the Nerdseq crashes almost every time you use it. Asking us to save every single time we enter new data makes work flow very cumbersome. Also how am I supposed to send you crash data if the file wasn't saved before it crashed? 

Most of the crashes come from using/loading samples. It's crashed so many times today while performing many different tasks that I lost count and also 'recreating' the crash seems nearly improbable when all you did was load reload a sample. It seems like it's crashing because the memory is full while I am replacing samples. Who knows... I don't have a saved file for it. 

If this function isn't possible, please start to raise the cash to pay for all the hospital treatment for the incoming brain aneurysms Nerdseq is causing us all. 



*EDIT*

Function idea: Auto save ON/OFF in set up along with time 1, 5, 10, 15, 30 minutes, etc. With a temporary message displayed in the bottom info bar where track names are, perhaps 5 seconds before it saves with the option to cancel the save using shift or something. Cancelling would seem backwards intuitive but of course autosave can also be annoying when you are editing.

Hey, damn! I'm sorry to hear that. 

Of course autosave would be possible. But i didn't implement it yet since saving takes a bit longer than loading and it can also disturb a lot since you can't do anything else then. Also you cant save while playing, so the player would stop. A good strategy would be needed and it's not as easy as it seems (imagine it can be started from extern at all times..).

More important, what is the crash problem? I never have any crashes and i am using it daily testing stuff, trying stuff and so on.

The problem with samples is definitely an issue and as you know a problem of fragmentation. That is in the manual and discussed many times.
You got to be carefull with loading and replacing many samples, especially when the memory is full. And even if the sample seems to be smaller than the free memory it can be an issue, because the free memory can be fragmented in multiple smaller parts. Thats where problems can occour.
There is not much samplememory and it is quite a hard task to proper deal 'seemless' with loading/replacing samples.
I guess that is your problem? Or are they any other cases where it crashes?

The NerdSEQ is very stable, unless you use a antique version. And if they are any issues beside the sample fragmentation then i would be happy to fix them directly...if they are reproducable for me.

So, yes, please i need to know what you did before it crashed, how does it crash (reset ot errorcode), and can it be reproduced with a saved project file.